At a glance
Pending Shipment is the dispatch backlog metric tracked from Newegg Marketplace data. It counts orders that are paid and awaiting dispatch right now. A spike above your 30-day average is the earliest warning of a fulfilment backlog, and a backlog is what turns into late shipments and a falling On-Time Shipping Rate if it is not cleared. Because it protects the loudest input to seller health, this card sits in the hero set for owners and operations.
| What it counts | The live count of orders that are paid and awaiting dispatch, as surfaced by the Newegg Marketplace integration. A real-time queue depth, not a period total. |
| Sample type | Backend API data from Newegg Marketplace, refreshed on the standard data refresh. |
| Why it matters | Pending orders are the dispatch backlog. A spike above the 30-day average signals you are falling behind, and an uncleared backlog becomes late shipments that drag On-Time Shipping Rate and seller health. |
| Reading the value | Read the current count against your normal 30-day average. A count near average is healthy queue churn; a count well above it means the backlog is growing faster than you are dispatching. |
| Currency | count |
| Time window | RT |
| Alert trigger | >2x 30D avg |
| Sentiment key | neg_pending_ship |
| Roles | owner, operations |
Calculation
Calculated automatically from your Newegg Marketplace data. The card reports the live count of paid orders awaiting dispatch and compares it against your trailing 30-day average queue depth, flagging when the current backlog runs well above that baseline. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Pending Shipment for a typical merchant on Newegg Marketplace. Suppose the queue normally sits around 25 orders awaiting dispatch and the card reads 58 mid-morning, more than double the 30-day average, so the alert fires. Checking Orders / Day shows yesterday ran hot on a promotion while a packer was out, so the queue built overnight. The merchant pulls an extra dispatch shift and clears the backlog by end of day, before any order passes its ship-by date, so On-Time Shipping Rate is never touched. Catching it as a live spike rather than as late shipments after the fact is the difference. For deeper investigation, use Vortex Mind to trace whether the backlog concentrates in specific SKUs or fulfilment paths; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
neg_on_time_ship_rate | Fulfilment sibling: the shipping rate this backlog threatens. |
neg_late_shipments | Fulfilment sibling: what an uncleared backlog becomes. |
neg_orders_per_day | Fulfilment sibling: the daily volume that feeds the queue. |
new_orders | Sales sibling: total order count over the window. |
neg_marketplace_health_score | Executive sibling: the composite health score a backlog can drag. |
Reconciling against Newegg Seller Portal
Where to look in the Newegg Seller Portal: Orders awaiting dispatch appear in the Seller Portal order management view, typically filtered to unshipped or pending-shipment status. The live count there should track the Vortex IQ figure. Confirm the status filter and whether SBN orders, which Newegg Logistics dispatches, are included before reconciling. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Evaluation timing. Vortex IQ reads the queue at its refresh; Seller Portal updates as you ship, so the two can differ by a refresh interval. | Variable | Allow for the refresh interval, or force a manual refresh. |
| Status scope. Vortex IQ counts paid orders awaiting dispatch; a Seller Portal filter may include or exclude unpaid or on-hold orders. | Variable | Match the status filter. |
| Fulfilment scope. SBN orders dispatched by Newegg Logistics may show differently from seller-fulfilled orders. | Variable | Confirm which order types each view counts. |