Batch Code Traceability: Build It Before You Need It

Most Indian D2C brands treat batch coding as a printing problem. Ink on a pouch, done. It is a records problem. The code on the pack is only useful if you can walk it backwards to a raw material lot and forwards to a set of shipments, invoices and orders. Brands discover the gap during their first quality incident, which is the worst possible time to build a system.

What the rules actually require

For food, the Food Safety and Standards (Labelling and Display) Regulations make a lot number, batch number or code number mandatory on prepackaged food. Bread and milk, including sterilised milk, are the notable exemptions. Packages with a surface area of 100 square centimetres or less get relief from several declarations including batch, which is why sachets and sample packs often carry less. Treat that as label real estate relief, not as permission to skip internal coding.

For cosmetics, the Drugs and Cosmetics Rules require a distinctive batch number preceded by B, Batch No., B. No. or Lot No., along with the manufacturing licence number. The exemption threshold is 10 g or less for solids and semi-solids and 25 ml or less for liquids. Soaps declare month and year of manufacture instead.

Legal Metrology sits alongside, not instead of. The Packaged Commodities Rules govern net quantity, retail sale price, manufacturer or packer identity, consumer care details and month and year of manufacture, and the ecommerce amendments require those same declarations to appear on the listing page. Penalties run to Rs 25,000 for a first offence, Rs 50,000 for a second, and up to Rs 1,00,000 or imprisonment for repeat offences. Batch is your food and cosmetics obligation. The metrology declarations are what marketplaces audit hardest.

Supplements sit in the awkward middle. Most nutraceuticals are regulated as food, so the food labelling rules apply, but buyers and platforms expect pharma-grade batch discipline. Build to the higher expectation.

What a recall actually needs

The Food Safety and Standards (Food Recall Procedure) Regulations, 2017 set the framework. Strip away the paperwork and a recall is two questions under time pressure. Which inputs went into this batch. Where did this batch go. One step back, one step forward.

Step back means your batch manufacturing record ties a finished goods batch to supplier lot numbers for every material that touched it, packaging included. If a flavour house sends a contaminated lot, you need every affected finished batch in minutes, not days. Step forward means every outbound movement carries the batch: the invoice, the e-way bill, the 3PL dispatch note, the marketplace shipment.

Most brands break at step forward. Their system records quantity shipped, not batch shipped. So when a complaint arrives quoting a code, they cannot say which distributor, which dark store or which fulfilment centre received it. The recall becomes total instead of targeted, and the cost multiplies. Pulling one batch from four cities is a manageable expense. A precautionary withdrawal of everything is a quarter written off.

Keep the code simple. Plant, line, date and shift, printed by a coder that logs what it printed, with a stock ledger that carries batch through every transaction. Human-readable date plus a serial works. Clever ciphers that only the QA head can decode fail during an incident.

Batch discipline across 3PLs and marketplaces

This is where Indian D2C loses the thread. Your 3PL warehouse system probably supports batch and expiry, but the feature is often switched off because it slows receiving. Insist on it at contract stage, not after go-live. Three specifics belong in the SOP.

• Receiving captures batch and expiry at GRN, with a hard block on putaway if the field is empty. No exception for urgent inbound.
• Picking follows FEFO by default, and the pick confirmation records the batch actually picked, not the batch the system assumed.
• Returns re-entering saleable stock keep their original batch. Returns that lost their outer pack and code go to quarantine, never back to sale.

Marketplaces add a constraint. Amazon and Flipkart fulfilment centres commingle by listing, not by batch, so once stock enters their network your visibility drops to shipment level. Your inbound record becomes the last clean checkpoint. Log batch against every shipment ID you send and keep the packing list. Quick commerce is better because inventory sits at identifiable dark stores, but you only get that if you push batch on the ASN and reconcile it against the platform GRN.

The mock recall test

Run one twice a year. Pick a batch at random, start a clock, and answer three questions: how much was produced, how much shipped and to whom, and how much is still in your control. Target 95 percent of the batch reconstructed within four hours from records alone, with no phone call to the plant manager.

Brands that pass share three habits. Batch is a mandatory field, never optional. Distribution records name the customer, the invoice and the quantity by batch. And one person owns the file, usually the QA or operations lead, with the founder as escalation.

Brands that fail usually find the same failure point. The co-manufacturer batch record lives in a WhatsApp group and a paper register. If you use a contract manufacturer, their batch record is your batch record. Get a digital copy with every dispatch, or you are relying on somebody else’s filing cabinet during your worst week.

Build it while it is boring. That is the entire argument.