At a glance
Pending Shipment is a fulfilment metric tracked from Vinted data. It counts paid orders still waiting to be dispatched. On Vinted the buyer pays up front and the ship-by clock starts at once, so the pending queue is the work standing between you and a clean dispatch record. A queue that grows faster than you can pack is the direct precursor to late shipments, cancellations, and unhappy buyers.
| What it counts | The live number of paid orders awaiting dispatch, before any have breached their ship-by deadline. |
| Sample type | Backend API data from Vinted, refreshed on the standard data refresh. |
| Why it matters | The pending queue is your packing backlog. Kept low it means dispatch is keeping pace; allowed to swell it converts into late-shipment alerts and the cancellations and rating damage that follow. |
| Reading the value | Lower is better relative to your normal pace. A queue well above your typical level, especially more than twice the recent average, signals a packing crunch that needs clearing today. |
| Currency | count |
| Time window | Real time |
| Alert trigger | Fires when the pending queue rises above roughly twice the recent average, signalling a dispatch backlog. |
| Sentiment key | vin_pending_ship |
| Roles | owner, operations |
Calculation
Calculated automatically from your Vinted data. Vortex IQ counts paid orders that have not yet been dispatched, comparing the live count against your recent average to judge whether the queue is building. 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 Pro seller on Vinted. The queue normally sits around 8 orders, cleared daily. After a weekend away it reads 21, more than twice the recent average, so the alert fires. None are late yet, but several are close to their ship-by deadline. The action is straightforward: clear the backlog today, prioritising the orders nearest their deadline, before they tip into the late-shipments list. The structural fix is a weekend packing plan or a holiday-mode pause so the queue never builds to this point. For deeper investigation, use Vortex Mind to see whether backlogs recur on the same days; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
vin_late_shipments | Alert sibling: the acute outcome when the queue is not cleared in time. |
vin_ship_within_5d_rate | Fulfilment sibling: the dispatch-speed rate the queue feeds. |
vin_orders_per_day | Fulfilment sibling: order inflow that builds the queue. |
vin_order_count | Sales sibling: total orders behind the queue. |
vin_revenue_at_risk | Executive sibling: revenue exposed if the backlog cancels. |
Reconciling against Vinted
Where to look in Vinted’s own dashboard: Vinted shows orders awaiting dispatch in your sold-items or “to ship” view, each with its ship-by countdown. Reconcile by counting orders shown as paid but not yet dispatched against this card. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Scan timing. A just-scanned label may still show pending until status updates. | Marginal | Allow for short scan-to-status lag. |
| Queue definition. Vortex IQ counts paid-not-dispatched; orders mid-cancellation may be handled differently. | Variable | Confirm how cancelling orders are treated. |
| Refresh timing. A live read may sit between the queue and the next refresh. | Marginal | Force a refresh for the latest count. |