What Is a SKU? How to Create a SKU System That Actually Scales [2026]

Every product in your warehouse needs a name your systems understand. That name is the SKU. Get your SKU system right early and inventory becomes simple. Get it wrong and you will spend years cleaning up 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 agree on.

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.

SKU vs Barcode vs UPC

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 related but 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. And never use a supplier's price or cost in the SKU, because those change.

A Practical SKU Naming Convention

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 Comparison

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.

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.

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.

Frequently Asked Questions

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.