> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/inventory-features/reports/order-status-report.md). # Order Status Report ### 🔎 Running the Report When generating the report, users can filter by: * **Date Range** – the period for which you want to view orders * **Warehouse** – filter for a specific warehouse * **Order Number** – optional; filter by a specific order if required * **Status** – choose the stage of the order to report on The report organizes orders based on their **status**, including: * **Orders received, not dispatched** * **Orders checked, not dispatched** * **Orders received, not checked** * **Orders received and dispatched** *** ### 📋 Report Columns Explained #### 📅 **Date Received** * The date the order was recorded in the system. *** #### 📦 **Date Dispatched** * The date the order was dispatched from the warehouse, if applicable. *** #### 🏗️ **Project Number** * The internal project or job number associated with the order. *** #### 🔖 **SO (Sales Order)** * The system-generated sales order number. *** #### 🧑‍🤝‍🧑 **Customer** * The customer who placed the order. *** #### 📌 **Status** * The current status of the order (e.g., received, checked, dispatched). *** #### 💰 **Cost Value** * The total cost of the items on the order. *** #### 💵 **Selling Value** * The total selling price of the items on the order. *** #### 🏢 **Warehouse** * The warehouse responsible for fulfilling the order. *** #### 🔢 **Lines** * The number of distinct product lines on the order. *** #### 📦 **Units** * The total number of units across all lines in the order. *** #### 📦 **Boxes** * The total number of boxes or packages required for the order. *** #### 🚚 **Dispatch Method** * How the order is being dispatched (e.g., courier, in-house delivery). *** #### 📍 **Delivery** * The delivery address or location for the order. *** ### ✅ Why Use the Order Status Report? * **Order Tracking**: Monitor orders from receipt through to dispatch. * **Operational Planning**: Identify bottlenecks in checking or dispatching orders. * **Customer Service**: Provide accurate updates to customers about their orders. * **Financial Insight**: Understand the cost and selling value of outstanding and completed orders. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.ordereazi.com/inventory-features/reports/order-status-report.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.