A stock keeping unit (SKU) is a business-created identifier for a specific inventory item or product variant. A company assigns its own SKUs, so there is no universal SKU registry or required format. The same product can have different SKUs at different businesses.
SKU stands for stock keeping unit. It can describe the distinct item being tracked or the internal code attached to it. A T-shirt in three sizes and two colors normally creates six SKUs because each variation is counted, sold, and reordered separately.
The SKU links a product to its inventory record. That record can hold the name, variant, category, supplier, cost, price, stock, location, barcode, reorder point, and transaction history. The code does not contain all this information; software uses it to find the correct record.
Every stock movement should reference the intended SKU. Receiving increases its quantity, a sale decreases it, and a transfer moves quantity between locations. Returns, damage, waste, and count corrections also update the SKU through distinct stock actions.
Consider COF-BEA-ETH-1KG:
| Segment | Meaning |
|---|---|
| COF | Coffee |
| BEA | Whole beans |
| ETH | Ethiopia |
| 1KG | One-kilogram pack |
This is an example, not a standard. Another business could use ETH-BEAN-1000 or CF-0142. The goal is consistency, internal uniqueness, system compatibility, and enough readability to prevent mistakes.
Create a separate SKU whenever an item must be counted, purchased, sold, or reordered independently. A single bottle and a case of 12 may need distinct SKUs if both are transacted as separate units.
Useful segments include category, product family, brand, model, material, color, size, flavor, and pack quantity. Put price, cost, stock, shelf location, and current supplier in separate fields.
Use one list so BLUE does not become BL, BLU, and BLUE. Avoid confusing characters such as O and 0 or I and 1 when staff type or read codes aloud.
For example, apply category-product-variant-size throughout the catalog. Add an explicit sequence to resolve collisions instead of appending random characters.
Check duplicates, blanks, spaces, repeated separators, unsupported characters, excessive length, missing variants, and conflicts with current records. Test sample products across every connected system.
Build a consistent format with the free Stash SKU and variant generator. It creates internal SKUs; it does not issue official UPCs or EANs.
Usually, yes. Every separately stocked variant should have its own SKU. A mug with two sizes and three colors creates six inventory records. Sharing one SKU makes it impossible to know which exact variant sold, which is low, or what should be reordered.
For POS catalog structure, see Square items, variations, SKUs, and categories.
| Term | Meaning |
|---|---|
| SKU | Internal identifier created by a business and unique within its catalog. |
| GTIN | Standardized GS1 trade-item identifier. |
| UPC / EAN | Retail identifiers commonly encoded in EAN/UPC barcode symbols. |
| Barcode | Machine-readable carrier for an identifier or other data. |
| Serial number | Identifier for one individual physical unit. |
| Supplier part number | Identifier in a supplier's catalog. |
An SKU is not inherently a barcode, but its value can be encoded in one. Businesses often encode alphanumeric SKUs in Code 128 for internal receiving, counts, picking, transfers, or checkout. This does not turn the SKU into a registered UPC or EAN. Read the complete barcode guide for format selection.
Clean SKUs make item-level counting, receiving, sales, purchase orders, reporting, reorder points, and transfers possible. The code alone does not create accuracy: every movement still needs the correct product, unit, quantity, and location. Regular cycle counts and controlled receiving keep records aligned with physical stock.
An internal identifier for a specific product or variant in a business's inventory system.
No. An SKU identifies a record; a barcode is a machine-readable way to encode a value.
No. The business creates an SKU. A UPC is part of the standardized GS1 identification system.
No. Businesses create their own. Official GTINs, UPCs, and EANs follow separate GS1 processes.
There is no universal length. Use the shortest format that remains clear, unique, and compatible.
Yes. Alphanumeric SKUs are common.
Yes, when each variant is stocked, sold, counted, or reordered separately.
Yes. SKUs only need to be unique within each company's catalog.
No. Price is a separate field and can change without changing product identity.
Encode it in a compatible format such as Code 128, print it, and test it with the real scanner and software. Use the free Stash barcode generator.
Start with the free SKU generator, then create labels with the free barcode generator. For ongoing stock, purchasing, suppliers, forecasting, and multiple locations, explore Stash inventory management.
Last reviewed: August 9, 2026.
Stash connects inventory tracking, forecasting, purchasing, suppliers, and multi-location visibility so growing physical businesses can act on the numbers with less manual work.