SKU Naming Conventions: Rules and Examples
A well-designed SKU naming convention makes stock readable at a glance, speeds up picking, and prevents the duplicate and clashing codes that quietly corrupt your inventory data. This guide gives you a set of copyable rules, a structure table you can adapt, and worked examples across apparel, food and electronics — plus the mistakes that turn a tidy scheme into an unusable mess. Copy the structure below and fill in your own attributes.
What a SKU is (and is not)
A SKU (stock-keeping unit) is an internal code your business assigns to identify a distinct sellable item — a specific product in a specific variant, such as a particular size and colour. It is not a barcode: a UPC or EAN barcode is a global identifier owned by GS1, while a SKU is yours to design and control. Good SKUs are meaningful to your team, unique per variant, and stable over the product’s life.
The core rules of a good SKU convention
- Make it unique per variant. Every size, colour or pack quantity that you track separately needs its own SKU.
- Keep it short but readable. Aim for roughly 8–16 characters; long enough to be meaningful, short enough to scan and print.
- Go from general to specific. Lead with category or brand, then product, then variant attributes. This groups related items when sorted.
- Use a consistent separator. Pick one delimiter (a hyphen is safest) and use it everywhere.
- Use only safe characters. Uppercase letters and digits only. Avoid spaces, slashes, and letters that look like numbers.
- Never start with a zero. Spreadsheets strip leading zeros, silently changing your codes.
- Do not encode price or cost. Those change; the SKU should not.
- Document the scheme. Keep a key of every segment and its allowed codes so the convention survives staff changes.
A copyable SKU structure
Design your SKU as a fixed sequence of segments. Copy this table and replace the segments with the attributes that matter to your catalogue.
| Segment | Meaning | Length | Example codes |
|---|---|---|---|
| 1 — Category | Broad product type | 2–3 chars | TSH (t-shirt), MUG, HDP (headphones) |
| 2 — Brand or line | Brand, supplier or range | 2–3 chars | ACM (Acme), NKE, OWN (own brand) |
| 3 — Product | The specific style or model | 3–4 chars | CREW, 2024, PRO2 |
| 4 — Variant A | Colour, flavour or material | 2–3 chars | BLK, RED, VAN (vanilla) |
| 5 — Variant B | Size or pack quantity | 1–3 chars | S, M, L, XL, 06 (6-pack) |
Joined with hyphens, this yields a pattern like CATEGORY-BRAND-PRODUCT-COLOUR-SIZE, for example TSH-ACM-CREW-BLK-M.
Worked examples across three catalogues
| Product | SKU | How it reads |
|---|---|---|
| Acme crew-neck t-shirt, black, medium | TSH-ACM-CREW-BLK-M | T-shirt · Acme · Crew · Black · Medium |
| Acme crew-neck t-shirt, white, large | TSH-ACM-CREW-WHT-L | T-shirt · Acme · Crew · White · Large |
| Own-brand vanilla protein, 1kg tub | SUP-OWN-WHEY-VAN-1K | Supplement · Own · Whey · Vanilla · 1kg |
| Pro headphones, blue, single unit | HDP-NKE-PRO2-BLU-01 | Headphones · Nike-style brand · Pro2 · Blue · 1 |
| Cola, 320ml, 6-pack bundle | BEV-OWN-COLA-320-06 | Beverage · Own · Cola · 320ml · 6-pack |
Notice that variants of the same product share the leading segments, so they sort together, while the trailing segments make each variant unique and instantly readable at the pick face.
Handling bundles, kits and multipacks
A bundle or kit is a sellable unit made of other SKUs, so it needs its own SKU — do not reuse a component’s code. A clear approach is to add a segment or prefix that flags it as a bundle, for example KIT- or a trailing pack count like -06. Your inventory system should then map the bundle SKU to its components so that selling one bundle correctly decrements each part. Keeping bundles as distinct SKUs prevents the double-counting that otherwise corrupts availability.
Smart versus sequential SKUs
There are two philosophies. Smart (intelligent) SKUs encode meaning in each segment, as above; staff can read them without a lookup, which speeds picking and reduces errors. Sequential (non-significant) SKUs are simple running numbers like 100001, 100002; they never run out of structure and cannot mislead when attributes change, but they mean nothing without the system. Many growing retailers use smart SKUs for daily readability, and let the software carry a separate internal ID for machine use. Choose smart if humans handle stock often; choose sequential if the catalogue is vast and volatile.
Common mistakes to avoid
- Reusing a retired SKU. Recycling an old code for a new product corrupts historical sales and returns data. Retire codes permanently.
- Leading zeros and ambiguous characters. A code starting with 0, or mixing O and 0, or I and 1, breaks in spreadsheets and misreads at the shelf.
- Encoding volatile data. Baking price, cost or a supplier’s own part number into the SKU means every change forces a renumber.
- Inconsistent separators or lengths. Mixing hyphens, slashes and underscores, or varying segment lengths, defeats sorting and filtering.
- Using the manufacturer’s barcode as your SKU. The barcode is fine to store, but it is not readable to your team and may repeat across suppliers.
- Not documenting the key. Without a written scheme, new staff invent their own segments and the convention drifts within months.
How WhiteBox helps
WhiteBox lets you manage SKUs, variants and bundles as one real-time source of truth, mapping bundle SKUs to their components so stock decrements correctly and never double-counts. Because stock syncs across Shopify, Lazada, Shopee, Amazon and TikTok Shop, your SKU scheme stays consistent on every channel, and barcode picking ties each code to the physical unit. Explore the inventory features or start a free trial.
Frequently asked questions
What is a SKU naming convention? It is a consistent set of rules for how you build stock-keeping codes — which attributes appear, in what order, with which separators — so every SKU is unique, readable and sortable.
How long should a SKU be? Around 8–16 characters is a good balance: long enough to encode meaning, short enough to scan, print and read aloud without error.
Is a SKU the same as a barcode? No. A SKU is your internal code that you design and control; a barcode (UPC/EAN) is a global identifier from GS1. You can store both against the same item.
Should SKUs contain meaning or just be numbers? Smart SKUs encode meaning for fast human reading; sequential SKUs are simple running numbers. Choose smart when staff handle stock often, sequential for very large, fast-changing catalogues.
Can I reuse an old SKU for a new product? Avoid it. Reusing a retired code mixes the histories of two products and corrupts sales, returns and forecasting data. Retire codes for good.
Related reading: Inventory Management Guide, Inventory Audit Checklist, Stocktake Checklist and Free Template, Best Inventory Management Software in Singapore.
