Food Traceability
What the exam tests
Food Traceability tests lot-level tracking, recall readiness, and regulatory traceability requirements. Expect questions on one-up/one-down, KDEs, CTEs, and mock-recall performance.
Core rules
- Traceability is the ability to follow a food through production, processing, and distribution; traceback identifies the source; traceforward identifies recipients.
- One-up/one-down records are the minimum for many systems; the lot or date code is the linking key.
- FSMA 204 Food Traceability Rule establishes the Food Traceability List, critical tracking events (CTEs), and key data elements (KDEs) for growers, receivers, processors, distributors, and retailers.
- GS1 standards: GTIN identifies the product, SSCC identifies the logistic unit, and GLN identifies the location.
- Mock recalls test speed, completeness, and mass balance: quantity recovered plus quantity accounted for should reconcile with quantity shipped.
- Blockchain can improve data sharing but does not guarantee data truth.
Worked example
A retailer receives a positive Listeria test on a lot of sliced apples. The traceability team identifies the lot code, finds the receiving record, and traces to the distributor and two stores within 4 hours. Mass balance shows 900 lb shipped, 850 lb sold or on hold, and 50 lb unaccounted for, so the recall is incomplete. The team expands the lookup to the repack date and finds the missing 50 lb in a mixed pallet. The reasoning: a fast traceback means little if mass balance does not close.
Traps
Equating traceability with food safety. Assuming one-up/one-down is enough for FSMA 204. Using a blockchain record as proof of accuracy. Forgetting commingled lots. Failing to test traceability with a mock recall.