What Is a SKU? Stock-Keeping Unit Definition, Examples and Best Practices

A SKU, or stock-keeping unit, is a unique alphanumeric code a business assigns to a specific product variant in its inventory. One SKU per variant. A blue large t-shirt gets a different code than the same shirt in green or medium. That distinction is the whole point.

SKUs are internal. You create them. Your trading partners have their own. The format is yours to define, which means there is no universal standard — but there are conventions that make them a lot easier to work with at scale, especially once you are exchanging inventory data with retail partners through EDI.

What Does SKU Stand For?

SKU stands for stock-keeping unit. The name describes what it is literally: a unit of stock that needs to be kept track of. Most people say "skew," not the initials.

The concept has been around since physical retail existed. Warehouses needed a way to identify products without relying on full product names, which are long, inconsistent across suppliers, and easily confused. An alphanumeric code that encodes the key attributes of an item — say, category, color, and size — solves that problem cleanly.

How Is a SKU Different from a UPC, GTIN, or Barcode?

This is where people get tangled up, so it is worth being direct about it.

A SKU is something you make up for your own internal use. A UPC (Universal Product Code) is a 12-digit standardized code issued through GS1 that identifies a product the same way everywhere it is sold. A GTIN (Global Trade Item Number) is the broader international family of codes that UPCs belong to.

The short version: your SKU is for you. UPCs and GTINs are for the world. When you sell through a major retailer, they care about the GTIN on the product. Your warehouse cares about the SKU.

A barcode is the scannable visual representation of either type of code. You can print a barcode for your internal SKU for warehouse picking. You also print a UPC barcode on product packaging for retail scanning. They coexist, and usually do. The SKU vs UPC comparison goes deeper on when each one matters.

Why SKUs Matter in Retail and Ecommerce

The cleaner your SKU system, the faster everything downstream moves.

At the warehouse level, a well-structured SKU tells a picker exactly what to grab without reading a paragraph-long product description. At the reporting level, it lets you break down sales by a specific variant, not just a product family. You can see that the red small hoodie is outselling the navy large four to one, which informs your next purchase order in a way that category-level data never could.

For companies using vendor-managed inventory, SKUs are the shared language between supplier and retailer. When a retailer sends an EDI 852 product activity document to signal what is selling and what needs replenishment, those signals tie to specific SKUs. If your internal codes do not map cleanly to the product identifiers in that document, you get reconciliation problems that take time to untangle.

In ecommerce, SKUs prevent overselling. When a product is listed across your own site, Amazon, and Shopify, a single SKU synced across all three channels means that if the last unit sells on one platform, it shows as unavailable everywhere else immediately. Without that, you are manually managing inventory across channels, which scales badly and fails publicly when a customer orders something you cannot ship.

How to Build a Good SKU System

A few rules that practitioners tend to learn the hard way:

Encode meaning into the code. A SKU like TSH-NVY-L-X communicates category (t-shirt), color (navy), size (large), and brand (X) at a glance. A SKU like 0000421 communicates nothing. The former is useful in a warehouse and in a spreadsheet. The latter requires a lookup every time.

Standardize the format before you have too many products to fix. The right time to establish a SKU convention is when you have ten products. The wrong time is when you have three thousand and need to retroactively recode everything.

Never reuse a SKU. When a product is discontinued, retire the SKU but keep it in your system as archived. If you recycle it onto a new product, historical sales data becomes unreliable and reconciliation against old purchase orders becomes a genuine headache.

Skip special characters. Stick to uppercase letters, numbers, and dashes or underscores as separators. Characters like #, &, and % can break older parsing systems and cause EDI document exchanges to fail. It is also worth avoiding O next to 0, and I next to 1, since they get misread during scanning in ways that are frustrating to debug.

Keep it reasonably short. Codes beyond 12 to 16 characters start causing display truncation in some systems and slow down manual entry when scanning fails.

How SKU Systems Connect to EDI

If you sell through major retailers, your SKU system and your EDI setup have to work together.

When a retailer sends you an EDI 850 purchase order, the line items in that document reference product identifiers. Depending on the retailer, those might be your supplier item number, a GTIN, or a buyer item number. Your EDI system has to map whatever the retailer sends to the correct SKU in your internal system so the right product gets picked, packed, and shipped.

