How to Find and Remove Duplicate Shopify Products After an Import

Suppose an import leaves your catalog with two records for the same tote bag. One has the right photos. The other has the latest supplier description. Deleting the newer record might remove the information you wanted to keep.

To find and remove duplicate Shopify products, start by matching titles, SKUs or barcodes. Then compare each group and decide which record belongs in your catalog before removing anything.

RP: Duplicate Finder & Delete groups matching products and variants so you can review them, choose keepers, and archive or delete selected duplicates. This guide covers the decisions to make around that cleanup.

Start with the import you want to check

If you have just imported a supplier catalog, keep the original file and any import notes available. They help you compare what you meant to add with the records you see now.

Write down the part of the catalog you expect to review. That might be one supplier’s products or the collection you recently imported. Start there when assessing the matches, even if your scan covers more of the store.

Avoid combining an import cleanup with a general deletion of old products. A duplicate record and a discontinued product need different decisions. Keeping the tasks separate makes it easier to check whether you removed the items you intended.

Choose a matching field you can trust

A match is a reason to compare records. It is not proof that one should be deleted.

Titles can be useful when the same product appears twice with the same name. But a supplier may call several different products “Canvas tote bag.” Small wording differences can also leave two copies with different titles.

SKUs are useful when your catalog assigns them consistently. Check whether a repeated SKU represents an accidental copy, an intentional arrangement, or a data entry error on two different items.

Barcodes give you another field to compare when they are present. Missing or incorrect barcode data limits what that comparison can tell you. A matching barcode still needs a product and variant check before removal.

Here is a hypothetical catalog review:

What matches	What the records show	What to check next
Same title	Two tote bags with different sizes	Confirm whether they are distinct products you intend to sell
Same SKU	Two records for the same blue tote	Compare variants, images and descriptions before choosing a keeper
Same barcode	A current record and an older supplier import	Confirm both represent the same item and inspect which data is current
Same title and SKU	One complete record and one incomplete copy	Review the incomplete copy for any information the keeper still needs

Don’t delete a size or color option just because its name resembles another variant. Review the product it belongs to and the option values before treating the match as redundant.

Decide what makes a good keeper

The oldest record is not always the best one. Neither is the newest.

Before choosing, compare the fields your store relies on:

• Product title and description.
• Images and variant options.
• Prices, SKUs and barcodes.
• Inventory information and supplier references.
• Product links used in your navigation, campaigns or connected tools.

For the tote bag example, suppose the original record has the correct images and variants, while the new copy has an updated description. Keep the original if it is the record you want to continue using, but review and transfer the information you need before removing the copy.

Do not assume duplicate cleanup will merge those records or move their data for you. This guide describes choosing and removing records, not a product-merging workflow.

RP: Duplicate Finder & Delete supports manual keeper selection and oldest/newest keeper rules. Use a date rule only after checking that it gives the right result for the groups you intend to process. A consistent import pattern can make a rule useful; a mixed catalog deserves closer review.

Choose between archiving and deleting

Once you know which record to keep, decide what should happen to the other one.

Archiving retains the product record and lets you unarchive it later. Shopify describes product deletion as permanent. See Shopify’s product guidance and our guide to archiving versus deleting Shopify products before choosing.

The duplicate finder supports both actions. Its activity log lets you review cleanup actions, but an activity log is not a backup. Do not rely on it to recover deleted product data.

Start with a small group that you understand. Confirm your keeper, take the selected action, and check the result before applying the same approach more broadly.

Check the products you kept

After cleanup, open a few keepers and check their product details and storefront presentation. Confirm that the expected variants, images and prices are still there. Check links you know pointed to a removed record and update them where needed.

Before your next CSV import, check the product handles and overwrite setting. Shopify’s overwrite option matches existing products by handle, not SKU. Reimporting a file does not automatically mean it will create duplicate products. Review Shopify’s CSV import guidance before changing your import process.

Keep a note of which source file and matching field helped identify the problem. That gives the next person handling the catalog something more useful than “we deleted some duplicates.”

Start with one group of matching products

The Free plan for RP: Duplicate Finder & Delete includes 30 product deletions per year. The allowance is annual, not monthly. Unlimited costs $49 per year for unlimited product deletions, with prices in USD. Check the current Shopify listing for plan details before choosing a plan.

Explore the duplicate product finder, then start with a match you can verify. Choose the record you want customers to buy from before deciding what to remove.