SKU checker for duplicate product codes

Find repeated SKUs and review codes that collide under your chosen matching rules. Your entries and files stay in your browser.

Choose your product codes

Source

One SKU per line. Up to 10,000 rows and 2 MB.

Choose matching rules

Letter case
Whitespace
Punctuation

Apply your format rules

Rows to review

5 of 6

Findings apply to your supplied list and selected rules.

Findings by type

Exact duplicate groups

1

Potential collision groups

1

Blank SKU cells

1

Missing SKU cells

0

Rows with format warnings

0

Six rows checked. Five rows need review.

Row findings

SKU findings by source row
RowReferenceOriginal SKUFinding
1None"00123"Exact repeat E1. Identical original value in 2 rows.
2None"00123"Exact repeat E1. Identical original value in 2 rows.
3None"blue-01"Potential collision N1. Different originals share a match after your selected normalisation.
4None"BLUE-01"Potential collision N1. Different originals share a match after your selected normalisation.
5None""Blank cell. The SKU cell is empty or contains only whitespace.

Showing all five findings.

JSON report with original SKU strings and row references.

Choose which product codes to check

Paste one stock keeping unit (SKU) per line, or choose a local CSV and select its SKU column. An optional reference column identifies the product or variant beside each finding.

The checker reads codes as text, so 00123 stays different from 123. If another application has already removed leading zeroes, load an export that retains them.

A blank cell contains no text or only whitespace. A missing cell means a short CSV record ends before the selected SKU column. Those findings stay separate.

CSV record 1 is the header. A quoted field with line breaks remains one record. Commas and doubled quotes inside quoted fields follow the documented CSV format.

Lists accept up to 10,000 rows. CSV files accept up to 10,000 records including the header, with at most 100 columns. Both sources have a 2 MB limit.

Set exact or normalised matching

Exact duplicates have identical original values, including their letter case and spaces. The checker always reports those groups.

Normalised matching also reports different originals that become equal under your chosen options. These are potential collisions for review. The checker keeps the original codes unchanged.

Ignore case converts letters to lowercase for matching. Trim ends removes surrounding whitespace. Remove all removes whitespace throughout a code. Remove punctuation removes Unicode punctuation, including hyphens and underscores.

The default ignores case and trims surrounding whitespace while keeping punctuation. Accents remain, and the checker does not merge different Unicode representations of the same visible letter.

An exact group can also belong to a potential collision group when another, different original matches it after normalisation. Group labels beginning E identify exact groups. N identifies normalised groups.

Inspect a small catalogue example

The fictional example starts with six rows. Rows 1 and 2 both contain 00123, so they form one exact duplicate group.

Row 3 contains blue-01 and row 4 contains BLUE-01. Ignoring case puts them in one potential collision group. Row 5 is blank. Row 6 contains SKU_9 and raises no finding.

The default result is five of six rows to review, with one exact group, one potential collision group and one blank cell. No format rule is selected.

Keep case separates rows 3 and 4, leaving three rows to review. Reset example restores every default, including the pasted list.

Repeated variant references remain separate source rows. Use the row number as well as the reference to find the correct record.

Apply your own SKU format rules

Enter minimum or maximum lengths only when your catalogue has those rules. Length counts Unicode characters in the original value, including spaces. A combined accent can count as another character.

Letters and digits accepts Unicode letters and numbers. The next option also allows hyphens and underscores. Your character set checks each original character against the exact characters you enter.

Format rules check original values before normalisation. A space can therefore raise a format warning even when trimming lets its code match another row.

These settings describe your conventions. A warning is not proof that a platform rejects the SKU, and a clear report does not certify an import.

Review the conflict report before importing

Download findings to keep a row-level JSON report with your settings, group labels and original SKU values. JSON preserves leading zeroes and formula-like text as strings.

The on-page table shows 25 findings at a time. Show more reveals the next 25. The download includes every finding, and one source row can have several findings.

The tool reports conflicts without renaming codes or updating your catalogue. Review each record against your intended products before changing the import file.

It does not look up live stock, identify products from a code or connect to a platform account. Closing or reloading the page clears the supplied data.