What Is a SKU? Meaning, Examples and How to Create SKU Codes

Every product in your warehouse needs a name your systems understand. That name is the SKU. A good SKU system keeps inventory simple as your catalogue grows. A weak one creates duplicates, mis-picks and confused reports. This guide explains what a SKU is, how it differs from a barcode or UPC, and how to build a SKU format that still works when you have 10,000 products.

What Is a SKU?

SKU stands for Stock Keeping Unit. It is the unique code you assign to each product or product variant in your inventory system. Unlike a product name, which can be long and descriptive, a SKU is short and unambiguous.

A SKU does the same job for products that a name does for people, but better. Names can be shared. Spellings vary. Descriptions change. A SKU is a single, fixed reference that your warehouse, website, accounting system and suppliers can all use.

When someone in the warehouse picks an order, they do not look for "the black men's trainers in size 10". They look for SKU ACME-SHOE-BLK-10-001. That code removes confusion and mistakes.

Three SKU examples from different kinds of product business, so you can see the pattern before the rules:

| Business | SKU | Structure | |---|---|---| | Clothing retailer, blue large T-shirt | TSHIRT-BLU-L | category + colour + size | | Bookstore tracking a title | BOOK-9780143127796 | category + ISBN | | Hardware store, 12V Makita drill | DRILL-MAKITA-12V | category + brand + key spec |

No two companies need the same structure. What matters is that every product in your catalogue follows the one you choose. Paste any of these into the free SKU generator to build a whole series in that format.

SKU Meaning in Inventory: Why It Matters

The SKU meaning in inventory goes beyond a simple label. It connects every part of your operation. A SKU links a product to its stock count, supplier, purchase history, sales velocity, and barcode. Without SKUs, you are managing inventory by description, and descriptions drift.

In practice, SKU-level tracking means you can:

• Run accurate stock counts by scanning barcodes tied to exact SKUs, not guessing which "blue shirt" is which
• Trace problems to their source when a customer returns a defective item, because the SKU tells you which batch and supplier it came from
• Make better purchasing decisions by seeing which variants sell fastest, not just which product line performs well on average
• Speed up order fulfilment because warehouse staff pick by code, not by reading labels

Businesses that track at the SKU level identify stock discrepancies and shrinkage faster than those running general inventory counts. The difference matters once you pass a few hundred products or open a second location.

What Is SKU Management?

SKU management is the process of creating, maintaining, and organising your SKU system across your entire product catalogue. It covers how you assign new SKUs when products arrive, how you keep them consistent as variants multiply, and how you use SKU data to make better purchasing and sales decisions.

A basic SKU system gives products a code. Good SKU management goes further:

• Consistent assignment - new SKUs follow the same format every time, whether one person or ten are adding products
• Deduplication - the system prevents two people from assigning different SKUs to the same product
• Variant-level tracking - each size, colour, and material gets its own SKU, with stock tracked separately per variant
• Shrinkage visibility - when stock counts drift from expected levels, SKU-level tracking pinpoints where items are going missing. Businesses tracking at the SKU level identify shrinkage 3-5x faster than those running general inventory counts
• Sales and margin analysis - with SKU-level data, you can see which variants drive revenue and which are slow movers tying up cash in your warehouse

The shift from basic SKU assignment to real SKU management usually happens when a business passes 200-500 products or opens a second location. At that scale, your SKU system either scales with you or becomes the bottleneck.

How to Build a SKU System That Scales

The difference between a list of product codes and a real SKU system is governance. Decide who can create a SKU, document the format in one place, and make the process part of every new-product launch. A warehouse team should never have to invent a code while receiving a shipment.

Keep a simple SKU register with the code, product name, variant attributes, launch date and status. Do not reuse a retired SKU for a new product. Historical orders, returns, supplier records and accounting exports may still point to it years later. Retiring the code preserves a clean audit trail. Recycling it creates bad data.

