What Is a SKU? Stock Keeping Unit Meaning, Examples and How to Set One Up
Practice · 8 min read
Nothing you paste is stored.
The scan could not run.
A live preview of Storekeeper's forecasting engine on fictional sample dataon the rows you pasted. The full product connects to your POS and store and runs this continuously.
A SKU (stock keeping unit) is a unique internal code you assign to each distinct product variant so you can track its stock, sales and reordering. Unlike a barcode, a SKU is yours: you design the format, and every size, color or pack of a product gets its own SKU. Good SKUs are short, readable and consistent, so a person can glance at one and know what it is, and software can group and forecast by it.
SKUs are the backbone of every inventory system. Get them right and counting, forecasting and reordering all line up cleanly. Get them messy, with duplicates, blanks or codes nobody can read, and every report downstream inherits the mess. Here is what a SKU actually is, how it differs from the codes it gets confused with, and how to build a SKU system that still makes sense when you have thousands of them.
SKU meaning: what the code actually represents
SKU stands for stock keeping unit. It is a code, usually 8 to 12 characters of letters and numbers, that uniquely identifies one sellable variant of a product. A blue medium t-shirt and a blue large t-shirt are the same product but two different SKUs, because you stock, count and reorder them separately. The SKU is the key that ties together everything you know about that variant: how many you have, how fast it sells, what it costs and when to reorder it.
SKU vs UPC vs barcode: what is the difference?
These get used interchangeably, but they are not the same thing. A SKU is internal and yours to design. A UPC is a standardized 12-digit number issued through GS1 that identifies a product globally, the same across every retailer that sells it. A barcode is simply the scannable image that encodes one of those numbers. You can scan a UPC barcode to look up a product, but you still assign your own SKU to manage it internally.
| Code | Who assigns it | Scope | Example |
|---|---|---|---|
| SKU | You, internally | Unique inside your business | TSH-BLU-M |
| UPC | GS1 (standards body) | Global, same everywhere | 012345678905 |
| Barcode | Generated from a number | A scannable image of a code | The striped label itself |
How to build a SKU: a worked naming example
A good SKU reads left to right from general to specific. Say you sell t-shirts. Start with a product-type code, add attributes that matter for stocking, and keep the order consistent across the catalog. A blue medium crew-neck t-shirt might become TSH-CRW-BLU-M: TSH for t-shirt, CRW for crew neck, BLU for blue, M for medium. The large version is TSH-CRW-BLU-L. Anyone on the team can read it, and your software can group every TSH-CRW-BLU together to see how the color sells across sizes.
Rules for a SKU system that scales
The difference between a SKU scheme that lasts and one you rebuild in a year comes down to a few disciplines. Set them before you create the first hundred codes, because renaming SKUs after the fact breaks history.
| Rule | Why it matters |
|---|---|
| Start with letters, not zeros | Spreadsheets strip leading zeros, silently corrupting numeric SKUs |
| Keep it short and readable | Staff read and type SKUs all day; 8 to 12 characters is the sweet spot |
| Be consistent in field order | Same attributes in the same positions lets software group and filter cleanly |
| Never reuse a retired SKU | Reusing a code merges two products' history into one useless line |
| Do not encode price or supplier | Those change; a SKU should be permanent, so keep volatile data in fields |
Why clean SKUs make every other number trustworthy
Every metric you care about is calculated per SKU. Turnover, sell-through, reorder points and forecasts all depend on each variant having one clean, stable code. When SKUs are duplicated or inconsistent, the same product shows up as two lines, its sales split in half, and its forecast reads low, which quietly causes stockouts. Clean SKUs are the unglamorous foundation that makes the analytics on top of them worth trusting.
SKUs are also how you compare your catalog to the outside world. When you want to see how a competitor prices or ranges a similar product, teams increasingly pull the competitor's catalog into clean, structured data and map it back to their own SKUs, rather than eyeballing web pages one at a time. The internal code becomes the join key between your data and everyone else's.
Where SKUs meet forecasting
Once your SKUs are clean, the payoff is that software can read each one's demand pattern and act on it. That is the difference between a system that merely stores a SKU list and one that forecasts per SKU and sets live reorder points. It is the core of what Storekeeper is being built to do, and it only works when the SKU underneath is a clean, single source of truth. If you are choosing a system, our guide to inventory control software covers what to look for.
Want to see your own SKUs read for demand? Paste your current stock and recent sales into the live stock scan at the top of the site. It works off your SKUs to flag which lines are about to run out and which are piling up.
See this math run itself
The free stock scan computes cover, safety stock and verdicts per SKU on sample data or rows you paste. No signup.
Run the stock scanMore from the stockroom
- Working capital GMROI: Formula, Benchmarks and How to Improve It
- Practice ABC vs XYZ Analysis: The Difference and How to Combine Them
- Working capital How to Value Inventory for Taxes: Methods, Rules and COGS
- Practice Consignment Inventory: How It Works, Pros and Cons, and the Accounting
- Practice Par Level Inventory: What It Is and How to Set Par Levels
- Practice How to Reduce Supplier Lead Time (9 Practical Ways)
- Working capital What Is Landed Cost? Formula, Components and How to Calculate It
- Practice Just-in-Time Inventory (JIT): How It Works and When to Use It
- Practice Min/Max Inventory: How the System Works and How to Set Levels
- Lost sales How to Avoid Stockouts: 7 Ways to Stop Running Out of Stock
- Practice How to Do a Physical Inventory Count (Step by Step)
- Metrics What Is a Good Inventory Turnover Ratio? (Benchmarks by Industry)
- Practice How to Reduce Inventory Carrying Cost (6 Practical Levers)
- Practice How to Forecast Inventory Demand (Methods and a Practical Process)
- Metrics How to Calculate Inventory Turnover (Formula, Example, Days)
- Practice How Much Safety Stock Should You Hold? (Formula and Service Levels)
- Practice How to Sync Inventory Across Multiple Sales Channels
- Metrics How to Calculate Inventory Value: FIFO, LIFO and Weighted Average
- Practice How to Reduce Inventory Without Causing Stockouts
- Metrics Inventory KPIs: The 7 Metrics That Actually Matter
- Metrics Days of Inventory on Hand (DIO): Formula, Benchmarks and How to Lower It
- Practice Inventory Optimization: Techniques to Cut Stock Without Stocking Out
- Practice Perpetual vs Periodic Inventory: Which System to Use and How COGS Differs
- Working capital Inventory Shrinkage: Formula, Causes and How to Reduce It
- Working capital Inventory Carrying Cost: Formula, Percentage and How to Lower It
- Practice Cycle Counting: What It Is, Methods and How Often to Count
- Metrics ABC Analysis in Inventory Management: Formula, Classes and a Worked Example
- Metrics Inventory Turnover Ratio: Formula, Benchmarks and What Good Looks Like
- Formulas Economic Order Quantity (EOQ): The Formula and When to Trust It
- Practice Inventory Management in Excel: How to Build It, and When to Stop
- Formulas Safety Stock: What It Is and How to Calculate It
- Formulas Reorder Point Formula: How to Calculate When to Reorder
- Working capital Dead Stock: Why It Happens and How to Clear It
- Lost sales Stockouts: The True Cost of Running Out