What Is A SKU Number? (And How to Fix Phantom Stock)

Ever spent twenty minutes hunting through a retail backroom or a busy efulfilment warehouse for a “Medium Blue T-Shirt” that the system swore was in stock, only to find three Large Yellow ones and a solitary sock? Welcome to the wild world of inventory management.

At its core, a SKU (Stock Keeping Unit) is a unique, alphanumeric code created internally by a retailer to identify, track, and manage specific product variants in inventory, including details like size, colour, and model.

In simple terms, it’s the shorthand your business uses to know exactly what’s what.

A typical SKU looks something like this:

TSH-BLU-MED-001

• TSH = Product category (T-shirt)
• BLU = Colour (Blue)
• MED = Size (Medium)
• 001 = Unique identifier

SKUs are kind of like your internal language for stock. When they’re clear and consistent, everything runs smoother, from warehouse picking to what actually ends up on the store shelves.

SKU vs UPC, barcode, and serial number: What’s the difference?

It’s easy to lump every string of numbers on a cardboard box into the same mental pile, but each identifier plays a very distinct role in the supply chain:

Identifier	Who creates it	Purpose	Scope	Format
SKU	Retailer/Brand	Internal inventory tracking	Unique per business	Alphanumeric
UPC	GS1 (global standard)	Identifies products at point of sale (POS)	Universal	12-digit numeric
Barcode	Generated from UPC	Scannable representation of product code	Universal	Visual (lines/spaces)
Serial number	Manufacturer	Identifies a specific individual item	Unique per unit	Alphanumeric

The key difference is the SKUs are internal and flexible, while UPCs and barcodes are external and standardised.

So, while a barcode allows a cashier to scan an item at checkout, the SKU is what ensured the warehouse team sent the right size to that store in the first place.

Why do SKUs matter?

Sure, a well-structured SKU system puts neat labels on your products. But there’s so much more to it than that. Do it right, and it keeps your entire operation running smoothly.

Here is how smart SKU tracking directly protects your bottom line:

1. Fewer picking and replenishment errors

When product variants are clearly defined by distinct codes, warehouse and store teams can pick and pack items with pinpoint accuracy. That means fewer costly mis-ships, lower return rates, and far fewer disappointed shoppers.

2. Reduce phantom inventory

Ever had a store system report three units available, but the physical shelf is completely bare? That’s phantom inventory, and it’s one of the biggest ecommerce logistics challenges modern brands face. Miscanned or poorly formatted SKUs cause system records to drift away from physical reality. Clear, unique SKUs align your digital records with store shelves, keeping ghost stock at bay.

3. Better sell-through tracking

Not all variants are created equal. SKU-level data allows you to look past high-level sales and analyse granular performance. Instead of vaguely knowing that ‘T-shirts are selling well’, you can see that Blue Medium is selling out in three days while Black Extra-Large sits untouched for three weeks, allowing you to adjust manufacturing and reordering cycles accordingly.

4. Improved on-shelf availability

When your SKU-level data is accurate, replenishment stops being a chaotic fire-fighting exercise and becomes proactive. You can set automated reorder triggers per variant, ensuring your bestsellers remain fully stocked on store shelves.

How to create effective SKU numbers

Creating SKUs isn’t rocket science, but creating good SKUs takes a bit of thought.

Here are five practical rules to follow when designing your SKU architecture:

• Keep it short and meaningful: Aim for 8-12 characters. Long strings might hold more detail, but they’re harder to read, remember, and use in practice.
• Start with letters: Leading with letters makes SKUs easier to scan visually and organise logically.
• Avoid special characters: Stick to letters and numbers. Symbols can cause issues across systems and software integrations.
• Structure by hierarchy: Put major product attributes first, moving from broad to specific: Category → Sub-category → Attribute (Colour/Size) → Sequential ID.
• Avoid confusing characters: Skip characters like O (letter) and 0 (number) – they’re easily mixed up.

4 costly SKU mistakes to avoid

Even experienced retailers sometimes trip up when it comes to creating SKUs. Watch out for these common mistakes:

1. Reusing old SKUs: Once a SKU is discontinued, lock it away forever. Re-assigning an old SKU code to a new product variant corrupts your historical sales data, breaks analytics trends, and causes reporting chaos.
2. Overcomplicating the code: You don't need the fabric composition, country of origin, and wash instructions in the SKU string. Keep non-essential traits in your product database instead.
3. Inconsistent vendor rules: If different teams or suppliers follow different formats, your system becomes fragmented and harder to scale. Enforce unified naming rules across all lines.
4. Duplicating attributes: Avoid redundant descriptors like adding BLU and NVY within a code structure that already specifies the shade code later.

Using SKU-level data for smarter merchandising & automation

Here’s where retail execution gets exciting. Collecting SKU data is useful, but connecting that data to real-time store environments is game-changing.

When you combine structured SKU tracking with smart retail technology, you can unlock:

• Image recognition audits: Advanced shelf cameras can instantly scan physical fixtures, cross-referencing on-shelf items against your master SKU database to verify planogram compliance in seconds.
• Predictive stocking alerts: Automated triggers that flag potential stockouts based on real-time sales velocity before the shelf actually runs empty.
• Regional performance insights: Instant visibility into how specific SKUs perform across individual stores, regions, or retail formats.

Of course, the ultimate challenge in retail is bridging the gap between what your digital inventory software thinks is happening and what is actually happening on physical store shelves.

Collecting SKU data is only step one. At Dee Set, we help brands turn raw SKU data into actionable field operations. By combining intelligent data platforms with experienced retail merchandising and field teams alongside end-to-end fulfilment & warehousing solutions, we ensure your highest-performing SKUs stay fully stocked, flawlessly presented, and ready to buy.

Want to maximise your on-shelf product performance? Speak to Dee Set’s retail execution specialists today.

SKU FAQs

Can two products have the same SKU?

No. Each SKU should be unique to a specific product variant within your business. Sharing SKUs can lead to tracking errors and inaccurate inventory data.

How long should an SKU number be?

The ideal length is 8 to 12 characters. This provides enough flexibility to capture necessary product attributes while keeping the code readable and easy to manage across inventory systems.

What is the difference between an SKU and an item number?

In many businesses, the terms are used interchangeably. However, an SKU is usually more structured and designed specifically for inventory management and tracking.

Are SKUs the same across different retailers?

No. SKUs are created internally, so the same product may have completely different SKUs across different retailers.