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.
