Duplicate ASIN issues come from one of three places: you created a second page for a product that already exists, Amazon merged your product into someone else’s page, or Amazon split a variation family that used to work. The fix depends on which of the three you are facing, and on how quickly you act. This guide shows you how to tell them apart, what to do in Seller Central, and how to stop the problem coming back.
TL;DR
- Amazon prohibits creating a new detail page for a product that already has one, and it flags duplicates for you to review in Manage Inventory.
- You have a 30-day grace period to respond to a Potential Duplicates notice. If you ignore it, the ASIN can be suppressed from search.
- Most accidental duplicates start with searching the catalogue by product name instead of by EAN or UPC.
- Wrongly merged or wrongly split pages are fixed with Amazon’s split tool, and refused if attributes are similar or the product is under Brand Registry and you are not the rights owner.
- If automated rejections loop, stop resubmitting the same appeal and ask for a supervisor-level escalation with the pattern documented.
Table of Contents
- What a duplicate ASIN issue actually is
- Why duplicates get created
- How to respond to a Potential Duplicates notice
- Fixing a wrong merge or a wrong split
- When the case goes in circles
- Protecting your listings from clones and hijacks
- Our perspective: duplicates are a data problem, then a money problem
- Keeping profit and ads clean while you fix it
- A weekly routine to prevent duplicate ASIN problems
- FAQ
- Sources
What a duplicate ASIN issue actually is
An ASIN is Amazon’s catalogue number for a detail page. Amazon supports only one detail page for a single product, so when two pages describe the same item, one of them is a duplicate. Creating one is against the Detail Page Creation policy, even if it happened by accident.
The symptoms differ depending on the cause:
| What you see | Likely cause | First move |
|---|---|---|
| A “Potential Duplicates” notice on your inventory | Amazon’s system matched your listing to another page | Review and respond within 30 days |
| Your ASIN is suppressed from search | The 30-day window passed, or a policy alert was not answered | Respond, then contact Seller Support with evidence |
| Your product now sits on a competitor’s page | A merge, often because attributes matched | Use the split tool, with proof the products differ |
| A variation family has broken into single listings | Attribute changes or catalogue clean-ups | Check parent-child data, then rebuild |
| Search results flooded by clones of your product | Other sellers creating pages for the same item | Brand Registry reporting and escalation |
The first step is always the same: work out which row you are in before you touch anything. Resubmitting data blindly is how a small problem becomes a suppressed listing.
Why duplicates get created
Searching by name instead of identifier
Amazon’s guidance tells sellers to match products using manufacturer-issued identifiers such as an EAN or UPC. Searching by product name is the most common route into duplicate creation, because names vary and you end up creating a new entry instead of matching the existing one.
Before you create any new listing:
- Take the EAN or UPC from the packaging or the supplier’s data sheet.
- Search the catalogue for that exact number.
- If a page exists, offer your stock against that ASIN rather than creating a new one.
- Only create a new page when the identifier returns nothing and you are certain the product is new to the catalogue.
Packaging, bundles and small changes
A redesigned box, a new photo set or a changed pack size can all push a seller to create a fresh ASIN. Sometimes that is legitimate: a genuinely different product, such as a different pack quantity, can have its own page. Where the product is the same item, though, the existing page is the right home. If you are unsure, ask yourself whether a customer would receive a different product. If not, do not create a new page.
Variation families built carelessly
Sellers also report variation families separating without warning. In one seller forum thread about variations separating, sellers describe families that had run for years splitting apart, with one explaining that an attribute change by Amazon had broken the relationship. Anecdotes are not policy, but they show that variation data needs checking regularly, not just at setup.
Selling across several marketplaces
One experienced seller’s account of ASIN mismatches in EU5 suggests creating the parent-child structure separately for each marketplace, such as the UK, Germany and France, rather than forcing one global structure. That is a seller’s experience rather than an Amazon rule, but it is sensible: each marketplace has its own catalogue, and what matches in one may not match in another.
How to respond to a Potential Duplicates notice
Amazon’s process gives you a window to act, and the 30-day grace period is the part sellers most often miss. If you do not respond, the ASIN can be suppressed from search, and recovery is harder than the original fix.
Work through it in this order:
- Open the Potential Duplicates page from Manage Inventory and list every flagged ASIN.
- Compare the pages. Check the identifier, brand, model number, pack size, colour and size. Note any real difference.
- Choose the right response. If it really is the same product, move your offer to the existing ASIN and let the duplicate go. If the products differ, say so and keep the evidence.
- Record the date the notice appeared and the date you responded. If you need to escalate later, a timeline helps.
- Check inventory. If you move offers, make sure stock is labelled against the correct ASIN before you send anything to a fulfilment centre.
Do not leave this until day 29. Notices are easy to overlook in a busy account, so put a weekly check in your calendar.
Fixing a wrong merge or a wrong split
When Amazon has put your product on the wrong page, or taken a product off the right one, the main route is the self-service split tool. Per Amazon’s help page on splitting products across different pages, requests are refused in these cases:
- the products have similar attributes;
- the product is not in your active stock;
- the ASIN is registered under Brand Registry and you are not the rights owner.
That last point catches many sellers out. If a Brand Registry product has been merged, the brand owner has to take the action.
Preparing a split request that works
- Photograph the product and packaging from several angles, including the barcode.
- Show the attribute that differs: model number, material, size, quantity, or manufacturer part number.
- Have active stock so the request is not rejected on that ground alone.
- Keep your wording factual. Describe the difference, not the inconvenience.
When Amazon will not merge your duplicate
The reverse also happens. You may want a duplicate merged into the right page and Amazon declines. The usual reason is that identifiers or attributes are not identical, and the system will not treat the products as one. In that case correct your own listing’s identifiers and attributes first, then ask again with a clear comparison.
When the case goes in circles
Sometimes your data is correct and the system still rejects it. One seller’s detailed escalation request describes an endless cycle of automated rejections and asks for supervisor-level handling. The practical lesson is to stop sending the same appeal. Instead:
- Write one short summary: the ASIN, the dates, what you submitted and the replies you received.
- Ask explicitly for escalation to a supervisor or the relevant specialist team.
- Describe the pattern, for example the same decision repeated against identical evidence, rather than the frustration.
- Keep every case ID in one document.
This does not guarantee a result, but a documented pattern gives a reviewer something to act on.
Protecting your listings from clones and hijacks
Sometimes the duplicate is not yours. Clone ASINs created by other sellers can split reviews and sales. If you own the brand, Brand Registry is your strongest lever, and it also stops your ASIN being merged away by other sellers. Report each clone with the identifier, the brand name and screenshots, and keep a log of what you report and when.
Good catalogue hygiene helps too. Strong titles, accurate attributes and correct identifiers make it clearer which page is the real one. For a wider look at how catalogue content affects discoverability, see this explainer on Amazon SEO and catalogue basics.
Our perspective: duplicates are a data problem, then a money problem
We build Osellpa for Amazon sellers who are tired of managing catalogue, ads and profit in separate spreadsheets. From that vantage point, duplicate ASINs cause damage in three quiet ways.
First, sales and reviews get split. When the same product trades on two pages, neither tells you the real performance of the item, so your decisions about stock and price rest on partial figures.
Second, advertising goes astray. A suppressed ASIN cannot win clicks, but campaigns can keep running against it. We cover that in our guide to pausing ads when a product is out of stock, and the same logic applies to a listing that has dropped out of search.
Third, profit becomes hard to read. Working out what each SKU really earns is only possible if each SKU maps cleanly to one ASIN. When products are merged or split unexpectedly, the numbers shift under you.
Our advice is simple. Treat the identifier as the source of truth, check your Potential Duplicates page on a fixed day each week, and keep a record of each ASIN and the SKU behind it. If you sell variations, our piece on building variation families that sell covers the structure side in more depth.
— Harry
Keeping profit and ads clean while you fix it
While you resolve a duplicate, your sales and ad data keep moving. Osellpa connects to Amazon’s API to give you profit tracking, automated and manual PPC optimisation, alerts and listing tools in one place, so you can see what each product is doing without rebuilding spreadsheets. Plans start at £10 per month for Launch, £20 per month for Scale and £40 per month for Advanced, or £96, £192 and £384 per year respectively. You can compare them on our pricing page.
A weekly routine to prevent duplicate ASIN problems
Prevention takes less time than a case. A short routine works for a seller of any size:
- Before creating a listing: search by EAN or UPC, never by name alone.
- Weekly: open Potential Duplicates and clear anything flagged.
- Monthly: check that variation families are still intact and that key attributes have not been altered.
- After supplier changes: confirm the identifier on the new packaging matches the one on the listing.
- Always: keep a sheet matching SKU, ASIN, identifier and date created.
If you are a new or part-time seller, the weekly check is the one to protect. It costs minutes and avoids most suppression events.
FAQ
How do I merge two ASINs on Amazon?
Amazon will only treat products as the same when their identifiers and attributes match. Check both pages, correct any differences on your own listing, and respond through the Potential Duplicates page if Amazon has flagged them. Brand Registry ASINs cannot simply be merged by other sellers.
How long do I have to respond to a duplicate notice?
The Potential Duplicates process gives you a 30-day grace period. After that, the ASIN can be suppressed from search. Respond as early as you can.
Why was my split request refused?
The usual reasons are that the products have similar attributes, you have no active stock of the item, or the ASIN is in Brand Registry and you are not the rights owner. Fix whichever applies and resubmit with clear evidence of the difference.
What should I do if Amazon keeps rejecting my appeal?
Do not resend the same message. Summarise the timeline, list your case IDs, and ask for supervisor-level escalation, pointing out the pattern of repeated rejections against correct data.
Sources
- Amazon Seller Central UK: splitting products across different pages
- Amazon Seller Central UK: searching for products by identifier
- Seller forum: listing product violations for duplicate ASIN
- Seller forum: ASIN and FNSKU mismatch across EU marketplaces
- Seller forum: request for supervisor-level escalation
- Seller forum: variations becoming separated
- Amazon SEO and catalogue basics
