What the card counts
The Fulfillment orders not pushed card in the Action Center shows fulfillment orders that:
- Have never been successfully pushed to a warehouse or fulfillment channel (pushed_at is blank), and
- Are not cancelled, shipped, or partially shipped, and
- Have a push destination — either a fulfillment channel or a destination OMS — configured, and
- Were created more than 30 minutes ago (orders inside that window may still be handled automatically by the auto-push job).
What the card does NOT count
| Situation | Why it is excluded |
|---|---|
| Fulfillment order created in the last 30 minutes | It is likely still in the automatic push queue. Counting it would produce a 'stuck' signal for orders that are actively being processed. |
| Fulfillment order with no fulfillment channel and no destination OMS | There is nowhere to push it. These cannot be resolved from the push button, so they do not belong in this work queue. Common examples: FBA transfer orders fulfilled outside Luminous. |
| Fulfillment order that was previously pushed (even if it later shows an error message) | The error message column is not used to determine push status. An order that was successfully pushed — even if an old error message is still stored — is not counted. |
| Cancelled, shipped, or partially shipped orders | These are closed or in progress and require no action. |
Why the card count may briefly differ from the drill-in list
The card count is cached for about 60 seconds to keep the page fast. If orders were pushed during that window, the card may briefly show a non-zero count while the drill-in list is empty. When this happens, Luminous automatically requests a fresh count in the background and updates the card — no manual reload is needed.
Per-channel breakdown cards
Below the main card you may see up to three sub-cards, one per fulfillment channel, showing which channel accounts for the most stuck orders. These are drawn from the same population as the parent card; they do not add to the total.
What to do when the count is non-zero
- Click View all to open the Fulfillment Orders grid, filtered to orders where
Pushed atis blank. - Review each order. Common causes: the fulfillment channel lost its connection, the order was on hold when the auto-push ran, or a push was attempted but failed.
- Use the Push to channel button on each row (available directly from the Action Center drill-in, or from the Fulfillment Orders grid) to send the order to the warehouse.
If every order in the list has a push destination and is older than 30 minutes but still shows here, the issue is likely a warehouse connection or channel configuration problem — check your fulfillment channel settings.
Permission required: The Sales Orders read permission is required to see this card.