Answering which finished goods contain a suspect raw batch — in minutes rather than days.
Batch traceability records which input lots went into which output batches, and where those outputs went. Backward tracing answers what a finished batch was made from; forward tracing answers which customers received product containing a given raw lot. Lot genealogy is the linked record that makes both possible.
Traceability matters on exactly one day, and on that day it matters enormously. A supplier notifies a contamination; you need to know within hours which batches are affected and which customers have them. Businesses that have never tested a trace discover during the incident that the chain breaks somewhere — usually at a repack or a bulk transfer.
Supplier batch recorded on goods receipt. A missing supplier batch breaks the chain at its first link.
Component issue to a work order records which lot was consumed by which output batch.
The finished batch receives its own number, linked to every input lot that contributed.
Which batch went to which customer on which delivery. Without this the forward trace stops at your gate.
Run a mock recall periodically with a defined time target. This is the only way to know the chain actually holds.
A supplier notifies you that a raw material batch delivered three months ago was contaminated. The regulator will ask what you did with it, and how quickly you can say.
With batch genealogy recorded through production, the backward and forward traces run in minutes. The raw batch went into six production batches; those went into four finished product batches; those shipped to 23 customers on identifiable delivery notes, with quantities. The recall covers those 23 customers and that quantity. The exercise is a report.
Without it, you know you received the material and you know what you produced that month, but not which went into which. The only defensible recall scope becomes everything produced in the window — potentially hundreds of customers and many times the product. The direct cost difference is large and the indirect cost is larger, because a broad recall damages customers who were never at risk. Traceability is not primarily about finding problems; it is about bounding them.
| Term | What it means |
|---|---|
| Batch | A quantity produced or received together, sharing characteristics and usually an expiry. |
| Forward trace | From a batch to everywhere it went — which products, which customers. |
| Backward trace | From a finished product to every input batch that went into it. |
| Genealogy | The full tree of parent and child batches through multiple production stages. |
| Recall scope | The set of affected product determined by the trace. Narrow scope is the whole objective. |
Decanting bulk into smaller containers commonly loses the link unless the transaction records it explicitly.
A complete internal trace that cannot say which customer received the batch is not a recall capability.
A mock recall exposes the gaps while they are cheap. Most organisations find at least one.
Returns, rework and samples also move material. Each is a place the chain commonly breaks.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Trace completion time | How long a full forward and backward trace takes. Practise it before you need it. | |
| Genealogy completeness | Share of production with unbroken batch linkage. Gaps are where traces fail. | |
| Recall simulation results | Periodic drills. The findings are always more useful than the confidence beforehand. | |
| Batch splitting and merging events | Where genealogy gets complicated, and where errors concentrate. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.