Every order, every channel - one loop to close it.
The order loop tracks customer demand from receipt through delivery. Allocation, fulfillment queueing, shipment, and close are explicit states with full event history and no ambiguous handoffs.
Allocated (4)
LMB-ORD-2026-1042
B2B · $4,920
LMB-ORD-2026-1102
DTC · $684
In Fulfillment (7)
LMB-ORD-2026-0041
Shopify · $1,120
LMB-ORD-2026-1089
B2B · $2,360
Shipped (12)
LMB-ORD-2026-0891
DTC · $148
LMB-ORD-2026-0037
B2B · $3,040
Multi-channel
Shopify, Square, B2B EDI, and manual orders in one loop
Allocated
Inventory reserved at order receipt before fulfillment queues
Closed loop
Delivery confirmation closes order and updates connected systems
From received to closed - every step on record
Orders move through explicit states that enforce valid transitions and preserve history for operations, finance, and customer teams. Partial shipment and cancellation behaviors stay visible and auditable.
- - RECEIVED → ALLOCATED → FULFILLMENT_QUEUED → SHIPPED → DELIVERED → CLOSED
- - Invalid transitions rejected to prevent accidental skips
- - Partial shipment supports backorder tracking
- - Cancellation releases inventory and emits downstream events
LMB-ORD-2026-0041
| SKU | Qty | Allocated | Status |
|---|---|---|---|
| LMB-BRS-001 | 24 | 24 | Ready |
| LMB-BRT-001 | 12 | 12 | Ready |
RECEIVED 14:02 → ALLOCATED 14:04 → FULFILLMENT_QUEUED 14:07
Allocation panel
Available before
2,840
Reserved for order
480
Available after
2,360
Lot LMB-LOT-2025-002 · 480 units · Pinned · Allocation confirmed
Allocation that protects your inventory
Reservation happens as soon as an order is accepted, so available stock reflects committed demand in real time. Regulated and high-value orders can be lot-pinned to keep execution and compliance aligned.
- - Inventory reserved at RECEIVED → ALLOCATED transition
- - Lot-pinned allocation for regulated or high-value orders
- - Allocated quantity removed from available stock in real time
- - Cancellation releases reservation automatically
B2B and wholesale orders - same loop, richer data
B2B flows carry buyer PO references, terms, and case-pack commitments without forcing a parallel workflow. DTC and wholesale orders share one order loop with channel-specific fields.
- - Buyer PO reference attached to loop instance
- - Case-pack and pallet quantity handling
- - Delivery window commitments tracked through execution
- - B2B invoicing events emitted at shipment
B2B Order · IRONRIDGE Construction
Buyer PO: PO-IR-2026-0089
Delivery window: Mar 10-14
Payment terms: Net 30
Case packs: 24 cases
ALLOCATED · Fulfillment window: 3 days
Built for operators
The order loop captures committed demand while fulfillment executes against it. When both loops close, inventory, finance, and customer status stay synchronized from one event chain.
API and integration
- REST API - order CRUD, allocation management, and cancellation endpoints
- Loop events - consumed by fulfillment, inventory, and finance integrations
- Commerce Gateway exposure for AI agents and customer portal tooling
Related modules
One loop from order received to order closed
Book a 30-minute demo. We will walk your order flow end to end.
Book a demo