Order statuses and lifecycle
The order statuses and lifecycle functionality defines how an order progresses from creation to completion, including handling exceptions such as backorders, refunds, or cancellations.
Each order is assigned a status that reflects its current state in the fulfillment and payment process.
Statuses can also be applied at the item level, providing detailed tracking for partial shipments and returns.
Statuses and lifecycle
| status | description |
|---|---|
| Inactive | Order exists in a “soft deleted” state. |
| Pending | Order created and awaiting processing. |
| Backorder | One or more items are out of stock. |
| On-hold | Order requires confirmation (can also be set later, for example after a failed capture/refund or manual review). |
| Refunded | At least one refund exists on the order. |
| Completed | All items are fulfilled with no remaining actions. |
| Partial | Some items are fulfilled with unfulfilled items remaining. |
| Cancelled | Order is cancelled. |
Typical flow
graph LR
A[Pending] --> B[On-hold]
A --> C[Backorder]
A --> D[Completed]
A --> E[Cancelled]
A --> F[Refunded]
B --> D
C --> D
B --> E
C --> E
D --> F
Common paths:
pending → completed(standard fulfillment)pending → on-hold → completed(manual review required)pending → backorder → completed(stock shortage resolved)pending → cancelled(order cancelled before fulfillment)pending → refundedorcompleted → refunded(refund processed)
Payment behavior
- Payment captures are triggered automatically upon fulfillment.
- Refunds or cancellations update the order status accordingly.
Item level statuses
Individual items within an order can also have their own statuses for more granular tracking:
- ready
- returned
- shipped
- cancelled
- backorder
Typical use cases
The order lifecycle functionality enables structured handling of order states across fulfillment, payment, and return flows.
1. Standard order processing
Track and manage the full lifecycle from order creation to fulfillment.
- An order moves from pending to completed once all items are fulfilled.
- Automatic payment capture is triggered when fulfillment is confirmed.
2. Managing exceptions
- Orders automatically placed into on-hold for manual review after a failed capture, refund, cancellation or when matched by a fraud detection rule (order filter).
- Orders automatically marked as backorder when stock runs out.
3. Partial fulfillment and returns
Support multi-step fulfillment and return workflows. Examples include:
- Shipping available items first while others remain in partial status.
- Processing returned items without changing the rest of the order.
Related functionality
| Type | description |
|---|---|
| Fulfillment | Updates order and item statuses upon shipment or completion. |
| Payment / capture | Automatically triggers payments when orders are fulfilled. |
| Returns | Adjusts item or order statuses when products are returned. |
| Inventory | Reflects stock adjustments when orders are fulfilled or cancelled. |