Seller guide
How do I normalize marketplace SKUs without creating collisions?
A safe batch-first workflow for standardizing SKU case, separators, and length without turning two distinct supplier or channel identifiers into the same value.
Treat a SKU as an inventory key, not display copy
A SKU can connect listings, inventory, labels, purchase orders, returns, and warehouse records. Changing punctuation may look cosmetic while breaking those joins. Name the seller-owned source of truth first, export every active and reserved SKU from it, and keep the original value beside every proposed value. Do not rename directly in one marketplace and hope the other systems catch up.
Write one explicit convention before touching the batch
Choose case, one separator, and a maximum length. Decide whether spaces, slashes, accented letters, and punctuation become separators or are removed. Keep the rule mechanical: a convention such as uppercase ASCII with hyphens is testable; an instruction such as 'make it clean' is not. Product meaning should remain in verified source fields rather than being inferred during cleanup.
Normalize every current and proposed SKU before checking uniqueness
Collision detection must happen after the transform. 'NW Bottle Blue', 'nw_bottle_blue', and 'NW-BOTTLE-BLUE' are distinct raw strings but collapse under an uppercase-hyphen rule. Length truncation creates another collision path when long variants share the same prefix. Compare the whole proposed batch with the normalized current catalog before assigning any replacement.
Resolve collisions with a ledger, then update dependencies deliberately
Use a deterministic suffix only after confirming which records represent different products. Record old SKU, proposed SKU, collision reason, chosen replacement, and every downstream system that needs review. A suffix makes the request unique; it does not prove that the identifier is free in a marketplace or that labels, orders, and integrations have been reconciled.
Tools that help with this
- Free blank marketplace upload preparation templates (free)
- SKU Naming-Convention Normalizer ($0.25) — Normalize a bounded batch, group post-transform collisions, and draft unique alternatives
- Cross-Listing Field Mapper ($0.25) — Keep source values and target-channel review gaps visible during cross-listing
- Bulk CSV Marketplace Listing Audit ($1.00) — Check the prepared listing CSV for duplicate SKUs and structural errors
Every paid output is a draft for your review before you publish, appeal, or activate anything. Friday does not access your seller account.