Skip to main content
ASA Compliance Group • Duplicate ASIN appeal • Since 2016

Amazon flagged a duplicate ASIN? We determine which catalog record should survive and why. We settle product identity first, then run the right catalog route. Amazon decides the outcome.

Two records for one product, or two products Amazon reads as one? Which it is changes the whole route.

For cases we accept: a field-by-field identity comparison, the catalog and contribution history, the right merge, split or correction route, and live verification.

  • The problem The notice names ASINs, not the fix. Closing an offer leaves the catalog records untouched, so the duplicate survives it.
  • Why appeals fail Different SKUs, prices, reviews or fulfilment channels get offered as proof the products differ. None of them is product identity.
  • What we do Establish which record is authoritative, prove which fields match, run the route Amazon can action, then verify it reached the live page.
Get my case strategy See what the file needs

A real person reads your case and replies within about an hour.

Or Shamosh on stage at the European Seller Conference, Prague, March 2025, speaking about Amazon enforcement and reinstatement
I speak about enforcement; I run appeals in Seller Central every day.

ASA Compliance Group operates Amazon Sellers Appeal. On duplicate-ASIN files we compare the products field by field, reconstruct the catalog history, and run the correction route in Seller Central.

Start here

Paste the notice and every ASIN

Include each ASIN and seller SKU, the brand, GTIN and pack count, photographs of the products and packaging, and any merge, split or case history. Four short steps. Or Shamosh reads every intake.

  • Every case is personally reviewed before we take it on.
  • Most first replies are sent within about an hour.
  • Eligible cases get a written Case Strategy tied to your Performance Notification.
Or Shamosh, Founder and CEO, ASA Compliance Group

Or Shamosh · Founder and lead strategist

5,500+ enforcement cases since 2016. Every intake is personally assessed before acceptance.

Send what you have, including prior DIY or agency appeals. We say what is viable in writing before you commit.

Questionnaire

If the questionnaire does not load, open intake on the account page.

What happens after you submit

  • You’ll receive a review email within about one hour.
  • If Amazon gave you a reply deadline, mention it in the form so we can time delivery to it.
  • If eligible, you receive a written Case Strategy: what is driving the enforcement, what we would argue, what evidence matters, and how we would run Seller Central.

Let's see if we can get you reinstated.

Why we ask: tell us what happened and a real Amazon specialist reads it, usually within an hour, then replies in writing with our read on the case and what we would argue.

About 3 minutes. We save your progress as you go.

What happens when we take over
You submit intake; we run the duplicate-ASIN file
YOU Submit intake with the notice, every affected ASIN and SKU, and photographs of the products and packaging
WE Compare the products field by field and establish which catalog record is authoritative
WE Run the merge, split, correction or dispute route and verify the result on the live page
GOAL A catalog state Amazon can verify; the final decision stays Amazon’s
  • Since 2016 · Amazon reinstatement specialists
  • 5,500+ documented cases
  • 98% scoped historical rate
  • Full Seller Central handling for cases we accept

Across ASA’s accepted and fully managed enforcement cases (all notice types we take on), not Duplicate ASIN matters alone. Details under Proof.

Knowledge

What Amazon usually means by a duplicate ASIN

A duplicate-ASIN finding means two or more catalog records appear to represent the same commercial product. It is a statement about product identity, not about your offer. That is why closing one offer does not clear it: the offer is yours, the record is Amazon’s catalog, and the duplicate records are still there afterwards.

How the second record arrived matters for the route but not for whether there is a problem. It may have been created by hand, by a feed, by a vendor or another contributor, through a GTIN error, or deliberately to preserve reviews, ranking or selling access. The first job is to establish the authoritative product identity and the correct catalog destination, and only then to choose what to ask Amazon to do.

Three questions decide the route, in this order:

Identity

Are these the same commercial product? Brand, model, GTIN, pack count, formulation, edition, region, generation, included components.

Authority

Which record should survive, and do brand, identifier, category and contribution rules actually allow the change you want?

State

What is live now, and what will be live after the merge, split or correction is processed?

Amazon’s product detail page rules carry the single-unique-product principle: one product, one detail page, and a materially different product needs its own record. The mirror problem is a false duplicate, where two genuinely different products are treated as one. Both are decided by the same comparison, which is why the page starts there rather than with a merge request.

Triggers

How these cases usually start

Most duplicate-ASIN files are not somebody gaming the catalog. They are ordinary catalog accidents, plus one pattern Amazon treats far more seriously. Which one you are in decides the posture.

1. The same product under more than one GTIN

The most common start. A manufacturer reissues a barcode, a distributor supplies a different UPC for the same unit, or a GS1 prefix changes hands. Two identifiers reach the catalog, so two records get created, and both describe the item now sitting in the warehouse.

  • The same physical unit scanning to two different UPC or EAN codes
  • A GS1 record whose brand or company prefix no longer matches the package
  • A manufacturer part number that maps cleanly to one record and only loosely to the other

