Overview
When Luminous calculates pending inventory from fulfillment orders (FOs), you can now choose exactly which FO lifecycle statuses reserve stock. This lets you match inventory commitments to your actual warehouse workflow.
Prerequisite: This setting only appears when "Enable count pending based on fulfillment orders" is turned on in Inventory Settings. If you are still using sales-order-based pending, the multi-select is not shown and this guide does not apply.
Where to find the setting
- Go to Settings → Inventory.
- Scroll to the Pending Calculation Settings section.
- Confirm the "Enable count pending based on fulfillment orders" toggle is on.
- The "Fulfillment order statuses that count toward pending inventory" multi-select will appear directly below the toggle.
Selectable statuses
| Status | When to include it |
|---|---|
| Pending | Standard active FOs — almost always selected |
| Planned | FOs waiting in a pre-pick queue; include to hold stock before the order enters the working queue |
| Awaiting Shipment | FOs ready to hand off to a carrier |
| On Hold | FOs paused by your team; include to keep those units off the available count |
| Partially Shipped | FOs where some lines have shipped; remaining unshipped quantity continues to count |
| Committed | FOs confirmed for a specific warehouse or carrier |
| Processing | FOs actively being picked or packed |
| Ready to Ship | FOs staged for carrier pickup (used by some WMS integrations) |
Note: Cancelled, Error, and Action Required FOs are always included in the pending calculation as a safety net, regardless of what you select here. This prevents stock from going unaccounted if an FO cancel or error event has not yet fully propagated.
Changing the selection
- Click the multi-select dropdown and check or uncheck statuses.
- Click Save Settings (top-right of the Inventory Settings page).
- Luminous automatically runs a pending recount for all affected SKUs — no manual action required. You will see PENDING SKU RECOUNT entries appear in affected SKU qty logs within a few minutes.
On Hold sync behavior
If you add or remove On Hold from the list, Luminous automatically keeps the legacy "Reserve inventory for on-hold orders" toggle in sync so that sales-order-side pending paths stay consistent.
Default behavior (if no selection has been saved)
If the multi-select has never been saved for your account, Luminous uses a built-in default list that mirrors the legacy behavior: all standard pending statuses are included, Planned is excluded, and On Hold inclusion is controlled by the separate "Reserve inventory for on-hold orders" toggle.
Common configurations
Standard 3PL workflow — include Pending, Awaiting Shipment, Partially Shipped, Committed, Processing.
Pre-allocation / pre-pick queue — add Planned so stock is reserved as soon as an FO is created, before it enters the active pick queue.
On-hold as a workflow pause only — exclude On Hold so paused FOs do not reduce available quantity, allowing those units to fill other orders.
Carrier-staged holding — add Ready to Ship to keep units reserved until a carrier scan confirms pickup.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| Multi-select is not visible | FO-based pending is not enabled — turn on the toggle above it |
| Available inventory jumped after saving | A previously included status was removed from the list; recount freed those units |
| Available inventory dropped after saving | A new status was added; orders in that state now reserve stock |
| Changes seem slow to appear | Pending recount runs in the background — allow a few minutes, then refresh the SKU page |