Amazon ASIN crackdown: 30-day deactivation notices

What's happening

On May 21, 2026 a new Seller Central forum thread confirmed what brand owners and resellers have been whispering about all month: Amazon is enforcing its ASIN Creation Policy at a scale sellers have not seen before. Listings flagged in the latest wave will be deactivated within 30 days (Amazon Seller Central forum thread). Nova users with FBA + FBM mix tend to see asymmetric impact here, and that is where the planning work should focus.

The pattern matches earlier reports out of TMARK PRO on May 5 and May 7, which described notices going out across home, beauty and grocery categories for Brand-Generic abuse, duplicate ASINs and variation stuffing (TMARK PRO analysis). Independent updates to listing attributes and enumeration values shipped the same window (Amalert ecosystem feed).

With Prime Day landing in June, a 30-day clock on a hero ASIN is not a back-office problem. It is a revenue problem. This piece walks through what triggers a notice, who is most exposed, and what to fix in the next four weeks.

Key facts at a glance

How we got here

What triggers a deactivation notice

The notices cite the ASIN Creation Policy, but the underlying patterns are catalog-hygiene failures Amazon has tolerated for years and is now actively policing.

A complementary read on parallel listing-integrity work: see the recent listing price rules update, and the May 14 change to how Amazon computes the customer service metric. Same theme: Amazon is rewriting the rules on what a "clean" account looks like.

Who is most exposed

What you should do in the next 30 days

1. 1

   Pull every active ASIN and tag the risk patterns

   Export your catalog. Flag every SKU with brand = "Generic", every parent with more than eight children, and every ASIN created against an existing Brand Registered catalog.

2. 2

   Prioritise by revenue, not by ASIN count

   Fix the flagged ASINs that drove the top 80 percent of trailing 90-day revenue first. A deactivated long-tail SKU is annoying; a deactivated hero ASIN one week before Prime Day is brand-defining.

3. 3

   Break and rebuild variation families

   Where a parent groups unrelated products, split it. Yes, you will lose the inherited reviews on the moved children. Lose them on your schedule rather than on Amazon's deactivation timeline.

4. 4

   Lock the listings you do own

   Use Brand Registry Listing Locks on the hero ASINs you cannot afford to lose to a hijacker edit. If you are not Brand Registered, this is the month to start the application.

5. 5

   Re-validate attribute feeds

   Pull the current enumeration set, re-run your bulk templates, and republish. Stale attribute values are the easiest violation to fix and the easiest one to forget.

How Nova helps

Catalog-hygiene risk is a data problem before it is an Amazon problem. You cannot prioritise fixes until you can see, in one view, which ASINs drive revenue and which ones carry the violation patterns. Products Feed gives you the full catalog with brand, parent, child and BSR fields side by side, so a "Generic" tag on a top-50 hero ASIN jumps out of the table.

Winners and Losers Ranks the deactivation impact: if Amazon pulled the bottom 10 percent of your catalog tomorrow, what is the revenue exposure? And what if it pulled the top 10 percent? Custom Breakdowns lets you slice that same view by brand, parent family or category so a brand manager can fix their portfolio in an afternoon.

For multi-brand operators, Nova for aggregators Rolls catalog risk across acquired portfolios, and Nova for agencies gives operators a per-client catalog hygiene dashboard. For brand owners, Nova for brand managers Ties listing health to P&L impact. The full platform sits behind Amazon analytics tool and Seller Cockpit.