Food traceabilityReceiving and suppliers
Supplier changes: review the records that depend on the old source
A supplier-change record should identify affected products, information reviewed, effective date and downstream updates. Changing a supplier name in a product list does not establish that receiving instructions, specifications and related assessments were reviewed.
At a glance
A supplier-change record should identify affected products, information reviewed, effective date and downstream updates. Changing a supplier name in a product list does not establish that receiving instructions, specifications and related assessments were reviewed.
Define the decision behind the record
Keep supplier identity separate from product identity. Identify which records rely on the outgoing source and who reviews the replacement. Preserve earlier relationships so a historical receipt remains associated with the supplier that actually delivered it.
Review the records that depend on the old source
Record the old and proposed suppliers, affected product and intended effective point. Identify dependent specifications, labels, receiving instructions, recipes and contacts. Changing a directory entry is different from reviewing the information and operational changes required for the new source.
Compare actual supporting evidence and record decisions by the authorised roles. Keep unresolved questions and conditional approvals visible. Historical receipts should retain their original supplier identity; they should not appear to have come from the new source merely because a shared contact or product record was edited.
Before use, confirm updated instructions reach receiving and production and identify the first affected receipt or batch. Test both current and historical retrieval. A colleague should distinguish the old source, proposed change and implemented new source without relying on a supplier name that has been overwritten everywhere.
Worked example
A site plans to source an ingredient from a new supplier. The change owner collects the relevant information, routes the review and identifies receiving and recipe records requiring attention. The first delivery is recorded against the actual new supplier.
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.
- Old and proposed supplier
- Affected product references
- Information and assessment
- Approval and effective date
- Records and teams to update
Example record and review decision
Fictional record example: CHANGE-05: old supplier SUP-A to SUP-B; affected ingredient, specification, label and receiving instruction references.
Identify which product records depend on the old source and document each reviewed update before the effective change.
Changing the supplier name in a directory does not update historical source evidence or confirm the new ingredient’s equivalence.
Test the review, not just the form
Compare a receipt before and after the change. Both should show the correct historical supplier. Verify how pending orders and stored specifications are handled rather than assuming a single master-data edit updates them safely.
A few useful answers
Should historical receipts show the new supplier name?
They should preserve the identity and context of the supplier involved in the original event.
Should the supplier directory update historical receiving records?
Keep their actual source context. The current directory can identify a new relationship, but older events still need the supplier and evidence that applied when they occurred.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
