Skip to main content
Metrics type: Key Metrics • Category: Marketplace
Listings hidden from search until missing attrs are filled, direct revenue blocker.

​
At a glance

Live count of your active ASINs that Amazon has currently suppressed (hidden from search and from Buy Box) for missing required attributes, image policy violations, GTIN failures, or category-specific compliance gaps. A direct, fully-recoverable revenue blocker.

​
Calculation

Calculated automatically from your Amazon (Selling Partner) 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 hybrid Shopify + Amazon hardware brand. 380 active ASINs across amazon.co.uk and amazon.de. Card snapshot at 09:14 BST on 28 Apr 26 reads 8 suppressed listings. Drilling into the per-ASIN reasons: Five things to notice that are specific to Amazon:
  1. Suppression = direct revenue loss, instantly. The 3 GTIN-suppressed ASINs were averaging 28 units/week at £24 ASP = £672/week of lost revenue per ASIN, or £2,016/week combined. The brand had not noticed them suppressed for 9 days before the card alerted, that’s £2,592 of lost revenue that will not come back.
  2. GTINs broke after Amazon tightened validation. On 11 Apr 26 Amazon rolled out stricter GTIN matching against the GS1 database in the home and hardware categories. 3 ASINs that had been live for 18 months were auto-suppressed because the GTINs didn’t match the GS1 record (a comma-separator vs space issue in the supplier feed). The fix was a one-line catalogue update; the cost was 17 days of being invisible.
  3. Image policy is the easiest fix, often the slowest to detect. The 2 image-suppressed ASINs had been flagged by Amazon’s automated image quality checker (image had text overlay, against policy). The fix is a 30-second re-upload of a clean image. The ASINs had been suppressed for 6 days before this card surfaced them, because image-policy suppressions don’t email the seller (unlike compliance ones). This card is the only reliable signal.
  4. Commission erodes the recovery, but suppression dominates. A non-suppressed ASIN at 92% Buy Box loses ~8% of revenue to the offer carousel. A suppressed ASIN loses 100%. Suppressions are an order of magnitude worse than Buy Box loss for the same ASIN. Always clear suppressions before tuning Buy Box.
  5. Brand approval is Amazon-side; you can’t expedite it. The Brand Registry approval suppression on amazon.de is sitting in Amazon’s queue. Sellers report 5 to 21 day turnarounds; nothing you upload changes the timeline. Mark it on the card as “blocked, Amazon-side” and don’t burn cycles on it. Use the Brand Registry Coverage card to track the broader picture.

​
Sibling cards merchants should reference together

Suppression is half of Revenue at Risk (live). Pair it with these to act:

​
Reconciling against the vendor’s own dashboard

Where to look in Amazon Seller Central:
  1. Inventory → Manage Inventory → Suppressed is the canonical view. Filter by Status: Suppressed to see every currently-suppressed ASIN with the reason code.
  2. Catalogue → Listing Quality and Help (formerly Fix Your Listings) groups suppressions by issue type and lets you bulk-fix similar reasons.
  3. Reports → Inventory Reports → Suppressed Listing Report is the downloadable CSV view that mirrors what this card pulls from the Reports API.
Why our number may legitimately differ from Seller Central: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

