Batch genealogy software that answers the recall question in minutes — not days.
Forward and backward traceability across raw lots, intermediates, finished batches and shipments — built as the batch runs, so a mock recall is a query, not a fire drill.
You searched 'batch genealogy software' because the last mock recall took two days.
Trace rebuilt by hand from batch records and delivery notes
Nobody can say quickly which finished lots used a suspect raw lot
Rework and blends break the lineage chain
Customer shipment data lives in a different system to production
Mock recall exercises fail the four-hour expectation
Genealogy exists on paper but not in a form you can query
What genealogy looks like when it is built, not reconstructed.
Parent / child lineage
Every consumption, split, merge, rework and repack writes a link — the tree is complete because it is a by-product of execution.
Forward and backward trace
From a raw lot to every customer shipment, or from a complaint back to the supplier lot and the operator on the step.
Mock recall in minutes
Run the exercise on demand, export the evidence pack, and keep the timing record your scheme audit asks for.
Where-used across sites
Multi-site and multi-stage genealogy in one tree, including intermediates shipped between plants.
Targeted holds
Quarantine exactly the affected lots — inventory status flips instantly so the material cannot be dispensed or shipped.
Evidence pack
Trace report, quantities, disposition and signatures exported as a single defensible document.
What changes when the tree is live.
- Mock recalls complete inside the four-hour window, with the timing evidenced
- Holds land on the affected lots only — not the whole warehouse
- Complaint investigations start with the batch, operator and supplier lot already known
- FSMA 204 key data elements are already captured, not retrofitted
- Customer trace requests answered same day
Standards your traceability evidence maps to.
FSMA 204 (21 CFR 1 subpart S)
Critical tracking events and key data elements for Food Traceability List items, retrievable in a sortable electronic format within 24 hours.
21 CFR 211.188 / 211.184
Batch production records and component traceability — lot numbers of each component used in each batch.
21 CFR 820.65 / QMSR
Traceability of devices and components where a failure could cause harm, through the device history record.
EU GMP Chapter 5 / GDP
Traceability of starting materials and distribution records enabling recall of any batch.
GFSI schemes (BRCGS, SQF, FSSC)
Documented traceability exercises with defined time limits and mass-balance reconciliation.
Batch genealogy and traceability software, answered.
Does it handle rework and blends?
Yes. Rework, blending, splits and repacks each write explicit lineage links, so a blended lot traces back to every contributing lot with quantities.
Can we do mass balance?
Yes. Trace reports include quantity in, out, scrap and remaining stock so the reconciliation your scheme audit asks for is part of the same output.
Does it cover shipments to customers?
Yes, where despatch runs in V5 or your ERP shipment data is synced — the tree continues through pallet, SSCC and delivery.
Is this enough for FSMA 204?
V5 captures the critical tracking events and key data elements at the point they occur and exports in a sortable electronic format, which is what the rule requires.
What about products made before go-live?
Historic lots can be imported with their component links so the tree does not start empty; anything not imported remains traceable through your legacy records.
How long to go live?
Sites already running V5 execution have genealogy from day one. Standalone traceability deployments typically go live within 6–10 weeks.
Run a mock recall this afternoon.
Free trial. Genealogy built as the batch runs, not after the phone call.