Overview
When an FSSAI inspector or a Blinkit complaint asks "where did this carton come from?", you need the answer in hours, not days. The FSSAI lot trail is the thread that ties every dairy batch back to the farm-stage milk lot it came from, the date it was processed into this SKU, the lot code printed on the carton, and the manufacturer's FSSAI licence on the label. Get the trail right and a recall is a few clicks; get it wrong and the trail breaks at the worst possible moment.
Paid Pack · locked
This article is part of the Dairy PackDairy Pack
You can read the guide. The actions it describes unlock when an owner adds this Pack in Billing & entitlements.
The trail ships with the Dairy Pack. The Owner installs the Pack from billing to switch it on — once it is active, the four trail fields appear on every dairy batch and the Recalls, Cold-chain and FSSAI Alerts screens light up.
Where to find it
The trail is not a single screen — it is data threaded through your batches, and you read it in three places. All three live under Dairy in the sidebar and are visible to the Owner only.
- Cold-chain log —
/dairy/cold-chain(the Dairy landing route/dairyredirects here). Answers "what temperature did this lot sit at?" across manufacture → warehouse → dispatch → transit → delivery. - Recalls —
/dairy/recalls. Where the trail does its real work — recalls are keyed on the FSSAI lot code. - FSSAI Alerts —
/dairy/fssai-alerts. Watches every FSSAI licence in the chain for expiry.
Web only. A dedicated single-page trail view (powered by the dairy-compliance and dairy-lot-temperature-trail query aggregators) is specified but not yet built — for now you assemble the trail from these three screens.
Key concepts
- FSSAI lot code — the regulator-format code printed on the carton. This is the recall axis: one recall is keyed on one lot code, and that one lot code can map to many affected SKU batches.
- Source milk lot — the farm-stage lot the milk was procured under. One source milk lot typically becomes several SKUs — curd, paneer, butter — so this is where recall queries pivot.
- Processing date — when the source milk became this SKU, recorded to the hour. Different from the broader "manufactured-on" label date.
- Manufacturer FSSAI number — the 14-digit licence on the label, captured as a copy on the batch. A carton's actual licence can differ from the manufacturer master (loan-licence runs, recent renewal), so it is captured independently.
- FSSAI licence chain — three licences feed the trail: the manufacturer's (14-digit, with validity and a state/central type), each supplier's (for milk-stage procurement points), and your own tenant FSSAI. The FSSAI Alerts screen watches all of them.
Common workflows
Open Dairy → Cold-chain (/dairy/cold-chain). The default view shows the last 7 days; widen the date range or filter by phase to see a lot's full manufacture → delivery temperature history. Out-of-range readings show in pink-ink so a breach jumps off the page.
Open Dairy → Recalls (/dairy/recalls) and hit Initiate recall. Enter the FSSAI lot code from the carton, a reason (at least 8 characters), and optionally the source milk lot ID. The system resolves the affected batches from the lot-code metadata link and records them on the recall. You can't open a second recall on a lot code while an earlier one for it is still running.
On the recall, hit Move to notifying. Neev computes every customer who received any quantity of any affected batch and creates one notification row each, so you can track recovery per customer.
On the Customers tab of the recall, hit Record recovery for each customer — log how much came back to the warehouse and how much was disposed of in-field. When recovery is in, hit Mark completed. Closure notes are mandatory. Completion is terminal — there is no re-open — so file the FSSAI report and finish recovery before you close.
Use File FSSAI report on the recall to record the report's path or URL. This is separate from closing, so you can file the report before every customer's recovery lands.
Role notes
Dairy Pack screens — including the whole FSSAI lot trail — are Owner-only. The Owner holds every non-Pack permission in Neev, and the dairy permissions bind to the Owner the moment the Pack is installed. There is no separate "dairy manager" role for these screens today; if other staff need to see the trail, the Owner is the account that opens it.
Two limits worth knowing even as Owner:
- You cannot remove the last Owner on the account — the guard keeps at least one Owner standing.
- Dairy permissions are not part of the all-access default; they only exist once the Pack is installed. Uninstall the Pack and the trail screens go read-only, then disappear.
Tips & time-savers
Keep the FSSAI Alerts screen (/dairy/fssai-alerts) in view through renewal season. It watches the manufacturer, supplier and your own tenant licences and warns you at 90, 60, 30 and 7 days out — long before an expired licence quietly breaks the trail on a fresh batch.
Gotchas
The FSSAI licence-number check is deliberately lenient — it accepts legacy 13- and 14-digit issuance and only shows a hint on a non-match, it does not block you. That means a typo'd licence number will save. Eyeball the number against the carton; the trail is only as trustworthy as what you type in.
Dairy trail data is kept for at least 60 months and, once past that floor, moves to cold archival storage and is never deleted — it is there for FSSAI audit and food-safety legal hold. Treat every recall and disposal entry as a permanent record.