Inventory

SKU

A SKU (stock keeping unit) is a store's own code for one exact item, like a lipstick in one shade and size. Each different version of a product gets its own SKU.

By Mike Akop, founderUpdated 4 min read

On this page
  1. How SKUs work
  2. SKU, barcode and other codes
  3. A worked example
  4. Where it usually goes wrong
  5. Tips for owners
  6. How MazalPOS handles SKUs
  7. Common questions

In short

  • A SKU is your own short code for one exact version of a product.
  • A different size, color or shade is a different SKU.
  • SKUs differ from barcodes, which are shared across stores.
  • Keep the format simple and never reuse a code.

How SKUs work

SKU stands for stock keeping unit. It is a code your store makes up so it can tell one exact item from another. Every product you can count on a shelf has one.

The word exact is the key. A red lipstick and a pink lipstick are different SKUs, even if they come from the same brand and cost the same. A 50 ml bottle and a 100 ml bottle of the same serum are two SKUs. Each one has its own count, price and sales history.

This matters because stock is counted by SKU. If everything shared one code, you could not tell whether you were out of red or out of pink. With a SKU for each, your system can say you have 6 of one and 0 of the other, and warn you before you run out.

A SKU also ties together every other record about the item: its cost, its selling price, its supplier, where it sits on the shelf, and how fast it sells. When you look up one code, you should find all of that in one place. That is why a clean list of SKUs is the backbone of good inventory control.

SKU, barcode and other codes

People mix these up, so here is the difference.

  • SKU: made up by you, for your own use. It can mean anything you decide, such as SER-50 for a 50 ml serum.
  • Barcode (UPC or EAN): a number printed on the package by the maker and shared by every store that sells it. Scanning it can look up your SKU.
  • Product name: what customers see. Names can repeat; SKUs cannot.
  • Variants: the sizes, colors or shades under one product. Each variant has its own SKU. See variant.

A good SKU is short and readable. Many shops use a pattern like brand, product, size and color: for example LUM-SER-50 for a Lumen serum, 50 ml.

A worked example

A boutique sells one candle in three scents and two sizes. That is one product with 3 x 2 = 6 SKUs:

  • CND-LAV-S, CND-LAV-L (lavender, small and large)
  • CND-CED-S, CND-CED-L (cedar)
  • CND-ROS-S, CND-ROS-L (rose)

Say you bought 12 of each small ($8 cost, $22 price) and 6 of each large ($14 cost, $38 price). That is 36 small and 18 large, or 54 candles.

A week later the report shows CND-ROS-S has sold 11 of 12, while CND-CED-L has sold 1 of 6. Without SKUs you would only know you sold 12 of 54 candles in total. With them you reorder rose small, stop reordering cedar large, and you can see the margin on each: the small makes $14 per sale and the large makes $24.

Where it usually goes wrong

  • Skipping SKUs. You end up with one number for products that are really different.
  • Reusing a code. If an old SKU is reused for a new item, history and reports become wrong.
  • Making them too clever. Long codes full of symbols are easy to mistype.
  • Changing codes often. Every change makes past reports harder to read.
  • Selling one item under two codes. Counts split in two and you think you are out when you are not.

Tips for owners

  • Decide on a pattern once and write it down for the whole team.
  • Use capital letters and numbers, no spaces, and keep the code to about ten characters.
  • Give every size and color its own SKU.
  • Put the SKU or barcode on shelf labels so counts are quick.
  • When you retire a product, keep its SKU in your records and never give it to a new item.

A tidy set of SKUs makes stock counts and receiving faster.

If you already have a messy list, clean it up in one session: merge duplicates, give every variant its own code and remove items you no longer carry. It takes an afternoon and saves you from wrong counts for years.

How MazalPOS handles SKUs

MazalPOS supports products with sizes and colors as variants and keeps one live stock count shared by the register, the online store and every location. For a product sold under two names or sizes, linked stock keeps the counts in step. Low-stock alerts and counting stock from your phone work from the same catalog.

Common questions

It stands for stock keeping unit. It is a code that identifies one exact item in your store.

No. A barcode is printed by the maker and shared by many stores. A SKU is your own code, used only in your system.

Services are usually listed by name and price. SKUs matter most for products you count and reorder.

Short enough to read and type, often 6 to 12 characters. Clear patterns matter more than the exact length.

Low stock alertOversellingCost of goods sold

Want the full guide? Read How to Sell Online and In Store From One Inventory.

Written by Mike Akop, founder of MazalPOS. We build and support the register, online store and staff app that stores from Las Vegas to Honolulu run on. Questions about this term? Talk to a real person.

Not sure where to start?

Talk to a real
person today.

Tell us how your store works and we will show you MazalPOS with your own products.

14 days free. No card. Cancel anytime.