What Are SKU Numbers? Definition, Examples, and How to Create Them

SKU numbers are how retailers keep track of every product in their inventory. If you have ever wondered what SKU stands for, how to create one, or how it differs from a barcode or UPC, you are in the right place. Below, we cover the definition, real industry examples, a step-by-step creation process, common mistakes to avoid, and best practices for keeping your SKU system clean as your business grows.

What Does SKU Stand For?

SKU stands for Stock Keeping Unit. A SKU number is a short alphanumeric code that a business assigns to a product to track it in its inventory. You create it. It belongs to your business. No other retailer uses the same SKU for the same product.

That last point matters. A SKU is not a universal standard. It is a private internal code you build to describe your products in a way that makes sense for your operation.

Here is what a SKU looks like in practice:

TS-BL-MD = T-shirt, Blue, Medium

Anyone on your team who knows your naming system can read that code and know exactly what product it refers to, without opening a product description or searching a database.

What Do SKU Numbers Actually Do?

A SKU number does one job: it gives every unique product variant a distinct identity inside your inventory management system.

When a customer buys a product, your POS system uses the SKU to update stock levels for that exact variant. When inventory runs low, the SKU tells your system what to reorder. When you pull a sales report, SKUs let you see performance by size, color, or any other attribute you have encoded.

Without SKUs, your inventory data becomes a blunt instrument. You might know you sold 40 shirts, but you would not know which sizes sold out and which are still sitting on the shelf.

Every Variant Gets Its Own SKU

The foundational rule of any SKU system is simple: every unique product variant needs its own unique SKU.

A blue t-shirt in size medium and the same t-shirt in size large are two different SKUs. Add a red version of that shirt, and you have a third. Bundle two shirts together, and that bundle needs its own SKU as well.

The moment a product differs in a way that changes how you track it, price it, or stock it, it needs a new code.

SKU Is Not a Barcode, UPC, or Serial Number

Many retailers confuse these terms. Here is a clear breakdown of each:

• A SKU is created by you, for internal use. It lives in your POS system or inventory management software. No other retailer shares it.
• A UPC (Universal Product Code) is assigned by an external organization called GS1. Every retailer selling that product uses the same UPC.
• A barcode is the scannable, machine-readable version of a SKU or UPC. It is generated from a code, not a standalone identifier. See our guides on how barcodes work and how barcode scanners work for more detail.
• A serial number is assigned by a manufacturer to one individual unit, typically for warranty or repair tracking.

The simplest way to remember it: a UPC tells the world what a product is. A SKU tells your business what it is, where it lives, and how it performs.

Do You Need to Buy SKU Numbers?

No. SKUs cost nothing and require no registration. You create them yourself inside your POS system or inventory software. With KORONA POS, you can build SKUs manually or have the system generate them automatically based on the product attributes you enter.

SKU vs. UPC vs. Barcode vs. Serial Number

In practice, retailers use more than one of these systems at the same time. Knowing which does what prevents costly setup errors.

Here is a side-by-side comparison:

When Each One Is Used in Practice

SKUs are used every day inside your store or warehouse. Your staff uses them to locate products, process returns, run stock counts, and read sales reports. They never leave your system.

UPCs come into play when you sell through external channels. If your products are stocked by other retailers, listed on Amazon, or sold through a distributor, those partners need a UPC. It is the code that lets different businesses talk about the same product without confusion.

Barcodes are printed on product labels. When a cashier scans an item at checkout, the scanner reads the barcode and pulls up the corresponding SKU or UPC in the system. The scanner does not store data. It reads the code and passes it to your inventory system to do the work.

Serial numbers are specific to manufacturers. A laptop, a piece of medical equipment, or a firearm each has a serial number that tracks that one physical unit through its entire life, from production to sale to repair. Most general retailers do not assign serial numbers unless they sell high-value goods that require warranty management.

Do You Need Both a SKU and a UPC?

It depends on where you sell.

If you sell exclusively through your own store or website, a SKU system is enough. You control the inventory, so you only need codes that work internally.

