IFS label review: controls and evidence for food manufacturers
IFS audits test more than whether a label looks correct. Auditors want to see that label information is derived from controlled product data and that changes are reviewed before release.
Show the link from product data to the label
Keep the current recipe, ingredient specifications, packaging information and the label version connected. The review should demonstrate how ingredient declarations, allergens, QUID, nutrition and other mandatory information were derived from controlled inputs.
Control label versions and approvals
Make it clear which artwork is current for each product, market and customer. Retain previous versions, approval dates and the responsible QA decision so obsolete artwork cannot be confused with the released version.
Demonstrate change control
When a recipe, supplier specification, packaging item, customer requirement or regulation changes, show how the organisation evaluated the impact on labels and specifications. The strength of the system is the trace from change to assessment to decision.
Keep unresolved issues visible
An open item should remain visible until it is resolved or formally accepted. Avoid workflows that allow a missing supplier statement or unreviewed market wording to disappear because the artwork has already been created.
Prepare the audit trail before audit week
A good IFS label-control process makes evidence available during everyday work: source documents, review findings, decisions, corrective actions and version history. Audit preparation then becomes retrieval rather than reconstruction.
Common control failures to avoid
Typical failures are not always technical mistakes. They are broken handoffs: a new supplier specification reaches purchasing but not QA, an old artwork remains in circulation, the market changes but the product review is copied, or a calculation is updated without recording the source. A robust system keeps those dependencies visible.
Where evidence is incomplete, keep the gap explicit. A documented open question is safer than a field silently completed from memory, a previous version or an assumption that no longer applies.
FOODQA / QA