Food Traceability System in India: Rules and What to Record

India does not have one law that requires a consumer-facing, farm-to-fork traceability system for most foods. As of October 2026, traceability duties come from several separate rules: FSSAI's food recall regulations, the lot number required on every packaged food label, APEDA's systems for certain exports, and the organic certification rules. A food business needs to know which of these apply to it, and keep batch records that satisfy all of them.

This guide sets out the rules that do exist, what buyers and exporters usually ask for on top of them, and a practical list of what to record for each batch.

Is food traceability mandatory in India?

Partly. We could not find any FSSAI regulation that requires a brand to give consumers a farm-level trace for ordinary packaged foods (checked October 2026). What the law does require is that a business can identify and recall a batch, and that the batch can be identified from the label.

The Food Safety and Standards Act, 2006

Section 28 of the Food Safety and Standards Act, 2006 deals with food recall (FSSAI food recall page). If a food business operator believes a food it has handled does not comply with the Act, it must start withdrawing that food from the market and inform the authorities. You can only withdraw "that food" if you know which lots it went into and where those lots went.

FSS (Food Recall Procedure) Regulations, 2017

The Food Recall Procedure Regulations, 2017 turn that duty into a procedure. They define traceability and set out how food under recall is to be retrieved from every stage of the food chain. FSSAI's food recall guidelines add that food businesses must keep an up-to-date recall plan, with a model plan annexed. In practice, a manufacturer or wholesaler needs records that link each lot it made or sold to its customers (one step forward) and to its suppliers (one step back).

The lot number on the label

The FSS (Labelling and Display) Regulations, 2020 require pre-packaged food to carry a lot, code or batch identification, along with date marking and the FSSAI licence number. The batch number is what connects the pack in a shop to your internal records. If it is missing, or if one "batch" covers a month of mixed production, a recall becomes much wider than it needs to be. For which licence number goes on the pack, see FSSAI licence for small food brands.

What traceability rules apply to food exports from India?

Exporters face more specific systems, run by APEDA.

• GrapeNet, HortiNet and related systems. APEDA's traceability systems began with GrapeNet for grapes exported to the European Union. APEDA describes HortiNet as a service that collects, stores and reports forward and backward traces and quality data entered by stakeholders, covering produce such as grapes, pomegranates, mangoes, vegetables and citrus. APEDA states that the stakeholders who enter the data are responsible for its accuracy.
• TraceNet for organic exports. APEDA describes TraceNet as an internet-based system for certifying organic products exported under the National Programme for Organic Production (NPOP). Certification bodies record inspection results in it, and operators record their organic production and trade data.

These are government systems with their own registration and data-entry steps. A private traceability tool does not submit data to them on your behalf, so exporters still enter data in APEDA's portals directly. The exporters page covers how internal batch records can sit alongside these portals.

What about organic food traceability?

The FSS (Organic Foods) Regulations, 2017 require organic food sold in India to be certified under NPOP or the Participatory Guarantee System for India (PGS-India), with an exemption for small producers who sell directly to consumers. FSSAI's Jaivik Bharat portal, built with APEDA and PGS-India, lets consumers look up certified products and producers. The certification is done by the certification bodies. A traceability record can show the certificate for a batch, but it cannot make a batch organic.

What do buyers and exporters ask for beyond the law?

Commercial buyers often ask for more than the regulations require. The usual requests are:

• A certificate of analysis for each lot, not a single annual test. A certificate of analysis that names the lot number is much more useful than one that only names the product.
• Source details: which farm, farmer group or supplier, and which district or region.
• Dates: harvest, receipt, processing, packing and dispatch.
• Certificates: FSSAI licence, organic certificate, GI authorised-user certificate if relevant, and any private standard certificates.
• Custody: who held the goods at each step, so that gaps in the chain are visible.
• A recall test: some buyers ask a supplier to trace a lot forwards and backwards within a set time during an audit.

All of these come down to the same batch records.

What should you record for each batch?

Use this as a minimum checklist. It covers the recall regulations, the label, and most buyer questionnaires.

Three habits make these records useful in a recall:

1. Keep batches small and distinct. Do not blend different source lots under one lot number unless the record lists every input lot.
2. Record quantities at every step. If 1,000 kg goes in and 1,400 kg comes out, something has been added that the record does not explain.
3. Attach documents to the batch, not to the product. A lab report filed under "turmeric powder" proves much less than one filed under lot TUR-2026-031.

Farm-to-fork traceability for FPOs and small brands

Farmer producer organisations collect produce from many members, so the source record is the hardest part. Recording each member's contribution at the collection point, with quantity and grade, is what makes later claims about origin hold up.

Making the record visible

Once batch records exist, they can be shared. In IndiTrace, for example, each confirmed batch record gets a QR code that opens a public trace page in the browser. The record is fingerprinted on the Polygon blockchain, which shows it was not edited after it was confirmed. That fingerprint does not show that the facts entered were true, which is why the attached lab reports and certificates matter.

Questions

Q: Is there a mandatory food traceability law in India? Not a single consumer-facing one for most foods (checked October 2026). The FSS Act and the Food Recall Procedure Regulations, 2017 require businesses to be able to recall food, and the labelling rules require a lot or batch number on packaged food.

Q: Which law covers food recall in India? Section 28 of the Food Safety and Standards Act, 2006, together with the Food Safety and Standards (Food Recall Procedure) Regulations, 2017.

Q: What is APEDA TraceNet used for? TraceNet is APEDA's internet-based system for certifying organic products exported under NPOP. Certification bodies and operators enter their inspection, production and trade data in it.

Q: What is the minimum a small food business should record per batch? The source and its location, dates, quantities at each step, the lot number on the label, who received the goods, and a lab report that names the batch.

Q: Does blockchain make a food traceability record true? No. A blockchain fingerprint shows that a record has not been changed since it was confirmed. Whether the facts are correct still depends on who entered them and on the documents attached.