Orders downloaded from /inbox/orders that haven’t been dispatched yet.
At a glance
Live count of confirmed AbeBooks orders downloaded from the inbox that haven’t yet been dispatched. The leading indicator for Dispatch SLA Compliance, an order sitting past 75% of its dispatch_due_by budget is about to become an SLA breach.
| What it counts | COUNT(orders WHERE confirm_shipment_at IS NULL AND order_status = "Confirmed"). Real-time view of the dispatch queue depth. |
| API endpoint + report | AbeBooks Inbound Orders feed (orders with no matching outbound-confirm event). The card recomputes every 4h alongside the feed refresh. |
| Listing-quality impact | Indirect via dispatch SLA. A swelling queue precedes SLA breaches by 24 to 72h, which precede a search-rank demotion by 3 to 7 days. Watch this card to act before the rank impact lands. |
| Fees / commission | Not applicable (count metric). |
| Refunds | Not applicable. |
| Cancellations | Cancelled orders leave the queue. A bookseller cancelling a stockout reduces this card; the cost surfaces on Cancellation Rate instead. |
| Currency | Not applicable. |
| Per-order time-to-deadline | Each order has a dispatch_due_by deadline (typically order time + 2 business days). The card aggregates count; the per-order view (sorted by deadline) lives in the AbeBooks dashboard order-list. |
| Multi-marketplace overlap | Pending Dispatch on AbeBooks and Alibris are separate queues even when the same fulfilment team works both. Cross-check Alibris Pending Dispatch. |
| Time window | RT (real-time, recomputed every 4h). |
| Alert trigger | >2x 30D avg. The dynamic threshold catches genuine queue swells while tolerating normal day-to-day variance. |
| Sentiment key | unfulfilled_count |
| Roles | owner, operations |
Calculation
Calculated automatically from your AbeBooks data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The same UK bookseller, snapshot 02 May 26 14:00 UTC. 30D average pending dispatch queue depth is 64 orders.| Time-to-deadline bucket | Orders pending |
|---|---|
| >36h remaining (just landed) | 84 |
| 24 to 36h remaining | 32 |
| 12 to 24h remaining | 18 |
| 0 to 12h remaining (urgent) | 9 |
| Already breached | 2 |
| Total Pending Dispatch (this card) | 145 |
- The 0 to 12h tier is the action queue. 9 orders in the 0 to 12h tier need to ship today or they breach. Sort the seller-dashboard order list by
dispatch_due_byascending and clear those nine first; everything else is healthy. - The 84 just-landed are usually fine. A daily inbound-feed cycle dumps a day’s orders at once; they appear as “just landed” with the full 2-day budget. The risk is not that they exist but that they outpace pick-and-pack capacity.
- The 2 already-breached are still recoverable, ship today. A breach reads as late but a same-day-as-breach dispatch (1 to 4h late) hits SLA much less than a 24h+ late dispatch. Get them out the door regardless.
- The 2.27x ratio usually maps to a real-world cause. Investigation on this snapshot showed: 2 staff sick yesterday (warehouse capacity ~50% normal), plus a Bank Holiday Monday in the previous 30D average that was already low. Ratios above 2x with a “feels normal in here” workshop are usually a feed-cadence misread, not a real backlog.
- Cross-marketplace: the Alibris queue is at 1.4x its avg. A bookseller running both AbeBooks and Alibris from the same warehouse will see correlated queue swells. If only one is high, the imbalance is in the picking workflow, not the order volume.
Sibling cards merchants should reference together
Pending Dispatch is the live operational gauge. Pair with these:| Card | Why pair it with Pending Dispatch |
|---|---|
| Dispatch SLA Compliance | The downstream effect. Queue swells precede SLA dips by 24 to 72h. |
| Avg Time to Process (hrs) | The throughput view. Queue divided by throughput = expected time-to-clear. |
| Cancellation Rate | The escape valve. Cancellations remove orders from this queue at the cost of seller standing. |
| Inbound Orders File Lag | If the inbound feed is delayed, your dispatch clock is already ticking before you see the order. |
| Last Successful Upload | Outbound-confirm uploads are how AbeBooks learns you dispatched. A failed upload = orders staying “pending” in AbeBooks’s view even after you ship. |
| Order Count | Context. Pending Dispatch = 145 vs daily Order Count = 42 means roughly 3.5 days of orders queued. |
| Alibris Pending Dispatch | Cross-marketplace queue depth from the same fulfilment team. |
Reconciling against the vendor’s own dashboard
Where to look in the AbeBooks seller dashboard: My AbeBooks → Order History → filter Status = Confirmed (Awaiting Dispatch). Sorted bydispatch_due_by, this is the row-level view of the queue.
Why our number may legitimately differ from the AbeBooks dashboard:
| Reason | Direction | Why |
|---|---|---|
| Feed refresh lag | Ours can lag by up to 4h | The Inbound Orders feed lands every 4h by default; new orders may not appear in this card until the next refresh. AbeBooks’s dashboard is real-time. |
| Outbound-confirm latency | Ours can lag, theirs lower | If you’ve dispatched but the outbound-confirm hasn’t run, AbeBooks shows the order as still pending. Our card uses our own outbound-confirm timestamp; if that’s accurate, we’ll show fewer pending. |
| Cancellation timing | Ours lags by ~4h | A cancelled order disappears from AbeBooks’s view immediately; from ours on the next feed refresh. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
alibris.al_pending_dispatch | Often correlated; same fulfilment team. | Different inbound-feed cadences (AbeBooks daily vs Alibris weekly common) make Alibris queue ratios less responsive. |
amazon.amzn_pending_orders_count | Independent. | Amazon FBA orders don’t go through your queue at all; only FBM orders do. |
Known limitations / merchant FAQs
My queue is at 2.5x average. What now? Open the seller-dashboard order list, sort bydispatch_due_by ascending, dispatch the top 10 to 20 first. The 0-to-12h-remaining tier matters most; the just-landed orders can wait. If the queue is structurally above target every day for 7+ days, the issue isn’t a queue-clearing exercise, it’s capacity, hire or extend handling time.
Vendor (AbeBooks) vs commerce-platform (Shopify), why doesn’t Shopify have a Pending Dispatch card?
Because Shopify’s “unfulfilled orders” aren’t on a third-party clock. You set the shipping promise; the buyer accepts it; you ship at your own pace. AbeBooks’s clock is binding and the SLA is enforced.
Are fees affected?
No, fees attach to sales, not queue depth. Indirectly: a swelling queue precedes an SLA breach precedes a search-rank demotion that precedes a revenue dip.
Multi-marketplace pricing arbitrage; if I cancel a queue item to ship via Alibris instead, what happens?
The order leaves this card and lands on Cancellation Rate. Cancellation rate has its own 3% threshold; repeated marketplace-arbitrage cancels close accounts.
Inventory-sync lag; the queue includes books I don’t actually have in stock anymore.
Common, especially when multi-marketplace inventory sync is daily. Cancel those orders within 1h of confirming the stockout (most booksellers’ SLA-recovery playbook). The fix is real-time inventory sync.
ISBN match quality; does it affect this card?
No, this card counts orders, not listings. ISBN issues affect upstream listing quality but don’t change the dispatch queue.
Rare books vs commodity books, do they show up differently?
Rare books are usually the long-tail of the queue: each order takes longer to pick (rare-book room, condition double-check, careful packaging) but represents 5 to 10x the per-order revenue. Two rare orders sitting unprocessed are operationally equivalent to ten commodity orders.
Why does today’s number swing so much?
Because the inbound feed lands in batches (typically once a day). Just after a feed cycle, this card jumps; through the working day, it falls as orders ship. The 4h refresh smooths some of this; nothing smooths it entirely. The 2x-vs-30D-avg alert is calibrated to ignore normal intraday variance.