> 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/catalog-2.0-docs/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.
The listing may also be filtered by Customer Name, Customer Address, and eCommerce ID, or by Status
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.
🛍 **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.
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 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://community.threekit.com/platform-documentation/catalog-2.0-docs/org-setup/orders/orders-list.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.