Order Lifecycle

A store-based delivery order follows this flow:

Code
┌──────────────┐
│  ACCEPTED    │  Order accepted by Shadowfax
└──────┬───────┘
       │
       ▼
┌──────────────┐    ┌──────────────┐
│  ALLOTED     │───▶│  CANCELLED   │
└──────┬───────┘    └──────────────┘
       │                   ▲
       ▼                   │
┌──────────────┐           │
│  ARRIVED     │           │
└──────┬───────┘           │
       │                   │
       ▼                   │
┌──────────────┐           │
│  DISPATCHED  │───────────┘
└──────┬───────┘
       │
       ▼
┌──────────────────────────┐
│ ARRIVED_CUSTOMER_DOORSTEP│
└──────────┬───────────────┘
           │
     ┌─────┴─────────────────┐
     ▼                       ▼
┌──────────┐    ┌─────────────────────┐
│ DELIVERED│    │ CANCELLED_BY_CUSTOMER│
└──────────┘    │   or UNDELIVERED     │
                └──────────┬───────────┘
                           │
                           ▼
                  ┌─────────────────────┐
                  │ RETURNED_TO_SELLER  │
                  └─────────────────────┘

Order Statuses

Callbacks may use ALLOTTED (double T) and additional statuses like UNASSIGNED.

Typical Timeline

Build your integration around callbacks for real-time updates. Use Get Order Details as a reconciliation fallback.

See the API Reference for full endpoint documentation.