SKU Crosswalk turns two catalogue files into a review of which source codes should map to which target codes. It suggests candidates and records your decisions. It does not update your shop or inventory system.
Start with two files
- Try the fictional sample to see an exact match, a pack conflict and duplicate candidates.
- Choose your source catalogue: the codes you want to map from. Choose your target catalogue: the reference codes you want to map to.
- Choose Delimiter for next file before opening it. The file-type default uses tabs for a
.tsvextension and commas otherwise. Select Semicolon, Pipe, Tab or Comma explicitly for another interpretation; semicolons and pipes are not guessed. Changing this choice leaves a loaded catalogue unchanged and abandons a pending read. Choose the file again to apply the new choice. - Use UTF-8 text with a header row containing unique, non-empty column names and the same number of fields in every record. The current limits are 50,000 data rows and 20 MB per file. XLSX workbooks are not accepted directly.
- Confirm the SKU column in each file. Product title, units per pack and dimensions are optional. Check the first-row preview and default dimension unit before comparing. Codes such as
00012stay text in the extension; keep the original files if a spreadsheet has already removed zeros.
Pack quantities must be positive whole numbers. Dimensions accept two or three ordered values, such as 10 x 20 cm. Supported units are millimetres, centimetres, metres and inches. A value the tool cannot interpret is unknown. It does not infer dimensions from product titles or treat rotated dimensions as equivalent.
Choose matching rules carefully
Surrounding spaces are trimmed for matching by default. You can also choose to ignore letter case, normalise Unicode width, or ignore spaces, dashes and underscores. These change the matching key; they do not rewrite the original codes. Broader rules can create collisions.
Candidates come from matching codes, an imported earlier alias, or an equal title when no code or alias candidate exists. An equal title is a reason to inspect a product, not proof of identity. This preview does not perform fuzzy title matching or infer product equivalence.
The default policy allows one source row per target code. If your task needs multiple supplier aliases to share a target, choose that policy and explain every approval in a review note. The same exact source code cannot be approved to different target codes.
Review every mapping
Select a source row, inspect the suggested target and compare the original product information. A supplied pack or dimension conflict blocks approval. Missing or unrecognised attributes, or different titles, require an explicit acknowledgement after you check them yourself.
Use Find a different target with at least two characters to search by code or title. You can add a note, approve the mapping, or leave it unresolved. Undo this row removes its decision; Undo review reverses the last review action, including a batch action. Changing source files, column selections or matching rules clears the current review after confirmation.
Review exact-match batch is a deliberate shortcut for eligible unique original-code matches with supplied, matching pack and dimension values and no remaining attribute warnings. It excludes ambiguous and normalised-code matches. Nothing is approved until you confirm the batch.
Export and keep your work
The review ZIP contains approved mappings CSV, unresolved rows CSV, an audit JSON and a readme. Every source row belongs to the approved or unresolved output. These are review outputs, not a ready-made import template for a particular platform; check the destination's requirements first.
CSV prefixes formula-like text with an apostrophe for spreadsheet safety. Use the JSON audit to recover literal original product codes. Keep notes and exports private when they contain business information.
Save workspace opens a passphrase dialog. Enter and confirm a long, unique passphrase of at least 12 characters, then choose Encrypt and save. Paste from a password manager is allowed. Spaces, letter case and the exact characters are significant. There is no recovery key if you forget it.
This deliberately keeps one encrypted copy in the current browser profile. Save again after later review changes. A successful save replaces the previous copy; a failed or cancelled save before the storage write keeps it. Once a storage write has been submitted, the dialog asks you to wait because that write cannot be cancelled. If another tab changed or deleted the saved copy, close the dialog and start a new action; that tab's change is kept.
The encrypted saved copy has an 8 MB limit. Large imports may not fit even when each input file was accepted. The review ZIP does not contain the complete catalogue workspace and cannot restore it. Keep the original catalogue files and your passphrase as well as the exported review. CSV, ZIP and JSON downloads are readable files; saving an encrypted workspace does not encrypt these exports. An earlier audit can supply alias suggestions for a new comparison; those suggestions require fresh approval.
Restore asks for the exact passphrase and rechecks a compatible saved copy's catalogue fingerprints and decisions before replacing current work. It opens the copy captured when the dialog was opened; another tab may have saved a newer copy since then. An older plaintext save offers a separate Open older unencrypted save choice. Opening it does not encrypt it; choose Encrypt and save afterward to replace it.
Start again opens a Clear current workspace? confirmation before clearing loaded catalogues, review decisions and notes, reviewer reference, aliases, column mappings and matching choices. Save or download first if needed. Choose Cancel or press Escape to keep current work; choose Clear current workspace to clear it. Any separately saved copy stays available under Restore.
Requesting Start again may cancel an unfinished Save workspace or Restore operation. Cancel keeps the current workspace and does not change any saved copy, but does not resume that cancelled operation; start it again if needed. A submitted storage write blocks reset until it finishes.
Delete the save separately in Privacy and data controls; deletion does not require its passphrase. Neither action removes downloaded files. The optional reviewer reference belongs to the current export and is not saved in the workspace.
The current preview has no checkout or paid feature restriction.
Looking for another detail?