Food traceabilityBatch traceability
Batch genealogy: record input-to-output links during production
Batch genealogy describes the relationships between input lots and output batches. Record those relationships when the transformation occurs so an investigation does not depend on reconstructing ingredient use from purchasing totals or recipes alone.
At a glance
Batch genealogy describes the relationships between input lots and output batches. Record those relationships when the transformation occurs so an investigation does not depend on reconstructing ingredient use from purchasing totals or recipes alone.
Define the decision behind the record
A recipe lists intended ingredients; the batch record needs the lots actually used. Model the relationship explicitly, including quantities and units where recorded. Keep a planned ingredient list distinct from confirmed consumption.
Capture the relationship when ingredients enter production
Identify the actual input lots and the output batch before recording a transformation. Keep the receipt or preceding event reference for each input. A recipe lists intended ingredients; genealogy records which physical lots and quantities were actually used in the specific production event.
Record each input-output relationship separately, including its unit and any documented conversion. If one ingredient lot serves several outputs, retain every link. If reworked or repacked material is involved, connect the preceding batch rather than assigning a new ingredient name that hides its history.
Test both directions: begin with one input and find all recorded outputs, then begin with one output and recover every input lot. Compare the returned relationships with the actual production records, not only with a recipe list. Preserve missing links as findings and repeat the search after correction; a graph display alone does not establish completeness.
Worked example
An operator uses two supplier lots in one preparation. The output batch links to both inputs, with the amounts actually recorded. Searching either supplier lot returns the same relevant output without pretending the recipe alone establishes the lot history.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Output batch identifier
- Actual input lot references
- Quantities and units
- Production event and time
- Operator and supporting record
Example record and review decision
Fictional record example: PREP-01 uses ING-A 8 kg and ING-B 2 kg; PREP-02 also uses ING-A 6 kg; each link references a receipt.
Start from ING-A to find both outputs, then start from PREP-01 to recover both inputs and their actual quantities.
Storing ingredient names in free text without source-lot identities cannot reliably reconstruct the batch relationships.
Test the review, not just the form
Run one forward lookup from an ingredient and one backward lookup from a finished batch. Check that both produce the same relationship set. Investigate missing input references before adding a more attractive genealogy chart.
A few useful answers
Does a saved recipe establish batch genealogy?
No. It describes the recipe; genealogy needs the actual lot relationships for the particular production event.
Can the recipe ingredient list replace actual lot links?
No. It describes the intended formulation, not necessarily the physical lots used. Retain actual batch relationships and the references needed to recover their receiving or preceding production records.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
