Track and trace basics: serialization, aggregation, and genealogy

When a defect escapes, the question is never "was quality important" — it is "which units, made from which lots, shipped to which customers." Track and trace is the system that answers in hours instead of weeks. The pieces are simple individually; the value is in connecting them without gaps.

Lot traceability vs serialization

Lot traceability tracks groups: raw-material lots consumed into production lots, shipped to customers by lot. Required in food, pharma, and automotive; usually sufficient for bulk and process industries.

Serialization gives every unit a unique identity (UDI in medical devices, serialized GTIN in pharma). Required where regulations or customers demand unit-level proof, and increasingly expected for warranty, anti-counterfeit, and service history. Serialization multiplies data volume and line-integration work — label printers, verifiers, cameras, and rework stations must all handle exceptions without stopping the line.

Choose the granularity the risk justifies: serialization where a recall costs millions or regulators require it, lot discipline everywhere else.

Aggregation: the parent-child map

Aggregation records containment: units into cases, cases onto pallets, pallets into shipments. Each parent carries the identities of its children, so scanning one pallet label resolves every unit inside. The failure mode is partial reads — a case scanned but its units missed — so aggregation stations need verification reads and a defined rework flow for broken parents. Commissioning (activating identities at pack-out) and decommissioning (samples, scrap, destruction) must be explicit events, not spreadsheet adjustments.

The MES data model that makes it work

Traceability lives or dies on four records, all timestamped and all linked:

1. Material lots with supplier, certificate, quantity, and status (quarantine → released → consumed).
2. Production orders and operations with the equipment, recipe version, and operators involved.
3. Consumption and production events tying input lots to output lots or serials — the genealogy backbone.
4. Shipping links tying output identities to customers and carriers.

Design for the recall query from day one: "given finished lot X, list every input lot" (backward) and "given input lot Y, list every finished lot and customer" (forward). If either query needs manual stitching across systems, the model has a gap. Test both directions in a mock recall at least annually — regulators and large customers increasingly require proof, not promises.

Line integration notes

Print-and-verify at the point of application, with grade thresholds that reject bad marks before they ship. Buffer label data upstream so a network outage stops labeling rather than shipping unverified product. And plan the human fallback: when the vision system faults at 2 a.m., the crew needs a written procedure for quarantine and relabeling that preserves the chain.

References

• MES vs ERP integration checklist — where traceability data lives
• Lot traceability, genealogy, and electronic batch record — Shopfloor glossary
• Recipe management: ISA-88 basics — batch identity done right