Finally, test your convention against a real future scenario: a new colour, size, bundle, second warehouse, or replacement supplier. If two people would build different codes for that product, the rule is not clear enough yet. Once the format is settled, use your inventory software to enforce uniqueness and connect the SKU to stock, barcodes and purchasing.

SKU vs Barcode vs UPC: What Is the Difference?

| | SKU | UPC / EAN (barcode) | ASIN | |---|---|---|---| | Who creates it | Your business | GS1 (global standards body) | Amazon | | Scope | Internal, unique within your business | Global, the same product has the same code everywhere | Amazon marketplace only | | Format | Alphanumeric, your structure | 12 digits (UPC) or 13 digits (EAN) | 10-character alphanumeric | | Where it appears | Inventory system, pick lists, POs | Barcode on the packaging | Amazon listings | | Purpose | Internal tracking and reporting | Product identification at point of sale | Identifying listings on Amazon |

These three terms get mixed up constantly. Here is the difference.

Term	What it is	Who controls it
SKU	Internal product identifier. Can be alphanumeric.	Your business
Barcode	A machine-readable image that encodes a number or text.	You generate it, but it follows a standard format
UPC	A 12-digit retail product identifier used mainly in North America.	GS1 issues company prefixes and numbers

You can have a SKU with no barcode, a barcode with no UPC, and a UPC that maps to a SKU. They are separate layers. For internal warehouse use, SKUs and barcodes are what matter. For products sold through major retailers, UPCs are usually required.

You can generate barcodes for your SKUs with our free barcode generator.

What Makes a Good SKU Format?

A SKU format is the pattern your codes follow. A good one has a few simple rules.

• Consistent. Every SKU should follow the same structure. Mixed formats make searching and reporting painful.
• Readable. A human should be able to glance at a SKU and know roughly what it is. That matters during stock counts and customer service.
• No spaces or special characters. Dashes and underscores are fine. Slashes, ampersands and spaces break spreadsheets, URLs and some barcode systems.
• Short. Aim for under 20 characters. Long SKUs are hard to scan, hard to type and hard to fit on labels.
• Structured segments. Break the SKU into meaningful chunks: brand, category, variant, sequence.

Avoid using the number 0 and the letter O together if possible. Avoid leading zeros unless your system preserves them reliably. Never use a supplier's price or cost in the SKU, because those change.

SKU Naming Convention: Rules That Actually Work

Let us build a real SKU format for a fictional shoe retailer called Acme.

Format: BRAND-CATEGORY-COLOUR-SIZE-SEQUENCE

Example: ACME-SHOE-BLK-10-001

Break it down:

• ACME = brand
• SHOE = category
• BLK = colour (black)
• 10 = size
• 001 = sequence number

This format is readable, sortable and scalable. When Acme adds brown boots in size 9, the SKU becomes ACME-BOOT-BRN-9-002.

The sequence number at the end is useful because two products can share brand, category, colour and size but still be different styles. It also gives you room to grow without rewriting the format.

SKU Format Options: Pick the Right Structure for Your Business

Different businesses need different SKU structures. Here are four common formats and when they work best.

Format	Example	Best for
Brand-Category-Variant	NIKE-SHOE-RED-9	Branded wholesale and retail
Category-Size-Colour	TSHIRT-L-WHT	Fashion and apparel
Supplier-Reference	SUP01-45892	Drop-shipping and multi-supplier businesses
Sequential	SKU-00001	Simple retail with few products

Most growing businesses should use a structured format. Pure sequential SKUs are fine at 50 products and become a nightmare at 500.

Common SKU Mistakes

Here are the mistakes we see most often when businesses set up SKUs.

Too long. A 40-character SKU will not fit on a small label and will frustrate warehouse staff.

Using spaces. Spaces cause problems in CSV files, URLs, barcode scanners and some inventory systems. Use dashes or underscores instead.

