What Is a SKU? Definition, Examples & Best Practices [2026]

If you have ever wondered why two products that look nearly identical carry different codes, or why your inventory system treats a red shirt and a blue shirt as completely separate items, SKUs are the answer. They are the foundation of every inventory tracking system, from a single-warehouse operation to a multi-location retail chain.

This guide explains what SKUs are, how to build a consistent SKU structure, how they differ from barcodes and ASINs, and what role good inventory software plays in managing them at scale.

SKU Examples: What They Look Like in Practice

SKUs are designed to be readable at a glance. A well-constructed SKU encodes information about the product so that a warehouse worker or buyer can identify what they are looking at without opening a catalog.

Here are three real-world examples:

A clothing retailer selling a blue large T-shirt: TSHIRT-BLU-L The structure is category + colour + size. A warehouse picker sees this code and immediately knows what to pull.

A bookstore tracking a specific title by ISBN: BOOK-9780143127796 The structure is category + ISBN. This works well because ISBNs are already globally unique identifiers for books.

A hardware store tracking a 12-volt Makita drill: DRILL-MAKITA-12V The structure is category + brand + key spec. Someone browsing the warehouse database can filter all drills, all Makita products, or all 12V tools depending on how they query it.

The patterns above are internal conventions. No two companies need to use the same structure. What matters is consistency: once you choose a format, every product in your catalog should follow it.

How to Create SKU Codes: Practical Rules

Creating a good SKU structure takes a small amount of upfront planning and saves significant operational pain later. Here are the rules that product businesses typically converge on:

Use capital letters and hyphens. Lowercase letters and special characters create confusion in warehouse environments where codes are scanned or typed quickly. WIDGET-RED-SM is unambiguous; widget_red_sm is not.

Encode meaningful attributes. Include category, brand, variant attributes (colour, size, flavour, voltage — whatever varies) in the code. This makes filtering and reporting far easier in your inventory system.

Keep codes short enough to be readable. Most businesses aim for 10 to 30 characters. Beyond that, SKUs become error-prone to enter manually and hard to read on pick-lists.

Do not use the supplier's code as your SKU. Suppliers change their own part numbers. If your SKU is tied to a supplier code, a supplier catalogue update can break your inventory records. Keep them separate.

Never reuse a retired SKU. When a product is discontinued, retire its SKU permanently. Reusing it for a new product corrupts historical sales data and creates reconciliation problems.

Be consistent across the entire catalog. If T-shirts use TSHIRT-[COLOUR]-[SIZE], every apparel item should follow the same pattern. Inconsistency means you cannot run reliable reports by category or variant.

SKU vs UPC vs Barcode vs ASIN

These four terms are often used interchangeably, but they serve different purposes and come from different sources:

| | SKU | UPC (Barcode) | ASIN | |---|---|---|---| | Who creates it | The business itself | GS1 (global standards body) | Amazon | | Scope | Internal — unique within your business | Global — same product has the same UPC worldwide | Amazon marketplace only | | Format | Alphanumeric, custom structure | 12-digit numeric (EAN is 13-digit) | 10-character alphanumeric | | Where it appears | Inventory system, pick lists, POs | Barcode on product packaging | Amazon product listings | | Primary purpose | Internal tracking and reporting | Universal product identification at point of sale | Identifying listings on Amazon |

The key distinction to internalise: a UPC is a global identifier that follows the product no matter where it is sold. A SKU is your own internal label. The same physical product can have one UPC that your supplier printed on the box and a completely different SKU that your warehouse uses for picking.

Most product businesses maintain both: the UPC for point-of-sale scanning and external trading, and the SKU for internal operations and reporting.

Why SKUs Matter for Inventory Management

SKUs are not just labels. They are the foundation that every inventory operation runs on:

Accurate stock tracking across locations. If you hold stock in multiple warehouses or fulfilment centres, SKUs let your system track how many units of each variant are in each location. Without variant-level SKUs, you lose the ability to route orders to the right location.

