Dispatch SLA Compliance, AbeBooks

Card class: Hero • Category: Marketplace

% of orders dispatched before dispatch_due_by, drives AbeBooks seller standing.

​

At a glance

Percentage of AbeBooks orders dispatched on or before the dispatch_due_by deadline AbeBooks set when the order was confirmed. The single biggest driver of seller standing alongside cancellation rate, and the one buyers see when they choose between two listings of the same ISBN.

​

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

A UK independent bookseller, 1,250 AbeBooks orders in the trailing 30 days, two-business-day handling time, single fulfilment location. Window 02 Apr 26 to 01 May 26. The card reads 95.8%, just above the 95% threshold; no immediate alert. Five things to notice that are specific to AbeBooks and the book trade:

1. The 24h-late tier is where the bookseller is losing margin without seeing it on this card. 38 orders dispatched 1 to 24h late do NOT trigger an SLA breach, but they DO trigger the “estimated delivery may be delayed” message that AbeBooks shows the buyer. That message correlates with a 4x rise in negative feedback for the late orders. The bookseller is sitting at 95.8% SLA but absorbing 38 negative feedback risks per month they could eliminate by shifting handling time from 2 days to 3 days (which would absorb most of that 24h-late tier into the on-time bucket without changing real-world dispatch behaviour).
2. A 14-order >24h-late tail can be dominated by one stockout event. Investigation showed 11 of the 14 came from a single Easter weekend (10 to 13 Apr 26) where two staff were absent and the warehouse-dispatch backlog grew. The remaining 3 were genuine “book turned out to be in worse condition than catalogued” events that should have been cancellations not late-dispatches. Filing the 3 as late-dispatches instead of cancellations cost 0.24 percentage points on this card; filing them as cancellations would have cost 0.24 percentage points on Cancellation Rate instead. Most bookshop ops teams pick the wrong bucket; the AbeBooks penalty is approximately equal either way.
3. AbeBooks’s seller standing tile lags this card by 24 to 48h. The bookseller’s Dashboard → Performance page on 01 May 26 shows 96.4% (ours says 95.8%). The reason is AbeBooks recomputes the dashboard tile once a day around 02:00 EST and includes the seller’s earlier dispatched-on-time orders that hadn’t yet been outbound-confirmed at the time we computed. By 02 May 26 our card matches within 0.1 to 0.2 points. This is normal; trust this card for the most recent 24h.
4. Rare books with 5-day handling are not what’s pulling the bookseller down. The seller’s profile permits 5 business days for orders flagged as “manuscript inspection required” (a small subset, mostly antiquarian). Those orders carry a longer dispatch_due_by and are essentially always on time. The breaches all came from commodity titles where the 2-day default applies; the antiquarian queue is structurally fine.
5. Cross-marketplace consistency matters more than the AbeBooks number alone. The same bookseller’s Alibris SLA Compliance is 91.4% in the same window, well below Alibris’s 95% threshold. The difference is the bookseller’s outbound-confirm cron job runs on a daily AbeBooks feed but a weekly Alibris feed; Alibris orders are actually dispatched on time but reported late. Fixing the Alibris feed cadence to daily would lift Alibris SLA into compliance instantly, with zero operational change.

​

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 AbeBooks seller dashboard: Two views matter:

1. My AbeBooks → Performance Dashboard. The official seller-standing view. AbeBooks publishes the rolling 30-day on-time-dispatch percentage here; this is the number that drives seller standing and search ranking.
2. My AbeBooks → Order History → filter by Late. Row-level audit of every order that was flagged late, with the actual late delta (1h to N days).

Why our number may legitimately differ from the AbeBooks dashboard: Cross-connector reconciliation: The dispatch-SLA concept exists on every marketplace, but the threshold and the clock-stopping rules differ. Treat each platform’s number on its own terms.

---

​

Known limitations / merchant FAQs

