Food traceabilityBatch traceability
Several input lots in one batch: avoid a single-lot shortcut
When a batch uses more than one lot of an ingredient, preserve every actual input relationship. A form that permits only one supplier lot can force staff to choose an inaccurate shortcut or put essential information into an unsearchable comment.
At a glance
When a batch uses more than one lot of an ingredient, preserve every actual input relationship. A form that permits only one supplier lot can force staff to choose an inaccurate shortcut or put essential information into an unsearchable comment.
Define the decision behind the record
Confirm that the record structure supports repeated ingredient lines or another explicit relationship model. The same product can appear more than once with different lot references. Planned consumption should not automatically replace what was actually used.
Use one relationship row for each actual input lot
Identify the output batch and every physical input lot used, including partial containers and any authorised reused material. Prepare a record that accepts several input rows. A single free-text lot field is easy to overwrite when the next ingredient or supplier lot enters the same production.
Record the actual quantity and unit for each input-output relationship and retain its receipt or preceding record reference. Keep repeated use of the same lot distinguishable from accidental duplicate entry. If several lots share a product name, the name can group them but cannot substitute for their separate identities.
Test backward retrieval from the finished batch and forward retrieval from each input. Every relevant search should recover the same output without losing the other ingredient links. Review the quantities and references against the actual batch sheet and preserve unresolved input identities as explicit gaps rather than choosing whichever lot is easiest to find.
Worked example
A container runs out during a preparation, and the authorised process continues with another identified input lot. The operator records both references against the output batch. A search from either input can identify the related production record.
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 and ingredient
- Every actual supplier lot
- Quantity and unit per line
- Relevant event and operator
- Review of missing references
Example record and review decision
Fictional record example: PREP-03: ING-A 4 kg and ING-B 3 kg, each with its own receipt; output identity remains PREP-03.
A backward search must find both ingredient lots; a forward search from either input must find PREP-03.
A single supplier-lot field invites one ingredient identity to overwrite another when the recipe uses multiple lots.
Test the review, not just the form
Trial an output batch using two lots of the same ingredient. Run forward and backward searches and export the results. Reject a form design that makes one lot disappear merely to satisfy a required single-value field.
A few useful answers
Can we combine the lot codes in free text?
Explicit searchable relationships are easier to review. If free text is used, confirm it preserves every identifier and remains retrievable.
Can one representative ingredient lot stand for the whole batch?
Not where several actual lots were used. Preserve each input relationship and its source reference. A representative value can hide affected ingredients and prevent a complete backward search.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
