Handles, SKUs, and barcodes · verified 2 August 2026
Are duplicate handles, SKUs, or barcodes valid in a Shopify CSV?
Repeated handles can be intentional; duplicate SKUs or barcodes usually require review. Shopify product CSVs repeat a product's URL handle across its variant and additional-image rows. A SKU or barcode identifies inventory or a sellable item at variant level, so an accidental duplicate can confuse fulfilment, reporting, feeds, and integrations even when the CSV remains structurally parseable.
Why is the URL handle repeated?
The URL handle groups rows that belong to one product. A product with several variants needs several rows, and extra product images can use further rows. Repeating the same handle on those related rows is therefore expected. The important question is not “does this value repeat?” but “are all rows with this value part of the same continuous product block?”
If the same handle appears in separated blocks, the file may have been sorted or assembled incorrectly. CatalogVigil raises a warning for a non-contiguous product block because later rows can be misread or overwrite values in ways that are hard to review.
What does an intentional product block look like?
| Row | URL handle | Purpose | Review point |
|---|---|---|---|
| 2 | linen-shirt | First variant | Contains product-level data and complete Option1 values |
| 3 | linen-shirt | Second variant | Keeps the next option combination in the same block |
| 4 | linen-shirt | Additional image | Uses the same handle and an image URL |
| 5 | wool-cap | Next product | Begins a new product block |
If linen-shirt appears again after the wool-cap block, pause and compare the row with a fresh export. It might be deliberate in a supplier file, but it should not pass silently.
Why are duplicate SKUs different?
A SKU is commonly used by merchants and connected systems as a stock-keeping identifier for a variant. Shopify files can contain blanks, and business rules vary, so CatalogVigil treats duplicate non-empty SKUs as warnings rather than universal blockers. The same SKU might be intentional for a bundle or a legacy workflow, but it may also cause warehouse, ERP, marketplace, or feed systems to update the wrong item.
Review duplicates in the context of the full option combination, product handle, fulfilment system, and source of truth. If uniqueness is a business requirement, fix the source system rather than generating arbitrary suffixes during import.
What risks come with duplicate barcodes?
Barcodes are normally assigned to specific sellable items. A repeated non-empty barcode can lead scanners, marketplaces, or fulfilment tools to resolve to the wrong variant. Leading zeros are also significant: spreadsheet software may remove them or convert a long code to scientific notation.
Import barcode columns as text in spreadsheet software. Compare the exported CSV value—not only the displayed spreadsheet cell—with the source record. CatalogVigil can flag suspicious duplicates and formula-like values but cannot validate a barcode against an external registry.
How can sorting damage a product CSV?
Sorting the complete table by a chosen column keeps rows intact, although it can still separate product rows if the primary sort key is not the handle. Sorting one column by itself is destructive because values move without their corresponding product, option, price, image, or inventory cells.
- Keep every column in the selected sort range.
- Use URL handle as the primary grouping key when product rows must remain together.
- Preserve the intended variant order within each product.
- Keep additional image rows beside the product they describe.
- After sorting, check the first and last row of several product blocks.
Should CatalogVigil automatically deduplicate values?
No. Deleting a repeated handle could remove a variant or image. Rewriting a SKU or barcode could break the merchant's source-of-truth relationship. The safer response is to show every affected row, classify the risk, and let the operator decide whether the duplicate is structural, intentional, or erroneous.
A practical duplicate-review workflow
- Filter the issue report to the repeated identifier.
- Compare handle, Title, option values, SKU, barcode, and image fields across the affected rows.
- Confirm that repeated handles form one continuous product block.
- Check duplicate SKUs or barcodes in the inventory or fulfilment source of truth.
- Correct the authoritative source and export again when possible.
- Stage a small import and verify the exact variants in Shopify and connected systems.
Primary source: Shopify Help Center: product CSV format and row relationships. Duplicate SKU and barcode findings are conservative CatalogVigil advisories because acceptable business rules can vary.