Using manufacturer part numbers as SKUs. A manufacturer part number is useful as a field on the product, but it should not be your SKU. If you buy the same product from two suppliers with different part numbers, your inventory will split into two products.

No system at all. Calling products "blue shirt" and "blue shirt 2" works until you have ten blue shirts. Then nothing makes sense.

Changing SKUs after launch. Once a SKU has been used in purchase orders, sales orders and barcodes, changing it creates historical chaos. Get it right the first time.

The SKU Proliferation Problem

There is such a thing as too many SKUs. Every new variant you add 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. The symptoms are rising dead stock, poor warehouse utilisation, more picking errors and demand forecasts distorted by dozens of near-zero lines.

A useful diagnostic: if more than 20% of your active SKUs sold nothing in the last 90 days, you have a proliferation problem. The fix is SKU rationalisation, deciding which variants to consolidate, discontinue or replace. The SKU rationalization strategy guide covers the full process, including how to find the SKUs dragging down gross margin.

How Many SKUs Do You Need?

One per distinct sellable variant. If a t-shirt comes in three sizes and four colours, you need twelve SKUs, not one.

Each variant can have a different cost, a different barcode, a different supplier and a different sales velocity. If they share one SKU, your stock levels, reorder points and profit reports will all be wrong.

A kit or bundle is a separate SKU that points to multiple component SKUs. That is fine, but the components still need their own codes.

SKUs and Variants: A Worked Example

You sell a cotton t-shirt called the Everyday Tee. It comes in small, medium and large, and in white, grey, navy and black.

Using the format TSHIRT-SIZE-COLOUR, your SKUs look like this:

Size	White	Grey	Navy	Black
Small	TSHIRT-S-WHT	TSHIRT-S-GRY	TSHIRT-S-NVY	TSHIRT-S-BLK
Medium	TSHIRT-M-WHT	TSHIRT-M-GRY	TSHIRT-M-NVY	TSHIRT-M-BLK
Large	TSHIRT-L-WHT	TSHIRT-L-GRY	TSHIRT-L-NVY	TSHIRT-L-BLK

Twelve SKUs from one product. Each is traceable, countable and reorderable on its own.

When Your SKU System Breaks Down

A spreadsheet SKU system works until it does not. You will feel the breaking point when:

• You pass a few hundred products and searching becomes slow.
• You open a second warehouse and the same SKU means different things in each location.
• You sell on multiple channels and each platform formats your SKU differently.
• Staff start creating SKUs on the fly, and duplicates appear.

At that point you need software. A proper inventory system enforces SKU formats, prevents duplicates, links SKUs to barcodes and tracks stock per location.

For businesses selling across online channels, a scalable SKU system also needs one source of truth. Our guide to inventory software for ecommerce explains how to keep product, order and stock data aligned as you add channels.

SKU Labels: Printing and Scanning Your Codes

SKU System Health Check: Find Problems Before They Multiply

A SKU system rarely fails in one dramatic moment. It frays at the edges. Two people create almost identical codes, a colour abbreviation changes halfway through a season, or a discontinued variant gets recycled because the old spreadsheet looked harmless. Run a short monthly check instead. Export the active catalogue, sort by SKU, and look for duplicates, blanks, inconsistent separators and codes that no longer match the product attributes they claim to describe.

Then test the system with a new starter. Give them three real products and ask them to locate the correct SKU from the product name, variant and label alone. If they need tribal knowledge, the format is doing too little work. A healthy SKU system makes the code predictable without trying to encode every possible detail. The product record can hold the long description, supplier reference and technical specifications.

Keep retired SKUs retired, document the abbreviations in one place, and make barcode labels mirror the SKU your team actually searches for. That discipline improves receiving, cycle counts and customer support long before the catalogue reaches 10,000 products. Teams that scan at the shelf can pair these rules with VNDLY's barcode scanner so the code, count and item record stay connected.