The card says I have 12 suppressed listings, but Seller Central shows only 9. Which is right? Both are right at different moments. The card refreshes every 30 to 60 minutes via the Listings Items API; Seller Central’s UI is real-time but the Suppressed Listing Report is async and lags 4 to 24 hours. If you’ve recently fixed listings, expect a 30 to 60 minute delay before the card drops the count. If the gap is the other way (card shows fewer), the connector hasn’t yet picked up new suppressions, look again in an hour. A persistent gap >2 hours is worth checking; the most common cause is an SP-API rate-limit backoff during a high-volume catalogue update. My listing is suppressed for “Missing GTIN”, but I provided a GTIN at listing time. Why? Amazon tightened GS1 GTIN validation in mid-2024 and has been progressively rolling out stricter checks across categories ever since. The most common cause is a GTIN that registers in your supplier feed but doesn’t validate against the GS1 database in Amazon’s eyes (typo, transposed digits, brand mismatch). Fix: confirm the GTIN at gs1.org/services/check-digit-calculator, then update via Manage Inventory or the Listings API. Allow 4 to 24 hours for Amazon to re-index. Does this card include “Inactive” listings? No. Suppressed (hidden from search until you fix something) is different from Inactive (stock = 0, you stopped selling). For inactive listings see Listings Inactive. Suppressed is recoverable revenue blocked by a fixable issue; inactive is intentional or out-of-stock. FBA vs FBM, are suppressions different? Slightly. FBM-suppressed inventory just sits on your shelves. FBA-suppressed inventory is doubly painful: you’re paying Amazon storage fees on stock that can’t sell. If you have FBA-suppressed listings, prioritise them, the storage clock is running. See Storage Fees and Long-Term Storage Risk for the cost view. ACOS spiked at the same time as my suppressed count went up. Why? Ad spend on a suppressed ASIN is fully wasted, the click goes to a product page that says “Currently unavailable” and the shopper bounces. Amazon Sponsored Ads doesn’t auto-pause suppressed ASINs (you have to). Result: ad spend continues, attributed sales fall, ACOS spikes. Pair with Ad Spend on Out-of-Stock ASINs for the explicit overlap (the card treats suppression similarly to OOS). Multi-marketplace, my UK listing is fine but the German one is suppressed for the same SKU. How does the card show this? The headline counts each suppressed ASIN-marketplace pair as 1. So a SKU live on UK but suppressed on DE counts as 1 toward the headline; if it were suppressed on both marketplaces it would count as 2. The drill-down splits by marketplace. Suppressions are almost always per-marketplace because each marketplace has its own catalogue rules (DE requires energy-label compliance for some categories, UK doesn’t, etc.). When will the Amazon settlement reflect a fix? Is there a clearance lag? Settlement is unrelated to suppression. Once a listing is unsuppressed, orders flow through the normal 14-day disbursement cycle. The “lag” you’ll feel is in Amazon’s organic ranking: a recently-unsuppressed listing usually returns to its prior search rank in 3 to 7 days, not instantly. Pair with Buy Box Trend to see the recovery curve. Return-window confusion, do return-window issues cause suppressions? Rarely directly, but high return rates can trigger Amazon to flag the ASIN as defective and suppress it under the “Customer-reported defect” reason. Once the ASIN crosses Amazon’s internal defect-rate threshold (typically 2 to 5%) the suppression triggers. Fix: address the defect (product issue, listing accuracy, packaging) and submit a Plan of Action through Seller Central. See ODR (Order Defect Rate) for the relevant trailing metric. Why isn’t the Shopify-Amazon channel app the source of truth here? Most brands don’t run it (it requires managing Amazon listings from inside Shopify, which most don’t). Even brands that do, the channel app reflects Shopify’s view of “what was published” rather than Amazon’s view of “what’s actually live and visible”. Amazon’s SP-API is the source of truth for suppression state; treat the Shopify channel app as a publishing tool only, not a monitoring tool. Why does today’s count fluctuate even when I haven’t changed anything? Two reasons. (1) Amazon runs validation passes on its own schedule; a listing live yesterday can be auto-suppressed overnight when Amazon re-validates GTINs or images against updated rules. (2) The Listings Items API can briefly return stale state during SP-API outages or rate-limit backoffs, the count can dip and then snap back. If the count moves by 1 or 2 with no apparent cause, wait an hour and re-check. If it persists, drill into the per-ASIN view to find the new suppression.

​
Tracked live in Vortex IQ Nerve Centre

Suppressed Listings is one of hundreds of KPI pulses Vortex IQ tracks across Amazon (Selling Partner) 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.