This Manufacturer Barcode Is Linked To More Than One ASIN: How To Fix It

This one never appears on a quiet day. It appears in the send and replenish inventory workflow, so you found it while restocking, which means the units are boxed and the shipment is already late. The message reads:

This manufacturer barcode is linked to more than one ASIN. Please check if you entered the correct product ID (International Standard Book Number (ISBN), UPC or European Article Number (EAN)).

We understand how that lands. The listing is still live and the offer still sells, yet you cannot send stock in, so the ASIN runs to zero while a catalogue argument you did not start plays out. The instruction in the message is the least useful part of it, because the product ID you entered is usually correct. The conflict is sitting in Amazon's catalogue, not in your form.

What the error actually means

For FBA to accept units labelled with a manufacturer barcode, that barcode has to resolve to exactly one ASIN. When the same GTIN sits on more than one ASIN, Amazon cannot tell which detail page your cartons belong to, so the workflow stops rather than guessing.

Sellers in the Seller Central forums have pointed out for years that the wording is misleading, because the condition is often the reverse: one ASIN carrying several product IDs. Source: Seller Central forums, Amazon primary. Either way it is a one to one mapping that is no longer one to one.

The four ways a barcode ends up on two ASINs

1. A reused code. A supplier retires a product, keeps the model name and issues the replacement under the same code, and by then both products exist in the catalogue.
2. A barcode that was never yours. Codes bought cheaply from resellers were issued to another company, and Amazon verifies UPCs against the GS1 database, stating that "UPCs that do not match the information provided by GS1 will be considered invalid". Sources: Amazon's product ID requirements, Amazon primary, and GS1 US, quoting the same requirement. Moving those SKUs onto codes issued under your own prefix is its own piece of work, and our UPC to GS1 barcode change page sets out how our team sequences it.
3. A supplier selling the same code to several sellers. Common with white label sourcing, where every buyer lists that code under a different brand name and several ASINs end up sharing one identifier.
4. A duplicate ASIN. Somebody created a second detail page for the same product, by accident during a bulk upload or deliberately, and put the GTIN on it.

There is a fifth cause that is nobody's doing. Amazon's catalogue processes merge and edit ASINs, and sellers report finding an identifier on a page they never touched.

How to tell which case you are in

1. Search the barcode digits in the Amazon search box. More than one detail page coming back means the conflict is visible from the shopper side, and that is your first piece of evidence.
2. Open the product identity fields on your own ASIN. Several GTINs on one ASIN is the reverse situation, and the ask becomes stripping the identifiers that do not belong there.
3. Check Potential Duplicates in Manage Inventory. Amazon surfaces suspected duplicate pages there, and a duplicate ASIN is a different job to a shared code.
4. Confirm who the code actually belongs to. A GS1 company prefix issued to your business is a fact you can evidence, and a code bought from a reseller is not. Knowing which you hold before opening a case saves a week of circular replies.

What to check before you change anything

The urge is to create a new SKU and move on, and it is worth pausing, because new SKUs leave stranded units under the old one, which is a second problem on top of the first.

1. Your GS1 ownership record. The company prefix certificate and your GS1 account entry turn "this is our barcode" into something the catalogue teams can act on. Our UPC to GS1 barcode page covers what a clean identifier set looks like.
2. Your Brand Registry status. Rights owner status changes what you can request, because Amazon restricts merges on registered brands to the rights owner.
3. The other ASIN's details. Your product on a duplicate page and a different product carrying your code are two different requests.
4. What is stranded right now. Units already at a fulfilment centre under the affected SKU need their own answer, separate from the correction.

Getting the barcode back to one ASIN

1. Build the evidence before opening anything. A case with attachments closes faster than a case with an explanation, and this step decides how many rounds you go.
2. Ask for the identifier to be separated from the ASIN that should not have it. Sellers describe this as asking Amazon to cleave the UPC or EAN from the incorrect ASIN, and an Amazon moderator confirmed on that thread that Seller Support had resolved the cases. Source: Seller Central forums, Amazon primary.
3. Use the merge route when the two pages are genuinely the same product. Amazon's guidance is strict, that "the products must be identical in all attributes including UPC", and merges on a registered brand can only be requested by the rights owner. Source: Merging duplicate product pages, Amazon primary.
4. Correct your own product ID by flat file where the identifier on your ASIN is wrong. The external product ID and its type go on the category template with update delete set to Update, and Amazon accepts the change only where the product behind the new identifier is the same one. Our flat file errors page covers what the processing report is saying when it rejects the row.
5. Keep the follow up on one case rather than opening five. Five cases produce five template replies from five agents, and the thread carrying the history is the one that reaches the catalogue team.

We will not promise a timeline, because these cases move at Amazon's pace and the first reply is often a template answering a question nobody asked. The answer is going again with the same evidence rather than rewriting the request.

The evidence that actually moves a barcode case

That last row matters. Cases argued around what the shopper sees are read differently to cases argued around what the seller is losing, and framing it that way costs nothing.

Shipping while the catalogue case runs

The workaround sellers report using is the Amazon barcode rather than the manufacturer barcode, so units carry an FNSKU that resolves to one SKU and the shipment stops depending on the disputed identifier. Source: Seller Central UK forums, Amazon primary. The path is Settings, then Fulfillment by Amazon, then the FBA product barcode preference section.

It is a workaround and not a fix, because the conflict stays in the catalogue and surfaces again on the next replenishment, but it keeps the ASIN in stock while the real correction is argued.

There is a deadline attached. Amazon has announced that commingling practices end on 31 March 2026 for inventory shipped on or after that date, with brand owners holding the Brand Representative role able to keep using manufacturer barcodes and resellers required to apply Amazon barcode stickers. Source: Amazon's announcement, Amazon primary, 2026.

How to keep this from happening again

1. One identifier per sellable unit, issued to your own company prefix. Every multipack, bundle and new size is its own product to the catalogue, and treating one as a variant of an existing code is where most conflicts begin.
2. Keep the certificate somewhere findable. The GS1 record is what every one of these cases turns on, and hunting for it mid emergency costs days.
3. Keep a register of which code sits on which ASIN. One sheet that stays current turns a two week investigation into a ten minute check.
4. Ask suppliers in writing whether the code is exclusive to you. With white label sourcing the honest answer is often no, which is cheaper to learn before the first shipment.
5. Limit who can create listings. Most duplicate ASINs come from a bulk upload run by someone who did not know a page already existed.

What we would do first if this were our account

Search the barcode on Amazon and screenshot whatever comes back, because that one image decides whether this is a duplicate page, a shared identifier or something Amazon's catalogue processes did. Then pull the GS1 record, because every version of this case rests on showing who the code was issued to.

Then switch the affected SKU to the Amazon barcode so stock keeps moving, and open one case with the evidence attached rather than five with none. If this is a catalogue conflict rather than a labelling one, our catalog troubleshooting page explains how our team works through it.

We cannot promise how quickly Amazon will act on a barcode case, and we would not trust anyone who did. What we can tell you before you spend anything is which of these situations you are in and what evidence the case needs, which is what the free, no-obligation audit covers.

Related guides

• FNSKU versus manufacturer barcodes
• Fixing a wrong browse node
• Why your listing edits keep reverting

Common questions about the manufacturer barcode error