Reconcile the GS1 record, the barcode on the package, the brand and the manufacturer product number before asking for anything. An identifier conflict resolved the wrong way merges two products that should have stayed apart.

2. A duplicate created by a feed

A flat file or integration submits a product that already exists, usually because a match key was blank, mistyped, or mapped to the wrong column. Nobody decided to create a second page; the feed did it on a schedule and may still be doing it.

Two things have to be true before this closes: the redundant record is dealt with, and the feed that produced it no longer can. A correction that leaves the integration untouched gets undone by the next upload, and Amazon sees the duplicate reappear after you said it was fixed.

3. Creating a page to preserve reviews, ranking or selling access

This is the pattern that changes the seriousness. A listing is suppressed, restricted or gated, so a second record is created for the same product to keep selling. It reads to Amazon as working around the restriction rather than as a catalog error, and the duplication is then the smaller of the two findings.

Amazon’s ASIN creation policy constrains new catalog records precisely to stop this: where the product already exists, the expectation is that you work with the existing record rather than add another one.

The same logic applies in reverse. Choosing which record survives because it holds the reviews and the sales history, rather than because it is the accurate one, is a catalog decision made for the wrong reason. State the identity case; do not argue the review case.

4. Another contributor created the record

A different seller, a vendor, or a brand feed created the second page. Preserve the contribution history, because it explains how the records arose and the current storefront does not show it. Then set it aside: the creator’s identity does not change what the catalog looks like today, and the current state is what the notice is about.

Amazon’s route here is a merge, correction or duplicate dispute supported by product evidence. What it is not is a reason to create a third record. If the brand field itself is the contested part, that is a brand misuse question and it is answered with different evidence.

5. A false duplicate: the products really are different

Amazon’s matching flags a potential duplicate on similarity, and similarity is not identity. Two records can look nearly identical in the catalog and still be different products in the customer’s hands.

Changes the customer’s product
Model or generation, pack count, formulation or ingredient list, size or dimensions, edition, region or voltage, compatibility, included components.
Does not change the customer’s product
Seller SKU, price, fulfilment channel, offer condition, review count, sales history, storefront, or which listing ranks better.

The second list is where most rejected appeals live. Every item in it is real and none of it is product identity, which is the single distinction this page exists to make.

Appeals

Why DIY duplicate-ASIN appeals get rejected

Reviewers compare what the notice names against what the catalog actually shows. Most rejected responses answer a question about offers when the question was about products.

Offer facts as identity

Different seller SKUs, prices, fulfilment channels or review histories are argued as proof the ASINs are different products. They describe offers, not the item in the box.

Closing the offer

The offer comes down and the duplicate records stay up. Nothing in the catalog changed, so nothing in the finding changed either.

Merge requested too early

A merge asked for before brand, identifiers, variation structure, contribution authority and category restrictions are checked. It either bounces or collapses two products that should have stayed apart.

A third record

One duplicate is removed and a new page is created for the same product. That is the pattern Amazon reads as circumvention rather than as a catalog mistake.

No product-level disposition

Generic ASIN-creation language, or the same answer given twice, with no statement of which record should survive, which should not, and why.

Prepared is reported as done

A submitted flat file or an accepted processing report is described as the fix. Neither proves the live detail page changed, and the live page is what is checked.

Get my case strategy
The file

What a correct duplicate-ASIN file usually contains

Identity first, route second, verification last. Depth comes from the products and the catalog history, not from argument.

Diagnosis

Read the exact notice and its scope. List every suspected duplicate ASIN with its seller SKU, brand, model, UPC, EAN or GTIN, pack count, category and marketplace. If the notice names error 8573, it is telling you Amazon’s matching found a close existing record at creation time, which is a different problem from a creation permission or approval block. Those belong to ASIN creation policy.

Then gather what the storefront cannot show you: creation and contribution history, Category Listings Reports, any earlier merge or split cases, flat files and their processing reports, and the variation family each record sits in. A record that looks simple today often has a history that explains the whole finding.

The product-identity comparison

This is the core of the file, and it is a table rather than a paragraph. Put the records side by side and record every field as identical or different, backed by photographs of the product and packaging and by manufacturer specifications:

  • Brand, as it appears on the product, on the package and in the catalog field
  • Model or manufacturer part number, generation and edition
  • GTIN, UPC or EAN on the package, checked against the current GS1 record
  • Pack count, size, weight and dimensions
  • Formulation, ingredients or materials where the product has them
  • Region, voltage, plug type, language and any market-specific variant
  • Compatibility and included components

Then write the conclusion the comparison forces: either one authoritative record with a named canonical destination, or a specific documented difference that changes what the customer receives. A comparison that ends in neither is not finished.

The route, chosen after the comparison

