Stock Keeping Unit

The SKU is a retail and warehousing invention, not a manufacturing one. A factory assigns a model number to a design. The business that stocks and sells that design assigns its own SKU on top of it. It needs to answer questions the model number was never meant to answer: how many units of this exact variant are on the shelf, how many are on order, and at what price this exact variant sells. The SKU is the unit that stock counts, reorder points, and sales reports are built around, which is the core of inventory management.

Because the business creates the SKU itself, the code is internal by definition. Two retailers selling the identical laptop from the same manufacturer will almost never use the same SKU for it. Each has its own numbering scheme, categories, and reasons for splitting or combining variants. A manufacturer part number works the opposite way: it identifies the same physical item the same way everywhere it is sold.

There is no single standard for what an SKU looks like. Unlike a barcode symbology, the format is whatever the business issuing it decides. Most schemes converge on one idea: a short alphanumeric string built from segments. Each segment encodes one fact about the item, and the string is read from left to right.

A well-designed scheme stays short enough for a person to read on a shelf label and for a scanner to print reliably. It also stays unique across the whole catalog.

Splitting stock by SKU rather than by product name is what makes several everyday inventory tasks possible.

Reordering only the variant that is running low, rather than the whole product line, requires knowing which SKU's stock count has dropped. Comparing which color, size or configuration sells fastest needs sales figures broken out per SKU, not per product. Reconciling a purchase order with what was delivered, the right quantity of the right configuration, is a line-by-line match at SKU level. That is exactly the discrepancy an IT procurement team checks when a shipment of laptops arrives.

The SKU sits in a small group of identifiers that look alike on a label, which is why they get mixed up. Each answers a different question about the same physical object.

In IT procurement and inventory work, the SKU appears earliest in the asset lifecycle, before a device is unboxed, tagged or assigned to anyone. Purchasing teams use the vendor's or reseller's SKU to specify exactly which configuration they order. A particular laptop model with a particular RAM and storage combination is one SKU. The same model with more storage is a different one. Getting the SKU right on a purchase order stops a warehouse from receiving the wrong configuration.

Once hardware arrives, the SKU's job in most organizations effectively ends and other identifiers take over. The SKU told procurement which product to buy. From the moment the box is opened, the serial number identifies that unit, and an internally issued asset tag or inventory number marks it as a tracked, owned item moving through assignment, maintenance, and retirement, the lifecycle that hardware asset management governs. A catalog of models used for purchase planning may still reference vendor SKUs. The daily record of who has which device, however, is built on serial numbers and asset tags, not on the SKU.

1. 1

   Specify

   Procurement picks the vendor SKU that matches the exact configuration, such as RAM and storage.

2. 2

   Order

   The SKU goes on the purchase order, so the warehouse ships the right configuration.

3. 3

   Receive

   Delivered units are checked against the order line by line, at SKU level.

4. 4

   Identify

   Each unit gets its serial number recorded, plus an asset tag or inventory number.

5. 5

   Track

   Assignment, maintenance, and retirement are then recorded against that unit, not against the SKU.

After delivery, the hardware inventory in Anexet keeps one card per device, with the manufacturer, serial number, inventory number, status, and location. The daily record therefore rests on the serial number and inventory number, not on the SKU.

An SKU scheme is only useful while it stays consistent. Recording the original SKU in a configuration management database keeps the history of an item in one place. Four recurring mistakes break that consistency over time:

• Reusing a retired SKU corrupts every historical sales and stock report for the original item.
• Under-splitting variants: different storage sizes under one SKU cannot be reordered accurately.
• Over-splitting variants: separate SKUs for changes that affect no price, stock or reorder.
• Inconsistent segment order: changing what each segment means makes older codes unreadable.

Write the segment rules down before the first SKU is issued, and keep the meaning of each segment fixed for the life of the catalog. Purchase records only cover what was bought through this process, so discovery is still needed to find hardware that arrived outside it.