Suppressed Listings on Amazon: The Three States Amazon's Own Data Model Tracks (2026)

Amazon does not track a single “suppressed” condition. Its own listings data model tracks two independent flags — whether shoppers can buy the item and whether shoppers can see it — plus a separate list of issues that may or may not have triggered an enforcement action. So a listing can be buyable but invisible in search, visible but unbuyable, or live and still carrying open warnings. Most guides on suppressed listings on Amazon collapse that into one word and one fix, which is why a seller can read three of them and still not know which problem they have.

This guide reads the states out of the place Amazon publishes them: the Selling Partner API listings model in Amazon’s own public repository.

The Short Answer: Three States, Not One “Suppression”

Amazon’s listings data model gives every listing a status array that can contain BUYABLE, DISCOVERABLE, both, or neither, and a separate issues array where each issue carries a severity of ERROR, WARNING, or INFO (Amazon, listingsItems_2021-08-01.json, checked 2026-08-21). The three states sellers run into map onto that structure directly:

1. Non-buyable — BUYABLE is absent. The offer cannot be purchased. This is what sellers usually call an inactive listing.
2. Non-discoverable — DISCOVERABLE is absent while BUYABLE is present. The item can still be bought, but it is hidden from search results. This is search suppression.
3. Live with open issues — both flags present, but the issues array is not empty. Nothing is taken down yet; Amazon has flagged something for review.

The flags are independent. Fixing the wrong one costs days, because the field that is actually missing never changes.

Where These Terms Come From, and What This Guide Won’t Do

Amazon publishes the Selling Partner API models as open source on GitHub. The listings model file listingsItems_2021-08-01.json is the machine-readable definition of what Amazon stores about a listing, and it is readable without a seller account. Two notification schemas in the same repository — ListingsItemStatusChangeNotification.json and ListingsItemIssuesChangeNotification_2023-12-13.json — define what Amazon pushes to sellers when those values change. All three were retrieved and read on 2026-08-21.

The seller-facing vocabulary comes from Amazon’s public seller site, which names the Seller Central location in its own words: “In the main menu, hover over Inventory, then select Manage All Inventory. Select the tab for Search Suppressed and Inactive Listings. From here you can select Incomplete listings, then look for matching conflicts,” and adds that “You can also use the Fix Your Products tool in Seller Central to resolve attribute errors” (sell.amazon.com, checked 2026-08-21).

Scope limits, stated up front. The Seller Central help articles that would describe each screen sit behind a login — checked 2026-08-21, those URLs return an empty shell or redirect to a sign-in wall. This guide therefore describes which field holds which answer, quoting Amazon’s own definitions. It does not walk through screen paths beyond the one Amazon states publicly above, and carries no Seller Central screenshots.

State 1: Non-Buyable — the Listing Is Inactive

BUYABLE is defined by Amazon as: “The listings item can be purchased by shoppers. This status does not apply to vendor listings.” The status notification schema is blunter about the inverse — “When provided, the listings item is buyable. When omitted, the listings item is non-buyable” — and states the general rule that “The absence of a value indicates the status state is not currently applicable to the listings item” (Amazon, ListingsItemStatusChangeNotification.json, checked 2026-08-21).

Two of Amazon’s four named enforcement actions remove buyability, and they are not the same event:

• LISTING_SUPPRESSED — “This enforcement takes down the current listing item’s buyability.” This hits your SKU. Other sellers on the same ASIN are unaffected.
• CATALOG_ITEM_REMOVED — “This catalog item is inactive on Amazon, and all offers against it in the applicable Amazon store are non-buyable.” This hits the ASIN, and every offer against it goes down with it.

That distinction is the fastest diagnostic here. If the page still sells from another seller and only your offer is gone, the action is SKU-level. If no buyable offer remains at all, the catalog item itself was taken down, and editing your SKU attributes will not bring it back.

Note what is not on the list: losing the Featured Offer. A listing with no Featured Offer is still BUYABLE — shoppers reach it through the other-sellers list instead of the main button. That is a merchandising outcome, not a suppression, and it runs on a different set of rules covered in Featured Offer eligibility.

State 2: Buyable but Non-Discoverable — Search Suppression

DISCOVERABLE is defined as “The listings item is visible to shoppers.” The notification schema adds the inverse: “When omitted, the listings item is non-discoverable.” The matching enforcement action is SEARCH_SUPPRESSED, which Amazon describes as: “This value indicates that the catalog item is hidden from search results” (Amazon, listingsItems_2021-08-01.json, checked 2026-08-21).

Read those two sentences together and the defining property of state 2 falls out: the offer is still live and still sellable — it just cannot be found by searching. A direct URL or a saved link still works. Existing repeat customers and any traffic you send from ads or off-Amazon keep converting. Organic discovery goes to zero.

This is why search suppression is diagnosed late so often. Sales do not stop; they decay. A seller watching order count sees a slow bleed rather than a cliff, and by the time it is obvious the listing has lost weeks of ranking history.

Note also whose object is hidden. Amazon’s wording makes the catalog item the thing hidden, not your offer — the same framing it uses for CATALOG_ITEM_REMOVED, and unlike the SKU-scoped wording of LISTING_SUPPRESSED. Treat search suppression as ASIN-level unless your own data says otherwise.

State 3: Live With Open Issues — ERROR vs WARNING

Every issue Amazon records against a listing carries a severity, and Amazon defines the three values as follows (listingsItems_2021-08-01.json, checked 2026-08-21):

The line to internalise: severity describes what happened to your submission, not what happened to your listing. An ERROR means the change you sent was rejected, so the listing still runs on its previous values. A WARNING means the change went through and still needs a look.

