Skip to main content
Metrics type: Key Metrics • Category: Marketplace

​
At a glance

A real-time alert for listings Amazon has suppressed in the last 24 hours, taken them out of search and Buy-Box eligibility so they cannot be found or bought, usually for a missing image, a missing required attribute, a pricing-error flag, or a compliance issue. A suppressed listing is invisible revenue: it still exists, but no customer can reach it. A burst of new suppressions is a fast, silent revenue leak, which is why this is a Key Metrics card watched in real time.

​
Calculation

Calculated automatically from your Amazon Seller Central 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 UK beauty seller on amazon.co.uk runs a bulk price update overnight. Snapshot taken 16 Mar 26 at 07:30.
Four things to notice:
  1. The bulk update caused the burst. Two of the three suppressions share the same reason, a price flagged above Amazon’s reference, right after an overnight price upload. That clustering points straight at the cause: the bulk update pushed prices past the threshold Amazon enforces.
  2. A top earner is dark. ASIN-A is the #3 revenue listing and it is now invisible in search and unbuyable. Until it is fixed, that ASIN earns nothing. This is exactly why a suppression alert is a Key Metrics card, the financial bleed is immediate and silent.
  3. The third suppression has a different cause. ASIN-C lost a required attribute when a template was re-uploaded. Different reason, different fix, supply the missing attribute. Reading the per-listing reason is what turns the count into an action list.
  4. Speed of fix equals revenue recovered. Each hour ASIN-A stays suppressed is lost sales on the #3 ASIN. Correcting the prices and resubmitting clears the suppression quickly; the longer the delay, the larger the loss.
The seller lowers the two flagged prices to within Amazon’s accepted range, re-adds the missing attribute on ASIN-C, and resubmits. The listings come back live and the alert clears.

​
Sibling cards merchants should reference together

A suppression burst is a trigger; these cards give you the standing picture and the catalogue context:

​
Reconciling against Amazon Seller Central

Where to look in Seller Central:
Inventory → Manage Inventory, filter to Suppressed (or use the Fix your products / listing-quality dashboard). Each suppressed listing shows the reason and the action required. This is where you supply missing data or correct prices to lift the suppression.
The suppressed filter shows the standing total; to reconcile new suppressions, look at the ones with the most recent suppression dates, those are what this 24-hour card captures. Timing and reporting-lag table: Why our number may legitimately differ from Seller Central: Cross-connector reconciliation against other connectors the same seller may run:

​
Known limitations / merchant FAQs

What does “suppressed” actually mean? Amazon has hidden the listing from search and made the offer unbuyable until you fix an issue. The listing still exists in your catalogue, but customers cannot find or purchase it. It earns nothing while suppressed. What are the most common suppression triggers? A missing main image or required attribute, a price flagged as too high or too low against Amazon’s reference price, a restricted-keyword or compliance trigger, a category-eligibility change, or an error in a feed or template upload. Why is this a Key Metrics card? Because a suppression is silent and immediate revenue loss. If a top ASIN is suppressed, it sells nothing until fixed, and you may not notice without an alert. A bulk feed error can suppress many listings at once. The real-time, any-suppression-fires framing reflects that urgency. How do I fix a suppressed listing? Open the suppressed-listings view in Seller Central, read the reason per listing, supply the missing data or correct the price, and resubmit. Most suppressions clear within a short window once the issue is resolved. A whole batch got suppressed at once, why? Almost always a bulk action gone wrong, a price update that pushed listings past Amazon’s reference threshold, or a template upload that dropped a required attribute. The shared suppression reason across the batch confirms it. Fix the input that caused it, then resubmit. Does suppression hurt my Account Health? Suppression itself is a catalogue / listing-quality issue rather than a customer-service defect, so it does not directly drive Order Defect Rate. The damage is lost sales and lost search visibility while the listing is dark. The listing shows live now but still counts here, why? Resolution lag. After you fix and resubmit, there can be a short delay before the listing drops out of the suppressed count. It clears on the next refresh once Amazon confirms the listing is republished.

​
Tracked live in Vortex IQ Nerve Centre

New Suppressions (24h) is one of hundreds of KPI pulses Vortex IQ tracks across Amazon Seller Central 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.