> For the complete documentation index, see [llms.txt](https://docs.resifactory.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.resifactory.net/the-console/orders.md).
# Orders
Orders reads your mail and builds a record of every purchase it finds — confirmations, dispatch notices, tracking numbers and delivery events, stitched into one row per order.
Nothing to set up. Orders appear as the mail that describes them arrives.
## The stat strip
| Figure | What it counts |
| ---------------- | --------------------------------------------------------------------------- |
| **Total orders** | Every order found. |
| **Active** | Ordered, preparing, shipped or out for delivery — anything still in flight. |
| **Delivered** | Completed. |
| **Cancelled** | Cancelled. |
| **Cancel rate** | Cancelled as a share of the total. |
The bar beside them shows active / delivered / cancelled proportionally.
**Top products** below summarises what you are buying most, grouped from the orders currently loaded.
## Status tabs
`All`, `Ordered`, `Prep`, `Shipped`, `Out for delivery`, `Delivered`, `Cancelled`, `Unknown` — each with its count. Click one to filter.
Counts ignore the status filter itself, so every tab stays accurate while you have one selected.
## The list
| Column | What it shows |
| ------------ | --------------------------------------------------------------------------------------------- |
| **Product** | What was bought, with the retailer. |
| **Qty** | Quantity. |
| **Pipeline** | A five-stage progress track: ordered → preparing → in transit → out for delivery → delivered. |
| **Account** | Which mailbox received the order mail. |
| **Order #** | The order number. |
| **Updated** | When the last event arrived. |
The pipeline is the fastest way to scan a long list — the filled portion tells you where each order is without reading anything.
## Filtering and sorting
| Control | What it does |
| ------------------------- | ------------------------------------------------------- |
| **Search** | Product name or order number. |
| **All retailers** | Narrow to one retailer. |
| **All batches** | Narrow to one [batch](/the-console/batches.md). |
| **Sort** | Change the sort field, and the arrow flips direction. |
| **Date range** | `from` and `to` — scopes the list *and* the stat strip. |
| **Compact / Comfortable** | Row density. |
| **Views** | Save the current filter set and recall it later. |
| **Export CSV** | Download the current filtered view. |
| **Resync tracking** | Force a fresh carrier lookup for selected orders. |
| **Refresh** | Re-fetch. |
### Saved views
**Views** stores the current combination of filters, sort and date range under a name. Useful for the handful of questions you ask repeatedly — "active orders this week", "everything cancelled this month".
## Order detail
Click a row.
It shows:
* **Status and retailer**, with the tracking number as a link to the carrier.
* **Pipeline**, with a date on each completed stage. **Expand** shows the full carrier event history — every scan, with times and locations.
* **Details** — retailer, order number, quantity, order date, last event, and the mailbox that received it.
* **Source messages** — the actual emails this order was built from. Click through to read them in the [Inbox](/the-console/inbox.md).
**Prev** / **Next** step through the filtered list without closing the panel.
### Refresh from the carrier
**Refresh from UPS** (or FedEx) pulls live tracking on demand. Tracking is refreshed automatically in the background; this is for when you want an answer right now.
## Bulk actions
Select rows with the checkboxes and a bar appears — the main action being **Resync tracking** across the selection.
## Making orders work well
{% hint style="success" %}
**Give order-tracking tools a wide enough** [**inbox window**](/imap/inbox-window.md)**.**
A shipping chain runs over days: confirmation, dispatch, out for delivery, delivered. A credential with a 1-hour window sees the delivery notice and never the order it belongs to. **Last 14 days** covers almost all retail cycles.
This applies to your IMAP tools. The Orders page itself always reads everything retained.
{% endhint %}
## If an order is missing
1. **Check the mail arrived.** Search the [Inbox](/the-console/inbox.md) for the order number. If the confirmation is not there, there is nothing to build an order from.
2. **Check the date range** and any active filters — the stat strip is scoped by them too.
3. **Check the retailer's format.** Orders are built by reading retail mail; an unusual sender or an image-only confirmation may not be recognised.
4. **Check the status tab.** It may have landed in `Unknown` rather than the tab you were looking at.
---
# 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://docs.resifactory.net/the-console/orders.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.