Amazon ASIN creation notices: brand authorization checks before you appeal

Recent US Seller Forums activity shows sellers discussing ASIN Creation Policy notices tied to Brand Registered products and brand authorization. That is a useful signal, but it should not be treated as proof of a new policy rollout. Treat the notice in front of you as the source of truth.

Amazon's public ASIN guidance already says the ability to create a new product detail page can depend on the seller's relationship with the product, and Brand Registry products may require a Brand Representative or a reseller authorized by the brand. For US and UK sellers, the practical work is to prove the catalog path, the permission path, and the cleanup path separately before another appeal.

Short answer: split the notice into three questions

Before you write anything, classify the notice. The important question is not only whether the goods are real. It is whether this seller had a defensible reason to create, match, edit, or keep this ASIN under this brand and marketplace setup.

• Catalog action: did you create a new ASIN, match an existing ASIN, upload a feed edit, change a brand attribute, or build a variation family?
• Brand permission: were you the brand owner, Brand Representative, authorized reseller, or an approved seller for that brand or category?
• Listing accuracy: was any branded product listed as generic, attached to the wrong product page, or grouped into a misleading variation or multipack?
• Amazon's request: is the notice asking for a Letter of Authorization, invoices, a selling application, listing removal, an acknowledgement, or evidence that there was no violation?
• Business exposure: which ASINs, SKUs, marketplaces, FBA units, open orders, funds, and Account Health records are affected right now?

Build the authorization evidence before you appeal

If Amazon is testing brand authorization, a normal supplier invoice may not be enough by itself. The evidence has to show both product source and permission fit. A seller can have genuine stock and still lack the authority Amazon expects for creating or controlling a branded ASIN.

• Preserve the exact notice, email, Account Health entry, case ID, affected ASINs, SKUs, and the date Amazon gave for deactivation or response.
• Keep a current Letter of Authorization or brand permission record that names the brand, seller entity, marketplace scope, products, and selling or listing rights.
• Use invoices from the brand or an authorized distributor when Amazon asks for source proof, and connect them to the affected ASINs and quantities.
• Save screenshots or exports from Brand Registry roles, Catalog Authorization, View Selling Applications, approval status, and any error such as 5461 if that is what started the issue.
• Map GTIN, brand name, manufacturer, model, product title, and package configuration so the reviewer can see why the ASIN was created or matched correctly.

Separate brand authorization from authenticity and IP

These cases sit close to inauthentic, intellectual-property, product-detail-page, and variation problems. The routes overlap, but the strongest response names the main issue first instead of attaching every document the seller can find.

• Use ASIN Listing Deactivation when the issue is the listing action itself: ASIN creation, page fit, product identity, brand attribute, feed edit, or catalog authorization.
• Use Intellectual Property when a rights owner, protected content, trademark use, patent claim, or withdrawal strategy is the central issue.
• Use Inauthentic Products when Amazon is mainly testing whether the goods are genuine and traceable through a credible supplier chain.
• Use Product Detail Pages Infringement when the product offered does not match the exact page, condition, bundle, model, or package customers saw.
• Use Misuse of ASIN Variations when the problem sits across a parent-child family, review sharing, or a misleading variation structure.

Clean the catalog record without creating a second problem

Rushed cleanup can make the record worse. Changing a branded product to generic, creating replacement ASINs, editing titles to hide a mismatch, or splitting variations without preserving the old state can make Amazon think the seller is still trying to work around the policy.

• Export the current listing, feed, variation, and inventory state before making corrections.
• Close or remove offers that cannot be supported while you investigate, but preserve screenshots and timestamps first.
• Do not relist the same branded product as generic if the product, packaging, or title carries a real brand.
• Do not create a replacement ASIN until you know whether Amazon expected you to match an existing page, apply for approval, or correct the current record.
• If FBA inventory is at risk, document unit count, removal or disposal options, stranded inventory status, and any deactivation deadline before acting.

When this belongs on the ASIN owner route

Most branded-ASIN notices should start on the ASIN Listing Deactivation route because the first job is diagnosis: what happened in the catalog, what permission Amazon expected, and what cleanup is already complete. If the evidence then points to a narrower IP, authenticity, PDP, or variation case, move there honestly instead of forcing one appeal to answer every possible theory.

The practical closing test is whether a reviewer can follow four facts without guessing: the affected ASINs, the catalog action that created the risk, the brand authorization or approval record, and the correction that prevents the same listing path from repeating. If any one of those facts is still weak, return to the ASIN listing owner context before another appeal hardens the wrong theory.