At a glance
Pending Shipment counts the paid Bonanza orders that are waiting to be dispatched. On Bonanza, every order in this queue is a buyer expecting their item to move, so a queue that suddenly swells is the clearest early sign of a fulfilment backlog. The card flags a spike above twice your 30-day average. Clearing the queue promptly protects on-time shipping, feedback, and booth standing.
| What it counts | The number of paid orders that have not yet been dispatched. |
| Sample type | Backend API data from Bonanza, refreshed on the standard data refresh. |
| Why it matters | A growing pending queue is the first sign fulfilment is falling behind, which puts on-time shipping, feedback, and booth standing at risk. |
| Reading the value | Read it as a plain count of orders awaiting dispatch; lower is healthier. A jump above twice your 30-day average flags a backlog. |
| Currency | number |
| Time window | RT |
| Alert trigger | >2x 30D avg |
| Sentiment key | bon_pending_ship |
| Roles | owner, operations |
Calculation
Vortex IQ counts the paid orders that have been confirmed but not yet marked as shipped, refreshed in real time. The figure rises as new paid orders arrive and falls as you dispatch them. The card compares the live count against your trailing 30-day average and flags when it climbs above twice that baseline, so a normal busy day reads differently from a genuine backlog. See the At a glance summary above for the spike threshold and the worked example below for a typical reading.Worked example
A representative reading of Pending Shipment for a typical merchant on Bonanza. On 14 Mar 26 a booth’s pending queue hit 48 orders against a 30-day average of 20, tripping the spike alert at more than twice the baseline. A weekend promotion had pulled in a burst of sales while packing ran on its usual weekday schedule. The interpretation was a demand spike rather than a stock or carrier problem, and the action was to add a packing session and prioritise the oldest orders so none breached their ship-by deadline. Vortex Mind traces the upstream cause, here a promo-driven order burst, and Ask Viq lets you ask “how many orders are still waiting to ship” in plain English.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
bon_on_time_ship_rate | Fulfilment sibling: On-Time Shipping Rate. |
bon_alert_dispatch_sla_miss | Fulfilment sibling: Late Shipments. |
bon_orders_per_day | Fulfilment sibling: Orders / Day. |
bon_cancellation_rate | Fulfilment sibling: Cancellation Rate. |
bon_order_count | Revenue sibling: Orders. |
Reconciling against Bonanza
Where to look in Bonanza’s own dashboard: Open your booth dashboard and review the order management area, filtering to paid orders that have not yet been marked shipped. That awaiting-dispatch list is what Vortex IQ counts. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ counts in real time; Bonanza dashboards may group orders by calendar periods. | Variable | Match the period range. |
| Time zone. Bonanza uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (booth, channel, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |