A stock keeping unit, or SKU, is a code a business assigns to each distinct item it sells to track stock, sales and prices. Every combination that needs separate counting, such as each size and colour of a shirt, gets its own SKU. SKUs are internal, so two stores usually use different codes.
One code per countable item
The rule behind a SKU is simple: if the warehouse needs to count it separately, it needs its own code. A mug in two colours is two SKUs. The same mug sold singly and in a gift set of four is also two SKUs, because the set is packed, stored and priced as its own unit.
SKUs exist for the seller’s convenience. Staff use them to pick orders, accountants use them to value stock, and buyers use them to decide what to reorder. Customers may see the SKU on a page or an invoice, but it is not designed for them.
SKU, GTIN, UPC and MPN compared
Several codes can describe the same product, and they are often confused. The key difference is who assigns each one and whether it stays the same across sellers.
- SKU: assigned by the seller, unique only inside that business, free in format
- GTIN: Global Trade Item Number, a standard barcode number issued through the GS1 system and shared by every seller of that item
- UPC: a 12-digit form of GTIN widely used in North America
- EAN: a 13-digit form of GTIN common in many other regions
- MPN: manufacturer part number, chosen by the maker to identify a model
In short, the SKU tells you how one shop organises its stock, while a GTIN or MPN tells you which product it is in the wider market.
When a new SKU is needed
Deciding when to create a new code is where many catalogues drift. A practical rule is that anything the customer could receive differently, or that the warehouse stores differently, gets its own SKU.
- A new size, colour, capacity or pack quantity
- A bundle or gift set that is packed in advance
- A refurbished or open-box version of a new item
- A supplier change that alters the product the customer receives
Changes that do not affect the item, such as a new photo or a reworded description, should keep the existing SKU so sales history stays in one place. Losing that history makes it harder to see how price changes affected demand over time.
Building a readable SKU format
A good SKU is short, consistent and readable at a glance. Many businesses build it from segments: a category or product code, then the attributes that make the item distinct. A blue ceramic mug of 350 ml might become MUG-CER-350-BLU.
- Start with the broadest group and move to the narrowest attribute
- Use letters and numbers only, avoiding spaces and characters that look alike, such as O and 0
- Keep the length fixed per category so codes sort neatly in lists
- Never reuse a retired SKU for a different product
SKUs and price matching across stores
Because SKUs are private, they cannot be used to match your product with a competitor’s listing. Your MUG-CER-350-BLU and a rival’s code 10442 may be the same mug, and nothing in the two SKUs shows it. Matching for price comparison relies on shared identifiers, such as the GTIN or the brand plus MPN, and on attributes when those are missing.
The practical step is to store those shared identifiers next to each SKU in your catalogue. When a product file brought in through product import carries both the SKU and the GTIN, every competitor price can be tied back to the exact internal item it relates to, and pricing decisions stay at the SKU level.
Pricing decisions at SKU level
Cost, demand and competition differ from one SKU to the next, so prices are best set and reviewed there. For example, assume a store sells a phone case at 24 dollars in three colours. Sales reports show the black SKU sells ten units for each unit of the green one. A competitor cuts the price on black only. Responding on black alone protects the margin on the other two colours, which face no direct pressure.
SKU-level data also reveals the long tail. A few codes often produce most of the revenue, while many others sell rarely and tie up cash. Seeing this by SKU helps decide where to compete hard on price and where a steady price is enough.
Mistakes that break SKU systems
- Using the supplier’s code as the SKU, then changing supplier and losing the history
- Giving two variants the same SKU, so stock counts mix
- Putting the price or the year into the code, which goes out of date
- Typing a GTIN into the SKU field and leaving the GTIN field empty
Each of these makes reports unreliable, and unreliable reports lead to poor pricing and reordering decisions.
The fix is usually a short written rule set: who creates SKUs, which segments they contain and what happens to a code when a product is discontinued. Once that rule exists, new staff and new suppliers fit into the same structure instead of inventing their own, and the catalogue stays clean as it grows.
Key takeaways
- A SKU is a seller’s internal code for each distinct item that needs separate tracking.
- GTIN, UPC, EAN and MPN are shared identifiers, while a SKU is unique only to one business.
- Build SKUs from consistent segments and never reuse an old code for a new product.
- Store GTIN or MPN next to each SKU so competitor prices can be matched to the right item.
- Set and review prices at SKU level because cost, demand and competition differ between items.
Frequently asked questions
Is a SKU the same as a barcode?
No. A barcode usually encodes a GTIN, which is shared by every seller of the product. A SKU is the seller’s own internal code. A shop can print SKUs as barcodes for internal use, but they still only mean something inside that shop.
Do I need a GTIN if I already have SKUs?
Often yes. Marketplaces and shopping channels may ask for a GTIN for branded products, and it is the most reliable way to match listings across stores. Products you make yourself may not have one, and the rules for exemptions vary by channel.
How long should a SKU be?
Long enough to be unique and readable, but short enough for staff to type. There is no standard length; many shops settle on a short code built from a few meaningful parts. Consistency matters more than any exact length.
Related terms
In BlackAha, Product Import helps you import products from a CSV template or a product feed.