When should duplicate Amazon ASINs be merged?
Request a merge only when two product pages represent the same physical product and their identity attributes agree. Similar products, revisions, pack sizes, conditions, brands, or compatible alternatives require separate catalog treatment even when shoppers could use them for the same purpose.
Amazon's duplicate-page guidance says key product attributes must match and notes restrictions involving different brands and Brand Registry ASINs. Confirm the current self-service tool result before assuming a merge is available.
Build a product-identity comparison
- Record both ASINs, marketplaces, brands, manufacturer, model, GTIN, part number, size, color, count, formulation, edition, condition, and package contents.
- Compare front, back, identifier, model, and package photos from controlled physical units.
- Map seller SKUs, FNSKUs, inventory, variations, offers, reviews, advertising, A+ Content, Store links, and external links attached to each ASIN.
- Identify the authoritative manufacturer or brand evidence and explain any harmless formatting difference.
- Stop the request when an attribute difference changes what the customer receives.
Choose the target ASIN deliberately
Select the target from verified catalog ownership, product identity, offer continuity, inventory mapping, content accuracy, and downstream dependencies rather than review count alone. Record why the target is correct and what must be preserved.
Before submitting, export both detail pages and affected operational records. A source ASIN redirect does not guarantee every seller-side mapping, report, campaign, or integration will behave as expected.
Submit and verify the merge
- Use Amazon's Merge Duplicate Product Pages workflow and enter only the pair supported by the identity evidence.
- Save the request, source and target ASINs, submitted attributes, confirmation, and decision.
- After approval, verify the target title, brand, identifiers, variation structure, images, bullets, offers, buyability, inventory, and category.
- Check ads, coupons, A+ Content, Store links, reports, APIs, and external URLs for stale source-ASIN references.
- If the merge is rejected or incorrect, reopen from the preserved evidence and identify the exact attribute or policy conflict instead of creating another duplicate page.
Scope and exceptions
Do not use a merge to combine valid variations, transfer reviews, change brands, repair an unrelated catalog error, or hide a materially different product. Brand Registry and marketplace rules can limit eligible pairs.
Review [Amazon's Merge Duplicate Product Pages guidance](https://sellercentral.amazon.com/help/hub/reference/external/G201950590?locale=en-US) and [product detail page rules](https://sellercentral.amazon.com/gp/help/external/G200390640?locale=en-US) before submitting.
Related Amazon seller guides
- [Create a catalog change log for faster troubleshooting](https://amazonmargincalculator.cloud/blog/amazon-catalog-change-log)
- [Repair an Amazon variation family without repeating the policy error](https://amazonmargincalculator.cloud/blog/amazon-variation-family-policy-repair)
- [Prepare an Amazon GTIN exemption before creating the listing](https://amazonmargincalculator.cloud/blog/amazon-gtin-exemption-evidence-readiness)