If you sell through third-party retailers, wholesale channels, or marketplaces like Amazon, you need UPCs as well. Those platforms require a universal code to list and identify your products. Your SKU and UPC will coexist on the same product, but they serve completely different purposes.

A useful way to think about it: SKUs run your back office. UPCs open doors to external sales channels.

Why SKU Numbers Matter

Most retailers understand that SKUs help with organization. What they underestimate is what happens to the business when the SKU system is weak or missing entirely.

Here is what breaks without a proper SKU system in place.

You Lose Visibility at the Variant Level

Knowing you sold 100 units of a product is not useful if you cannot tell which size, color, or configuration moved. Without SKUs, your sales data sits at the product level. You end up overstocking variants that do not sell and running out of the ones that do. A well-structured SKU system ties every transaction to a specific variant, so your reports show exactly what is performing and what is not.

Returns and Exchanges Become a Guessing Game

When a customer returns an item, your staff needs to identify it quickly and accurately, put it back in the right location, and update stock levels for the correct variant. Without a SKU, that process relies on manual description and human memory. With a SKU, the scan does all of that in seconds.

Reordering Gets Costly

Retailers who reorder without SKU-level data consistently make two mistakes: they over-order slow-moving variants and under-order fast-moving ones. Over time, that imbalance ties up cash in dead stock and causes stockouts on the products customers actually want. SKUs give you the data to reorder based on what is actually selling, not what you think is selling.

Multi-Location Stock Management Falls Apart

If you run more than one location, tracking inventory without SKUs is almost impossible. You need to know not just how many units you have across the business, but which variants are at which location. Our guide on multi-store inventory management covers how this works in practice. SKUs are what make that level of visibility possible.

You Cannot Run Meaningful Reports

Sales reports, product performance analysis, and demand forecasting all depend on clean, SKU-level data. Without it, you are working from incomplete information. Tools like ABC retail analysis use SKU data to rank products by revenue contribution, so you know where to focus your buying and marketing efforts. That analysis is not possible without a SKU system underneath it.

How to Create SKU Numbers

There is no universal standard for SKU creation, though there are some industry SKU standards. You build them to fit your business. That said, there are clear principles that separate a SKU system that scales from one that creates problems as you grow.

Follow these steps when building yours from scratch.

Step 1: Define Your Top-Level Category

Every SKU should start with a short code that identifies the broadest product grouping. Keep it to two or three characters.

For example:

• TS = T-shirts
• JK = Jackets
• SH = Shoes

The first characters of a SKU should tell any staff member immediately what type of product they are holding, before they look up anything else.

Step 2: Choose Your Attributes and Their Order

After the category, you add the attributes that differentiate one variant from another. Common attributes include color, size, material, and style.

The order of attributes matters. Put the attribute your team searches for most often first. For a clothing retailer, that is usually color before size. For a hardware store, it might be material before dimension.

A consistent structure for a clothing SKU might look like this:

[Category] + [Color] + [Size]

TS-BL-MD = T-shirt, Blue, Medium TS-BL-LG = T-shirt, Blue, Large TS-RD-MD = T-shirt, Red, Medium

Anyone who knows the system can read those codes without looking anything up.

Step 3: Set Your Formatting Rules

Before you create a single SKU, decide on the rules and write them down. These rules need to apply to every SKU in your system without exception.

The core rules to establish:

• Length: Keep SKUs under 12 characters where possible. Longer codes increase the chance of data entry errors.
• Characters: Use alphanumeric characters only. No spaces, slashes, or special characters. These break barcode generators and cause errors in databases.
• Case: Pick all caps or all lowercase and stick to it. Mixed case leads to duplicates that your system may treat as different SKUs.
• Separators: Use a hyphen between segments only, and apply it consistently across every SKU.

Step 4: Document Your Naming Convention

Write down every rule, every category code, and every attribute abbreviation in a single reference document. Call it your SKU key.

