> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/order-intake-cockpit/cockpit-views/orders.md).

# Orders

The Orders view shows sales orders created from Order Intake Cockpit processing, including order status and order details for follow-up.

The **Orders** view lists all successfully processed customer orders that were created from emails with attachments or by uploading documents directly in the cockpit. Only orders that came through the email channel are displayed.

The table provides key order details, including order number, link to the related order intake document, status, customer, order date, delivery date, delivery address, payment, and order value.

Use this view to verify that order intake processing has resulted in the expected orders and to access individual records for further review or follow-up.

Orders displayed in the Order Intake Cockpit are also visible in the Management Dashboard. However, orders from channels other than *email* are not shown here.

<figure><img src="https://994915088-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXembrzntBOyi7ynrVRB%2Fuploads%2Fgit-blob-9cbec8507f127b5ce59910a0ce78459c328dd30e%2Forder_intake_cockpit_orders.png?alt=media" alt="Orders table with columns and status badges"><figcaption><p>Orders — sales orders from order intake</p></figcaption></figure>

## Order details

The Order details view shows the full information for a selected order. Open an **Order number** from the table to access this view. It allows you to review all data captured during the order intake process.

At the top of the page, you see the order identifier along with a status badge.

The page is organized into sections that group key information:

* **Order** - Includes data such as date, channel, site, market, and payment method.
* **Customer** - Displays details such as name, email, customer ID, and company.
* **Addresses** - Shows both Ship To and Bill To information.

The order items table lists all products included in the order. For each item, you can review the product (image, identifier, and label), as well as quantity, net price, tax, and gross price.

<figure><img src="https://994915088-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXembrzntBOyi7ynrVRB%2Fuploads%2Fgit-blob-48a7ce61d39fe35dcdc25c049eef32c6aba10f3e%2Forder_intake_cockpit_order_details.png?alt=media" alt="Order details page with summary cards and order items table"><figcaption><p>Order details view</p></figcaption></figure>


---

# 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://developer.emporix.io/order-intake-cockpit/cockpit-views/orders.md?ask=<question>&goal=<user_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.
