Food recall readiness starts with connected traceability records
The first hours of a food safety issue should be spent evaluating the facts, not searching five databases to discover which lot went where.
Trace one lot, then verify every link
Start with an ingredient or packaging lot and identify affected finished products, production dates, quantities and the customers or locations supplied. Reconcile the result to receiving, production and dispatch systems.
FSANZ says traceability records should cover appropriate supplier, customer, identifier, transaction and quantity information. The correct operational detail varies by product and business.
A written recall plan is mandatory for relevant food businesses
Food manufacturers, wholesale suppliers and importers must have a written recall plan under Standard 3.2.2. FSANZ guidance covers responsibilities, contact information, tracing affected products, communications and retrieval.
A software database is not a substitute for a tested plan, accurate stock records, the right regulatory notifications or appropriately trained people.
- Confirm the supplier and source lot
- Identify related production and finished lots
- Reconcile shipments and customer recipients
- Record quality decisions and corrective actions
Why the specification matters too
A traceability result becomes more useful when investigators can also find the effective product specification, material declaration and recent changes. Linking those records helps technical, quality and supply chain teams form a consistent picture.
SupplySpec is designed to connect these records while leaving formal recall decisions and legal obligations with the manufacturer.
General information only. SupplySpec supports documentation, record control and review workflows. It does not provide legal advice, independent certification or a guarantee of regulatory compliance.