> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/org-setup/orders/orders-list.md).

# Orders List

The Orders tab allows for visibility on placed orders from an eCommerce system. Information is presented in a tabular format, sortable by Date and Status.<br>

<figure><img src="https://2668731230-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fknvt0jlDBXmk91mWaWXB%2Fuploads%2FofkwZJCWDTz4NzReNPXI%2FOrders_1.png?alt=media&amp;token=6487cb30-9016-4cd7-901c-021bc4a89af9" alt=""><figcaption></figcaption></figure>

The listing may also be filtered by Customer Name, Customer Address, and eCommerce ID, or by Status<br>

<figure><img src="https://2668731230-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fknvt0jlDBXmk91mWaWXB%2Fuploads%2F7cBYlgtVaqADsDEBwLko%2FOrders_2.png?alt=media&amp;token=64fc7ae5-c203-4db1-8af8-c0ab726bc5f7" alt="" width="249"><figcaption></figcaption></figure>

Clicking into a specific order presents all relevant order information, allows the user to update the status, and provides a path to opening each ordered catalog item with the configuration specified in the order.<br>

<figure><img src="https://2668731230-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fknvt0jlDBXmk91mWaWXB%2Fuploads%2FnSl8w0VYvnwXGX7DRk91%2FOrders_3.png?alt=media&amp;token=c282f743-4025-4f1a-a625-5bc3819ac199" alt=""><figcaption></figcaption></figure>

🛍 **Configuration groups** can be created to store wishlist-style configurations using the extended Orders functionality. To differentiate between “wishlists” and items that have been purchased, Order statuses have been updated to include “List” and “In Cart”. The statuses, individual configurations, and quantities can be updated via Threekit public APIs.This will help keep track of configurations as move through workflows and will enable analytics for configurations and states.<br>

<figure><img src="https://2668731230-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fknvt0jlDBXmk91mWaWXB%2Fuploads%2F1Ltgzp9NgFCzjRZIGW92%2FOrders_4.png?alt=media&amp;token=eef1552d-31cc-4b36-9f3c-f8a09b41c35f" alt=""><figcaption></figcaption></figure>

Full documentation here: [Orders API.](https://developer.threekit.com/reference/listorders)


---

# 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://community.threekit.com/platform-documentation/org-setup/orders/orders-list.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.
