Skip to content

SKU consistency checker

Review repeated SKUs and shared comparison keys

Paste one SKU per line to see blanks, exact repeats and different spellings that share a comparison key. Keep the original text and line numbers visible while you decide what needs review.

A repeated SKU can be legitimate across purchase lots. This tool previews a comparison; it does not validate an import or decide which purchase a payout belongs to.

Check a SKU list

1. Check a list

Use a plain list with no header. Choose Check SKUs to create a report, Load example to try the invented list below, or Clear to remove the list and report. Editing the list removes the previous report so it cannot describe an older version.

Preparing checker controls. The method and worked example below remain available.

Paste plain text, up to 500 lines and 100,000 characters. This is a comparison preview, not a CSV upload or import validator. Nothing is saved as an import.

CRLF, CR and LF separate lines. One final line ending finishes the last line; another adds a blank line. Visual wrapping adds no lines. Characters are Unicode code points after line endings become LF, including the final line ending.

Back to contents

2. Understand the comparison

Each line keeps its original text. For comparison only, the checker trims whitespace from the two edges and converts the remaining text to uppercase using the same comparison operation as ResaleCraft's item-code matching. It does not remove inner spaces, punctuation or leading zeros.

Blank line
A line whose comparison key is empty, including a line containing only whitespace removed at the edges. Blanks are kept with their line numbers and excluded from repeated-identifier groups.
Exact repeat
The same nonblank original text appears on more than one line. Its spelling, case and spaces are identical.
Shared comparison key
Two or more nonblank lines produce the same key. A group may contain exact repeats, different spellings, or both. A mixed group keeps each spelling and all its line numbers visible.

The flagged-line count includes each blank line and each nonblank line in a shared-key group once. Exact-repeat patterns and groups with different spellings describe overlapping categories; adding those counts would misstate the total.

This is a precise preview of this comparison operation, not a universal Unicode or database equivalence rule. Visually similar characters, accents and other spellings can still produce different keys. A different key does not prove a different product.

The report makes hidden spacing and format characters visible with notation such as \u{200B} for a zero-width space. This changes how the text is displayed, while the original value and comparison key stay unchanged.

Back to contents

3. Worked example: one mixed group and one blank

This invented nine-line list has no header and no final line ending. Quotation marks below make the original values' edge spaces visible; the quotes are display notation, not part of the input.

On a narrow screen, scroll the table horizontally to read every column.

Invented SKU list and expected comparison keys
LineOriginal textComparison keyReview note
1"ARC-17""ARC-17"Exact repeat of line 2; shares a key with line 3.
2"ARC-17""ARC-17"Exact repeat of line 1; a separate purchase lot may legitimately reuse it.
3" arc-17 ""ARC-17"Different spelling: case and edge spaces change the text, not this key.
4"0007""0007"Leading zeros remain. This key differs from line 5.
5"7""7"A different key from 0007; that does not prove a different product.
6"BOX 2""BOX 2"The inner space remains.
7"BOX-2""BOX-2"The hyphen remains. This key differs from line 6.
8""""Blank line; counted separately from shared keys.
9"PIN-9""PIN-9"No shared key within this example.

Expected result: 9 lines, 1 blank, 1 shared-key group and 4 flagged lines. The three ARC-17 lines count once each; blank line 8 adds one.

There is 1 exact repeated text pattern, on lines 1 and 2, and 1 group with different spellings, on lines 1–3. These overlap in a mixed group. Repeating ARC-17 across two purchase lots can be correct; review the intended lot before changing either identifier.

Back to contents

4. Input rules and limits

  • Enter one identifier per line, without a header. A first line reading SKU is treated as an identifier. Commas and quotes remain literal text; CSV quoting and columns are not parsed.
  • CRLF, bare CR and LF are line separators. One final separator finishes the last line without creating another row. An additional separator creates a blank row: A followed by two line endings is one identifier and one blank.
  • Leading and interior blank rows remain in the report. A nonempty list containing only whitespace or line endings is reviewed as blank rows; an empty input asks you to enter a list.
  • The limits are 500 lines and 100,000 characters. Characters mean Unicode code points after CRLF and CR become LF; every line break, including a final one, counts. A visible character formed from multiple code points can count more than once. Visual wrapping in the text area adds no input rows.
  • If either limit is exceeded, the entire check is rejected with no partial report. The checker does not silently shorten the list.

The checker performs no upload, external lookup or inventory change. It does not test GTINs, marketplace rules, workspace uniqueness or whether an import would succeed. It only compares the list you enter.

Back to contents

5. Review before matching a purchase

Check the original records before standardizing spelling or removing a repeated line. Separate lots can share a SKU, while lookalike identifiers can refer to different products. A SKU key alone is not enough for payout matching: the channel, purchase status, available quantity and intended purchase also matter.

Repeated external import references follow a different rule from reused SKUs. See the CSV preview and correction guide for the actual import fields and errors, and payout purchase matching for ambiguous matches. If you are still evaluating inventory, use the reseller buying checklist.

Back to contents

6. Source and scope

The comparison preview follows ResaleCraft's current item-code comparison. The example is invented and does not use customer or supplier data.

For another product's spreadsheet workflow, Lightspeed documents finding duplicate SKUs in a product CSV. That guidance concerns Lightspeed's product rules; it does not establish universal SKU uniqueness or validate a ResaleCraft import.

Back to contents

Start with a sample

Follow one buy all the way through.

The guided demo uses sample data. No email is required, and practice changes are not saved to a real workspace.

Sample demo Open now

Sample opportunities, payouts and results. Nothing you try is real performance evidence.

Explore the demo

Pilot workspace By invitation

Your own records, after a separately approved invitation. Requesting access does not create an account.

Request pilot access