Merge, split, correction, offer closure or dispute are five different asks and they are not interchangeable. Merge only where the records really are one product and Amazon’s brand, identifier, category and contribution rules allow it. Separation only where the material difference is proven. Where the catalog fields are wrong but the records are not duplicates, it is an incorrect detail page correction instead.

Two cautions that decide cases. A merge is irreversible in practice and it moves review and sales history with it, so an incorrect merge attaches reviews to a product that never earned them. And where the records sit inside a parent family, the merge interacts with the variation structure, which is its own enforcement lane: see variations abuse.

Live verification

Four states, and they are not the same thing: prepared, uploaded, processed and live-verified. A flat file can be ready, sent, accepted row by row, and the customer facing page can still show the old values. Only the last state is evidence, and it is the one Amazon checks.

So the file closes with a fresh look at the live ASIN, offer, title, identifier and reviews, plus the Amazon case result and a current report. Say which state each item is actually in. Reporting a prepared change as a completed one is the fastest way to lose the reviewer on the next round.

Have ready when you submit intake

  • The exact notice text and every ASIN it names
  • Every suspected duplicate ASIN and its seller SKU
  • Brand, model, GTIN, pack count, category and marketplace for each
  • Photographs of the products and of the packaging, including the barcode
  • Manufacturer specifications and the current GS1 record
  • Contribution, merge and split history, and any Category Listings Report
  • Every prior appeal, case and Amazon reply

If part of this does not exist, say so rather than reconstructing it. A stated gap is workable; an invented record is a second problem sitting permanently on the case log.

Get my case strategy
Proof

Documented outcomes

Scoped historical outcomes on cases we accepted and fully managed. One seller voice below; deeper galleries live on account reinstatement.

Since 2016 Amazon reinstatement specialists
5,500+ Documented enforcement cases
98% Scoped historical reinstatement rate
Seller Central We run the appeal for cases we accept
What the 98% figure means (population, success, review)

Population: historical cases ASA accepted and fully managed (we prepared the compliance response and ran follow-ups in Seller Central). The figure combines reinstatement and restoration work across notice types in that managed population, not Duplicate ASIN matters alone. Declined intakes and self-serve template buyers are not in the rate.

Success: reinstatement or restoration of the privileges Amazon had restricted for that file (account, listing, verification, funds, or related, depending on the case). Amazon decides every outcome; the rate is not a guarantee for future cases.

Review: the underlying records were independently reviewed. Verified as of .

More methodology context and galleries: account reinstatement proof.

“In less than 24 hours after the appeal, my account was reactivated with all products available for sale.”

Alex Huditan · Seller · Account reactivated

More outcomes and video proof: account reinstatement proof.

Get my case strategy

FAQ

For sellers who already have the Performance Notification. Broader questions: full FAQ library.

What makes two ASINs duplicates?
Two ASINs are duplicates when they represent the same commercial product, not merely similar items. Compare brand, model, GTIN, pack count, formulation, edition, region, dimensions and the other attributes a customer would notice. The comparison should end in one authoritative catalog destination, or in the documented characteristic that makes the products genuinely distinct.
Do different seller SKUs make the products distinct?
No. A seller SKU is an internal offer identifier, and several sellers can use different SKUs against the same ASIN. Identity depends on the actual item: brand, model, GTIN, quantity and the other material attributes. Map each SKU to the physical product first, then decide whether the catalog records are duplicates.
Should the ASINs be merged or separated?
Merging can be right when the records truly represent one product and Amazon’s brand, identifier, category and contribution rules allow it. Separation is right when a customer-relevant difference is proven. Reconcile the authoritative identity first, then choose merge, correction, split, offer closure or dispute, and verify the live result.
What if another seller created the duplicate?
Preserve the records and the contribution history, then focus on the correct product identity and the final catalog state. Provide the physical product, packaging, GS1, manufacturer and catalog evidence and use Amazon’s merge, correction or duplicate-dispute route. Who created the record does not remove the catalog problem that exists now.
How do I prove the products are genuinely different?
Build a side-by-side matrix of brand, model, GTIN, pack count, formulation, size, edition, region, compatibility, included components and packaging, supported by photographs and manufacturer records. Then explain which of those differences changes the customer’s product experience, and why each ASIN needs its own accurate record.
What do you need to start?
The notice text and its scope, every ASIN and seller SKU involved, brand, GTIN and pack count for each, photographs of the products and packaging, whatever catalog and contribution history you can pull, and every prior appeal or Amazon reply.
What is in the Case Strategy?
For eligible cases: which record we think should survive and why, the identity comparison that supports it, the route we would run and the order we would run it in, and how we would verify the live catalog afterwards. Amazon’s decision is never guaranteed.

Send the notice. Get the strategy.

If Amazon flagged a duplicate ASIN or a potential duplicate, start with the questionnaire.

Get my case strategy Account reinstatement services

Listing removed rather than duplicated: listing reinstatement. Other notice names: all suspension types.