Food Recall in India: 24 Hours, a List, a Report

The clock starts the moment you know

A supplier calls. One of your batches is being pulled. Or an inspector walks in with a recall order. Either way, the FSS (Food Recall Procedure) Regulations 2017 give you 24 hours to notify the Food Authority — not 24 hours to start thinking about it, 24 hours to file.

Most food business operators don't know this number until they're already past it.

What the regulations actually require

The FSS (Food Recall Procedure) Regulations 2017 lay out three distinct reporting obligations, and they're easy to confuse:

• Regulation 6(3): Notify the Food Authority within 24 hours of deciding a recall is necessary. This is the Schedule I notice — the formal Food Recall Notice with lot/batch codes, the reason for recall, and the distribution list of who received the stock.
• Regulation 9: File a weekly status report (Schedule II) while the recall is active — how much stock has been recovered, what's still outstanding, disposal actions taken.
• Regulation 11: Submit a post-recall report once the exercise is complete.

Separately, regulation 6(1) requires every food business operator to keep distribution records — supplier name, customer name, lot/batch code, manufacture date, expiry date — for one year past the expiry date of the product.

That last point is the one that trips people up. The records have to exist before a recall happens. You can't reconstruct a distribution list from memory at 11 pm on the night you get the call.

The distribution list problem

Picture a typical mid-sized grocery or distributor. A batch of cooking oil comes in from a supplier. Over the next three weeks it moves out across dozens of invoices — some to retail counters, some to a hotel, some transferred to a second godown. A few units come back as returns.

Now the supplier tells you the batch has a contamination issue. The Food Authority needs to know, within 24 hours, exactly where that batch went.

If your records are in a stack of paper invoices or a billing system that doesn't tag stock by batch, you're spending those 24 hours hunting. If you find everything, you're lucky. If you miss even one destination, you've handed an inspector a reason to question every other claim you make.

The recall regulations don't ask for a best-effort list. They ask for the full picture, in Schedule I format, on time.

Why the Reuters crackdown coverage matters here

Reuters reported in September 2026 that FSSAI tests over 100,000 samples a year and roughly one in five come back unsafe, substandard or mislabelled. About 8,000 food business licences have been cancelled in three years. A Navi Mumbai warehouse was found relabelling expired and near-expiry stock of major brands with fake expiry dates — roughly US$80,000 of seized goods.

The enforcement environment has changed. Raids are happening. Outlets of large chains have had permits suspended. The operators being caught aren't all running shady operations — some simply didn't have the records to show they were doing the right thing.

For more on what inspectors look for when they walk in, see what FSSAI expiry inspectors actually check.

What a proper batch record looks like

For a recall to be manageable, you need — at minimum — the following for every batch received:

• Supplier details: name, FSSAI licence number, invoice number and date
• Batch/lot code as printed on the pack
• Manufacture date and expiry date
• Quantity received
• Where it went: every sale, transfer, return, donation — with the recipient's name and date

This is the backward-and-forward traceability that regulation 6(1) requires. Backward to the supplier invoice. Forward to every buyer. One document, complete.

For a detailed walkthrough of how to set this up from the receiving dock, the batch and lot traceability setup guide covers the full flow.

The FSSAI licence number on every bill

One detail that's easy to overlook: FSSAI requires your 14-digit licence/registration number on every bill, cash memo, invoice and receipt — effective since 1 October 2021. During a recall, every document in that distribution list needs to carry it. If your billing system isn't printing it automatically, that's a gap worth fixing before an inspector notices it first.

What the weekly report actually covers

Once a recall is active, Schedule II status reports go in every week. These aren't just a formality. The Food Authority uses them to track:

• How much of the recalled batch has been physically recovered
• What's still unaccounted for and why
• What disposal action has been taken — destruction, return to supplier, donation with appropriate clearance
• Any complications: stock that was repackaged, transferred across state lines, exported

If your disposal records aren't granular — quantity, reason, action taken, date — the weekly report becomes a problem. And if you're disposing of stock without a written record, you're creating a different kind of risk.

The honest limits of a notebook

A well-kept paper register can, in theory, give you a distribution list. If someone writes down every batch code on every outward invoice, you have the data.

The problem is retrieval speed. When you have 24 hours and a batch that moved across 40 invoices over three weeks, flipping through paper is slow. And paper doesn't flag you when a batch is nearing expiry, so you're often reacting to a recall rather than having already moved the stock through legitimate channels.

A notebook also can't block an expired batch from being billed. That matters because one of the most common enforcement findings is expired stock still on the shelf or still moving through the supply chain.

What software should do here — and what ShelfLifePro does

ShelfLifePro captures batch and expiry at receipt — by scanning the GS1 DataMatrix, photographing the label (OCR reads the date), or importing the supplier's file. Every movement after that — sale, transfer, return, donation — is tagged to the original batch.

When a recall happens, the distribution list is a one-click PDF. Backward to the supplier invoice, forward to every recipient. The recall workflow records the lot, blocks it everywhere stock moves, starts the 24-hour authority-notice clock, generates the Schedule I Food Recall Notice, and tracks weekly status through to the post-recall report.

Expired stock cannot be billed. Not a warning — a refusal. And the FSSAI licence number prints on every bill and receipt automatically.

The FoSCoS quarterly submission for expired and rejected stock is a manual upload — the software prepares the batch-level data, but the submission itself is yours to file. That's worth knowing before anyone tells you otherwise.

ShelfLifePro serves food businesses across grocery, FMCG distribution, dairy and bakery, restaurants, and other verticals.

Start with the Distributor Expiry Claim Register — a practical template for keeping the batch-level records that make a recall manageable before one ever happens.