% of orders dispatched before dispatch_due_by, drives Alibris seller standing.
At a glance
Percentage of Alibris orders dispatched on or before the dispatch_due_by deadline Alibris set when the order was confirmed. Drives Alibris seller standing alongside cancellation rate; the metric buyers see when choosing between two listings of the same ISBN.
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 independent bookseller, 666 Alibris orders in trailing 30 days, two-business-day handling time, single fulfilment location. Window 02 Apr 26 to 01 May 26.
The card reads 94.4%, BELOW the 95% threshold; alert is firing. The seller is at risk of search-rank demotion within 24 to 48h.
Six things to notice that are specific to Alibris and the book trade:
- The 28 orders dispatched 1 to 24h late are the most preventable category and represent 76% of the breach. All 28 came from a confirm-shipment cron job that runs daily at 23:00 EST while the warehouse pack-and-ship operation closes at 17:00 EST; the 6h gap puts every same-day shipment into the late bucket on the next-day’s dispatch_due_by deadline. Moving the cron to 17:30 EST would absorb most of these.
- A 9-order >24h-late tail can be dominated by one stockout event. Investigation showed 7 of the 9 came from a single 3-day inventory mismatch (28 to 30 Apr 26) where a warehouse pallet had been moved without the inventory tool being updated. The remaining 2 were genuine condition-mismatch events that should have been cancellations.
- Alibris’s seller standing tile lags this card by 24 to 48h. The bookseller’s Performance page on 01 May 26 shows 95.1% (ours says 94.4%). Alibris recomputes the dashboard tile once a day around 02:00 PST. By 02 May 26 our card matches within 0.1 to 0.3 points.
- Alibris Library Services orders (institutional buyers) have a different threshold expectation. Libraries often have internal procurement rules requiring 96%+ seller-standing. Falling to 94.4% may not just demote search rank, it may trigger your account being filtered OUT of library-buyer search results entirely, costing you the high-AOV institutional cohort. The financial impact is disproportionate to the percentage drop.
- Cross-marketplace consistency matters more than the Alibris number alone. The same bookseller’s AbeBooks SLA Compliance is 95.8% in the same window. The difference is the confirm-shipment cron runs daily on Alibris but hourly on AbeBooks; Alibris orders are actually dispatched on time but reported late. Fixing the Alibris feed cadence to hourly would lift Alibris SLA into compliance.
- The 7-day recovery path is well-defined. If the bookseller fixes the cron schedule today (01 May 26), the daily SLA contribution flips from 90 to 95% breach rate to 99% on-time tomorrow. The 30-day rolling figure climbs by ~0.4 points/day; back above 95% by 04 May 26 (3 days). Search-rank demotion typically reverses 7 to 14 days after the metric clears.
Sibling cards merchants should reference together
SLA Compliance is the operational vital sign. Pair with these to interpret it:Reconciling against the vendor’s own dashboard
Where to look in the Alibris seller dashboard: Two views matter:- Sellers → Performance Dashboard. The official seller-standing view with the rolling 30-day on-time-dispatch percentage.
- Sellers → Manage Orders → filter by Late. Row-level audit of every late-flagged order with the actual late delta.
Cross-connector reconciliation:
The dispatch-SLA concept exists on every marketplace, but threshold and clock-stopping rules differ. Treat each platform’s number on its own terms.