An Order is a mutable, in-progress purchase record. It represents a sale that has not yet been finalised — for example, an eCommerce cart checkout in progress, a layby, or a pending POS sale.Documentation Index
Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
Use this file to discover all available pages before exploring further.
Orders vs Transactions
| Order | Transaction | |
|---|---|---|
| State | In-progress, mutable | Completed, immutable |
| Typical source | eCommerce checkout, layby, pending sale | POS completion, fulfilled order |
| Can be updated | Yes | Yes, but discouraged — prefer void |
| Triggers aggregations | No | Yes |
| Triggers reactions | Depends on configuration | Yes |
| Customer sees | No | Yes (Clienteling, Profile Portal) |
Creating an order
Reading an order
Updating an order
Orders can be updated as the purchase progresses — for example, when items are added or removed, or the status changes:Completing an order
When the order is fulfilled and payment is confirmed, create a Transaction referencing the order. Provide theorder_id field in the transaction payload to link them:
Deleting an order
Content needed: order status enum values, full field reference, and relationship to Shopify checkout in the Shopify extension context.