Whether a listing is taken down sits in a different field. Each issue can hold an enforcements object containing an exemption status of EXEMPT, EXEMPT_UNTIL_EXPIRY_DATE, or NOT_EXEMPT. Amazon is explicit about the last one: when the status is NOT_EXEMPT, “it signifies that Amazon has already taken the specified enforcement actions.” EXEMPT is the opposite — Amazon “acknowledges the existence of enforcement actions but ensures the user that these actions are not applied to the listing.”

An open issue that lists an enforcement action but is marked EXEMPT is therefore a live listing carrying a defused problem — and when that exemption expires, the action lands on a day nothing was edited.

Amazon also publishes what each issue is about. The category values include MISSING_ATTRIBUTE, INVALID_ATTRIBUTE, MISSING_IMAGE, INVALID_IMAGE, MISSING_PRICE, INVALID_PRICE, DUPLICATE, and QUALIFICATION_REQUIRED — plus PRODUCT and LISTING, which exist only to say whether the issue attaches to the ASIN or to your SKU.

The Four Enforcement Actions Amazon Names

These four values, quoted verbatim from Amazon’s model, are the complete published list. Any cause taxonomy you read elsewhere resolves into one of them.

ATTRIBUTE_SUPPRESSED is the most misread of the four. It does not take the listing down — it rejects one field. The listing stays buyable and discoverable while running without the bullet, value, or image you submitted, which is how a listing can be “fine” and underperforming at once. If your detail page looks oddly incomplete but sells normally, check this first, then listing optimization.

How to Tell Which State You’re In

You can reach the answer from public behaviour, before any dashboard.

The exact-title test is the cheapest of these: paste the full product title into Amazon’s search box in a logged-out browser. A listing that buys fine by direct link and is absent from an exact-title search is non-discoverable, and no amount of price or inventory work changes that. To run the sweep across a catalogue rather than one ASIN at a time, see Amazon listing analyzer tools.

The Fourth Case: You Were Never Eligible to List It

One situation looks like suppression and is not: the listing was never allowed to exist. Amazon publishes this separately in the Listings Restrictions model, with three reason codes (listingsRestrictions_2021-08-01.json, checked 2026-08-21):

• APPROVAL_REQUIRED — “Approval is required to create a listing for the specified ASIN. A path forward link will be provided that may allow Selling Partners to remove the restriction.”
• NOT_ELIGIBLE — “Not eligible to create a listing for the specified ASIN. No path forward link will be provided to remove the restriction.”
• ASIN_NOT_FOUND — “The specified ASIN does not exist in the requested marketplace.”

The difference is in the second half of each sentence: APPROVAL_REQUIRED comes with a route out, NOT_ELIGIBLE explicitly does not. Appealing a NOT_ELIGIBLE restriction spends time Amazon has already said will not produce a path forward.

Common Mistakes

• Treating “suppressed” as one problem. Buyability and discoverability are separate flags. Restoring stock fixes neither if the missing flag is DISCOVERABLE.
• Fixing your SKU when the ASIN was removed. If no seller has a buyable offer, the enforcement is CATALOG_ITEM_REMOVED and your attributes were never the cause.
• Reading ERROR as “my listing is down.” Amazon defines severity in terms of the submission, not the listing. An ERROR means your edit did not apply.
• Assuming a fix is instant. Sellers posting in Amazon’s public Seller Forums describe suppression alerts persisting for a day or more after the attribute is corrected, some citing a roughly 48-hour wait from Seller Support. That is a seller-community observation, not an Amazon-published figure — no timing commitment appears in any model or public page checked on 2026-08-21.
• Trusting cause lists with no source. The familiar main-image / category / prohibited-keywords / duplicate-ASIN list circulates across seller blogs (observed 2026-08-21) and broadly matches Amazon’s published issue categories, but Amazon publishes no ranked list of suppression causes. Use the categories it does publish.

Frequently Asked Questions

Is a suppressed listing the same as an inactive listing?

No. Amazon’s own tab name puts them side by side — “Search Suppressed and Inactive Listings” (sell.amazon.com, checked 2026-08-21) — because they are two conditions. Inactive means non-buyable: BUYABLE is gone. Search suppressed means non-discoverable: BUYABLE remains, DISCOVERABLE is gone.

Can shoppers still buy a search-suppressed listing through a direct link?

Yes, provided the listing is still BUYABLE. SEARCH_SUPPRESSED is defined only as the catalog item being “hidden from search results” and does not touch buyability. Ad traffic and saved links keep converting, which is why the problem gets noticed late.

Do WARNING-level issues take a listing down?

Not by themselves. Amazon defines WARNING as an issue that “has not prevented the submission from processing.” What takes a listing down is an enforcement action recorded against the issue with an exemption status of NOT_EXEMPT.

Is this the same thing as stranded inventory?

No — stranded inventory is the fulfilment side of the same symptom: units sit in Amazon’s network with no listing to sell them against, whereas here the listing itself is in the wrong state. Causes and fixes differ, and are handled in Amazon stranded inventory.

Does a suppressed listing affect my Account Health Rating?

Nothing in the sources checked on 2026-08-21 connects a listing state to an account score — the listings model carries no account-level field. Listing states attach to a SKU or ASIN; the score described in Amazon Account Health Rating attaches to the account. Amazon publishes no link between them, so do not assume one.

Conclusion

Generic advice on suppressed listings on Amazon fails because it answers a question Amazon does not ask. Amazon stores no field called “suppressed.” It stores whether the item is BUYABLE, whether it is DISCOVERABLE, which issues are open at what severity, and which of four named enforcement actions has been applied — and whether an exemption is holding it off.

Diagnose in that order: establish which flag is missing before touching anything, find the enforcement action that removes that flag, then fix the attribute the issue names. Every source above is readable without a seller account, so the question can be settled before you open Seller Central.