What is a SKU and how do you create one?
A SKU is a unique internal code identifying one exact product variant. Build one from meaningful segments, typically category, brand, size, colour and a sequence number, joined consistently. Slaytic generates every combination across your variants at once so the scheme stays uniform.
How this works in your browser
Segments are normalised to uppercase alphanumerics, truncated to the segment lengths you set, and joined with your chosen separator, with a zero-padded sequence appended. Ambiguous characters are avoided in generated sequence values for the same reason coupon codes avoid them: these get read aloud and typed by hand far more often than people expect. Batch mode takes the cartesian product of the attribute lists you supply, which is what makes generating an entire size and colour range a single step. Everything runs in your browser.
Who uses SKU Generator
Setting up a new catalogue
Define a scheme once and generate codes for the whole range.
Adding a product line
Extend an existing scheme consistently rather than improvising.
Size and colour variants
Generate every combination in one batch.
Migrating from ad-hoc codes
Replace inconsistent legacy codes with a structured scheme.
Frequently asked questions
What makes a good SKU?
Short, readable, and structured so a person can decode it at a glance. Roughly eight to twelve characters, most significant attribute first, and a consistent segment order across the whole catalogue. If someone has to look a code up to know what it is, the scheme is not doing its job.
Should a SKU contain the barcode or UPC?
No. A UPC or EAN is issued by GS1 and identifies the product globally; a SKU is yours and identifies it within your business. Keep them as separate fields, because you will want to change your internal scheme at some point and you cannot change a registered barcode.
What should I avoid in a SKU?
Letters and digits that look alike, notably capital O against zero and capital I against one, since codes get read aloud and typed by hand. Also avoid starting with a zero, because spreadsheets strip leading zeros and will quietly corrupt your whole list on import.
Should the SKU encode the price?
No. Prices change and SKUs should not, otherwise every price rise orphans your stock history. Encode durable attributes such as category, size and colour only.
Is my product data uploaded?
No. Codes are generated in your browser, so an unreleased range stays confidential.