Listing hygiene: the monthly audit that finds sales you are already losing
Suppressed listings, inactive offers, orphaned SKUs, and quiet attribute edits cost sales without triggering any alarm. Here is a monthly checklist to catch them.
September 29, 2026 · 6 min read
Most catalog problems on Amazon do not announce themselves. A listing gets suppressed because an image no longer meets a style rule, an offer goes inactive because a price tripped a guardrail, a child variation detaches from its parent after a catalog merge. Nothing emails you in a way you notice. Sales on that SKU just get softer, and the easy explanation is seasonality or competition.
Listing hygiene is the boring habit of checking, on a fixed schedule, that every SKU you think is for sale is actually for sale, looks the way you set it up, and is attached to the right detail page. It takes an hour a month once you have a routine. Here is the routine.
Start with a single list of what should be live
You cannot audit against nothing. Before you look at Seller Central, write down (or export from your own records) every SKU you intend to be selling right now, with its ASIN, its fulfillment channel, and the price range you consider normal. This is your baseline. Most sellers skip it and end up auditing Amazon's view of the catalog against Amazon's view of the catalog, which finds nothing.
Then pull an active listings report and an inactive listings report and compare them against your baseline. Every SKU lands in one of four buckets: live and correct, live but wrong, not live, or live and not on your list at all. The last two buckets are where the money is.
Suppressed and inactive: the listings that are silently off
A suppressed listing is not searchable even though you may still have inventory for it. The usual causes are missing or non-compliant attributes: a main image that fails the requirements, a title that is too long or contains restricted characters, a missing required field for the category, or a condition note problem. An inactive offer is different: the listing may exist, but your offer is not available to buy, often because of a pricing error flag, an out-of-stock state that never recovered, or an account-level hold on that SKU.
Both states hurt more for FBA sellers, because the inventory keeps sitting in a fulfillment center accruing storage while it cannot sell. If you have ever found stranded inventory, you already know the pattern: the unit is fine, the listing is the problem.
- Check the suppressed and inactive views in your inventory screen, not just the dashboard alerts, which are easy to dismiss and do not persist.
- For each one, record the reason Amazon gives and the date you first saw it. Reasons change, and a SKU that keeps getting suppressed for the same attribute usually has a template or feed problem upstream.
- Fix the root cause in the source you actually edit from (your flat file, your listing tool, or the Seller Central form) so the next feed upload does not undo the fix.
Live but wrong: attribute drift
Amazon's catalog is shared. Other sellers on the same ASIN, brand registry contributions, and Amazon's own data pipeline can all change what shoppers see. Titles get rewritten, bullet points reorder, the main image swaps, the item weight or dimensions change. Some of these edits are harmless. Some quietly move your product into a different size tier, change which browse node it sits in, or replace your best image with a worse one.
The fix is a snapshot habit. Once a month, capture the title, main image, bullets, category, and listed dimensions for your top SKUs and compare them against last month's snapshot. You are looking for changes you did not make. When you find one, decide whether it matters, and if it does, correct it through the proper channel: a listing update if you own the content, or a catalog or brand support case if you do not.
- Dimension or weight changes are the expensive ones: they can change the fulfillment fee on every unit sold. Compare the fee you were charged on recent orders against the fee you expect.
- Category changes can change the referral fee rate and whether the listing shows up where shoppers browse.
- Main image changes affect click-through before they affect anything else. If sessions hold steady but orders drop, look at the image first.
Variation families that fell apart
Parent-child variations concentrate reviews and make it easy for a shopper to switch size or color without leaving the page. When a child detaches, it becomes a standalone listing with fewer reviews, weaker ranking, and a detail page most shoppers never find. It still technically sells, which is why it goes unnoticed.
During the audit, open each parent ASIN and confirm every child you expect is present and selectable. A missing child is usually a variation theme mismatch or a missing attribute value on the child. Fixing it is often a one-field correction, but you only find it by looking.
Orphans and duplicates
Over time, most catalogs accumulate SKUs nobody remembers creating: an old FBA SKU from before a relabel, a test listing, a merchant-fulfilled duplicate of an FBA offer, a bundle that was discontinued but never closed. These are not just clutter. Duplicate SKUs on the same ASIN can split inventory and sales history, confuse replenishment, and make your own reports disagree with each other.
For each SKU that is live but not on your baseline, decide: adopt it into the baseline, close it, or merge its inventory into the SKU you actually use. Write down the decision so the same SKU does not show up as a mystery next month.
Prices and quantities that make no sense
The last pass is a sanity check on numbers. Sort live offers by price and look at both ends. A price far below your normal range may be a repricer misfire or a typo that is selling units at a loss; a price far above may have tripped a pricing flag that made the offer inactive or cost you the Buy Box. Do the same for quantities: an FBA SKU showing available units but no sales for weeks is worth a closer look, as is a merchant-fulfilled SKU showing stock you no longer have.
None of these checks are clever. Their value comes entirely from doing them on a schedule, so a problem is found in weeks instead of months.
A one-hour monthly routine
- Update your baseline list of SKUs that should be live.
- Compare active and inactive listings reports against it; sort every SKU into live-correct, live-wrong, not-live, or unknown.
- Work the suppressed and inactive list: reason, date first seen, root-cause fix.
- Compare this month's snapshot of titles, images, categories, and dimensions against last month's for your top SKUs.
- Open each parent ASIN and confirm every child is attached.
- Adopt, close, or merge every orphan SKU.
- Scan both ends of price and quantity for outliers.
- Log what you changed and why, one line per SKU.
Where MySellerHQ fits
MySellerHQ reads your listings, inventory, orders, and fees from Amazon's Selling Partner API with read-only permissions. That makes the tedious half of this routine automatic: it can show which SKUs are inactive or stuck, flag stock that is sitting without sales, and line up the fee actually charged per SKU against what you expect, so a dimension or size-tier change surfaces instead of hiding in a settlement report.
It does not edit listings, change prices, or open cases for you; writes are off by design. The decisions and the fixes stay with you. The point is to spend your hour fixing problems rather than hunting for them.