What does Amazon error 5461 mean?

Error 5461 means you don't have permission to create a new ASIN for that brand. It fires when the brand name on your submission is enrolled in Brand Registry (or matches a brand with existing catalog protection) and your GTIN isn't registered to that brand in the GS1 database.

What does Amazon error 8541 mean?

Error 8541 is a matching conflict. An attribute you submitted, usually the UPC, EAN, title, brand, manufacturer, or model number, does not match what Amazon already has on file and published for that ASIN.

What does Amazon error 8572 mean?

Error 8572 means the UPC, EAN, ISBN, or JAN code you submitted does not match the product in Amazon's records, verified against the GS1 database. It usually means the code is already assigned to a different product, isn't GS1-registered, or was bought from a reseller instead of issued directly by GS1.

What does Amazon error 5665 mean?

Error 5665 means Amazon hasn't approved you to sell under that brand name yet. It appears on both registered and unregistered brands and blocks listing creation until you complete brand approval.

Can I still sell while one of these errors is open?

Usually yes, on existing ASINs. All four codes block creating a new ASIN or publishing a specific attribute change. They do not, on their own, suspend your account or remove listings you already have live, unless the underlying issue (for example a disputed UPC) also triggers a separate listing policy case.

How long does a GS1 UPC dispute take to resolve?

Sellers report anywhere from a few days to several weeks once a Seller Support case is opened with a GS1 certificate attached. Cases with a complete GS1 certificate and Letter of Authorization attached on the first submission resolve faster than cases that get escalated after an incomplete first attempt.

Do these four error codes suspend my seller account?

No, not by themselves. All four block a specific listing action, creating an ASIN, publishing an attribute, or using a UPC, rather than the seller account itself. Account-level suspensions follow a separate performance or policy-violation process.

What should I attach to a Seller Support case for error 8572?

Attach your GS1 certificate showing the UPC or EAN is registered to your company, plus the product name, brand name, manufacturer name, and the exact code in question. If you're a reseller rather than the brand owner, add a Letter of Authorization from the brand and a distributor invoice.

Is there a way to list my product without fixing the brand error first?

For error 5665, yes as a short-term workaround: enter "Generic" or "Unbranded" in the brand field to get the listing live, then submit the brand approval application afterward. This does not work for 5461 or 8572, where the identifier mismatch has to be resolved before Amazon accepts the submission.

Amazon Error Codes 5461, 8541, 8572, and 5665: What Each One Means

Amazon error codes 5461, 8541, 8572, and 5665 all block a listing action rather than suspend your account, but each one has a different root cause and a different fix. 5461 and 5665 are brand-permission errors. 8541 and 8572 are identifier-matching errors tied to what Amazon already has on file or what GS1 has registered.

What These Four Error Codes Have in Common

Open a Seller Central ticket for any of these four and you'll notice the pattern: none of them are vague "something went wrong" messages. Each one points at a specific field, your brand name, a UPC, an attribute value, that Amazon's catalog system rejected against an existing record. That specificity is good news. It means the fix is usually a documentation problem, not a mystery.

The bad news: Seller Support reps often give generic advice ("try resubmitting") because the error code itself doesn't appear in their standard scripts. Knowing exactly what triggers each code, and what to attach to your case, cuts weeks off the resolution time.

Error 5461: You May Not Create New ASINs for This Brand

Error 5461 reads "You may not create new ASINs for this brand. You are free to add offers to any existing ASIN for this brand." It fires when you try to create a brand-new ASIN and the brand name you entered is already enrolled in Brand Registry, or otherwise protected in Amazon's catalog, and your GTIN doesn't match that brand's registered identifiers in GS1's database.

Three ways this shows up:

You're reselling a registered brand. The brand owns the GS1 prefix and your UPC wasn't issued to you by them, so Amazon won't let you spin up a new listing under their name.
You typed a real brand name into the Brand field by mistake, even though your product isn't that brand. Amazon's catalog treats the brand field as a protected claim, not free text.
You own the brand but haven't completed brand approval for this specific category, so Amazon doesn't yet recognize your account as authorized to create ASINs under it.

The fix depends on which of those three you're in. If you're adding to an existing listing rather than creating a new one, skip ASIN creation entirely, just add your offer to the existing ASIN. If you own the brand, apply for brand approval in that category through Seller Central before attempting ASIN creation again. If you're reselling and don't own the brand, either get a Letter of Authorization from the brand owner or remove the brand name from the Brand field and use your own seller name there instead, listing the actual brand only in the title and description where it's accurate, not a protected claim field.

Error 8541: Attribute Value Doesn't Match Amazon's Published Record

Error 8541 is a conflict error. You submitted an attribute, most often UPC, EAN, title, brand name, manufacturer, or model number, and it doesn't match what Amazon already has published for that ASIN. This is different from 8572: 8541 can trigger on any catalog attribute, not just the product identifier.

