You always notice duplicate SKUs at the worst possible moment. Right after a sale launches, during the year-end peak, the morning after a big batch of new products went live—you spot something off in the inventory, follow the trail, and end up at the punchline: the same SKU was assigned to multiple products or variants.
The tricky thing about duplicate SKUs is that day-to-day operations rarely surface them. Shopify does not strictly check SKU uniqueness when a product is created (same goes for barcodes). So if you accidentally hand out the same number, no error fires at that moment. It is only when a sync app runs that the link cannot resolve to a single target and the issue manifests as an error or inconsistency. In this article we cover how to live well with duplicate SKUs.
Why duplicate SKUs appear
There are a few common patterns behind duplicates. In rough order of frequency, here is what we see.
- When a product was duplicated, the SKU got copied along with it
- A CSV import registered multiple rows with blank SKUs as "unset"
- Different staff members used the same naming convention and independently issued the same SKU
- An old product was kept live (not archived) and the same number was reused on a new product
- A color variant existed but the trailing color code was never added
The first one—"copied from a product duplication"—is by far the most common pattern in the wild. When you press the Duplicate button in the Shopify admin, SKUs and barcodes are copied as is. You mean to fix them later, but you get pulled into editing the description or swapping images and forget to touch the SKU. That is the classic chain of events.
How to detect duplicates
Left alone, duplicate SKUs quietly multiply. That is why you need to detect them on a regular schedule. It is not complicated—the standard features of Google Sheets are more than enough.
How to surface duplicates in Google Sheets
Google Sheets has functions and features that are perfect for finding duplicates. The flow is: export all products from Shopify and load the CSV into a sheet. Then follow these steps.
- 01Select the SKU column, then go to Data, Data cleanup, Highlight duplicates
- 02Duplicate cells get colored, giving you a quick sense of how many there are
- 03For more detail, enter a formula like "=COUNTIF(A:A, A2)" in a helper cell to show how many times each SKU appears
- 04Filter to only the rows where the count is 2 or higher
- 05Copy the filtered results into a separate sheet and keep them as your duplicate list
Running this flow even once a month keeps duplicates from growing into a large problem. Weekly is ideal, but starting with monthly without overextending yourself is fine.
Use your sync app's warnings
Apps like Sync Master include warnings such as "The same key appears in multiple rows" in connection test and sync execution reports. If you have made connection tests a regular habit, you will catch duplicates early as they appear. The fact that it finds them automatically—without you opening the sheet and building formulas yourself—is a significant advantage.
Resolution options
Once you find a duplicate, the next step is the cleanup. Rather than blindly deleting one of them, choose your option based on the situation.
- Option A: rewrite one of them to a new, correct SKU (the most common move)
- Option B: archive the older one and keep only the active product live
- Option C: if this is a duplicate registration of the same product, delete one entirely and consolidate the inventory
- Option D: if the variant naming convention was too loose, rewrite the rules and reissue SKUs across the catalog
Use Option A when both are currently sold as distinct products. Option B is the right call when one is a discontinued item from years ago that was never cleaned up. Option C requires careful judgment. Confirm whether they really are the same product or just look similar, including by checking order history, before you execute.
Rules to stop duplicates from being created
After cleanup comes prevention. Duplicate SKUs are the kind of thing that, as long as humans assign them by hand, can show up at any time, so you need systemic safeguards.
- 01Document your SKU naming convention and keep it visible in your wiki and the sheet
- 02Before issuing a new SKU, always run a COUNTIF check against the existing list
- 03Make verifying SKU and barcode a required task immediately after duplicating a product
- 04Keep an SKU history sheet that includes archived products as well
- 05Once a month, always run your duplicate detection script or a connection test
The fifth one—"monthly detection"—is unglamorous but high impact. The sooner you find a duplicate, the easier the recovery. If you only notice it six months in, you can no longer accurately trace which orders were linked to which side, and the investigation alone can take a full day.
Another unglamorous but powerful rule is to forbid SKU reuse. Decide that an SKU from a discontinued product will never be reused on a new product, and you eliminate collisions with historical records. Remember the principle: SKUs are one-use.
Wrap-up: with duplicates, it is all about when you notice
As long as you are running a store, you cannot completely prevent duplicate SKUs. No matter how careful you are, a slip during duplication or an unexpected CSV import behavior will produce one. That is why what matters is when you notice. Catch it right after it happens and cleanup is a matter of minutes. Miss it for six months and you are looking at a full day of investigation.
Make three things habitual—monthly Google Sheets checks, your sync app's connection test, and verification right after duplicating a product—and duplicate SKUs drop from "worst possible moment" to "small daily task." Pick just one and start today.