> ## Documentation Index > Fetch the complete documentation index at: https://docs.colossal.sh/llms.txt > Use this file to discover all available pages before exploring further. # Orders > What was bought, by whom and for how much, created from checkout or synced from an ERP. An order captures what was bought, by whom, and for how much. ## How to use Orders are a standalone primitive. You can use them as part of the Colossal platform — created automatically from a [checkout](/concepts/checkout-and-payments), linked to a [customer](/concepts/customers), and referencing the [products](/concepts/products) that were purchased — or sync them to and from third-party systems like ERPs, fulfillment providers, or accounting tools to keep order data consistent across platforms. ## Surfaces Events for the order lifecycle. Actions for fetching, updating, and managing orders. LLM-callable tools for reading and updating orders. GraphQL queries for fetching orders on your storefront. ## Order status Order created. Payment not yet authorized. Payment authorized and order accepted. Order shipped or delivered. Refund issued after confirmation. Can apply in full or in part. Order cancelled and will not be fulfilled. ## Line items Each order contains one or more line items, capturing the variant, SKU, quantity, unit price, and total at the time of purchase. Variant properties and product images are snapshotted on the line item, so the order remains accurate even if the product is later edited or archived.