Commerce Backorders

Track unfulfilled demand, allocate incoming inventory, and prioritize backorder fulfillment.

How It Works

1. Create backorders when ordered items are out of stock.
2. Set priority and expected/promised dates.
3. Allocate incoming inventory (from POs, production, or transfers) to backorders.
4. Fulfill backorders partially or completely as stock becomes available.
5. Monitor backorder summaries by SKU and priority.

Usage

• MCP tools: list_backorders, create_backorder, update_backorder, allocate_backorder, fulfill_backorder, cancel_backorder, get_backorder_summary, get_sku_backorder_summary.
• Writes require --apply.

Backorder Statuses

• Pending -> PartiallyFulfilled -> Allocated -> ReadyToShip -> Fulfilled (or Cancelled)

Priority Levels

• Low, Normal (default), High, Critical

Fulfillment Sources

• Inventory (default): existing warehouse stock
• PurchaseOrder: incoming supplier shipment
• Transfer: inter-warehouse transfer
• Production: manufacturing output

Output

{"status":"partially_fulfilled","backorder_id":"BO-2025-0015","sku":"WIDGET-001","quantity_ordered":100,"quantity_fulfilled":60,"quantity_remaining":40}

Present Results to User

• Backorder number, SKU, and priority.
• Quantities ordered, fulfilled, and remaining.
• Expected and promised dates.
• Fulfillment source (PO, production, etc.).
• SKU-level backorder summary across all orders.

Troubleshooting

• Allocation expired: re-allocate or extend expiration date.
• Cannot fulfill: verify available inventory matches allocation.
• Priority conflict: Critical backorders should be fulfilled before Low/Normal.

References

• references/backorder-management.md
• /home/dom/stateset-icommerce/crates/stateset-core/src/models/backorder.rs
• /home/dom/stateset-icommerce/crates/stateset-embedded/src/backorder.rs