Find identifiers shared by different variants
Check a variant CSV for shared SKUs or barcodes, missing identifiers, scientific notation and supported GTIN check-digit errors.
When is a repeated barcode a variant conflict?
A barcode shared by different variant IDs is a conflict for this review. Repeated rows for the same variant ID do not create that cross-variant collision. The same rule is applied to SKU values.
Input requirements and report limits ↓Inputs
Copy a table from Excel or Google Sheets, including its header row, and paste it below. CSV/TSV files also work. Use “Map your columns” for different headers. IDs stay as text.
Free: UTF-8 CSV/TSV · 200 KB / 500 rows per input · 5 successful reviews per browser per day. CSV calculations run locally.
Need larger files or repeat batches? View editions →
Reuse a column profile
A profile stores column names only. It does not store your file contents.
Review report
Before you use this review
| Bring | Catalog variant identifiers, SKUs and barcodes preserved as text. |
|---|---|
| Check | Shared identifiers across different variant IDs; supported numeric GTIN lengths are 8, 12, 13 and 14 digits. |
| Read the result | Missing identifiers, collisions, scientific-notation warnings and supported check-digit failures. |
| Cannot establish | GS1 ownership, product identity, recovery of rounded digits or validity of every custom barcode format. |
Required input
Provide variant_id, sku, barcode, with one barcode per row. Variant ID is required. Keep identifiers as text so spreadsheet formatting does not remove leading zeroes or replace long codes with rounded scientific notation.
What is checked?
The report flags missing SKUs and barcodes, identifiers shared across variants, scientific-notation patterns and incorrect check digits for numeric GTINs of 8, 12, 13 or 14 digits. Other nonempty formats are marked for custom-barcode review, since some systems allow them.
A valid check digit does not verify GS1 ownership or confirm that the barcode belongs to the intended product. Already-rounded spreadsheet data cannot be recovered. This tool does not validate every relationship within repeated rows or update a catalog. Use Variant Audit when reviewing product handles and option combinations.
How do I check duplicate barcodes in an Excel export?
Keep variant IDs, SKUs and barcodes as text, then paste the header and data rows or export CSV/TSV. The file picker does not accept XLSX workbooks. Review identifiers shared by different variant IDs; repeated rows for the same variant alone do not create a collision.
Can this repair barcodes shown in scientific notation?
No. A notation warning helps you find rows to check, but cannot restore digits that Excel already rounded or removed. Return to the original catalog export and import identifier columns as text before checking again. A clean check-digit result is not proof of product identity.
Prepared by Supplier Desk Team · Updated . Examples are synthetic.
Who this is for
Small retail and wholesale operations teams reviewing supplier exports before changing catalog, stock or purchasing records. This is a focused review worksheet; it does not connect to your store or post transactions.
Related background
Read the source discussion or documentation. This describes the broader workflow. Use the input requirements and calculation rules above to decide whether this particular check fits your task.
Free tools with optional offline batch editions. Higher file limits, saved batch configurations and grouped report exports. No automatic store changes.