When you send an EDI 856 advance ship notice, it needs to include accurate item-level data, including quantities and identifiers that match what the retailer expects. An ASN where the item identifiers do not reconcile with the purchase order is one of the fastest ways to trigger a chargeback, even if the physical shipment is correct.

Orderful handles the mapping between your internal SKUs and each trading partner's required product identifiers automatically, through API integration with your ERP or order management system. You define your SKU structure once. Orderful translates it for each partner's specific requirements on the back end. For brands managing SKU catalogs across multiple retailers, that translation layer removes a significant amount of manual reconciliation work. You can explore how it works on the platform overview or see the pricing page for what it costs.

SKUs in Sales and Marketing

SKU data is useful beyond operations. It is one of the better tools for understanding what customers actually want versus what you assume they want.

Sales velocity by SKU tells you which variants are pulling weight and which are dead stock you need to discount or discontinue. If the navy colorway consistently outsells everything else across sizes, that is a signal about customer color preference that should inform your next production run. If XS and XL barely move while medium and large sell out every cycle, you are producing the wrong size mix.

Bundle decisions benefit from the same data. Pairing a high-velocity SKU with a slower-moving one in a bundle can clear inventory that would otherwise sit, while also increasing average order value. None of that analysis is possible without SKU-level tracking.

Business agility in retail comes partly from how quickly you can read demand signals and act on them. A clean SKU structure makes that reaction time shorter.

SKUs, UPCs, GTINs, Barcodes and Serial Numbers: How They Fit Together

These codes all show up in the same workflows, so here is the practical distinction between them:

SKU: Internal identifier you create. Specific to your business. Not shared externally unless you choose to. Used for warehouse operations, reporting, and internal tracking.

UPC: Standardized 12-digit code issued through GS1. The same code for the same product regardless of who sells it. Required by most major retailers and marketplaces. Part of the GTIN system.

GTIN: The umbrella term for all standardized product identification codes globally, including UPCs, EANs (European Article Numbers), and others. Used in EDI documents and cross-border commerce.

Barcode: The scannable visual format printed on packaging. Not a code itself — the visual representation of a UPC, GTIN, or internal SKU that allows machines to read it quickly.

Serial number: Assigned to an individual unit rather than a product type. Used for warranty tracking, recalls, and service history. A SKU covers all units of the same variant. A serial number covers one specific unit.

For brands entering retail, these distinctions matter because major retailers like Walmart and Target require valid GTINs and GS1-compliant labels on every shipment. Your SKU system works alongside those requirements internally. The GS1 label generator Orderful provides makes generating compliant shipping labels fast, without needing to navigate GS1's full compliance process manually.

Common Questions About SKUs

What Is a SKU Number?

A SKU number is a unique alphanumeric code a business creates to identify a specific product variant in its inventory. Unlike UPCs, which are standardized globally, SKU numbers are internal identifiers that each company defines in whatever format works for its operations.

What Does SKU Mean in Retail?

In retail, SKU refers to a unique identifier assigned to each distinct product variant, such as a specific color, size, or configuration. Retailers and suppliers use SKUs to track inventory levels, manage purchase orders, and coordinate fulfillment across warehouses and sales channels.

How Is a SKU Different from a Barcode?

A SKU is an internal code you create to identify a product variant. A barcode is the scannable visual representation of a code, whether that is a SKU, a UPC, or a GTIN. A barcode can encode your internal SKU for warehouse use, or a standardized UPC for retail scanning. They serve different purposes and often coexist on the same product.

Can Two Products Have the Same SKU?

No. Each SKU must be unique within your system. Assigning the same SKU to two different products causes inventory errors, reporting inaccuracies, and fulfillment mistakes. When a product is discontinued, its SKU should be archived rather than reassigned to a new item.

How Long Should a SKU Be?

Most practitioners keep SKUs between 8 and 16 characters. Short enough to display correctly in most systems and enter manually when needed, and long enough to encode the key attributes of the product without becoming ambiguous.

How Do SKUs Work with EDI?

In EDI, product identifiers in documents like purchase orders (EDI 850) and advance ship notices (EDI 856) need to match what both trading partners expect. Your internal SKU gets mapped to the product identifiers your retail partners use in their EDI specifications. EDI platforms like Orderful handle this mapping automatically, translating your SKU data into the right format for each partner's requirements.