A SKU label is the physical or digital tag that links a product in your warehouse to its record in your inventory system. Without labels, your SKU system exists only in software. Scanning and stock counting become guesswork.

What goes on a SKU label:

• The SKU code itself (human-readable, for visual picking and receiving)
• A barcode encoding the SKU (or a separate barcode number mapped to the SKU)
• Product name or description (optional but useful for visual confirmation)
• Variant information: size, colour, lot number (anything that distinguishes this variant)

Label formats by use case:

• Warehouse bin labels, typically larger (A4 or half-sheet) with big barcode, SKU, and description clearly visible from a metre away
• Product labels, smaller (like a 50x25mm Dymo or Zebra label) that attach directly to each unit or inner pack
• Packing labels / pick labels, generated at dispatch time to confirm what's in each box

Generating SKU labels: Use your inventory software to export SKU data, then print via any label printer. VNDLY exports to standard formats; you can pair it with Dymo, Zebra, or Brother label printers. For custom barcode images, the free barcode generator creates Code 128 or QR codes from any SKU string.

Scanning: VNDLY's free iOS and Android mobile app scans barcodes and QR codes tied to SKUs for receiving, stock counts, and order picking. The barcode does not need to encode the SKU directly. It can encode any unique identifier that your system maps back to the SKU. What matters is consistency: the barcode on the label, in the system, and on the purchase order must all agree.

Common label mistake: printing labels before the SKU system is finalised. If you change a SKU format after printing 500 labels, you're reprinting all of them. Lock the format, then print.

From the Founder

For more on tracking stock across locations and managing variant-level data, see our guides on inventory management for small businesses and barcode scanning for inventory management.

How VNDLY Manages SKUs

VNDLY gives every product and variant its own SKU, then links that SKU to barcodes, suppliers, purchase orders, sales orders and stock levels. You can auto-assign SKUs based on your chosen format, import existing SKU lists and scan barcodes straight back to the right product.

Because VNDLY tracks cost, velocity and stock per SKU, you can see which variants are profitable, which are slow movers and which need reordering without manual reports. If you're building out your inventory system beyond just SKUs, see the inventory management system feature overview or the inventory management best practices guide for the full picture, including how ABC analysis uses SKU-level data to prioritise your best sellers.

Frequently Asked Questions

What does SKU stand for?

SKU stands for Stock Keeping Unit. The term comes from physical retail, where every distinct item held in a store or warehouse needed its own code so stock could be counted and reordered. It now applies to every product business, from ecommerce to manufacturing to distribution.

Is a SKU the same as a barcode?

No. A barcode, usually a UPC or EAN, is a globally standardised number issued through GS1 and printed on the packaging for scanning at point of sale. A SKU is an internal code you create for your own inventory tracking. The same product often has both, and your inventory system maps one to the other.

What does SKU stand for?

SKU stands for Stock Keeping Unit. It is your business's internal product identifier.

How long should a SKU be?

Aim for under 20 characters. Shorter is better for labels, scanners and spreadsheets, but not so short that the code becomes meaningless.

Can I change a SKU once it is in use?

You can, but it creates problems. Purchase orders, sales history, barcodes and integrations all reference the old SKU. It is much easier to design the format correctly at the start.

What is the difference between a SKU and a part number?

A SKU is your internal code. A part number is usually the manufacturer's code. You might store both, but your SKU should be the one you use for inventory and orders.

How do I assign barcodes to SKUs?

Generate a barcode image for each SKU using a barcode generator, then print and attach the label. The barcode value can be the SKU itself or a separate number that maps to the SKU in your inventory system.

What is the difference between a SKU and a barcode?

A SKU is your internal product code. A barcode is the scannable image that encodes that code, or a different number, into a format a scanner can read. You can have a SKU without a barcode, but you cannot scan a SKU that has no barcode assigned to it. For a full breakdown, see the SKU vs Barcode vs UPC section above.