> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trackstarhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Trackstar is a unified REST API for WMS, cart, and carrier systems. Base URL: https://production.trackstarhq.com. There is no SDK; call the API with plain HTTP.
> Send x-trackstar-api-key on every request. Endpoints scoped to one connection also need x-trackstar-access-token. Read both from environment variables and never print them.
> Reads return data Trackstar has already synced from the connected system. Writes (POST, PUT, PATCH, DELETE) are forwarded to the connected system immediately.
> A new connection has no data until its initial sync finishes. Wait for the connection.historical-sync-completed webhook, or poll GET /connections/{connection_id} and check historical_sync_completed.
> List endpoints page with page_token and next_token (limit is capped at 1000). Repeat every filter on every page. Filters use field[operator]=value, for example created_date[gte]=2026-01-01T00:00:00Z.
> Write bodies must not contain null or empty strings; omit the field instead. Call GET /integrations/{integration_type}/{integration_name}/write-info first to learn the exact fields an integration accepts.
> To test without real credentials, POST /sandbox/generate-sandbox/{wms|cart|carrier} with the API key returns a sandbox access token. Start at https://docs.trackstarhq.com/how-to-guides/build-with-ai.md and install the skills with: npx skills add https://docs.trackstarhq.com

# Cart Orders

> Cart orders with line items, and the order status lifecycle

An order is a purchase made by a customer. It contains information about the order,
including the individual line items. Each line item contains a `product_id` that
can be passed to the [`/cart-api/products/{product_id}`](/api-reference/cart-api/products/get-item) for more details.
The line item may also include the item's `sku`, the parent product's ID, and the parent product's `sku`.

### Order Statuses (in order of lifecycle)

| Status | Definition |
| :- | :- |
| `open` | Order has been placed. |
| `confirmed` | Order has been confirmed by the cart system. |
| `processing` | Order is being processed by the warehouse. |
| `partially_fulfilled` | Order has been partially fulfilled. |
| `fulfilled` | Order has been fulfilled and shipped. |
| `backordered` | Order cannot be fulfilled because of a lack of available inventory. |
| `exception` | There is an issue with the order. |
| `cancelled` | Order has been cancelled by either the platform, warehouse, or customer. |
| `other` | Status of the order can't be determined. Often due to a custom status being used. See the `raw_status` field for more information |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.