Variant-level sales reporting. SKUs let you see that your black hoodie in size M sells ten times faster than the same hoodie in size XL. Without that granularity, you cannot make good buying decisions.

Reorder point automation. Inventory software sets reorder points at the SKU level. When on-hand quantity for HOODIE-BLK-M drops below its threshold, the system triggers a restock alert or auto-generates a purchase order. This only works if every variant is tracked separately.

Picking accuracy in warehouse operations. Pick lists use SKU codes to direct warehouse staff to the exact product and variant. A SKU on a pick list is unambiguous. "Blue T-shirt, large" leaves room for error; TSHIRT-BLU-L does not.

Supplier communication and purchase orders. When you raise a purchase order with a supplier, SKUs appear on every line item alongside the supplier's own part number. This eliminates ambiguity about exactly what you are ordering.

The SKU Proliferation Problem

There is such a thing as too many SKUs. Every new variant you add to your catalog creates an independent unit of inventory to track, forecast, purchase, store, and pick. At some point, the tail of slow-moving variants costs more to hold than it generates in sales.

Common symptoms of SKU proliferation include rising dead stock, poor warehouse utilisation, increasing picking errors, and distorted demand forecasts where dozens of near-zero lines obscure the real movers.

The process for diagnosing and fixing this is called SKU rationalization — identifying which variants should be consolidated, discontinued, or replaced. The SKU rationalization strategy guide covers the full process, including how to calculate which SKUs are dragging down gross margins.

How Inventory Software Manages SKUs

At a handful of products, managing SKUs in a spreadsheet is manageable. At hundreds or thousands of SKUs with multiple variants each, a proper inventory management system becomes essential.

Here is what good inventory software does with SKUs:

Variant matrix creation. Rather than creating each SKU manually, modern systems let you define a product and its variant dimensions (size, colour, material) and generate the full SKU matrix automatically. A product with 3 sizes and 4 colours produces 12 SKUs in one operation.

Bulk SKU import and editing. Migrating from spreadsheets to an inventory system typically involves a bulk import. Good systems accept CSV files with SKU, product name, variant attributes, supplier codes, cost price, and opening stock quantities in one upload.

Auto-suggest during product creation. Some systems propose a SKU code based on the product name and variant attributes you enter, using a template you define. This speeds up catalog building and enforces consistency.

Supplier cross-reference. Inventory systems store both your internal SKU and the supplier's own part number for each product. When you raise a purchase order, both codes appear — your SKU for internal use, the supplier code for theirs.

VNDLY handles all of the above. You can create products with full variant matrices, import bulk SKU catalogs, set reorder points per SKU, and see variant-level stock across locations from a single dashboard. The purchase order module references SKUs on every line, so the connection between a supplier order and your internal inventory records is automatic.

Frequently Asked Questions

What does SKU stand for?

SKU stands for Stock Keeping Unit. The term dates back to physical retail, where every distinct item held in a warehouse or store needed its own tracking code to manage stock levels. The concept has carried forward into every form of product business, from e-commerce to manufacturing to distribution.

Is SKU the same as a barcode?

No. A barcode (typically a UPC or EAN) is a globally standardised number assigned through a standards body like GS1 and printed on product packaging for scanning at point of sale. A SKU is an internal code created by the business for its own inventory tracking. The same product will often have both: a UPC printed on the box and a SKU used inside the business's inventory system. The two codes serve different purposes and are maintained separately.

How many SKUs is too many?

There is no universal number, but the practical threshold depends on your warehouse capacity, your demand planning capability, and your minimum viable order quantity from suppliers. A useful diagnostic: if more than 20% of your active SKUs generated zero sales in the last 90 days, you likely have a proliferation problem. Products with very low turn rates tie up working capital, increase picking complexity, and inflate holding costs. The SKU rationalization guide walks through a structured process for deciding which SKUs to cut.