Mon – Sat: 9:00 AM – 7:00 PM IST
Quality

Batch traceability and lot genealogy

Answering which finished goods contain a suspect raw batch — in minutes rather than days.

In short

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.

Why It Matters

Why this matters in practice

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.

Backward trace: what went into this batch
Forward trace: where did this input end up
Limits recall scope to affected batches rather than everything
Required in food, pharmaceutical and many regulated sectors
How It Works

How it works in practice

1

Capture at receipt

Supplier batch recorded on goods receipt. A missing supplier batch breaks the chain at its first link.

2

Link at consumption

Component issue to a work order records which lot was consumed by which output batch.

3

Record the output

The finished batch receives its own number, linked to every input lot that contributed.

4

Capture at despatch

Which batch went to which customer on which delivery. Without this the forward trace stops at your gate.

5

Test the trace

Run a mock recall periodically with a defined time target. This is the only way to know the chain actually holds.

Worked example

A worked example: four hours or four weeks

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Breaks at repack and bulk transfer

Decanting bulk into smaller containers commonly loses the link unless the transaction records it explicitly.

Batch not captured at despatch

A complete internal trace that cannot say which customer received the batch is not a recall capability.

Never testing the trace

A mock recall exposes the gaps while they are cheap. Most organisations find at least one.

Traceability only in production

Returns, rework and samples also move material. Each is a place the chain commonly breaks.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

Many regulated sectors expect affected batches to be identifiable within a few hours. The practical test is a mock recall against a target you have agreed internally or with a regulator.
A batch covers a quantity produced together; a serial number identifies one individual unit. Serial tracking is finer and more effort, and is used where individual units must be identifiable.
At minimum one step back and one step forward, which is the common regulatory baseline — you must know your immediate supplier and your immediate customer. Full internal genealogy through production goes considerably further and is what makes a narrow recall scope possible. Retention periods should follow your sector's requirements and the shelf life of the product, whichever is longer.
Batch splitting and merging without recording the linkage, rework that re-enters production without a new batch identity, bulk storage where batches physically mix, and manual processes where the batch number is written down rather than scanned. The last is the most common: a batch number transcribed by hand at one step is a genealogy link that may or may not be correct, and you discover which during a recall.
Yes, at least annually, and treat the findings seriously. A drill reliably reveals things no review finds: a production step that does not record batch linkage, a customer delivery record that cannot be matched to a batch, a trace that takes six hours when the regulator expects four. Discovering those during a drill costs a day. Discovering them during an actual recall costs considerably more.
No — they answer different questions. Batch traceability identifies a quantity produced together, which is sufficient for most food, chemical and general manufacturing requirements. Serialisation identifies each individual unit and is required in specific regulated contexts, notably pharmaceutical supply chains. Serialisation is substantially more demanding to implement, so the first question is whether your obligations actually require unit-level identity or batch-level identity.
Related

Where to read next

Quality management in ERP

Read more

FIFO vs FEFO

Read more

Serialisation in pharma

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.