Without it, the second person who creates SKUs in your business will do it differently. That inconsistency compounds over time and eventually corrupts your inventory data.

Your SKU key should answer these questions for any new product:

• What category code does it get?
• Which attributes are included and in what order?
• What are the approved abbreviations for each attribute value?

Step 5: Enter SKUs Into Your System

Once your naming convention is set, enter SKUs into your inventory or POS software. With KORONA POS, you can input them manually for small catalogs or bulk-import via CSV for larger ones.

Step 6: Generate and Print Barcodes

Once a SKU is saved in your system, a barcode can be generated from it. That barcode goes on the product label. When a cashier scans it at checkout, the system reads the SKU behind the barcode and updates stock levels for that exact variant automatically.

If you use a barcode POS system, this process is built into your workflow. You do not manage it manually.

SKU Number Examples by Industry

SKUs look different depending on what a business sells. The attributes that matter most to a clothing retailer are not the same ones that matter to a liquor store or an electronics shop. Here are real-world examples across six industries so you can see how the logic applies to your own catalog.

Apparel

In apparel, the attributes that matter most are product type, gender or target demographic, color, and size. A retailer selling both men’s and women’s clothing needs gender in the SKU to avoid any overlap between lines.

Grocery

Grocery SKUs need to encode product type, key attributes like organic or conventional, and package size. Perishables move fast, and restocking decisions depend on quickly reading variant-level sales data.

Electronics

Electronics SKUs focus on item type, storage capacity or specs, and color. A customer returning a 512GB black laptop and a 1TB silver laptop should trigger two completely different stock updates. The SKU is what makes that distinction automatic.

Liquor Store

For a liquor store, the key attributes are spirit type, brand or variant, bottle size, and proof where relevant. Inventory at this level is tightly regulated in many states, so accuracy at the variant level is not optional. You can see how KORONA POS handles this in our guide on liquor store inventory management.

Smoke Shop

A smoke shop carries a wide range of products across rolling papers, cigars, pipes, and accessories. SKUs need to encode product type, brand variant, and size or quantity clearly. Our guide on smoke shop inventory management covers how to structure this in more detail.

Ecommerce

SKUs work the same way in eCommerce as they do in a physical store, but they carry additional weight. On platforms like Shopify, WooCommerce, or Amazon, your SKU connects a product listing directly to your inventory count. When a customer places an order, the platform uses the SKU to decrement stock for that exact variant. If your SKUs are inconsistent across channels, your stock counts will not match, and you will end up overselling products you do not have.

Common SKU Mistakes and How to Avoid Them

A bad SKU system causes more problems than no SKU system at all, because it gives you false confidence in data that is wrong. These are the mistakes retailers make most often, and what to do instead.

Mistake 1: Duplicate SKU Codes

Two different products sharing the same SKU is the most damaging error in any inventory system. Every time either product is sold, returned, or restocked, the data goes to the same record. Your stock counts become wrong, your sales reports become unreliable, and the problem compounds silently until it surfaces as a major discrepancy during an audit.

Mistake 2: Reusing a Retired SKU

When a product is discontinued, its SKU should be retired permanently. If you reassign that code to a new product, every historical record tied to the old code now appears to belong to the new product. Your sales history, reorder reports, and cost analysis for both products become corrupted.

Mistake 3: Using Special Characters or Spaces

Spaces, slashes, ampersands, and other special characters inside a SKU code cause errors in databases, barcode generators, and eCommerce platforms. A SKU like “T-Shirt / Blue & Med” will break in most systems before it even gets saved correctly.

Mistake 4: Inconsistent Formatting Across Channels

If your in-store SKUs follow one format and your online store uses a different format for the same products, your inventory data cannot reconcile between channels. You end up with separate stock counts that do not talk to each other, which means you are managing two inventories instead of one.

Mistake 5: SKUs That Are Too Long or Too Cryptic

A 20-character SKU full of random codes is not readable by your staff. If no one can interpret a SKU without looking it up, it loses one of its core functions: letting your team identify a product quickly during a return, stock count, or order fulfillment.

