Mismatched or conflicting data across variation children

Symptoms: broken variant selector, one child listing displaying the wrong image or price. Fix: audit every child listing's attributes for consistency, particularly after a bulk update.

Stale inventory counts

Symptoms: "in stock" showing when you're actually out, or vice versa, usually from a sync delay between your inventory system and the marketplace. Fix: check your feed/integration sync frequency (see Feed Management Fundamentals) and consider more frequent syncs for fast-moving SKUs.

Duplicate listings

Symptoms: the same product appearing under two different listings, splitting reviews and sales history. Fix: identify which listing has more sales/review history and consolidate into it, following the marketplace's specific listing-merge process; prevent recurrence by always checking for an existing listing before creating a new one (see How to Determine Whether a Product Already Exists).

Bulk upload errors

Symptoms: a batch upload partially fails, with some listings updated and others silently unchanged. Fix: always review the upload's error/status report line by line rather than assuming success — most bulk upload tools flag row-level failures that are easy to miss in a large batch.

Category or attribute drift after a marketplace taxonomy update

Symptoms: a previously-fine listing develops a new attribute warning after the marketplace updates its category requirements. Fix: periodically re-audit older listings against current category requirements, especially for older, "set and forget" catalog items.

Broken variation family

Symptoms: a size/color selector missing an expected option, showing the wrong image for a selected variant, or a child listing that appears to have "fallen off" the family entirely. Fix: check every child's variation-defining attribute values for consistency (spelling, exact value match) — see Product Variations, Explained — and confirm each child is still active rather than accidentally deactivated.

Orphaned or zombie listings

Symptoms: an old listing from a discontinued product line still technically live and occasionally selling stale inventory, discovered only during a catalog audit. Fix: run a periodic full-catalog export and reconcile it against your actual current product line, closing out anything genuinely discontinued rather than letting it linger indefinitely.

Attribute or content overwritten by another party

Symptoms: on a shared listing with multiple sellers (see Creating a New Listing vs. Adding an Offer), content you didn't write (a title change, an attribute edit) appears on a listing you're attached to. Fix: on a shared catalog listing, any authorized contributor can typically edit shared content — monitor for unwanted changes and use the marketplace's content-dispute or catalog-correction process where one exists, rather than repeatedly re-editing back and forth.

A general framework for triage

When you notice a catalog error and aren't sure which category it falls into, ask three questions in order: (1) Is this one listing or many? (many points toward a systemic/feed/account cause rather than a one-off content issue). (2) Did anything change recently — a bulk upload, a taxonomy update, an inventory sync — that correlates with when the error appeared? (3) Is this cosmetic (a display glitch) or does it affect buyability (price, inventory, or purchasability)? A buyability-affecting error is always the higher priority regardless of how many listings are involved.

Best practices for catalog health at any scale

  • Schedule a recurring (at minimum quarterly) full-catalog audit rather than only reacting to individual error reports as they surface.
  • Track which error types recur most often in your own catalog — the fix for a chronic issue is usually a process change (stricter feed validation, a pre-upload checklist) rather than repeatedly fixing the same symptom.
  • Keep bulk-upload error reports on file even after a successful re-run, so a later-surfacing issue can be traced back to the specific batch that introduced it.

FAQs

  • How do I tell a listing-level error from an account-level one? If the same type of error appears across many otherwise-unrelated listings at once, treat it as a likely account or feed-level cause (see Feed Management Fundamentals and How to Troubleshoot a Suppressed Listing) rather than debugging each listing individually.
  • Should I fix catalog errors manually or push a corrected feed? For a handful of listings, a manual fix is usually faster; for anything affecting more than a small number of listings, a corrected bulk feed update is generally more reliable and leaves a clearer audit trail than many individual manual edits.