Why recall readiness matters
A food recall may be required when a product presents a safety or compliance concern. The response should be driven by traceability, evidence and risk control rather than only by portal completion.
Core recall-readiness records
- Batch and production records.
- Supplier/raw-material traceability.
- Distribution and customer details.
- Complaint, test or inspection findings.
- Internal decision and authorisation records.
- Withdrawal, communication and corrective-action evidence.
Practical response sequence
- Identify the affected product, batch and time period.
- Stop further dispatch or sale where appropriate.
- Trace recipients and document communications.
- Use the current FSSAI/FoSCoS functionality where applicable.
- Record quantities recovered/disposed and corrective action.
Current note
FoSCoS currently highlights implementation of Food Recall functionality. Check the live FSSAI/FoSCoS guidance for the current workflow.
Official reference
Practical preparation workflow
- Confirm that FSSAI Food Recall & FoSCoS Recall Functionality – Practical Guide is the correct filing, statement, application or compliance route for the entity and the relevant period.
- Reconcile the underlying books, registers, declarations, challans, approvals or source records before entering data into the portal.
- Check names, registration numbers, dates, reporting period and attachments against the master records. Avoid copying an older filing without checking whether the facts or portal fields have changed.
- Preview the completed filing before submission and retain the acknowledgement, payment/challan record and a complete copy of what was filed.
Records to reconcile
The exact attachment requirement depends on the facts and the current portal. As a working file, keep the following records together and reconcile them before submission:
- FSSAI licence/registration and product scope
- Batch/lot and production records
- Supplier and raw-material traceability
- Distribution/customer records
- Complaint or laboratory findings
- Recall decision/authorisation record
Review after filing
A successful upload does not by itself prove that every underlying compliance requirement has been satisfied. Preserve the acknowledgement and filing copy, update the organisation's compliance calendar or statutory records where relevant, and watch the portal/email for any defect, clarification, notice or status change. If a correction is required, use the current correction, amendment or reply mechanism rather than altering supporting records merely to match an earlier filing.
Current-source check
Portal fields, filing frequency, fees, due dates and administrative practice can change. Before acting, re-check the live guidance of FSSAI / FoSCoS – Food Recall functionality for the exact period and facts. This guide is designed to help organise the records and understand the filing context; it does not replace the live statutory form, portal instructions or case-specific professional review.