Mistake 6: No Documented Naming Convention

Among growing businesses, the absence of a documented SKU convention is the most common setup error. The first person to build the system does it one way. The next person hired does it differently. Within six months, your catalog has three formats, and no one knows which is correct.

SKU Best Practices for Scaling

Getting a SKU system right for ten products is easy. Keeping it clean at a thousand is where most retailers run into trouble. These practices keep your system reliable as your catalog and team grow.

Standardize Before You Scale

The worst time to fix a broken SKU system is after you have 500 products in it. Reworking codes at that point means updating every record in your inventory system, every product label, and every channel listing. Do it correctly from the start, even if your catalog is small. A clean system with ten products is far easier to expand than a messy one.

Never Create a New SKU for a Price Change

A price change does not make a product a different variant. It is the same item at a different cost. Creating a new SKU for a repriced product splits your sales history in two and makes trend data useless. Update the price in your system and leave the SKU untouched.

Audit Your SKUs on a Regular Schedule

SKUs accumulate errors over time. Products get discontinued, but their codes stay active. New staff create codes that do not follow the convention. Variants get added without a proper structure. A quarterly SKU audit catches these issues before they affect your reporting. Pair it with a physical stock count for a full picture of where your data and your actual inventory stand.

Cut Underperforming Variants Using SKU Data

Your SKU reports will show you which variants are not selling. A color that has not moved in six months, a size that you reorder every quarter but never sells through, a bundle that looked good on paper but sits on the shelf. Use that data to cut those variants. Fewer active SKUs means a cleaner system, less dead stock, and sharper reorder decisions on the products that actually move.

Keep Your SKU System Consistent Across New Categories

When you add a new product category, apply your existing naming convention to it before you create a single SKU. Do not let new categories develop their own format organically. That is how inconsistency starts. Update your SKU key document first, then create the codes.

Use Your POS Reporting to Manage SKU Performance

A SKU system only delivers value if you use the data it generates. The best inventory management software gives you SKU-level reporting on sales velocity, stock levels, and reorder points. Review those reports on a set schedule, not only when a problem surfaces.

Frequently Asked Questions

1. What is a SKU number?

A SKU (Stock Keeping Unit) number is an internal alphanumeric code a retailer creates to identify and track a specific product variant in their inventory. SKUs are not universal. Each business creates its own, based on the attributes that matter most to their operation.

2. What is a SKU number example?

A SKU for a women’s blue t-shirt in size large looks like TS-WM-BL-LG. Each segment identifies one attribute: product type, gender, color, and size. The format is yours to define, as long as it stays consistent across your entire catalog.

3. Is a SKU the same as a barcode?

No. A SKU is the alphanumeric code you create internally to identify a product. A barcode is the scannable, visual representation of that code printed on a product label. The barcode points back to the SKU in your system when scanned.

4. How long should a SKU number be?

SKU numbers should be kept under 12 characters where possible. Shorter codes are easier for staff to read, less prone to data entry errors, and less likely to cause issues in barcode generators or ecommerce platforms.

5. Can two products have the same SKU?

No. Every product variant must have a unique SKU. Two products sharing a code will corrupt stock counts, sales reports, and reorder data. Most modern inventory systems flag duplicates automatically before saving, but manual checks are still recommended.

6. What is the difference between a SKU and a model number?

A model number is assigned by the manufacturer to identify a product design. A SKU is assigned by the retailer to identify a specific variant in their inventory. The same manufacturer model number can correspond to multiple SKUs if the retailer carries it in different sizes or colors.

7. How are SKUs used in Shopify or Amazon?

On Shopify and Amazon, a SKU links each product listing directly to the retailer’s inventory count. When a sale is made, the platform decrements stock for that specific SKU. Consistent SKUs across all sales channels keep inventory counts accurate and prevent overselling.

8. Do I need a different SKU for each size and color?

Yes. Each size and color combination is a separate variant with its own stock level, sales history, and reorder threshold. Every variant requires its own unique SKU.