How Do I Track Batch Genealogy?

You track batch genealogy by connecting every important movement in the life of a batch: raw material receipt, supplier lot, quality status, material issue, production consumption, finished goods output, quality release, storage, dispatch, and customer delivery.

Batch genealogy is the story of a product batch. It answers two critical questions:

• Backward traceability: what went into this batch?
• Forward traceability: where did this batch go?

For pharma manufacturers, this is essential for quality investigation, complaint handling, recall readiness, expiry control, and operational confidence. If the team needs hours or days to reconstruct batch history from registers and spreadsheets, the system is too fragile.

AICAN Optiwise helps manufacturers connect inventory, production, quality, sales, finance, and reporting so batch records are easier to follow.

Start with batch-wise receiving

Batch genealogy begins at material receipt. When raw materials or packaging materials arrive, the system should capture the supplier, item, supplier lot, internal batch number if used, quantity, manufacturing date, expiry or retest date where applicable, and storage location.

If this step is weak, everything after it becomes weak.

For example, if a raw material is received only as "500 kg" without lot identity, production cannot later prove which lot went into which finished batch. This makes investigation difficult.

A good ERP should make batch or lot entry part of the receiving workflow, not an optional note.

Connect quality status to material lots

After receipt, materials often go through quality inspection. The material may be under inspection, approved, rejected, blocked, or held.

Batch genealogy should include this status history.

The system should help answer:

• Was the material approved before use?
• Who approved or rejected it?
• When did the status change?
• Was the lot ever blocked or held?
• Was any part of the lot rejected or returned?

This connects traceability with quality discipline.

Record batch-wise material issue

When production starts, materials should be issued to a specific production batch. The ERP should capture exact material lots and quantities.

A proper material issue record includes:

• Production batch number
• Item code and name
• Raw material lot or batch number
• Quantity issued
• Quantity consumed
• Quantity returned where applicable
• Storage location
• User and time record

This is the heart of backward traceability. Without it, the finished batch cannot be reliably connected to inputs.

Capture production output and yield

The production batch should record actual output, yield, wastage, rejection, rework, and stage completion where relevant.

Batch genealogy is stronger when production data connects to both input materials and finished goods.

For example:

• Production batch PB-102 consumed raw material lots RM-10 and RM-11.
• It produced finished goods batch FG-204.
• FG-204 had 950 kg released, 20 kg rejected, and 30 kg under hold.

This type of record helps production, quality, finance, and management understand what happened.

Link finished goods to quality release

Finished goods should not become freely available for dispatch until the defined quality process is complete.

Batch genealogy should include:

• Finished goods batch number
• Production batch reference
• Quality inspection result
• Release or hold status
• Rejection reason where applicable
• Release date and responsible user where configured

This matters because forward traceability should not only show where goods went. It should also show whether they were released according to the company’s process.

Track dispatch and customer movement

Forward genealogy connects finished goods batches to sales invoices, delivery challans, customers, locations, and shipment dates.

The ERP should answer:

• Which customers received this finished batch?
• What quantity was dispatched to each customer?
• Which invoice or delivery record was used?
• Is any quantity still in stock?
• Was any quantity returned?

This is important for complaint handling and recall readiness. If a customer reports an issue, the company can trace the affected batch and understand related dispatches quickly.

Use a batch genealogy report

A useful batch genealogy report should show the full relationship in one place.

For a finished batch, the report should show:

• Finished goods batch details
• Production batch reference
• Raw material lots consumed
• Packaging material lots used
• Supplier details where needed
• Quality status and release records
• Output quantity and yield
• Dispatch records
• Customer details
• Remaining stock

For a raw material lot, the report should show all production batches and finished goods batches where it was used.

This two-way view is what makes genealogy operationally useful.

Why spreadsheets fail batch genealogy

Spreadsheets can store batch numbers, but they rarely enforce traceability. Users can skip fields, enter inconsistent formats, overwrite old data, or forget to update linked sheets.

Common spreadsheet problems include:

• Different batch number formats
• Missing supplier lot details
• Material issue not linked to production batch
• Quality status stored separately
• Dispatch records not connected to finished goods batch
• No reliable audit trail
• Slow investigation during complaints
• High dependency on one person who knows the file

ERP reduces this risk by making genealogy part of the transaction flow.

Where Optiwise fits

Optiwise helps manufacturers build connected traceability across inventory, production, quality, sales, and reporting.

A practical implementation can support:

• Batch-wise material receipt
• Quality status control
• Batch-wise material issue
• Production batch tracking
• Finished goods batch creation
• Quality release visibility
• Dispatch traceability
• Batch genealogy reports

AICAN approaches ERP as a practical plant management system, where traceability should be available when teams need it, not reconstructed after panic starts.

Founder’s Note

Batch genealogy is one of those features that feels boring until the day it saves the team. When a complaint comes in or a quality question appears, the factory should not depend on memory. At AICAN, we believe the system should tell the batch story clearly: what came in, what was used, what was made, what was released, and where it went. Learn more at About AICAN.

FAQs

What is batch genealogy?

Batch genealogy is the traceable relationship between raw material lots, production batches, finished goods batches, quality records, stock movement, and customer dispatches.

How do I track batch genealogy?

Use ERP to capture batch-wise receiving, quality status, material issue, production consumption, finished goods output, quality release, dispatch, and customer movement in one connected flow.

What is backward traceability?

Backward traceability shows which raw material lots, packaging materials, suppliers, and process records contributed to a finished goods batch.

What is forward traceability?

Forward traceability shows where a finished goods batch was dispatched, which customers received it, and what quantity was shipped.

Why is batch genealogy important in pharma?

It supports quality investigation, complaint handling, recall readiness, expiry control, and confidence in batch records. It also reduces the time needed to reconstruct batch history.