A stock-keeping unit (SKU) is a distinct item or product variant that an organization tracks separately in its inventory system. The term also commonly refers to the internal code assigned to that item. A SKU identifies a category of interchangeable units for stock-control purposes, rather than an individual physical object: many identical shirts can share one SKU, while otherwise similar shirts in different sizes or colors usually have different SKUs.
Scope and identification
An organization defines SKUs according to the distinctions needed for purchasing, storage, sales, and replenishment. Relevant attributes may include:
- Product model or design.
- Size, color, material, or technical specification.
- Package size or quantity.
- Condition, such as new or refurbished.
- Configuration or bundle contents.
For example, a retailer selling one shirt design in three colors and four sizes would ordinarily maintain 12 SKUs if every combination is offered. Holding 50 identical shirts of one size and color means holding 50 units of one SKU—not 50 different SKUs.
The boundary depends on business requirements. A manufacturer may distinguish components that a retailer never handles separately, while a retailer may distinguish sales packages made from the same underlying product. A single bottle and a case of twelve bottles may have separate SKUs, or may be represented through linked units of measure and packaging records.
A SKU is normally unique within the organization or system that assigns it, not universally unique. Different companies can use the same code for unrelated goods or different codes for the same goods.
SKU codes
SKU codes can consist of numbers, letters, or a combination of both. There is no universal mandatory format. A hypothetical code such as TS-104-BLU-M might identify shirt model 104 in blue, size medium.
Two broad approaches are common:
- Meaningful codes encode attributes that staff can recognize.
- Non-meaningful codes use sequential or otherwise generated identifiers, with product attributes stored in separate database fields.
Meaningful codes can make manual identification easier, but become cumbersome when product characteristics or classification schemes change. Non-meaningful identifiers provide less information on their own but avoid tying product identity to changeable descriptions.
An organization’s coding rules generally address uniqueness, permitted characters, maximum length, and the treatment of discontinued items. Preserving historical identifiers helps prevent old orders, returns, and sales records from being associated with a different product.
Distinction from related identifiers
A SKU serves an internal inventory-management purpose and should be distinguished from several related concepts.
| Identifier or record | Main purpose | Relationship to a SKU |
|---|---|---|
| Product model or family | Groups related goods | May encompass many SKUs, such as different sizes and colors |
| [[global-trade-item-number | Global Trade Item Number (GTIN)]] | Identifies trade items under GS1 standards |
| Serial number | Identifies an individual physical unit | Many serialized units may belong to one SKU |
| Lot or batch number | Identifies a production or handling group | One SKU may have stock from several lots |
| Storage-location code | Identifies where stock is held | One SKU may be stored in multiple locations |
A barcode is a machine-readable representation of data, not inherently a SKU. Depending on the system and barcode format, it can encode an internal SKU, a GTIN, or other information. The familiar retail UPC and EAN barcode formats generally carry standardized trade-item identifiers rather than a retailer’s internal SKU.
Mappings between identifiers are not necessarily one-to-one. Multiple supplier records or external product identifiers may map to one internal SKU when the organization treats the goods as interchangeable.
Operational uses
SKUs connect product records with inventory movements and commercial transactions. Purchases, receipts, transfers, sales, returns, and stock adjustments can all be recorded against the relevant SKU. This makes SKU-level information a basic component of supply chain management.
Typical uses include:
- Replenishment: monitoring stock levels and determining when and how much to order.
- Order fulfillment: selecting the correct product variant during picking and packing.
- Stock counting: comparing recorded quantities with physical stock.
- Performance analysis: measuring sales, margins, turnover, and slow-moving inventory.
- Assortment planning: deciding which variants to introduce, retain, or discontinue.
In e-commerce, a customer-facing product page often groups several SKUs under one listing. Selecting a size, color, or capacity determines the specific SKU ordered. In omnichannel retailing, a common SKU can connect inventory and sales records across stores and online channels.
Inventory is often tracked at a finer level than SKU alone. A system may maintain balances by SKU, warehouse, storage bin, lot, and stock status. Consequently, the existence of one SKU does not imply a single undifferentiated stock balance or that all recorded units are available for sale.
Assortment complexity and limitations
The number of SKUs measures assortment breadth at a particular level of detail, not the amount or value of stock. A business with many SKUs may hold little stock of each, while another with few SKUs may hold very large quantities.
Adding variants can support product differentiation, but also increases forecasting, purchasing, storage, and record-maintenance requirements. When demand is spread across more variants, some may sell infrequently, tying up working capital. Greater variety can also reduce opportunities for economies of scale in purchasing or production.
A SKU system is only as reliable as its underlying records. Duplicate codes, inconsistent packaging conversions, and incorrect mappings can distort stock availability and sales analysis. Maintaining clear item definitions and controlled product records is therefore a data governance issue as well as an inventory-management task. SKU identification alone does not provide serial-level traceability, batch history, expiry information, or an inventory valuation method; those require additional records and rules.