How to merge existing Amazon product listings?

Originally published Updated

Cleaning up duplicate product pages is a useful part of looking after an Amazon catalog. First, keep the shared product detail page separate from a seller’s offer. The important question for a merge is whether two ASINs describe exactly the same physical product. A request should answer that question with evidence, rather than try to remove an inconvenient competitor.

A clean catalog helps shoppers understand the item they are buying. It takes careful checking: the same photograph is not enough, and a successful variation does not become a duplicate just because you want another search position.

Adapted from an article originally published on Bindwise; reviewed and updated for Hopted by Vlad Rudenko and the Hopted editorial team.

The multiple listing problem & how to solve it

Amazon’s Product detail page rules say not to create a duplicate page for a product already in its catalog. Selling a private-label product does not provide a blanket exception: a genuinely different branded product needs its own page, while another offer for an existing product belongs with that product.

Consider “Bob’s Brand Garlic Press.” Two pages with the same photographs and slightly different titles deserve a closer look. But a similar name such as “Bob Brand Garlic Press” is a reason to investigate, not proof of a duplicate. Check the actual brand and product identity before drawing a conclusion.

A different brand, size, color, model or pack configuration may describe a different item. Do not change a brand name or other identifying details just to make two pages look eligible for a merge.

Why it is a problem

Imagine one product appearing on 20 separate pages rather than one page with 20 offers. That is an illustration, not a measured result. Amazon’s guidance on duplicate ASINs explains that separate pages can split traffic and confuse buyers.

That is reason enough to care about duplicates. It does not establish that merging them will raise your organic position, reduce your cost per click or make your product appear on the first page. Judge catalog accuracy first; measure commercial results separately.

Check that the ASINs are genuine duplicates

Start with the current US Merge Duplicate Product Pages requirements. Amazon requires matching product attributes, including brand, size/color/style, manufacturing details, category attributes and product ID. Check the tool’s active-listing requirements for your account and ASIN pair before preparing the request. Parent ASINs cannot be merged, and removed ASINs are ineligible. Brand-registered ASINs have additional controls; only the rights owner can request their merge.

Compare packaging, manufacturer documentation and identifiers alongside the detail pages. Photographs alone are a weak basis for a decision. If important attributes disagree, resolve the discrepancy honestly before requesting any catalog change. A little tedious, yes.

Take action: prepare the merge request

Use the self-service tool linked from Amazon’s merge help page. Amazon describes a target ASIN to retain and a source ASIN to merge into it. Prepare around three questions:

  1. Which ASIN should be kept? Record the proposed target and why it is the accurate catalog record.

  2. Which ASIN is the duplicate? Identify the source clearly. Assess each pair on its own evidence.

  3. Why are they the same product? Describe the matching identifiers and attributes, and keep the supporting documentation ready.

For the garlic press, an explanation might read: “These ASINs represent the same Bob’s Brand garlic press, with the same manufacturer model, product identifier, material, dimensions and package quantity. The attached packaging and manufacturer information show these matches.” Use that wording only when every detail is true.

Choose the target on catalog accuracy and eligibility. Do not choose it because an offer lacks Prime, its presentation is poor, or you want to weaken another seller’s position. Amazon’s Seller Code of Conduct requires accurate information and fair use of its services, and prohibits attempts to damage another seller or their listings.

Also, “lowest BSR” does not mean weakest seller. Amazon explains that a lower Best Sellers Rank generally indicates stronger sales within a category. BSR and keyword search rank are different measures. Neither is evidence that two products are identical.

How will Amazon respond?

If self-service cannot complete the merge, Amazon directs you to Selling Partner Support. Keep the ASIN pair, evidence and case history together so the issue is easy to assess.

Read the reason for any rejection before replying. If it is unclear, ask which attribute or eligibility requirement prevents the merge. Supply accurate additional evidence through the appropriate support route; repeated requests with unchanged evidence do not resolve an eligibility problem. A different source/target order should reflect a factual catalog correction, not an attempt to bypass the decision.

What will the catalog look like?

Amazon says the source page redirects to the target after a successful merge, and inventory and sales history combine under the target. Reviews may be shared only when eligible. Do not budget around an automatic transfer of every review.

Afterward, check the target’s identifiers, title, images, offers and inventory against your records. Review your advertising and reporting references too. Keep a small record, for next time. If the page now represents the wrong product, investigate the catalog error instead of treating a commercial improvement as proof that the merge was correct.

More listing merge possibilities: variations and unmerging

Do not combine unrelated products to collect their reviews. Amazon permits valid product relationships, not a collection of unrelated items chosen for their ratings. Its Product variations overview requires products in a family to share their core function, product type and brand, with differences covered by an allowed variation theme.

Keep three different operations separate

  • Merge duplicates: combine two catalog pages for the same physical item.

  • Create or correct a variation family: connect distinct, related child ASINs using a supported theme. The parent is a non-buyable grouping; each child identifies a purchasable variant. See Amazon’s Variation relationship FAQ.

  • Reverse an incorrect merge: ask Amazon to separate genuinely different products that were previously merged. The Split Different Products into Different Pages tool requires merge history, an active offer and evidence of the differences. It is not the tool for detaching a successful variation to gain another search result.

Consider a glove sold in several sizes and left- or right-hand versions. A Medium Right glove and a Large Left glove are distinct variants, not identical products to collapse into one ASIN. Whether they belong in one family depends on the variation themes permitted for that product type. Never substitute “color” for hand orientation merely to force the relationship.

Their success does not justify describing an ordinary variation as a fundamentally different product. If a family is wrong, correct it with accurate evidence. If a valid family simply needs better presentation, review the titles, attributes and images. Do not use catalog changes as a promise of three first-page placements.

Variation displays by category

Amazon’s current variation guidance says available themes depend on the category and product type, and that supported themes are regularly updated. Check the current listing form or product spreadsheet for your product, rather than relying on an old category list.

Search visibility needs its own check. Inspect what shoppers actually see for relevant searches, then verify that each child’s title and attributes describe that specific item accurately. Do not infer ranking or click behavior from one display example. For the glove, check the available hand and size options as well as the option selected when the detail page opens.

For example, do not put “Left or Right, All Sizes Available” into every child title if it obscures the variant being purchased. Aim for a clear family and an unambiguous selected option. The detail page rules require accurate product descriptions and valid variations.

Review counts also need a separate check. Amazon’s 2026 review-sharing guidance limits sharing to eligible variations with minor differences that do not affect functionality. A valid family is not a guarantee that every child will share every review.

Take action! One more time

Look after the catalog, document genuine duplicates and check the result of a change. Start with your important products and recheck them when something looks wrong.

Build each request around what the physical products actually are. Merge identical pages, use supported variations for related options, and request an unmerge when different products have been combined incorrectly. Then measure sales and advertising performance without assuming the catalog change will deliver a particular result.

Take the next step.

Work with Amazon data in Google Sheets — without manual exports.