Overview
Dairy goes bad when it gets warm. The cold-chain log is your single screen that shows every temperature reading your stock has seen — from the plant, through the warehouse, onto the truck, all the way to delivery. When a platform raises a deduction claiming you broke the cold chain, or an FSSAI inspector asks "what temperature did this lot sit at?", this is where you prove it.
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.
This screen turns on when the Owner installs the Dairy Pack. Until then the dairy menu does not appear.
This is a read-only screen. Readings land here automatically from your sensors and warehouse logging — you do not type temperatures in here.
Where to find it
Web only. In the admin sidebar, open Dairy → Cold-chain (/dairy/cold-chain). The plain /dairy link redirects straight here, so it is the front door of the Dairy Pack.
Only the Owner sees the dairy menu and this screen. There is no mobile version.
Key concepts
Phase — where in the journey the reading was taken. Five stages: manufacture, warehouse, dispatch, transit, delivery. The Phase tag on each row tells you exactly where the temperature was measured.
Reading status — every reading is judged against the product's allowed temperature range and lands as one of three states:
- In range (mint) — temperature was fine.
- Out of range (the breach) — too warm or too cold. The temperature number turns pink so you spot it instantly.
- Sensor failure — the device could not give a clean reading.
Anchor — what the reading is attached to. A warehouse reading anchors to a warehouse (black tag). A reading taken on the road anchors to a transit vehicle (pink tag) — the registered truck carrying the lot. The transit vehicle is the part the cold-chain Capability does not track on its own; the Dairy Pack adds it so on-the-road readings have somewhere to live.
Breach — an out-of-range reading. The screen counts breaches in the last 24 hours and today, so a warm spell jumps out at you.
Common workflows
Go to Dairy → Cold-chain. It opens already showing the last 7 days, so you see live readings without setting anything up. The three tiles up top read Active vehicles, Breaches today, and Last reading at.
Read the "Out-of-range · last 24h" strip — the big number is your breach count for the day and the line chart shows which hour they clustered in. A flat line means a clean cold chain.
Use the status pills and tap Out of range. The table now shows only the readings that broke the limit, with the temperature in pink.
Pick a stage in the Phase dropdown (e.g. Transit) to see only on-the-road readings. Change the From / To dates to widen or tighten the window — there is no upper limit on how far back you look.
Type a vehicle ID into the vehicle filter to pull the readings for one truck. This matches the vehicle's ID, not its number plate — copy the ID from the Anchor column of any row to filter by it.
Role notes
Only the Owner reaches this screen, and even the Owner can only read it — the cold-chain log has no add, edit, or delete action for anyone. Readings arrive on their own from your sensors and warehouse logging; nobody keys them in here.
The dairy permissions bind to the Owner only once the Dairy Pack is installed. Before install, even the Owner does not hold them — there is no dairy menu to open.
A single role with read-only access, so there is no who-can-do-what grid to show here.
Tips & time-savers
Tap the Out of range status pill to skip straight to the readings that matter — the ones that broke the limit — instead of scanning the whole table.
Gotchas
The vehicle filter matches a truck's internal ID, not its number plate, so typing the plate (e.g. PB-10-AB-1234) finds nothing. Copy the ID shown in the Anchor column and filter by that instead.