> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Listings Processed With Errors, AbeBooks > Rows AbeBooks rejected during inbound processing, surface so the merchant fixes them before next upload. How to read it, why it matters, and how to act on... **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) > 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. | | | | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `COUNT(rows WHERE last_upload_status = "processed_with_warnings")` over the trailing 7 days of upload cycles. The error-class field is preserved per row in the response file. | | **API endpoint + report** | AbeBooks Outbound Confirmation feed (response file from inventory upload). Each row in the upload returns one of three statuses: `accepted`, `processed_with_warnings`, `rejected`. This card counts the middle bucket; [Top Upload Error Types](/nerve-centre/kpi-cards/abebooks/top-upload-error-types) breaks the same data down by warning class. | | **Listing-quality impact** | **Direct, leading.** Listings in this state generate roughly 20 to 35% less search-rank weight than clean-accept peers, and convert to suspensions at 40 to 60% within 72h. The card is the early-warning indicator for [Suspended Listings](/nerve-centre/kpi-cards/abebooks/suspended-pending-listings). | | **Fees / commission** | Not applicable. | | **Refunds** | Not applicable. | | **Cancellations** | Not applicable. | | **Currency** | Not applicable (count metric). | | **Common warning classes** | ISBN-not-found (\~45% of warnings), condition-code-unknown (\~22%), binding-missing (\~14%), price-format-irregular (\~8%), other (\~11%). The breakdown moves slowly; a sudden shift in the mix usually means a script change in the bookseller's upload pipeline. | | **Multi-marketplace overlap** | Listings with warnings on AbeBooks usually also throw warnings on Alibris and often on Amazon Books too. Same root cause; cross-check [Alibris Listings Processed With Errors](/nerve-centre/kpi-cards/alibris/listings-processed-with-errors). | | **Time window** | `7D` (trailing). Long enough to absorb daily-upload cycles, short enough to drive operational action. | | **Alert trigger** | `>0`, in practice the bookseller-tolerable level is 1 to 2% of total listings. | | **Sentiment key** | `missing_attrs` | | **Roles** | owner, operations | ## 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. | Day | Listings uploaded | Clean | Warnings | Rejected | | ---------------------------------------------- | ----------------- | ----------------- | --------- | -------- | | 26 Apr 26 | 4,180 | 3,940 | 220 | 20 | | 27 Apr 26 | 4,290 | 4,020 | 248 | 22 | | 28 Apr 26 | 4,150 | 3,890 | 245 | 15 | | 29 Apr 26 | 4,310 | 4,055 | 235 | 20 | | 30 Apr 26 | 4,225 | 3,970 | 240 | 15 | | 01 May 26 | 4,380 | 3,800 | 560 | 20 | | 02 May 26 | 4,260 | 3,840 | 405 | 15 | | **7D total** | **29,795** | **27,515** | **2,153** | **127** | | **Listings Processed With Errors (this card)** | **2,153** | (7.2% of uploads) | | | 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)](/nerve-centre/kpi-cards/abebooks/revenue-at-risk). 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](/nerve-centre/kpi-cards/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](/nerve-centre/kpi-cards/abebooks/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: | Card | Why pair it with Listings Processed With Errors | | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Top Upload Error Types](/nerve-centre/kpi-cards/abebooks/top-upload-error-types) | The breakdown by warning class. Tells you which 1 to 3 root causes drive most warnings. | | [Suspended Listings](/nerve-centre/kpi-cards/abebooks/suspended-pending-listings) | The downstream effect. 40 to 60% of warnings convert to suspensions within 72h if unaddressed. | | [Failed Batches (7d)](/nerve-centre/kpi-cards/abebooks/failed-batches) | Adjacent metric. Failed batches are uploads that crashed entirely; warnings are uploads that succeeded with caveats. Together they describe upload-pipeline health. | | [Revenue at Risk (live)](/nerve-centre/kpi-cards/abebooks/revenue-at-risk) | The financial size of the problem. Each warning is a potential listing-suspension worth £5 to £40 of next-30D revenue depending on velocity. | | [ISBN Coverage](/nerve-centre/kpi-cards/abebooks/isbn-coverage) | Lifetime view of ISBN data quality. Listings without ISBN throw warnings here on every upload cycle. | | [Listing Quality Score](/nerve-centre/kpi-cards/abebooks/listing-quality-score) | The composite quality view AbeBooks computes. Warnings here drag this down; clean uploads pull it up. | | [Alibris Listings Processed With Errors](/nerve-centre/kpi-cards/alibris/listings-processed-with-errors) | Same root-cause behaviour on the peer marketplace. Usually correlates 0.7 to 0.9 with this card. | ## Reconciling against the vendor's own dashboard **Where to look in the AbeBooks seller dashboard:** 1. [**My AbeBooks → Reports → Upload History**](https://www.abebooks.com/dashboard). Per-batch status with row-level error logs. Compare 7-day total against this card. 2. [**My AbeBooks → Inventory → filter Status = Active With Warnings**](https://www.abebooks.com/books/inventory). Row-level view of every flagged listing currently live. **Why our number may legitimately differ from the AbeBooks dashboard:** | Reason | Direction | Why | | ----------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Trailing-window drift** | Either | We use rolling 7D from current UTC time; AbeBooks's Upload History is calendar-week. Boundary days drift the count by 100 to 400 listings on a typical bookseller. | | **Re-upload deduplication** | Ours lower | If the same listing throws warnings on Monday's upload and the bookseller fixes-and-reuploads it Wednesday cleanly, our card counts only the latest state (clean). AbeBooks's history view shows both events. | | **Warning-vs-error classification** | Tiny | A handful of edge-case warnings get re-classified as errors (or vice versa) when AbeBooks updates its catalogue rules. Rare; typically \<0.1% of rows. | **Cross-connector reconciliation:** | Card | Expected relationship | What causes legitimate divergence | | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | [`alibris.al_processed_with_errors`](/nerve-centre/kpi-cards/alibris/listings-processed-with-errors) | Strongly correlated; same root causes. | Alibris's catalogue is slightly stricter on edition matching; expect Alibris to throw 5 to 15% more warnings than AbeBooks on the same upload. | | [`amazon.amzn_listings_suppressed_count`](/nerve-centre/kpi-cards/amazon/suppressed-listings) | Different metric (Amazon goes straight from upload to suppression for many issues). | Amazon's Books category is gated and rejects more aggressively; upload warnings on AbeBooks may already be suppressions on Amazon. | ***
Marketplace-peer documentation cross-reference (for booksellers on multiple marketplaces) The "processed with warnings" concept maps roughly across marketplaces but with different terminology and thresholds. AbeBooks and Alibris are similar; Amazon's equivalent (Listing Quality Issues / Suppressions) is harsher. * [`alibris.al_processed_with_errors`](/nerve-centre/kpi-cards/alibris/listings-processed-with-errors) * [`amazon.amzn_listings_suppressed_count`](/nerve-centre/kpi-cards/amazon/suppressed-listings)
## 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](/nerve-centre/kpi-cards/abebooks/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](/nerve-centre/kpi-cards/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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.