CPG Terms Explained, a series by Cyril Ovely

What Is a SKU? The Building Block of CPG Product Data

A SKU (Stock Keeping Unit) is a unique identifier assigned to each distinct product variant in a CPG brand's range, enabling inventory tracking, sales measurement, and supply chain management at the individual product level.

The short answer

A SKU (Stock Keeping Unit) is the fundamental unit of product identification in CPG. Every distinct product variant gets its own SKU: a different flavor, a different pack size, a different count. If it's a separately sellable item with its own barcode, it's a SKU.

A brand might have 50 SKUs across its range: 10 flavors in 5 pack sizes. Each combination is a distinct SKU with its own sales data, inventory levels, and distribution tracking.

Why it matters in CPG

The SKU is the atomic unit of everything in CPG: sales measurement, inventory management, distribution tracking, planogram design, and promotion analysis. Every metric you calculate in this glossary (ACV, TDP, velocity, market share) is ultimately computed at the SKU level and then aggregated upward.

Why SKU management matters:

  • Range complexity: A typical CPG brand has 50 to 500 SKUs. A major retailer might carry 30,000 to 100,000 SKUs across all categories. Managing this complexity requires rigorous SKU governance.
  • Proliferation risk: Without discipline, SKU counts grow unchecked as new flavors, sizes, and limited editions are added. Each additional SKU adds supply chain cost, shelf space requirements, and management overhead.
  • Rationalization decisions: Category reviews and range rationalization exercises evaluate each SKU's contribution. Underperforming SKUs get delisted to make room for better performers.
For the technically minded: In a CPG data model, the SKU is the core product entity. It sits at the intersection of the product hierarchy (brand > sub-brand > flavor > pack size > SKU), the supply chain (SKU > warehouse > store), and the measurement layer (SKU > sales > velocity > market share). Every analytical query in a TPM, SFA, or analytics platform ultimately resolves to the SKU level before aggregating. SKU master data includes: SKU code, description, UPC/GTIN, pack size, case configuration, weight, dimensions, and status (active/delisted/seasonal).

How it works in practice

Example: A coffee brand's SKU structure

BrandVariantPack SizeSKU CodeUPC/GTINStatus
Alpha CoffeeOriginal200g jarAC-ORG-200012345678901Active
Alpha CoffeeOriginal400g jarAC-ORG-400012345678902Active
Alpha CoffeeDark Roast200g jarAC-DRK-200012345678903Active
Alpha CoffeeDark Roast400g jarAC-DRK-400012345678904Active
Alpha CoffeeDecaf200g jarAC-DEC-200012345678905Delisted

Each row is a distinct SKU. The Decaf 200g was delisted after a range review showed it had insufficient velocity to justify its shelf space. The remaining 4 SKUs form the active range.

Key metrics & related concepts

  • SKU Count: the total number of active SKUs in a brand's or retailer's range
  • SKU Rationalization: the process of reviewing and removing underperforming SKUs
  • UPC / GTIN: the barcode number that uniquely identifies a SKU at the point of sale
  • Average Items Carried (AIC): how many SKUs the average stocking retailer carries
  • Product Hierarchy: the structured grouping of SKUs into brands, sub-brands, and variants

Common mistakes & misconceptions

Mistake #1: Confusing SKU with product.
A "product" might refer to a brand or a sub-brand. A SKU is the specific variant. "Alpha Coffee" is a brand. "Alpha Coffee Dark Roast 400g" is a SKU. Precision matters in data and measurement.

Mistake #2: Letting SKU counts grow without governance.
Every new SKU adds complexity. Without a formal SKU governance process (requiring business cases for new SKUs and regular rationalization reviews), ranges bloat and profitability declines.

Mistake #3: Not distinguishing between listed and active SKUs.
A SKU might be listed in a retailer's system but not actively selling. Distinguish between listed SKUs (in the system), active SKUs (generating sales), and phantom SKUs (listed but zero movement).

Mistake #4: Using different SKU codes across systems.
The manufacturer's SKU code, the retailer's item number, and the UPC/GTIN barcode are all different identifiers for the same product. Mapping between them is essential for data integration.

Regional variations

Global: SKU management is universal but practices vary:

  • US: Highly structured SKU management. Major retailers have strict new SKU submission processes and regular range reviews. NielsenIQ and Circana track sales at the individual SKU level.
  • UK: Similar to the US. Retailers use planogram driven SKU management with regular resets. Range rationalization is a standard practice.
  • India: SKU proliferation is common due to the need for small pack sizes and price points for traditional trade. Brands may have 3x the SKU count of developed market equivalents.
  • NZ/AU: With concentrated retail, SKU management is negotiated at chain level. Coles and Woolworths have formal new SKU listing processes.

How leading CPG teams use SKUs

Leading brands treat SKU management as a strategic discipline. They maintain SKU governance frameworks that require business cases for new additions, conduct quarterly rationalization reviews to remove underperformers, and use data analytics to optimize their range for each channel and retailer. The goal: the right number of SKUs, each contributing meaningfully to the brand's performance.

Sources and further reading


Lighthouse for CPG

See how Lighthouse turns these terms into retail execution

Lighthouse connects distribution, execution, trade, and supply into one system your commercial teams act on at the store and SKU level.

Request a demo
Cyril Ovely
Co-Founder and CTO, Vxceed

Cyril is the Co-Founder and CTO at Vxceed. With over two decades of experience in engineering and entrepreneurship, he focuses on building scalable SaaS solutions that transform demand chain execution and help businesses operate with greater agility in evolving markets.