Key takeaways
- Only brand owners and authorized sellers can create new ASINs on Amazon in 2026.
- Amazon now uses automated detection to enforce ASIN creation rules, issuing 30-day deactivation notices.
- Common triggers include 'Generic' brand fields, duplicate ASINs, and unrelated product variations.
- FBA inventory can be stranded or disposed of if a listing deactivates before removal orders are placed.
- Review your inventory for catalog issues before Q4 to avoid costly disruptions.
Who can create an ASIN on Amazon has a narrower answer in 2026 than it had two years ago: the brand owner, and sellers who can document the brand's authorization. Amazon now enforces that with automated catalog detection, and for most sellers the first sign is a deactivation notice with a thirty-day clock attached. The notice cites the Seller Code of Conduct, names the ASIN, and gives you until the window closes to produce authorization or correct the record.
Sellers began reporting these notices in a Seller Central forum thread in May 2026, concentrated first in home, beauty and grocery. The rules themselves are old. What changed is that detection no longer waits for a brand to complain.
Who can create an ASIN on Amazon, and who cannot
The short version: brand owners enrolled in Brand Registry, and sellers who hold documented permission from them. Everyone else is expected to add an offer to the detail page that already exists rather than build a new one.
That has been the written rule for years. What is new is that it is now checked by machine rather than by complaint, so a listing created in 2021 is as visible as one created last week.
What triggers a notice about how the ASIN was created
Three patterns cover most of what sellers report:
- Generic in the brand field. The ASIN was created with Generic as the brand for a product that belongs to a registered brand.
- Duplicate ASINs. A second detail page for a product that already has one on a Brand Registry enrolled catalog.
- Variation stuffing. Unrelated products grouped under one parent so the children inherit reviews and ranking.
Amazon's ASIN creation documentation has described all three for years.
What clears the thirty-day window
Sellers who kept their listings report two documents doing the work: a letter of authorization from the brand, or invoices from an authorized distributor covering the product. Neither is something you can produce in an afternoon if you have never asked for it, which is the real reason the thirty days matters.
Expect inconsistency. One seller in that thread submitted identical documentation across thirty listings of the same brand and reported twenty-one reinstated and eleven denied. Budget for a second submission.
The cost nobody plans for: your FBA units
This is where a catalog problem becomes a cash problem. If the listing deactivates while units are still in the fulfillment center, that inventory is stranded, and it can be disposed of if no removal order was ever created. A deactivation in September takes the ASIN out of Q4 and can take the stock with it.
The order of operations that protects you is the reverse of instinct: create the removal order first, then work the appeal. A removal you did not need costs a removal fee. A disposal you did not expect costs the whole unit.
How to find your exposure before a notice arrives
Pull your inventory report and look for three things, in this order:
- Any SKU where the brand field reads Generic but the product carries someone else's brand.
- Any ASIN you created for a product that already had a detail page.
- Any parent whose children are not genuine variations of each other.
That list is your exposure, and it is worth working through before Q4 rather than during it.
The failure mode is the same one as listing-level deactivation under OTDR: the account stays healthy and the listing goes dark, so nothing in the account health dashboard warns you first. Catalog hygiene has stopped being tidiness and become operational risk, the same way titles over 75 characters and labelling AI-generated images did.
Amazon has not published a dated announcement for this enforcement wave, and the detail above comes from trade coverage of the May 2026 notices and from sellers reporting in the forum. Treat the timing as seller-reported, and verify the specifics of any notice against the message in your own account.
Sources
- Seller Central Forums - Major Policy Shift You Need to Know About (ASIN Creation Crackdown) sellercentral.amazon.com
- Amazon Seller Central - ASIN creation policy (no verificable sin login) sellercentral.amazon.com
- Novadata - Amazon ASIN crackdown: 30-day deactivation notices novadata.io
- SentryKit - Amazon ASIN Creation Crackdown 2026: 30-Day Notices sentrykit.com