A common trigger: you're updating an existing listing's title or manufacturer field, and the value you're submitting conflicts with a previous submission Amazon already accepted, even one made months ago by a different seller on the same ASIN. Amazon's catalog locks onto whichever value it accepted first and treats later conflicting submissions as the error, not the correction.

The fix: pull up the ASIN's current live listing and match your submission to what's actually published, character for character, including the UPC or EAN. If you're confident the published data is wrong and yours is correct, you'll need to go through Seller Support with documentation (invoice, GS1 certificate, or manufacturer spec sheet) rather than just resubmitting the same value again. Sellers who've hit a wall with manual edits report success deleting the listing and resubmitting after waiting roughly 48 hours, which gives Amazon's catalog cache time to clear the old conflicting value. If none of that resolves it, open a case specifically referencing error code 8541 so it routes to a catalog specialist instead of general listing support.

Error 8572: UPC, EAN, or ISBN Doesn't Match the Product

Error 8572 means the UPC, EAN, ISBN, or JAN code you submitted doesn't match what GS1 has on record for that code. Amazon checks every product identifier against the GS1 database, and a mismatch there is treated as invalid regardless of whether the code looks correctly formatted.

This happens for one of three reasons: someone else is already using that exact code for a different product, the code was never registered with GS1 in the first place (common with codes bought cheaply from a reseller instead of issued directly by GS1), or you mistyped a digit when entering it.

The fix: open a Seller Support case and request to list the item using your UPC, attaching your GS1 certificate and, if you're a reseller rather than the brand owner, a Letter of Authorization from the brand plus a distributor invoice. Amazon only accepts a UPC for new product creation if what you submit matches GS1's record exactly, so pull your certificate before opening the case rather than after Amazon asks for it, that's the step that adds the most delay. If you bought your UPC from a third-party reseller rather than GS1 directly, budget extra time, since Amazon increasingly treats non-GS1-issued codes as unverifiable even when the reseller's paperwork looks legitimate.

Error 5665: Amazon Needs to Approve Your Brand First

Error 5665 means Amazon hasn't approved your account to list under that brand name yet. Unlike 5461, this isn't about a GTIN conflict, it's a standing brand-authorization gate that applies before you've submitted any product identifiers at all.

The fix has three paths depending on your situation. If you have a registered or pending trademark, enroll the brand in Brand Registry, which grants listing permission automatically once approved. If you don't have a trademark but are authorized to sell the brand, complete the "selling application for catalog authorization" form, Amazon links directly to it from the 5665 error message in Seller Central. If you need the listing live immediately and can sort out brand approval afterward, use "Generic," "Unbranded," or another neutral placeholder in the Brand field as a temporary workaround, then submit the approval application and update the brand field once it clears.

Comparing the Four Error Codes

Code	What it blocks	Root cause	Who it usually hits
5461	Creating a new ASIN	Brand protected in catalog; your GTIN isn't registered to it	Resellers of registered brands
8541	Publishing an attribute update	Submitted value conflicts with Amazon's existing published record	Sellers editing an established listing
8572	Using a specific UPC/EAN/ISBN	Code doesn't match GS1's record for that product	Sellers with non-GS1-issued or reused codes
5665	Listing under a brand name	Brand not yet approved for your account	New sellers or first-time brand listings

How to Open a Seller Support Case That Gets Routed Correctly

Mention the exact error code in your case subject line and first sentence. Catalog and identifier disputes get routed to a different queue than general listing help, and omitting the code is the single most common reason a case bounces between reps without resolution.

Attach documentation before the rep asks for it: a GS1 certificate for UPC or EAN disputes, a Letter of Authorization if you're reselling rather than owning the brand, and a screenshot of the exact error as it appears in Seller Central. Cases that arrive complete on the first message resolve measurably faster than cases where Amazon has to request the same documents a second time.

What NOT to Do When You Hit One of These Codes

Don't keep resubmitting the same data expecting a different result. If 8541 or 8572 rejected your UPC once, Amazon's catalog will reject the identical submission every time until the underlying GS1 or published-record conflict is actually resolved.

Don't buy a "replacement" UPC from a marketplace reseller to work around 8572. Amazon increasingly flags non-GS1-issued codes during review, which can convert a simple identifier mismatch into a longer catalog integrity investigation.

Don't leave the brand field blank to dodge 5665 entirely. An empty brand field triggers a separate listing-quality flag. Use "Generic" or "Unbranded" instead if you need to list before approval clears.

Run a free Amazon listing audit to check whether a brand or identifier mismatch is affecting other live ASINs in your catalog beyond the one throwing the error, catching a second conflicting listing before it throws its own error code saves a separate round of Seller Support back-and-forth. If the error you're fighting turned out to be a brand mismatch rather than an identifier one, the wrong brand on listing fix walks through correcting the brand field without triggering a second catalog conflict.