Home / Blog / Traceability

Traceability

Why lot genealogy matters for recalls and audits

By Karel Quintana · Updated October 10, 2026

Lot genealogy is the map from a raw-material lot to the finished goods that contain it, and from those goods to the customers who received them. On a quiet week that map feels optional. Plants keep it in formulation records, batch tickets, and shipping files, and someone who has been there long enough can usually stitch an answer together.

The week stops being quiet when a supplier calls about a lot, a customer asks what went into a tote, or an auditor points at a batch and waits. “We can reconstruct it” then means days of digging, a wider recall than you may have needed, and a conversation nobody wants to have while the binders are still open.

Forward trace and backward trace are both the job

A usable genealogy answers in both directions. Backward: this finished lot was made from these component lots, on this batch, with this release status. Forward: this raw lot was consumed by these batches, which produced these finished lots, which shipped to these customers. One direction without the other leaves either the cause or the exposure unanswered.

The map has to include what actually happened, not only the formula:

• Lots consumed, including substitutions and rework additions.
• The batch or job that consumed them, and the finished lots it created.
• Holds, QC release, and anything that should not have shipped.
• Shipments, so “affected product” becomes a customer list instead of a warehouse guess.

If consumption is written on paper at the end of the shift, the map and the batch can disagree. Genealogy starts during the run. That is the same capture described in in-process visibility. You cannot bolt a clean trace onto a batch record that was filled in later.

What the phone call actually costs

The expensive part of a recall is not only the product you take back. It is the time the plant spends proving scope, the product you hold because you are not sure, and the confidence of the person who has to call the customer. A trace that takes minutes lets you name the lots that are in and the lots that are out. A trace that takes days tends to grow, because uncertainty is safer to include than to explain.

Audits are the same question with a calendar. The auditor is not impressed that the plant can eventually find the ticket. They are checking whether the record exists as the way you work. MFGMAX Nutra ERP is built for lot genealogy, QC release, and recall-ready traceability in nutraceutical, cosmetic, and pharmaceutical operations. The software does not replace your quality system or your regulatory obligations. It keeps the lots, the batch, and the shipment in one place so the answer is not a project.

Repair stations live a related version of this problem under FAA records, certified parts, and return to service. MFGMAX Aviation is for that record. It does not replace the repair station manual, the certificate, or an approval.

Where genealogy usually breaks

The breaks are ordinary. A substitution written in the margin. A rework batch that consumed a finished lot and was tracked on a side sheet. A shipment picked from two lots and billed as one. An ingredient received under a supplier lot that never got its internal lot number. Each one is small until the question arrives, and then each one is a gap in the map.

This is the fourth of the five decisions: are we ready to ship with a record we can defend? The plants that are ready did not start the trace on the day of the call. They recorded the lot when it was consumed, which is also what makes expiration visible to the schedule before the batch starts. One lot record serves planning and the recall. Two unofficial lists serve neither.