Dispatch SLA Compliance, Alibris

Card class: Hero • Category: Marketplace

% 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:

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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:

1. Sellers → Performance Dashboard. The official seller-standing view with the rolling 30-day on-time-dispatch percentage.
2. Sellers → Manage Orders → filter by Late. Row-level audit of every late-flagged order with the actual late delta.

Why our number may legitimately differ from the Alibris dashboard: 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.

---

​

Known limitations / merchant FAQs

My SLA dropped to 92% and Alibris just demoted my listings. What do I do? Three actions in order: (1) Look at Pending Dispatch right now, drain the queue if anything is sitting past 75% of its budget. (2) Audit Top Upload Error Types for outbound-confirm failures, a broken upload cron is the most common cause of false-late readings. (3) Extend handling time from 2 to 3 business days in the seller profile if workload outgrew capacity. Once SLA recovers above 95%, the search-rank demotion typically reverses within 7 to 14 days. Why does this card differ from Alibris’s own seller-standing percentage? Alibris recomputes once daily (around 02:00 PST); we recompute every 4 hours. By day 3 they match within 0.2 points. If they’re more than 1 point apart over a 30-day window, the cause is usually outbound-confirm latency, dispatches happen on time but the confirm event reaches Alibris late. Run outbound-confirms hourly to fix. Vendor (Alibris) vs commerce-platform (Shopify), why doesn’t Shopify have a dispatch SLA card? Different contract. Shopify is your DTC site; you set the shipping promise; the buyer accepts it; if you miss it, the buyer is unhappy but no third party imposes a threshold. Alibris is a marketplace; Alibris sets the buyer’s expectation, owns the buyer relationship, penalises you for missing the deadline. Marketplace-side dispatch SLAs require different operational discipline than DTC shipping promises. Are fees deducted from this calculation? Does payout timing matter? Neither, this is a count-based ratio. No fees, no money. The relationship to fees is indirect: SLA breaches that drop you below 95% trigger a search-rank demotion that reduces revenue (and therefore commission). Alibris doesn’t directly fine the seller for SLA breaches. Alibris Library Services / institutional buyers, do they affect SLA differently? Yes, importantly. Library buyers often use net-30 terms and have internal procurement rules requiring vendors to maintain 96%+ on-time-dispatch. Falling below 96% can trigger automatic exclusion from library-buyer search filters even though Alibris’s published threshold is 95%. The financial impact of dropping from 96% to 94% is disproportionate because it loses you the high-AOV institutional cohort. Treat 96% as your real internal target if you do meaningful Library Services volume. My multi-marketplace pricing arbitrage means I sometimes cancel Alibris orders to ship via AbeBooks instead. Does that hurt this card? Cancellations don’t hit this card directly (excluded from denominator), but they do hit Cancellation Rate with its own 3% threshold. The arbitrage strategy you’re describing is also a violation of marketplace terms (selling outside the platform after taking the order); Alibris closes accounts for repeat patterns. Don’t do this. Take the listing off Alibris proactively, not after the order lands. Inventory-sync lag, the book sold on AbeBooks 5 minutes before Alibris confirmed the order. Will this hurt SLA? Stockout cancellations sit on Cancellation Rate, not here. Excluded from this card’s numerator and denominator. They hurt seller standing differently: Alibris tracks “seller-error cancellation rate” with a 3% threshold; oversold-stock breaches that. Real-time inventory sync via single-source-of-truth platform is the structural fix. ISBN match quality, does it affect SLA? Indirectly. ISBN-mismatch flags trigger Alibris to ask for refund, becoming a cancellation, hitting Cancellation Rate not here. Booksellers with chronic ISBN Coverage issues have higher cancellation rates and worse seller standing overall, but this card is structurally insulated from ISBN-data quality. Rare books vs commodity books, do they have different SLAs? Same SLA threshold (95%), same clock, same penalty. The difference is operational margin: rare books are slow-pick (find the book in the rare-book room, double-check condition, package carefully), commodity is fast-pick. Most booksellers run a single 2-day handling time for both, which is fine for commodity and tight for rare. Booksellers selling >50% rare typically need 3-business-day handling. Why does today’s number swing so much, and should I worry about a one-day dip to 92%? Today’s number swings, especially on lower-volume booksellers. A bookseller doing 22 orders/day will see this card move 4.5 points per single late dispatch. The 30-day rolling number is the only one to act on; one-day dips below 95% are noise unless you see a structural cause.

---

​

Tracked live in Vortex IQ Nerve Centre

Dispatch SLA Compliance 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.