Lot-by-lot trace records and recall drills for small packaged-food makers
TL;DR Lotledger gives small packaged-food makers a lot-level record of which raw-material bills went into each batch and which distributor took it. When a lab report or complaint lands, the owner can name the affected lots and buyers within an hour. Makers pay a monthly fee per plant. And no, there's no blockchain.
FSSAI has had recall regulations since 2017, and it keeps tightening how they're used. In June 2024 it told states that once a sample is found unsafe and the appeal route is closed, officers should push for a recall under those regulations[1]. In March 2026 it went further - food businesses must now log the recalls they start inside FoSCoS[2].
The pressure is real. FSSAI's own 2022–23 data showed roughly a quarter of the domestic products it checked were non-compliant[3]. In August 2023, packaged curd from one dairy made 280 people ill at two stations in Kutch, and the investigators asked for better record-keeping and traceability[4]. Yet a small pickle, namkeen or spice maker usually keeps batch details in a register and invoices in accounting software.
Ask which shops got a given lot and most can't answer the same day.
What it does, in regulatory terms: record-keeping and recall support only. Lotledger doesn't test food, certify anything as safe, or file with FSSAI on the maker's behalf. The licence holder stays responsible under the 2017 recall regulations[1].
Every pack already has to carry a lot or batch number[5]. At packing, the supervisor scans or keys that code and ties it to the raw-material bills used that shift. Dispatch comes from the invoice - lot, quantity and distributor. When something goes wrong, the owner enters one lot code and sees its inputs, any other lots that shared those inputs, and every buyer with a phone number. Lotledger drafts the distributor message and lays out the details FoSCoS asks for. Once a quarter it runs a mock recall and times how long the trace took.
I reframed the seed, which pitched blockchain, IoT and AI. A small maker's records are missing, not tampered with, so a shared ledger adds cost and fills no gaps. I kept the goal of fast tracing and dropped the ledger.
The owner or quality head of a licensed small or mid-sized food manufacturer pays. My test price is ₹2,000–5,000 a month per plant, which is an assumption to check. What do they use today? A paper register, which is free, or enterprise suites from US traceability vendors, which are built for large brands working to US rules[6]. Cluster associations could later buy seats for their members.
The March 2026 FoSCoS order made recalls something a business records in a government system, with officers able to open one that the maker then sees[2]. That came on top of the June 2024 directions linking unsafe samples to recalls[1]. GS1 India now sells a traceability tool for source-to-shelf tracking[7], which tells you the standards body expects brands to trace.
I found no public figure for Indian spending on traceability or recall software. The firmest India number is the regulator's own - about one product in four failed its checks in 2022–23[3]. Adjacent context from the US shows what an enforced system produces. The FDA logged 26,877 food recalls from 2012 to 2024, 37.6% for bacterial contamination and 33.6% for undeclared allergens[8]. One US vendor says more than 2,500 brands use its tools[6].
US enterprise suites have traceability and recall modules, framed around the US FSMA 204 rule[6]. GS1 India's tool tracks a product's journey on GS1 barcodes[7], but it needs registered GTINs and its site doesn't describe a recall workflow. Accounting tools record invoices and sometimes batches, but in my view they don't link inputs to output lots or rehearse a recall.
I didn't find an Indian recall tool priced for small makers, though my search this session was limited.
| Difficulty | Moderate (38/100) |
| Starting capital | ₹45–85 L |
| Time to launch | 5–8 months |
The software is simple. The hard part is habit, which means getting a supervisor who also runs the packing line to link lots every shift. The trace also stops at the distributor, because sub-distributors and retailers sit outside the system. Selling takes patience, one cluster at a time.
No product licence. The software itself needs nothing beyond the baseline, but your clients' recall duties shape what you build.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't let AI decide whether a recall is needed. That call and the filing stay with the licence holder.
Want to work out the AI layer for Lotledger? Talk to Yash →
Here's what can go south -
I like this one more than the flashy version. If you've run quality or operations in a food plant and can sell owner to owner inside one cluster then it's a good fit. If you're hoping to sell "blockchain traceability" to big brands then skip it. First prove that 20 plants keep logging lots for eight straight weeks and can finish a mock recall in under an hour.
My estimate is ₹45–85 L, mostly product build, onboarding staff and the first year of sales.
No product licence. The maker stays responsible for recalls under the 2017 regulations, and you need DPDP consent for the contacts you message.
Yes. Most markets require lot codes and recall plans, so the need exists. Map your output to the local regulator's recall process first.
The free Lotledger validation kit has the line-by-line capital breakdown, the effort scoring, the recall and labelling checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for food makers, and 5 assumptions to test. Download the kit →
Thinking about building Lotledger or something close to it? The make-or-break work is getting plant supervisors to link lots every shift without being chased, and that's the kind of thing I help founders figure out. If you need a hand, you know where to find me. Talk to Yash →
For illustration only. Names are fictional and ideas hypothetical; sourced facts are real but may be out of date. Nothing here is legal, financial or professional advice, and Yash Khatri is not personally liable for any use of it. Read the full disclaimer.