Skip to main content
Metrics type: Key Metrics • Category: Marketplace

​
At a glance

Live alert table listing every Alibris order whose dispatch_due_by deadline has passed without a confirm-shipment event. Each row is an SLA breach in progress; the longer it stays, the larger the seller-standing damage and the higher the buyer-complaint risk.

​
Calculation

Calculated automatically from your Alibris data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A US bookseller, 666 orders/month average on Alibris, 2-business-day handling. Snapshot 01 May 26 09:00 UTC. Card reads 7 orders; alert is firing. Six things to notice that are specific to Alibris and the book trade:
  1. The 7 late orders represent 1.05% of monthly volume but disproportionately impact SLA. Each costs ~0.15 percentage points on a 666-order/month seller. SLA at 95% drops to 93.95%.
  2. Triage by hours-overdue, not by order date. AL-1233762 is 56.8h late and AL-1234521 is 1.4h late; the former needs immediate intervention, the latter just needs to ship today.
  3. The 3 institutional orders (AL-1234307, AL-1234044, AL-1233762) are P0 institutional risk. Library Services buyers escalate slowly but have long memories; chronic late-dispatch on academic procurement gets you filtered out of library-buyer search.
  4. The 1 rare-book order (AL-1233897, $180 Oxford) is high reputational impact. Rare-book buyers leave detailed feedback. Ship today with courier upgrade.
  5. Confirm-shipment-late vs actually-late. Investigation showed AL-1234438 and AL-1234189 actually shipped on time but the confirm-shipment cron only runs daily at 23:00 EST. Move to hourly.
  6. The $343 of revenue across 7 orders isn’t the headline. Seller-standing damage (search-rank suppression) far exceeds direct revenue exposure. Library Services exclusion if it persists is a much larger downstream loss.

​
Sibling cards merchants should reference together

Late order processing is the active-breach view. Pair with these:

​
Reconciling against the vendor’s own dashboard

Where to look in the Alibris seller dashboard:
  1. Sellers → Manage Orders → filter by Late. Row-level audit; Alibris highlights overdue rows.
  2. Sellers → Performance Dashboard. Aggregate seller-standing.
Why our alert may differ from Alibris’s UI: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

The alert just fired with 7 orders. What do I do in the next hour? (1) Sort by hours-overdue descending; address worst breaches first. (2) Spot-check institutional / rare orders; ship today with courier upgrade. (3) Identify cause per breach; don’t bulk-cancel. Why does Alibris penalise me here when the book actually shipped on time but my confirm-shipment was late? Alibris can only see what your outbound feed tells them. Run outbound-confirm cron every 15 minutes minimum. Multi-marketplace, can I avoid this by selling exclusively on Alibris? Single-marketplace concentration carries 3 to 5x the platform-failure risk. Operational discipline (tight cron, daily ops review) is the right answer, not channel concentration. Listing-quality / Buy Box impact, recovery time after a breach cluster? Each breach hits SLA for 30 days. If cumulative drops below 95%, search-rank demotion within 24h; demotion lifts 7 to 14 days after returning above. Total recovery 30 to 45 days. Inventory-sync lag, false positives? Yes. Confirm-shipment cron schedule mismatched with warehouse pack times produces false-late readings. Run cron every 15 minutes during business hours. ISBN match quality, can it cause late dispatches? Indirectly. Wrong-ISBN-against-physical-book causes warehouse delays at picking. Rare books vs commodity, breach impact difference? Per-breach financial weight 30 to 80x higher on rare. ALWAYS triage rare-book breaches first. When does the card auto-clear? Each row clears on confirm-shipment event. Whole card empty when no row is past dispatch_due_by. Is there ever a reason to cancel rather than ship a late order? Yes if book on inspection is materially worse than catalogued. Use Out-of-stock reason on Alibris. Alibris-specific: Library Services / institutional buyers, special handling? Yes. Institutional cohort has long memories; chronic late-dispatch on academic procurement risks filtered-out from library-buyer search filters. Treat institutional orders carefully even if their dispatch window is longer.

​
Tracked live in Vortex IQ Nerve Centre

Late Order Processing Queue is one of hundreds of KPI pulses Vortex IQ tracks across Alibris and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.