SKU (Stock Keeping Unit)

Every time a product attribute changes in a way that affects how it is stored or fulfilled size, color, material, bundle configuration a new SKU is created. A white t-shirt in size medium and a white t-shirt in size large are two different SKUs. The same white t-shirt in medium sold as a single unit and as part of a three-pack is two different SKUs. The distinction matters operationally because each SKU has its own inventory count, its own reorder point, and its own fulfillment identity.

SKU vs. Other Product Identifiers

SKUs are often confused with other product identification systems. Understanding the distinctions clarifies when each applies:

SKU is merchant-defined and internal. Each business creates its own SKU system based on its own logic. A SKU from one merchant means nothing to another. It is an operational tool, not a universal standard.

Barcode (UPC/EAN) is a standardized, globally recognized product identifier assigned by the manufacturer or brand owner. Where a SKU is internal to the merchant, a barcode is universal — the same product sold by multiple retailers carries the same barcode regardless of who is selling it.

ASIN (Amazon Standard Identification Number) is Amazon's proprietary product identifier, assigned to every product listed in their catalog. Each ASIN maps to a specific product page on Amazon. A merchant selling on Amazon needs both a SKU for their own inventory management and an ASIN for Amazon's catalog system.

GTIN (Global Trade Item Number) is the overarching family of standardized product identifiers that includes UPCs (12-digit), EANs (13-digit), and ISBNs (books). GTINs are required for selling on most major marketplaces and for Google Shopping product feeds.

How SKUs Are Structured

There is no universal standard for SKU format each business designs its own system. The best SKU structures are logical, readable, and scalable. A well-designed SKU encodes key product attributes in a compact, consistent format that humans can interpret at a glance and systems can process reliably.

A common approach uses a hierarchical structure that moves from broad category to specific variant:

Category code Product code Attribute codes Variant code

Example: APP-TSHIRT-WHT-M Apparel, T-shirt, White, Medium

Or for a more complex catalog: SKN-SERUM-VCE-30ML Skincare, Serum, Vitamin C & E, 30ml

The key principles of good SKU design are consistency every SKU follows the same structural logic, readability someone looking at the SKU can understand what it refers to without a lookup table, uniqueness no two SKUs are ever identical, and scalability the system can accommodate new products, variants, and categories without requiring a structural overhaul.

Common mistakes in SKU design include using special characters that confuse systems, starting SKUs with zeros that some platforms strip, using spaces that break database queries, and creating overly long codes that slow down manual operations and increase data entry errors.

Why SKUs Matter in E-Commerce Operations?

Inventory accuracy. SKUs are the foundation of accurate stock counts. Without a unique identifier for every variant, it is impossible to know precisely how many units of each specific configuration are available. A store that tracks "blue jeans" as a single item rather than separate SKUs per size and wash cannot fulfill orders accurately or reorder intelligently.

Fulfillment efficiency. In a warehouse environment, SKUs are what pickers use to locate, identify, and verify the correct item. A clear, logical SKU system reduces pick errors, speeds up fulfillment, and makes training new warehouse staff significantly easier.

Reporting and analytics. SKU-level data is what separates surface-level performance analysis from actionable insight. Knowing that "sneakers" sell well tells you little. Knowing that SKU FTWR-SNK-WHT-42 has a 4.2x higher sell-through rate than FTWR-SNK-BLK-42 tells you something you can act on in purchasing, in merchandising, and in advertising.

Multi-channel management. For brands selling across their own website, Amazon, eBay, and wholesale channels simultaneously, SKUs serve as the common thread that links inventory across platforms. A centralized SKU system prevents overselling, simplifies reconciliation, and enables accurate cross-channel reporting.

Reorder and forecasting. Each SKU carries its own demand history, reorder point, and safety stock level. Effective inventory replenishment is impossible without SKU-level granularity aggregating demand across variants produces forecasts that are wrong in both directions simultaneously.

SKU Proliferation - When Too Many SKUs Become a Problem

SKU proliferation is a common and underappreciated operational risk in growing e-commerce businesses. Every new color, size, bundle, or variant adds a SKU and with it, a unit of inventory that needs to be purchased, stored, tracked, picked, and reported on.

The operational cost of each additional SKU is real. More SKUs mean more purchase orders to manage, more warehouse locations to maintain, more reorder points to monitor, and more data to analyze. At a certain point, the long tail of rarely-sold SKUs generates more cost than revenue tying up working capital in slow-moving inventory while adding complexity to every operational process.

Signs of SKU proliferation becoming a problem include a high percentage of SKUs with zero or near-zero sales in the past 90 days, growing storage costs driven by slow-moving variants, increasing pick errors as warehouse staff navigate a more complex catalog, and difficulty identifying true best-sellers because performance data is fragmented across too many variants.

The remedy is SKU rationalization a disciplined process of identifying and eliminating underperforming SKUs while protecting the variants that drive the majority of revenue and margin.

Key SKU Metrics to Track

• SKU velocity: the rate at which each SKU sells, measured in units per day or week. High-velocity SKUs need different safety stock and reorder logic than low-velocity ones

• SKU contribution margin: revenue minus all direct costs per SKU, identifying which variants are actually profitable versus which generate revenue while destroying margin

• Days of inventory on hand per SKU: how many days of current demand the existing stock level covers, highlighting both stockout risk and overstock exposure

• SKU return rate: return rates that vary significantly by SKU signal product-specific issues worth investigating before scaling

• Dead SKU percentage: the proportion of active SKUs with zero sales in a trailing 90-day period, a measure of catalog efficiency

💡 Pro tip: Design your SKU system before you need to scale it. Most e-commerce brands create SKUs reactively as products are added, without a defined logic or structure. This works at 50 SKUs. It becomes an operational nightmare at 500. Investing a few hours in designing a consistent, logical SKU architecture before your catalog grows saves hundreds of hours of reconciliation, data cleaning, and system migration work later.