SKU Meaning: What a Stock Keeping Unit Is

SKU Meaning: The Definition

A SKU (Stock Keeping Unit) is a unique, company-assigned alphanumeric code that identifies a single distinct product or item variant for the purposes of tracking inventory, sales, and purchasing. Pronounced "skew," it is the most granular unit by which a business identifies what it stocks. Two items that differ in any meaningful attribute — size, color, configuration, pack quantity — receive different SKUs, because the business needs to count and reorder them separately.

Because each organization creates and controls its own SKUs, the same physical product can carry an entirely different SKU at every company that buys or sells it. A SKU is an internal language, not a universal one. That distinction is the source of most confusion around the term, and it is where the comparison to other identifiers becomes useful.

SKU vs. UPC vs. Part Number

SKUs are frequently confused with UPCs and manufacturer part numbers. They serve related but different purposes, and a single item often has all three at once.

The practical upshot: a UPC is the same everywhere, a manufacturer part number is the same for a given maker, and a SKU is whatever your company decides. In procurement systems, the SKU is usually the field your catalog and purchase orders run on, while the UPC and part number help you match items across suppliers. A useful way to remember the distinction is by ownership: you control your SKUs and can change them at will, but you do not control the UPC or the manufacturer part number, because those belong to the maker. That ownership is exactly why SKUs are so flexible — and why they require governance, since nothing external stops two people in the same company from coding the same item two different ways.

Why SKUs Matter in Procurement

For procurement and accounts payable teams, SKUs are the connective tissue between what is ordered, what is received, and what is paid for. A clean SKU on a requisition lets the system pull the right catalog price, apply the negotiated contract rate, and route the order through the correct approval path. It is also what makes accurate spend analytics possible: without consistent item-level identifiers, classifying spend into meaningful categories becomes guesswork.

SKU discipline also fights two persistent procurement problems. Duplicate SKUs for the same item fragment your buying power, hiding the fact that you are purchasing the same thing from several suppliers at different prices. Missing or inconsistent SKUs invite maverick buying outside catalogs and contracts. Tightening item data is therefore closely tied to disciplined tail spend management, where fragmented, low-value purchases are exactly the ones that escape good identification.

It is worth distinguishing the SKU from the broader concept of a material or item master record. The SKU is the identifier; the item master is the full record behind it, holding the description, unit of measure, supplier links, pricing, and classification. A clean SKU scheme is the index that makes the item master usable. When the two drift apart — when SKUs exist without complete master records, or master records carry inconsistent codes — every downstream system inherits the confusion, from purchasing to receiving to reporting. This is why item-data governance is treated as foundational work in any serious procurement transformation: almost everything else depends on knowing, unambiguously, what each thing you buy actually is.

How to Structure a SKU

There is no single correct format, but strong SKUs share several traits. They are short enough to read and type, unique across the entire catalog, and built from meaningful segments that encode stable attributes such as category, supplier, and variant.

• Keep it meaningful but stable. Encode attributes that do not change — category, model, color — and never embed values that move, such as price.
• Avoid ambiguous characters. Letters like O and I clash with 0 and 1; leading zeros get stripped by spreadsheets.
• Stay consistent. A uniform convention across the catalog matters more than the cleverness of any single code.
• Plan for growth. Leave room in each segment so new variants and categories fit without restructuring.

Item master and SKU data sit at the heart of catalog-driven buying in any source-to-pay platform, which is why governance of this data is a recurring theme across our reference library. For the full set of procurement terms, see our procurement glossary.

SKUs, Data Quality, and AI

Messy SKU data quietly undermines automation. AI-assisted spend classification, three-way matching, and catalog normalization all depend on reliable item identifiers; when SKUs are duplicated, missing, or inconsistent, even sophisticated tools fall back to manual review. This is the same data-quality dependency that shapes outcomes in invoice processing and inventory disciplines such as economic order quantity calculation. Increasingly, AI tools help by deduplicating item masters, mapping SKUs across suppliers, and enriching sparse records — but they amplify good governance rather than replace it. Our independent procurement AI buyer's guide covers how to evaluate that capability when selecting tools.

A Worked SKU Example

A short example makes the structure concrete. Suppose a company stocks office chairs in several colors and sizes. Rather than a meaningless sequential number, a well-built SKU encodes stable attributes in fixed segments — for instance FURN-CHR-ERG-BLK-L, read as furniture, chair, ergonomic model, black, large. A buyer or AP clerk can interpret that code at a glance, and the system can group, filter, and report on any segment: all furniture, all ergonomic chairs, every black variant.

Contrast that with two failure modes. A SKU like 0012345 carries no meaning and, worse, risks losing its leading zeros the moment it touches a spreadsheet. A SKU like CHAIR-149.99 embeds a price, which changes — forcing a re-code every time the cost moves and breaking historical reporting. The discipline is simple: encode what is permanent, leave out what is not, and keep the convention identical across the whole catalog.

SKU Rationalization in Procurement

Over time, catalogs accumulate duplicate and near-duplicate SKUs: the same item entered twice under slightly different codes, or functionally identical products sourced from competing suppliers. This SKU proliferation is quietly expensive. It fragments demand so you lose the volume leverage that comes from consolidating purchases, it inflates inventory carrying cost, and it corrupts spend analysis because the same spend appears under several identifiers. SKU rationalization is the periodic exercise of deduplicating the item master, retiring redundant codes, and consolidating demand onto fewer, better-negotiated items.

The payoff is concrete. Cleaner item data sharpens spend visibility, strengthens your hand in negotiations, and reduces the exception rate in downstream matching. It is closely tied to inventory discipline such as setting an economic order quantity for each item and to the broader work of governing a source-to-pay platform. Increasingly, AI tools accelerate rationalization by detecting likely duplicates and mapping equivalent items across suppliers — turning a manual, months-long clean-up into a continuous, assisted process. As always, the software amplifies governance rather than substituting for it.

Frequently Asked Questions