My SLA dropped to 92% and AbeBooks 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; this stops the bleeding. (2) Audit Top Upload Error Types for outbound-confirm failures, a broken upload cron job is the single most common cause of false-late readings, especially after a server move or credential rotation. (3) Extend your handling time from 2 to 3 business days in the seller profile if the workload genuinely outgrew your capacity; this absorbs the 1-to-24h late tail into the on-time bucket. Once SLA recovers above 95%, the search-rank demotion typically reverses within 7 to 14 days. Why does this card differ from AbeBooks’s own seller-standing percentage? AbeBooks recomputes once daily (around 02:00 EST); we recompute every 4 hours. For the most recent 24 to 48h our number is more current. 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, your dispatches are happening on time but the confirm-shipment event reaches AbeBooks late, so AbeBooks counts them as late. Run outbound-confirms hourly to fix this. Vendor (AbeBooks) vs commerce-platform (Shopify), why doesn’t Shopify have a dispatch SLA card? Because the contract is different. Shopify is your DTC site; you set the shipping promise; the buyer accepts it; if you miss it, the buyer is unhappy but there’s no third party imposing a threshold. AbeBooks is a marketplace; AbeBooks sets the buyer’s expectation, AbeBooks owns the buyer relationship, AbeBooks penalises you for missing the deadline they set. Marketplace-side dispatch SLAs are categorically different from DTC-side shipping promises and require different operational discipline. Are fees deducted from this calculation? Does payout timing matter? Neither, this is a count-based ratio of on-time orders to total dispatched orders. No fees, no money, no FX. The relationship to fees is indirect: SLA breaches that drop you below 95% trigger a search-rank demotion that reduces revenue (and therefore reduces fees paid to AbeBooks); AbeBooks doesn’t directly fine the seller for SLA breaches. My multi-marketplace pricing arbitrage strategy means I sometimes cancel AbeBooks orders to ship them via Alibris instead. Does that hurt this card? Cancellations don’t hit this card directly (they’re excluded from the denominator), but they do hit Cancellation Rate, which has 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); AbeBooks closes accounts for repeated patterns of it. Don’t do this. If your Alibris price is genuinely better and you want the order on Alibris, take the listing off AbeBooks proactively, not after the order lands. Inventory-sync lag, the book sold on Alibris 5 minutes before AbeBooks confirmed the order. The AbeBooks order will be a stockout cancellation. Does this hurt SLA? Stockout cancellations sit in Cancellation Rate, not here. They’re excluded from this card’s numerator and denominator. But they do hurt seller standing in a different way: AbeBooks tracks “seller-error cancellation rate” with a 3% threshold; oversold-stock breaches that. The structural fix is real-time inventory sync via a single-source-of-truth platform (Brightpearl, Zoho, custom) pushing to all marketplaces with a per-marketplace sub-second decrement; daily-feed inventory is too slow for fast-moving textbook stock. ISBN match quality, does it affect SLA? Indirectly. ISBN-mismatch flags (where the buyer reports the book they received doesn’t match the ISBN listed) sometimes trigger AbeBooks to ask the seller to refund, which becomes a cancellation, which sits in Cancellation Rate not here. Booksellers with chronic ISBN Coverage issues tend to 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 in the operational margin: rare books are slow-pick (you have to find the book in the rare-book room, double-check condition, package carefully), commodity books are fast-pick (pick from numbered bin, drop in postal mailer). Most booksellers run a single 2-day handling time for both, which works fine for commodity and is tight for rare. Booksellers selling >50% rare typically need 3-business-day handling to hit 95%; AbeBooks lets you set up to 5. Why does today’s number swing so much, and should I worry about a one-day dip to 92%? Yes, today’s number swings, especially on lower-volume booksellers. A bookseller doing 30 orders/day will see this card move 3.3 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 (server outage, vacation forgotten, illness). The alert is calibrated to 30D vsP for exactly this reason.

---

​

Tracked live in Vortex IQ Nerve Centre

Dispatch SLA Compliance is one of hundreds of KPI pulses Vortex IQ tracks across AbeBooks 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.