SKU: What the Abbreviation Means and How to Assign It Correctly

What is a SKU? Definition 

SKU stands for Stock Keeping Unit. It's an internal code a company assigns to each of its products to uniquely track inventory and sales. There's no required format. Every company decides for itself how its SKUs are structured.

The term comes from warehouse logistics: a SKU is the smallest unit that needs to be distinguished in inventory, meaning not just the product itself but every sellable variant of it. A T-shirt in three colors and four sizes is twelve different SKUs, even though it's "one product" from a merchandising standpoint.

Key takeaways:

• A SKU can be made up of numbers, letters, and special characters. There's no required format.

• Retailers assign their SKUs individually and internally.

• Ideally, the SKU reveals key product attributes at a glance.

How does a SKU differ from EAN, GTIN, UPC, and a serial number? 

A SKU is an internal, non-standardized code with no official issuing body. EAN, UPC, and GTIN are internationally standardized, globally unique trade codes issued through the GS1 system. A serial number identifies a single physical unit, while a SKU describes an entire product variant.

This distinction gets mixed up often, but it's critical for clean processes across warehouse, storefront, and marketplaces:

In practice: a T-shirt style has a UPC (or GTIN) per variant (size/color) that's valid for retail worldwide. That same variant also gets a SKU your company defines internally. Sell 500 units of that variant and all 500 share the same SKU and the same UPC, but if the product requires serialization (electronics, for example), those 500 units also get 500 different serial numbers.

Why do SKUs matter? 

SKUs are the foundation of accurate inventory tracking, error-free picking, and functioning multichannel reporting. Incorrect or duplicate SKUs are one of the most common causes of inventory discrepancies. Inventory inaccuracy costs global retail $1.73 trillion annually (IHL Group, 2025).

1. Accurate inventory tracking 

Every SKU is assigned only once within your company. That means you can always state exactly how much stock you have of a specific product variant, with no risk of confusing it with a similar item.

2. Error-free picking, fewer wrong shipments 

When every variant (size, color, configuration) carries its own unique SKU, the risk of mix-ups during picking drops sharply. Without that clean mapping, you get exactly the scenario that drives the most returns in practice: a customer orders medium in blue and receives large in black.

3. Functioning multichannel reporting 

If you sell across multiple channels (your own store, Amazon, eBay, in-person retail), the SKU is the common anchor you use to track sales, inventory, and performance across channels. Without consistent SKU logic, your reporting fragments into isolated spreadsheets per channel.

4. The foundation for automation 

Automatic reordering, low-stock alerts, and pick-and-pack workflows only work reliably when every SKU is unique and consistently recorded in the system.

The economic context: why this isn't a minor detail 

Inventory inaccuracy, often a direct consequence of incorrect, duplicate, or inconsistent SKUs, is one of the most expensive operational problems in retail. According to a September 2025 analysis by IHL Group, global retail loses $1.73 trillion annually to the combination of out-of-stock and overstock situations, equal to 6.5% of worldwide retail sales.

The problem persists despite $172 billion in improvement investments over the past year. A clean, consistent SKU system is only one piece of the solution, but it's an unusually cheap one: it costs nothing but discipline in how you assign codes, and it can be fully automated with an ERP system.

How do you create a SKU? Format and examples 

There's no required way to create a SKU. Common practice is combining key product attributes from broad to specific, such as category, variant, size, and color. What matters is that every SKU in your company follows the same, consistent pattern.

Why consistency matters 

A unified SKU system delivers three core benefits:

• Every code is assigned only once internally, preventing mix-ups and duplicate stock entries.

• Staff instantly recognize which product it is just from the SKU's structure.

• Consistent SKU number ranges make it easier to cluster products by category, season, or supplier.

Real-world examples 

Example 1: Apparel

A black women's bootcut pant in size 8 (US):

PNT-W-BCUT-08-BLK

• PNT = category (pants)

• W = gender (women's)

• BCUT = fit (bootcut)

• 08 = size

• BLK = color (black)

Example 2: Electronics

A smartphone from brand SAMPLE, model "Supreme," 512 GB, silver housing:

SMP-SUPR-512-SLV

• SMP = brand

• SUPR = model

• 512 = storage capacity

• SLV = color

Manual vs. automated assignment 

With a small catalog, you can assign SKUs by hand. Once your catalog grows, or you carry multiple variants per item, automated assignment through an ERP system pays off. It eliminates typos, enforces consistency, and links every SKU directly to inventory, pricing, and sales channels.

How many SKUs should your catalog have? 

There's no fixed number, but revenue per SKU helps you gauge it. A growing catalog only makes sense if revenue per SKU doesn't decline. Many e-commerce platforms also impose practical or technical thresholds past which specialized tools become necessary.

A larger SKU count isn't automatically better. A useful framework from e-commerce retail is revenue per SKU: divide your online revenue by your number of active SKUs. If that number drops as your catalog grows, you're increasingly tying up capital, warehouse space, and operational attention in items that aren't paying off proportionally (Zentail).

There are practical thresholds too, where standard tools hit their limits. Shopify's native inventory management, for example, covers most needs up to around 300 orders per month or roughly 200 SKUs. Beyond that, you typically need a specialized app or an ERP connection to maintain inventory accuracy and visibility. At the other end of the scale, Amazon shows how large SKU catalogs can get: the marketplace manages roughly 12 million of its own SKUs plus more than 300 million third-party listings, though that only works with massively specialized, purpose-built infrastructure (fabric.inc).

For most growing retailers, the relevant question isn't "how many SKUs can I technically support" but "which SKUs actually drive revenue." An overly broad, uncurated catalog makes picking harder, ties up working capital, and dilutes the shopping experience.

Common mistakes in SKU assignment 

The most common SKU mistakes are: inconsistent formats over time, duplicate codes from manual upkeep, missing variant mapping, and SKUs that are too long or too cryptic to be practically usable.

• Drift over time: New staff or new product categories often introduce deviating patterns. Without a documented policy, the system fragments.

• Duplicates from manual upkeep: Especially with spreadsheet-based management, or when items get created both manually and via import, duplicate SKUs with parallel inventory entries creep in easily.

• Missing variant mapping: If every size, color, or configuration isn't cleanly mapped to its own SKU, variants blend together in the system. That leads to picking errors and wrong shipments.

• Overly long or cryptic codes: A SKU should be readable by staff at a glance. Codes longer than roughly 15 to 20 characters, or without a recognizable logic, lose that practical value.

An ERP system like Xentral structurally prevents most of these mistakes: it enforces unique assignment, automatically links every variant to its own SKU, and makes duplicate item creation technically impossible.

Bottom line 

The SKU isn't a bureaucratic detail, it's the foundation for everything downstream: accurate inventory tracking, error-free picking, functioning multichannel reporting, and automated processes. Unlike EAN or GTIN, there's no official issuing body and no requirement for consistency across company boundaries, but that's exactly why the responsibility for a clean, consistent system sits entirely with you.

With a small catalog, a manually maintained, consistent logic is enough. Once your catalog or your number of product variants grows, automated assignment through an ERP system becomes the key lever for avoiding the errors that contribute meaningfully to the $1.73 trillion in global retail inventory inaccuracy.