Catalog ops

SKU Generator

A SKU scheme invented ad hoc at product #5 becomes a warehouse mystery at product #500.

A good SKU encodes what a human needs at a glance — brand or line, category, variant, sequence — in a fixed, sortable pattern. TSH-BLK-M-001 tells a picker it's a t-shirt, black, medium, first of its line, without opening a single system. This generator takes your prefix, category code and variant list and produces the full combination set with zero-padded sequence numbers, so every future product follows the same scheme. Consistency is the whole game: mixed SKU styles are how mispicks, double-listings and unsellable stock start.

Want a calculator like this on your site? See the free embeds →

Frequently asked questions

What makes a good SKU format?

Short segments (2–4 characters), all caps, hyphen-separated, most-general to most-specific: LINE-CATEGORY-VARIANT-SEQUENCE. Avoid meaningless random SKUs (humans can't sanity-check them) and avoid over-encoding (price or supplier in the SKU goes stale). 8–16 characters total handles almost any catalog.

Should SKUs ever start with a zero or contain special characters?

No leading zeros on the whole SKU (spreadsheets strip them) and nothing beyond letters, digits and hyphens — marketplaces reject or mangle slashes, spaces and symbols. Zero-padding belongs inside the sequence segment (001, 002) where it keeps sorting correct.

Is a SKU the same as a barcode or UPC?

No. The SKU is your internal identifier — free, structured your way, unique per variant in your catalog. UPC/EAN/GTIN are purchased global identifiers the retail ecosystem shares. A product typically has both; this tool generates the internal one.

How do I handle variants like size and color?

Each sellable variant gets its own SKU — one per size-color combination, not one per product. List your variant codes (BLK-S, BLK-M, RED-S…) and the generator produces the full matrix, which is exactly the row set your inventory system expects.

More merchant tools