Skip to content
Guide · product organisation

How to create SKU codes

A reference system takes an afternoon to design and ten years to live with. Here is what belongs in one, what absolutely does not, and the format decisions that are expensive to undo.

Written for people making physical products · jewellery, clothing, accessories, beauty. There is a free SKU generator that builds the codes described here.

What a SKU actually is

A stock keeping unit is one thing you can pick off a shelf and sell. Not a product · a sellable variant. A signet ring in gold in size 52 is one SKU. The same ring in silver in size 52 is a different one. The same ring in gold in size 54 is a third.

That sounds pedantic until the first time you need to know how many you have. "We have eleven signet rings" is useless if a customer wants gold in a 54 and you have eleven silvers in a 50. The SKU exists so that a count means something.

Three words get used interchangeably and should not be:

TermWhat it identifiesWho owns it
ModelThe design · "the signet ring"You
SKUOne sellable variant · gold, size 52You
GTIN (EAN/UPC)The same variant, globallyGS1 issues the prefix

You need models and SKUs from day one. You need a GTIN only when somebody else sells your product · more on that in the barcode guide.

What must never go in a SKU

One rule covers almost every disaster: nothing that can change.

All of these are real and useful · they are just attributes. They belong in columns beside the SKU, where they can change without breaking anything.

Building the format

A workable format is three to five segments, read left to right from the most stable to the most variable:

A format that holds up
TSD · RNG · 001 · GLD · 52

brand · category · model number · colour · size

Pick one separator · hyphen, dot, or nothing · and never mix. Sorting a column with TSD-RNG-001 and TSDRNG1 in it is an afternoon you will not get back.

Colour and size codes

Derive colour codes from the first three letters, then check for collisions by hand. "Gold" and "Golden" both give GOL, and now two products share a reference. The generator flags this, because it happens to almost everyone once.

Sizes are easier: use the number or the letter you actually print on the label. If you sell rings in both EU and US sizing, pick one for the code and keep the other as an attribute · a code that has to be converted is a code nobody trusts.

Numbering, and leaving room

Three digits gives you 999 models per category. For most brands that is a lifetime. For a brand selling small accessories at volume, it is four years. Decide which you are before you print anything, because going from 001 to 0001 later means every old code is a different length, and length is the one thing systems sort on.

Two more things worth deciding now:

Five mistakes that cost a reprint

  1. Starting with a digit. Open the CSV in a spreadsheet and 0012 becomes 12. Start every code with a letter.
  2. Spaces and slashes. They break URLs, filenames and half the imports you will ever do. Letters, digits and one separator, nothing else.
  3. Accented characters. DORÉ survives your laptop and dies in somebody else's system.
  4. Encoding the season. Covered above, and it is still the most common one.
  5. Two codes for one object. Usually from renaming a colour. Once a code is printed on anything, it is permanent · rename the label, keep the code.

Where SKUs live after you make them

A list of codes in a spreadsheet is the easy half. The hard half is a season later, when you need to know which prototype that code refers to, which supplier made it, which photos belong to it and whether the version in the lookbook is the one you approved.

That is the point where a spreadsheet stops being the right tool · not because it cannot hold the codes, but because it cannot hold what they point at.

Next, depending on where you are: barcodes if a stockist has asked for one, pricing once you know your real cost, or all the guides.

Where the reference meets the rest

In Teseo, a reference belongs to a product that carries its materials, its variants, its sample history, its supplier and its photos. Model numbers are allocated and stay stable when you rename things · which is the part a spreadsheet cannot do for you.

Questions

Can I change my SKU format later?

You can, but it is painful in proportion to how far you have got. Labels, invoices, your accountant's records, a stockist's system and anything you have already shipped all carry the old codes. The usual outcome is that both formats live side by side forever.

If you are going to change it, change it before your first production run, not after.

Should every colour have its own SKU?

Yes, if you hold stock of it separately · which you do. A SKU exists so that "we have four left" means something. If gold and silver share a code, the number four tells you nothing useful.

What about one-size products?

Leave the size segment out entirely rather than writing OS or ONE everywhere. A shorter code is easier to read and you can always add sizes to a future category without breaking the existing ones.

Do I need a separate code for a bundle or a gift set?

Yes. A set is a thing you hold in stock and sell · it is its own SKU, even though its contents have their own. Give sets their own category code so they are obvious in a list.