A SKU number is an internal code you create to identify one exact version of one product: this size, this color, this flavor. Square’s small business guide defines it as “a unique code that retailers create to track their products internally,” usually up to eight alphanumeric characters. You invent your own. Nobody assigns them to you.
That is the whole idea, and it is also why SKUs go wrong. Because you invent them, nothing stops you from inventing three codes for the same croissant. Once that happens, every count, every reorder point, and every sales report built on top is quietly wrong.
This guide covers how to design a SKU structure you can read at a glance, how to apply it, and how to use the resulting data to reorder and to price. It is the layer underneath everything else, and the reason a clean SKU scheme has to exist before you shop for warehouse inventory management software, not after.
Save 80% of delivery management time
We handle everything:
- Dedicated operations manager
- Real-time tracking dashboard
- Automated customer notifications
- Urgent issue resolution
The Bottom Line
- A SKU is yours; a UPC is not. You create SKUs. UPCs come from GS1, which sells individual GTINs for $30 each or a company prefix starting at $250.
- Structure beats randomness. Category, then product, then variant, then size, always in the same order, so staff can read a code without looking it up.
- 8 to 12 characters, letters and numbers only. No spaces, slashes, or punctuation. Start with a letter.
- One product, one SKU, forever. Duplicate codes for the same item are the single most common cause of wrong counts.
- The payoff is in the reports. Consistent SKUs are what make sell-through, reorder points, and slow-mover reports trustworthy.
- Never encode the price. Prices change; codes shouldn’t.
What a SKU number tells you
A good SKU answers four questions without anyone opening a system: what kind of product this is, which product in that category, which variant, and what size or pack.
Take BRD-SRD-LRG. Category bread, product sourdough, size large. A picker reading a shelf label knows immediately whether they are holding the right thing. Compare that to 10045127, which is correct, unique, and completely mute.
This readability is not cosmetic. It determines:
- Picking accuracy. Staff distinguish near-identical items on sight instead of guessing.
- Count accuracy. During a physical count, a readable code is self-checking, because you notice when the label doesn’t match the box.
- Report quality. Category prefixes let you total sales by product line without building a separate taxonomy.
- Reorder decisions. Variant-level codes show you that the large sells and the small doesn’t, which an item-level code hides.
SKU vs UPC vs serial number vs part number
These get mixed up constantly, and mixing them up leads to costly mistakes.
| Code | Who creates it | What it identifies | Unique per |
|---|---|---|---|
| SKU | You | One sellable variant in your business | Variant, within your business |
| UPC / GTIN | GS1 assigns the prefix; you apply it | The product globally, across every seller | Product, worldwide |
| Serial number | The manufacturer | One individual physical unit | Single item |
| Part number | The manufacturer | A component or model as the maker names it | Component, per manufacturer |
| Lot or batch number | You or your supplier | A production run | Batch |
Two practical consequences. First, as Square puts it, “a product has the same UPC no matter where it’s sold, but different stores assign it different SKUs,” so you cannot use a UPC to mean your own packaging or bundling. Second, a serial number is not a SKU: a hundred units of the same mixer share one SKU and have a hundred serial numbers.
If you sell through retailers or distributors, you will need UPCs as well as SKUs. GS1 US sells individual GTINs at $30 each, or a company prefix from $250 if you have a growing product line.
How to create a SKU number system
Six steps. Do them in this order, and do them once for the whole catalog rather than product by product.
1. List your attributes, then pick three or four. Usually category, product, variant, and size. Resist adding supplier, year, or location unless you will filter by them. Every extra segment makes the code longer and less readable.
2. Fix the order and never change it. Broadest first. CATEGORY-PRODUCT-VARIANT-SIZE. The order is what lets someone scan a shelf and spot the odd one out.
3. Choose segment lengths and stick to them. Three characters per segment is a good default. FLW-ROS-RED-12 is instantly parseable; FLWROSRED12 is not.
4. Use letters and numbers only, starting with a letter. No spaces, slashes, commas, or symbols. Slashes and leading zeros break in spreadsheets and some systems, and a leading-zero code is the classic way to lose 012 to 12.
5. Keep it to 8–12 characters. Long enough to encode meaning, short enough to type, read aloud, and fit on a label.
6. Write it down and assign one owner. A one-page document listing every category prefix, plus one person who issues new codes. This is the step everyone skips, and it is the reason duplicate SKUs appear six months later.
Then label everything. A SKU that exists only in a spreadsheet does no work on the warehouse floor.
SKU number examples by business type
Bakery: BRD-SRD-LRG (sourdough, large), PAS-CRO-CHC-06 (pastry, croissant, chocolate, 6-pack), CAK-VAN-08 (cake, vanilla, 8-inch).
Florist: FLW-ROS-RED-12 (roses, red, dozen), ARR-BRD-MED (arrangement, bridal, medium), VAS-GLS-TAL (vase, glass, tall).
Catering: TRY-SAN-VEG-20 (tray, sandwiches, vegetarian, serves 20), EQP-CHF-STN (equipment, chafing dish, stainless), BEV-COF-URN (beverage, coffee urn).
Wholesale food: OIL-OLV-XV-05L (olive oil, extra virgin, 5 litre), CHS-MOZ-FRS-CS (cheese, mozzarella, fresh, case), FLR-BRD-25K (flour, bread, 25kg).
Notice what’s missing from all of these: price, supplier name, and the year. Those change while the product stays the same.
SKU numbering mistakes that break your counts
- Duplicate codes for one item. “Choc Croissant,”
choc-croissant, andCC-LRGas three products means three partial counts, three slow-mover flags, and zero usable data. - Reusing a retired SKU. When a discontinued code comes back on a new product, your sales history becomes a blend of two different things.
- Encoding the price.
CRO-350is wrong the day you change the price, and then you either lie or relabel everything. - Copying the supplier’s part number. Suppliers change part numbers, and two suppliers can collide. Map theirs to yours instead.
- Letting the webstore invent its own. If your online channel auto-generates SKUs, you now have two catalogs that disagree. Push your codes into it.
- Leading zeros and special characters. Spreadsheets eat them, and so do some imports.
- Codes nobody can read aloud. Staff call out SKUs on the phone and across a stockroom. If a code is ambiguous spoken, it is the wrong code. Avoid pairing I with 1 and O with 0.
Where to find a SKU number on a product
On your own products, the SKU is wherever you put it: usually a shelf label, a printed barcode label, or the packing slip. It is not printed by the manufacturer, because the manufacturer doesn’t know it.
On something you bought from a retailer, the SKU appears on the price tag, the receipt, or the product page of that retailer’s website, and it will differ from store to store. The 12-digit number under the barcode is the UPC, not the SKU.
To look up a SKU, search your own inventory system or point of sale by product name. There is no public SKU database, and there can’t be, because the codes are private to each business. Any tool promising a universal SKU lookup is searching UPCs instead.
How to use SKU data to reorder at the right time
Codes are only worth maintaining because of what you can do with the data afterwards. Reordering is the first payoff.
For each SKU, three numbers turn history into a decision:
- Average weekly usage. Units sold per week over a representative period, not last week alone.
- Lead time. Days from placing the order to having it on the shelf, including receiving.
- Safety stock. The buffer that covers a bad week or a late supplier.
Your reorder point is weekly usage divided by seven, times lead-time days, plus safety stock. A cheese case selling 42 units a week with a 5-day lead time and 20 units of safety stock triggers a reorder at 50 on hand.
This only works at variant level. If large and small share one code, average usage is a blend of a fast mover and a slow one, and you will reorder both wrong.
How SKU-level sell-through drives pricing decisions
Sell-through rate, units sold divided by units received over a period, is the report that tells you which products deserve shelf space. At SKU level it gets specific enough to act on.
Three bands, three actions:
- High sell-through, frequent stockouts: raise the reorder point, or test a higher price.
- Middling sell-through: leave it alone and watch for seasonality. If you do decide to discount, do it deliberately: there are markdown strategies that protect margin rather than just cutting the price.
- Low sell-through over two selling cycles: it isn’t a pricing problem any more, it’s a disposal decision. Choosing between a markdown, a bundle, a bulk buyer, and an auction is covered in our guide to turning inventory liquidation into opportunity.
The common failure is running this report on messy codes. Split one product across three SKUs and all three look like slow movers, so you discount stock that was selling fine in aggregate.
SKUs and getting delivery orders right
For businesses that deliver their own orders, SKU discipline shows up at the customer’s door rather than in a report.
Two similar cases, fresh mozzarella and smoked mozzarella or red roses and burgundy roses, are where short picks and wrong picks happen. A readable variant-level code on the shelf label and on the pick list closes most of that gap, because the picker is matching a code rather than judging a product by sight.
Three things worth doing if you deliver:
- Put the SKU on the pick list and the shelf label, in the same format on both.
- Print SKU barcodes so picking is a scan, not a transcription. Typing is where errors enter.
- Show the SKU on the packing slip so the customer can report a specific problem instead of “the cheese was wrong.”
Do you need software to manage SKUs?
For a few dozen products, a spreadsheet with one row per SKU and a locked format is fine. Build the structure, print labels, keep the owner document.
You have outgrown it when any of these is true: more than one person creates products, you hold stock in more than one place, you sell on more than one channel, or you want committed-versus-available stock rather than a count. At that point the codes need a system around them, so see our comparison of warehouse inventory management software, which includes free tiers you can start on. If most of your orders come through an online storefront, the shortlist is different again, and those tools are compared in our roundup of ecommerce inventory management software.
Whatever you move to, clean the codes before you migrate. Importing duplicates just makes them permanent.
Frequently asked questions
How many characters should a SKU be? Eight to twelve. Short enough to read and type, long enough to carry category, product, variant, and size.
Can two products share a SKU? No. One SKU equals one sellable variant. If two things share a code, your counts for both are wrong.
Is a SKU the same as a serial number? No. A SKU identifies a product type; a serial number identifies one individual unit. A hundred identical units share a SKU and have a hundred serial numbers.
Do I need a UPC if I already have SKUs? Only if you sell through retailers or distributors who scan at their own checkout. UPCs come from GS1: $30 for a single GTIN, or from $250 for a company prefix.
Should I use a SKU generator? A generator is fine for producing sequential codes once you’ve designed the structure. It is no substitute for designing the structure, because a generator doesn’t know your categories.
What do I do with a discontinued SKU? Retire it and never reuse it. Keep the history attached to the original code.
Getting your SKUs right from the start
The work here is a single afternoon: pick your attributes, fix the order, set the segment lengths, write the one-page document, name an owner, and print labels. Everything downstream rests on that afternoon: accurate counts, reliable reorder points, and sell-through numbers you can trust.
The businesses that struggle are not the ones with primitive systems. They’re the ones whose codes drifted, so no report can be trusted and every decision goes back to a gut feel. Fix the codes and the data starts working for you.