SKU, Lot, Serial or Asset ID? Put the Right Code on the Label

Use a SKU for a product variant, a lot for a production group and a serial number for an individual unit. Keep these as distinct, clearly named fields on labels and records.

A product SKU, a batch number, and a serial number answer different questions. Combining them into one unlabeled string makes receiving and service work harder. Decide which question staff must answer at each scan, then give each identifier a clear role.

Match the identifier to the object

Identifier What it identifies Illustrative example
SKU A stocked product or variant GLOVE-M-BLU
Lot or batch A defined production or receiving group L260817A
Serial number One individual unit SN008417
Asset ID One organization-controlled asset AST-00421
Location Where an item is stored A03-B02-L01

These examples are internal formats, not GS1 assignments. A lot can contain many units of the same SKU. One serial number should resolve to one individual item within the defined system. An asset ID can remain stable even when a manufacturer serial is difficult to read or is not unique across manufacturers.

Make variants distinct before printing

If blue medium gloves and blue large gloves are counted separately, give them separate item records. Keep color and size in explicit fields so staff can filter them. A compact code can appear on the label, but write the readable variant too. Color printing alone is insufficient: people may work in poor lighting or have difficulty distinguishing colors.

For an illustrative apparel record, use TEE-014-NVY-M, description Crew tee, color Navy, and size Medium. Do not assign the same barcode to every size and expect a handwritten size note to prevent mistakes. Scan each variant during the pilot and confirm that the correct stock record opens.

Design labels around the main transaction

A receiving label might use this layout:

NITRILE GLOVES — BLUE / MEDIUM

  • SKU: GLOVE-M-BLU
  • Lot: L260817A
  • Received: 2026-08-20
  • Barcode: generate from the approved receiving key

An equipment label has different priorities:

  • Asset: AST-00421
  • Device: Packing scale 2
  • Barcode: encode AST-00421
  • If found: Contact facilities

Keep purchase date, maintenance history, and custodian in the asset record unless they are essential at the point of use. A crowded label is harder to read and leaves less room for a dependable symbol.

Decide how compound data is handled

A barcode containing SKU|LOT works only if the receiving application knows how to parse that structure. Do not invent separators and assume other systems will interpret them. Where trading partners require GS1 structured data, use the applicable application identifiers and approved formatting. GS1's GS1-128 guidance illustrates separate identifiers for GTIN and lot data.

For a simple internal system, two clearly named fields may be easier than one compound scan. If printing two barcodes, label their purposes and test whether nearby symbols cause accidental scans. Consider workflow prompts that ask for the SKU first and lot second.

Keep traceability when stock moves

Record quantities by SKU and lot at receiving. When splitting a case, transfer the lot reference to the smaller containers before discarding the original carton. Reconcile the quantity moved and keep source documentation available. Never replace a manufacturer lot with an internal receiving date without retaining the original relationship. For serialized equipment, record the manufacturer, model, manufacturer serial, internal asset ID, current location, and status.

An illustrative checkout log is:

Asset ID Issued to Date out Due back Returned / condition
AST-00421 Packing team 2026-08-20 2026-08-21 Complete on return

Select materials for service conditions

A label used on a cardboard stock bin faces different conditions from one on a frequently cleaned tool. Define the surface, handling, cleaning chemicals, temperature, and required life before choosing adhesive and material. Zebra links media selection to application life and environment. Apply a sample to the actual surface, let it settle according to its instructions, then inspect adhesion and scanning after normal handling.

Keep human-readable identifiers available for exceptions, and record any replacement label against the same asset or lot record.

One shipment can need several identifiers

A case of medium blue gloves can carry SKU GLOVE-M-BLU and lot L260817A. Several cases can share that SKU and lot. Their warehouse location can change from receiving to picking without changing either identifier. A serialized instrument, by contrast, also needs its individual serial or asset record retained through every move.

Sources

Related guides

Back to blog