Ecommerce

Stock Keeping Unit (SKU)

Also called SKU, item code, article number

The internal code a shop gives each sellable item so stock, orders and reporting all refer to the same thing.

Quick facts: Stock Keeping Unit (SKU)

Category
Ecommerce
Also called
SKU, item code, article number
Level
Beginner
Affects
Stock accuracy, feed approval, reporting, order fulfilment
Where to see it
Your platform's inventory list, Merchant Center item ids, GA4 item reporting
In this article4
  1. How a stock keeping unit works
  2. Why stock keeping units matter
  3. Common mistakes with stock keeping units
  4. Getting it right

How a stock keeping unit works

A stock keeping unit is a code you invent and control. Each one points at exactly one thing a customer can buy — not the style, but the particular size and colour of it — so a shirt sold in a range of sizes and colours is a single product and a whole set of stock keeping units.

It is not a barcode. A global trade item number is issued by the manufacturer, identifies the same item in every shop in the world and cannot be altered. A stock keeping unit is private to your business, means whatever you decide it means, and exists so that your own systems can agree with each other about what was sold.

Why stock keeping units matter

They are the thread joining systems that otherwise have nothing in common. The website, the product feed, the ad platform’s item reporting, the invoice, the stock sheet and the courier manifest each hold a fragment of the story of one order, and the code is what lets you lay those fragments side by side. Without it you can see that sales rose and that returns rose, but not whether it was the same item doing both.

The moment they matter most is when something has to be traced: a faulty batch from a supplier, a variant that is being returned heavily, an item advertised at the wrong price. With a consistent code that takes minutes. With a different naming habit in every system it takes a week, and the answer is still partly a guess.

Common mistakes with stock keeping units

Reusing a retired code for a new product causes the most lasting damage. Historical sales, returns and reviews attach themselves to the wrong item, and no report from that point forward can be fully trusted. Close behind it is one code per product rather than per variant, which makes stock counts meaningless the moment sizes exist.

Then come the format problems. Codes that encode something changeable — price, supplier, shelf location — go stale and then mislead. Spaces, slashes and accented characters break exports and feeds. Leading zeros disappear the first time a file passes through a spreadsheet. And when several people each invent their own scheme, the catalogue ends up holding more than one code for the same item with no way to tell which is authoritative.

Getting it right

Agree one scheme and write it down: a short prefix a human can read, then attributes that will never change, in a fixed order, with the same separator throughout. Use plain uppercase letters, digits and a hyphen. Keep it short enough to type from a printed label and structured enough to stay unique as the catalogue grows.

Then hold the line. One system is the source of truth and everything else copies from it. A code is never reused, and a discontinued item keeps its own forever. When a shop is replatformed, map every old code to its replacement before the migration rather than after — that mapping deserves as much care as the redirect list and belongs in the plan for any ecommerce website build. Pass the same code as the item identifier in your product feed and in analytics, and the reporting starts joining itself up without further effort.

Do and do not

Do

  • Give every sellable variant its own code
  • Agree one scheme and write it down
  • Map old codes to new before any migration

Do not

  • Reuse the code of a discontinued product
  • Encode price or shelf location in the code
  • Use spaces, slashes or leading zeros

Questions people ask about this

What is the difference between a SKU and a barcode?

A barcode number is assigned by the manufacturer and identifies the product globally, so every retailer selling it uses the same one. A stock keeping unit is yours: you create it, you decide its structure, and it only has to be unique inside your business. Shops need both, because they answer different questions for different audiences.

Should a SKU describe the product?

Partly. A short readable prefix for the category or brand, followed by fixed attributes such as size and colour, helps staff work from a printed list without opening a screen. What it must never encode is anything that changes, such as price, supplier or shelf location, because a stale code is worse than an opaque one.

Can I change my SKUs later?

Yes, but only with a full mapping from the old code to the new one, applied everywhere at once: shop, feed, accounting, warehouse and reporting. Without that map you lose the sales history for every item you renamed. The rule that must never be broken is reuse, because reusing an old code silently merges two different products' histories.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.