SKU Generator
Generate clean, consistent SKUs from a prefix, product attributes, and a numeric sequence — preview every combination and export as CSV. Runs entirely in your browser.
Product line or category, e.g. TSHIRT, MUG-15OZ.
e.g. colors: BLK, WHT, NVY
e.g. sizes: S, M, L, XL
3 → 001, 002…
TSHIRT-BLK-S-001
TSHIRT-BLK-M-002
TSHIRT-BLK-L-003
TSHIRT-BLK-XL-004
TSHIRT-WHT-S-005
TSHIRT-WHT-M-006
TSHIRT-WHT-L-007
TSHIRT-WHT-XL-008
TSHIRT-NVY-S-009
TSHIRT-NVY-M-010
TSHIRT-NVY-L-011
TSHIRT-NVY-XL-012Good SKUs are short, unambiguous (avoid O/0 and I/1 mixes), never reuse retired codes, and encode attributes consistently in the same order across your whole catalog.
Frequently asked questions
What makes a good SKU?
Short (8–16 characters), human-readable, consistent attribute order across the whole catalog (e.g. LINE-COLOR-SIZE-SEQ), no ambiguous characters (avoid mixing O with 0 and I with 1), and never reused after a product is retired. SKUs are for your operations — they are not barcodes and don’t need GS1 registration.
What is the difference between a SKU and a UPC?
A SKU is your internal identifier — you invent it, and the same product has different SKUs at different retailers. A UPC/EAN is a globally unique, GS1-licensed barcode number that stays with the product everywhere. Most sellers need both: SKUs for inventory, UPCs for marketplaces and retail.
Should I encode meaning into SKUs or use random codes?
For most small and mid-size catalogs, meaningful SKUs win: pickers and support staff can read them at a glance. Random codes only make sense at warehouse scale where software does all the reading. Whatever you choose, enforce one pattern — mixed conventions are worse than either.
Does this tool store my product data?
No. Everything is generated in your browser; nothing you type is transmitted or saved.