> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/platform/overview/communication-insights/order-status-page-report.md).
# Order Status Page Report
The Order Status Page report provides an overview of the traffic on your Order Status page.
## Use Case
Using this report, you can understand how often your customers use the space.vars.Product\_OrderStatus in your online shop and view the satisfaction rate of the communications sent during shipping and carrier performance.
## space.vars.Report\_CIOSPage Report Features
This report is based on the creation date of the tracking for the parcel. It contains data for the last two years.
The top-level row shows the core metrics of this report and the date the report was last refreshed above it. This gives you an overview of your space.vars.Product\_OrderStatus traffic for your shops and the performance of your communications and carriers for the current period. It can be compared against a fixed previous period, which is based on the current period selected (for example: if the current period selected is 30 days, then the previous period used will be the previous 30 days from the current period).
More detailed charts are included in the space.vars.Report\_CIOSPage report to help you understand usage of your space.vars.Product\_OrderStatus.
{% hint style="info" icon="book" %}
**Check out the parcelLab guides**
For further information on using the report and metrics, see our [user guide documentation](https://docs.parcellab.com/guides/communication/communication-insights/order-status-page-report).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.parcellab.com/docs/platform/overview/communication-insights/order-status-page-report.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
