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.
| What it counts | COUNT(listings WHERE status = 'SUPPRESSED') from the SP-API Listings Items API. Each row is one ASIN that exists in your catalogue but is invisible to shoppers. |
| API endpoint + report | SP-API GET /listings/2021-08-01/items per SKU, plus the Suppressed Listings Report (Reports API report type GET_MERCHANT_LISTINGS_DEFECT_DATA) for backfill and reason codes. |
| ASIN vs account scope | Account-level count rendered in the headline, with per-ASIN drill-down by reason (missing GTIN, missing main image, length compliance, category-specific). |
| Buy Box impact | Suppressed = invisible. The ASIN cannot win Buy Box, cannot appear in search, cannot generate organic or paid orders. Direct, total revenue loss for that ASIN until cleared. |
| FBA vs FBM | Both. FBM listings see suppressions slightly more often (Amazon validates less aggressively at intake). FBA-suppressed inventory is doubly painful because you’re paying storage fees for stock that can’t sell. |
| Fees / commission | Not applicable (this is a count). |
| Refunds | Not applicable. |
| Cancellations | Not applicable. |
| Currency | Not applicable. |
| Marketplace dynamics | Suppressions are per-marketplace. A single SKU listed on amazon.co.uk and amazon.de may be suppressed on one and live on the other; the count sums both. |
| Return-window vs refund-window | Not applicable to a state count. |
| Time window | RT (real-time, refresh interval 30 to 60 minutes). |
| Alert trigger | >0, the card is designed to be quiet at zero. Any suppression deserves attention. |
| Sentiment key | missing_attrs. |
| Roles | owner, operations, marketing. |
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:| Reason code | ASINs | Marketplace | Severity | Typical fix time |
|---|---|---|---|---|
| Missing GTIN / EAN | 3 | UK + DE | High (catalogue blocker) | 4 to 24 hours |
| Main image policy violation | 2 | UK | Medium | 30 minutes (re-upload) |
| Listing length compliance | 1 | DE | Low | 15 minutes (edit title / bullets) |
| Hazmat documentation missing | 1 | UK | High (compliance) | 3 to 7 days |
| Brand approval pending | 1 | DE | High (locked) | 5 to 21 days (Amazon-side) |
| Total live | 8 ASINs |
- 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.
- 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.
- 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.
- 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.
- 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:| Card | Why pair it with Suppressed Listings |
|---|---|
| Revenue at Risk (live) | Translates this count into a £/month figure. The suppression term is usually the larger half. |
| New Suppressions (24h) | Burst alert for new suppressions in the last 24h. Fixes here are time-sensitive; act fast. |
| Suppressions Detail | The per-ASIN drill-down with reason codes. |
| Listings Total | Denominator for the suppression-rate calculation (suppressed ÷ total). >5% is a structural problem. |
| Catalogue Drift vs DTC | Drift between Amazon and DTC product data often correlates with suppressions (price or attribute changed on DTC, didn’t sync to Amazon). |
| Brand Registry Coverage | Brand Registry-related suppressions (e.g. brand approval pending) live here. |
| Account Health Status | Account-health flags can trigger broad suppression cascades. |
| Shopify Total Revenue | DTC counterpart for hybrid brands. Shopify has no suppression concept; you control the storefront entirely. |
Reconciling against the vendor’s own dashboard
Where to look in Amazon Seller Central:- Inventory → Manage Inventory → Suppressed is the canonical view. Filter by Status: Suppressed to see every currently-suppressed ASIN with the reason code.
- Catalogue → Listing Quality and Help (formerly Fix Your Listings) groups suppressions by issue type and lets you bulk-fix similar reasons.
- Reports → Inventory Reports → Suppressed Listing Report is the downloadable CSV view that mirrors what this card pulls from the Reports API.
| Reason | Direction | Why |
|---|---|---|
| Time zone | None at the live state level | Suppression is a state, not a windowed metric, so timezone doesn’t apply directly. The Suppressed Listing Report itself is generated on Pacific Time stamps. |
| Settlement-period lag | Not applicable | Suppression is unrelated to disbursement timing. |
| API rate limits | Ours can lag by 30 to 60 minutes | The Listings Items API is throttled. The connector polls every 30 to 60 minutes per marketplace, so a freshly-cleared suppression may still show on this card for up to an hour. |
| Reports API generation latency | Either | The downloadable Suppressed Listing Report has a 4 to 24 hour generation delay on first request. Our card uses the most recent successful pull, which can be either ahead of or behind the Seller Central UI depending on cache state. |
| Per-marketplace state | Equivalent | The Seller Central UI defaults to one marketplace at a time; our card aggregates across every marketplace tied to your seller account. To match, switch the marketplace selector in Seller Central and sum manually. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
shopify.total_revenue | No relationship. | Shopify has no suppression concept. The DTC analogue is “products with broken images / missing prices” surfaced in different cards. |
bigcommerce.total_revenue | No relationship. | Same as Shopify. |
amazon_ads.aads_acos | Indirect: ad spend on suppressed ASINs is fully wasted (the listing isn’t visible). | Use Ad Spend on OOS ASINs for the explicit overlap. |
shipbob.fulfilment_rate | None directly | ShipBob handles FBM fulfilment; suppressions are catalogue-side and unrelated. |