Skip to main content
Metrics type: Key Metrics • Category: Marketplace
Rows AbeBooks rejected during inbound processing, surface so the merchant fixes them before next upload.

​
At a glance

Listings AbeBooks accepted into the catalogue with at least one warning (typically ISBN-not-found, condition-code-unknown, missing-binding, or price-format-irregular). Technically live but flagged; high probability of suspension within 24 to 72h unless fixed.

​
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, 38,400 active listings, last 7 days of upload activity to 02 May 26. The card reads 2,153, well above the 5% (~1,500) alert threshold. Five things to notice that are specific to AbeBooks and the book trade:
  1. The 01 May 26 spike to 560 warnings is a single root cause, not 560 problems. Investigation showed 412 of the 560 came from a wholesaler CSV that the bookseller imported overnight; the wholesaler’s “condition” column used “GOOD” / “VERY GOOD” / “FINE” while AbeBooks’s catalogue requires “Good” / “Very Good” / “Fine” with that exact capitalisation. AbeBooks’s import accepted the rows but flagged them with condition-code-unknown. Fixing the case-mapping in the import script and re-uploading cleared 412 of 560 warnings within 12 hours; the remaining 148 were genuine ISBN issues the wholesaler had passed through.
  2. 45% of warnings are ISBN-not-found, and many are pre-1970 books with no ISBN at all. Of the 2,153 warnings, roughly 970 are ISBN-not-found. Of those, about 580 are books the bookseller knows have no ISBN (manuscript editions, antiquarian, ephemera) and the warning is benign, AbeBooks accepts the listing under its own SKU but flags the lack of ISBN. The remaining ~390 are books with an ISBN that AbeBooks’s catalogue lookup didn’t match (often because the ISBN-13 was entered with a typo, or the book is a non-US edition AbeBooks’s catalogue hasn’t indexed). Those 390 are the actionable subset.
  3. Listings in this state convert to suspensions at 40 to 60% within 72h. Of the 2,153 listings currently in this card, the bookseller’s historic conversion rate suggests 860 to 1,290 will move to Suspended unless fixed. That’s directly recoverable revenue tracked on Revenue at Risk (live). The financial cost of leaving the warnings unaddressed is meaningful even though the listings are technically still live.
  4. Cross-marketplace propagation is fast and consistent. Cross-checking Alibris Listings Processed With Errors shows 1,840 warnings on Alibris in the same 7-day window, mostly the same ISBNs as the AbeBooks 2,153. Fixing the upload pipeline once usually fixes both marketplaces; running both fixes separately is wasted effort.
  5. The trend matters more than the level. A bookseller running steady at 1.5 to 2% warnings is operating cleanly. Spikes (like the 01 May 26 jump above) are almost always a script change, a wholesaler change, or a manual data-entry batch from a new staff member. The trend on this card is more diagnostic than the absolute level; cross-check on Top Upload Error Types for the warning-class shift.

​
Sibling cards merchants should reference together

Listings Processed With Errors is the leading indicator. Pair with these to act on it:

​
Reconciling against the vendor’s own dashboard

Where to look in the AbeBooks seller dashboard:
  1. My AbeBooks → Reports → Upload History. Per-batch status with row-level error logs. Compare 7-day total against this card.
  2. My AbeBooks → Inventory → filter Status = Active With Warnings. Row-level view of every flagged listing currently live.
Why our number may legitimately differ from the AbeBooks dashboard: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

A spike on this card; should I worry? Yes, but the right response is diagnostic, not panic. Open Top Upload Error Types and look for a single warning class that grew. Most spikes are one root cause: a script change, a wholesaler-CSV import, a manual data-entry batch from a new staff member. Fix the cause once, the spike clears. Are these listings actually live? Will buyers see them? Yes, all of them are live and discoverable. The warning state means AbeBooks accepted them but is sceptical; they get a search-rank penalty (20 to 35% less weight) and a higher conversion rate to suspension. They sell, just at a lower rate than clean listings. Vendor (AbeBooks) vs commerce-platform (Shopify), why does Shopify not have a warnings card? Because Shopify’s product catalogue is your catalogue; warnings exist only when a third-party catalogue (AbeBooks’s, Alibris’s, Amazon’s) needs to validate your data against its own rules. DTC has no such third party. Are fees affected by this metric? No, fees apply only to actual sales. But warnings reduce listing rank, which reduces sales, which reduces the fees you’d otherwise pay. Indirectly, this card is a leading indicator for revenue (and therefore for the fee bill). Multi-marketplace pricing arbitrage; if I fix the warning on AbeBooks does it fix Alibris too? If the root cause is in your upload pipeline (which it usually is), yes. If the root cause is marketplace-specific (e.g. AbeBooks’s catalogue lookup vs Alibris’s), no. Run the fix once, watch both Alibris Listings Processed With Errors and this card; if both drop, the fix worked. If only one drops, the issue is marketplace-specific and you need a per-marketplace remediation step. Inventory-sync lag; if I deactivate a listing, does it stop being a warning? Yes. Deactivation removes the listing from the active inventory; it stops counting on this card on the next inventory-feed refresh (within 4h). ISBN match quality, what’s the practical fix for ISBN-not-found warnings? Three fixes in order of effort: (1) Auto-validate ISBNs at import time using the ISBNdb or OpenLibrary API; reject rows with invalid ISBNs before they reach AbeBooks. (2) For pre-1970 books with no ISBN, leave the ISBN field blank rather than fabricating one; AbeBooks will accept it under its own SKU. (3) For typo’d ISBNs, use a fuzzy match against the OpenLibrary database to surface the likely correct ISBN; staff confirm. Rare books vs commodity books, do they throw different warnings? Yes, very different. Commodity books almost always throw ISBN-not-found (when the ISBN is wrong) or condition-code-unknown (when the import script’s case-mapping is wrong). Rare books throw binding-missing (when the rare book has no binding info), price-format-irregular (when the rare-book pricing convention “GBP 4,500” trips the strict comma-vs-decimal parser), or ISBN-not-found (because pre-1970 books don’t have ISBNs, this is benign for rare). The mix shifts toward binding-missing as the rare-book share of catalogue rises. Why does today’s number swing so much? Because the card refreshes per upload cycle, not per hour. A daily-upload bookseller will see step-changes once a day; an hourly-upload bookseller will see continuous movement. The 7D rolling view smooths this.

​
Tracked live in Vortex IQ Nerve Centre

Listings Processed With Errors 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.