Search
Beginner Certificate on pass

SKU & Barcode Fundamentals

Give every product a clean code and a scannable barcode so stock is accurate and fast to handle.

4 lessons 35 min 5-question assessment 70% to pass

What you’ll learn

  • Explain what a SKU is and why it matters
  • Design a clear, consistent SKU scheme
  • Use barcodes to speed receiving and selling
  • Avoid common SKU and barcode mistakes

Course content

4 lessons · 35 min of reading
01
Lesson 1 of 4 Reading 8 min

What a SKU is

A SKU (stock keeping unit) is your own unique code for a specific product variant — a particular item in a particular size, colour, or pack. It is how the system tells one product apart from every other.

SKUs matter because without a unique identifier you cannot reliably count, reorder, or report on anything. "The blue one, large" is ambiguous; "TSH-BLU-L" is not.

A T-shirt sold in 3 colours and 4 sizes is not one product but 12 SKUs — TSH-BLU-S, TSH-BLU-M, and so on. If you track it as one SKU, you can never tell that the blue larges are sold out while red smalls overflow. Distinct SKUs make each variant countable and reorderable on its own.

Key takeaways

  • A SKU is a unique code for one specific product variant.
  • Without it you cannot reliably count or reorder.
  • It removes the ambiguity of plain-language descriptions.
  • Example: one T-shirt in 3 colours × 4 sizes is 12 SKUs.
02
Lesson 2 of 4 Practice 9 min

Designing a SKU scheme

A good SKU scheme is short, consistent, and readable — usually segments for category, attribute, and a sequence, like "SHO-NIK-42-BLK". Stick to one pattern across the whole catalogue.

Consistency matters because the scheme is only useful if everyone follows it. Mixed styles ("shoe1", "NIKE_BLACK_42", "sku00042") make sorting, searching, and bulk edits a nightmare.

Decide your segments once: a 3-letter category, a 3-letter brand, size, then colour — SHO-NIK-42-BLK for a black Nike size 42 shoe. New staff can then read or build a code without asking, and AWRA can group and filter by segment because every SKU shares the same shape.

Key takeaways

  • A good scheme is short, consistent, and readable.
  • Use segments like category, attribute, and sequence.
  • Everyone must follow one pattern across the catalogue.
  • Example: SHO-NIK-42-BLK reads as category-brand-size-colour.
03
Lesson 3 of 4 Reading 9 min

How barcodes speed work

A barcode is a machine-readable label tied to a SKU. Scanning it at receiving, picking, and the till replaces typing — faster and far less error-prone than reading codes off by hand.

Barcodes matter because manual entry is slow and mistakes compound: one mistyped digit can sell or count the wrong item. A scan is a fraction of a second and effectively error-free.

A cashier scanning 30 items takes seconds and never fat-fingers a price; keying them in by hand takes minutes and risks charging KES 250 for a KES 2,500 item. At receiving, scanning a delivery of 500 units against the PO catches a short shipment instantly instead of at the next stocktake.

Key takeaways

  • A barcode is a machine-readable label tied to a SKU.
  • Scanning replaces slow, error-prone typing.
  • One mistyped digit can sell or count the wrong item.
  • Example: scanning a 500-unit delivery catches a short shipment instantly.
04
Lesson 4 of 4 Reading 9 min

Common coding mistakes

The usual mistakes are reusing a retired SKU for a new product, encoding things that change (like price) into the code, and creating duplicate SKUs for the same item. Each quietly corrupts your data.

Avoiding them matters because a SKU is meant to be a stable, lifelong identifier. If it shifts meaning, every past sale and count tied to it becomes misleading.

If you reuse "SHO-001" for a new shoe after discontinuing the old one, last year’s sales of the old shoe now appear to belong to the new one — your history is poisoned. Likewise, two SKUs for one product split its stock so neither ever hits its reorder point. Keep codes unique, stable, and never tied to price.

Key takeaways

  • Do not reuse retired SKUs for new products.
  • Do not encode changing data like price into the SKU.
  • Duplicate SKUs split stock and break reordering.
  • Example: reusing SHO-001 poisons the old product’s sales history.

Finished the material?

Take the 5-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center