SKU generator
Design a reference system once, then generate every variant of every model in one go. Colours, sizes, numbering. Copy it, or take the CSV into your spreadsheet.
A system you will not regret
The test of a reference system is not today. It is the day you add a second category, the day a colour gets discontinued, and the day someone else has to find a piece from its code alone. Three rules carry most of it:
- Nothing in a code that can change. Not the price, not the season, not the collection, not the supplier.
- Leave room in the numbers. Three digits is a hundred models per category · four if you sell many small pieces. Renumbering later means reprinting everything.
- One format, forever. Mixing
TSD-RNG-001andTSDRNG1costs you an afternoon every time you sort a spreadsheet.
The longer version, with the mistakes that are expensive to undo, is in how to create SKU codes.
Questions
What is a SKU, exactly?
A stock keeping unit is one thing you can actually pick off a shelf and sell. A ring in gold in size 52 is one SKU. The same ring in silver in size 52 is a different one. "The ring" is not a SKU · it is a model.
That distinction is the whole reason SKU systems go wrong. If your code cannot tell gold-52 from silver-52, your stock count cannot either.
Is a SKU the same thing as a barcode?
No. A SKU is yours · you invent it, it means something to you, and nobody outside your company needs to agree with it. A barcode number (a GTIN, which includes EAN-13 and UPC-A) is a global identifier, it has a fixed length and a check digit, and you get the prefix from GS1.
Most brands need SKUs from day one and barcodes only when a retailer asks. We wrote a guide on barcodes and there is a barcode generator here too.
Should the price or the season be in the SKU?
No. Put nothing in a SKU that can change. Prices change, seasons get reissued, a product moves between collections. A code with SS26 in it becomes a lie the first time you carry a piece over, and then you have two codes for one object.
Season, collection, price and supplier are attributes. They belong in columns next to the SKU, not inside it.
How long should a SKU be?
Short enough to read aloud on the phone, long enough not to run out. Twelve to eighteen characters covers almost everything. Avoid spaces, accents, slashes and leading zeros that a spreadsheet will eat · this tool warns you about those.
Does this send my product names anywhere?
No. The whole tool is JavaScript running in your browser. There is no account, no upload and no request · you can watch the network tab while you use it.
What do I do with the CSV?
Open it in a spreadsheet and add your own columns · cost, price, supplier, stock. Or import it into whatever runs your catalogue. The columns are deliberately plain: reference, model number, colour, colour code, size.
A reference is only useful attached to something
In Teseo, a reference belongs to a product that also carries its materials, its variants, its prototypes, the supplier making it and the photos of it. Model numbers are allocated for you, and they stay stable when you rename things · which is the part a spreadsheet cannot do.