06 · Capabilities
Opt-in

Cold-chain temperature logging

Track fridge/freezer temperatures against per-location thresholds, auto-open a breach when readings go out of range, and acknowledge/resolve it — for perishable stock.

5 min read · updated 28/05/2026

Opt-in Capability · off

Cold Chain is switched offCold Chain

You can read the guide. An owner or manager flips this Capability on in settings — it then lights up across the app.

Overview

If you move milk, vaccines, frozen goods or anything that spoils when it gets warm, the fridge going off at 3 AM is a real loss — and you only find out when the stock is already gone. Cold-chain logging keeps a temperature record for every storage location, checks each reading against the safe range you set, and raises a breach the moment a reading falls out of range. You see what happened, when, how cold or how warm it got, and what you did about it.

Opt-in Capability · off

Cold Chain is switched offCold Chain

You can read the guide. An owner or manager flips this Capability on in settings — it then lights up across the app.

This Capability is not a switch you flip on its own. It turns on automatically when the Owner installs a Pack that needs it — today that is the Dairy Pack or the Pharma Pack. Install either and cold-chain is force-enabled for the tenant.

Where to find it

The live, reachable screen today is the Dairy Pack cold-chain log at Dairy → Cold-chain (/dairy/cold-chain), and only after Dairy Pack is installed. It is a read-only view of the temperature trail — the readings and any breaches that were raised.

There is no standalone cold-chain screen in the menu yet. The direct controls for setting thresholds, keying in manual readings, and acknowledging or resolving breaches are built and described below, but they are reached through a Pack — they are not a separate page you can open on their own right now. Web only; there is no mobile cold-chain screen.

Key concepts

  • A threshold is the safe temperature envelope for one storage location — a minimum and a maximum in °C, for example 2°C to 8°C for a vaccine fridge. You set one threshold per location.
  • A reading is a single temperature measurement at a location, with a timestamp. Its source is either manual (someone typed it in) or sensor (a logger device pushed it in automatically).
  • A reading is out of range (OOR) when it falls below the minimum or above the maximum for that location.
  • A breach is the record opened when a location goes out of range. It tracks the peak (warmest) and trough (coldest) temperature seen while it was open, and moves through three states: open → acknowledged → resolved.
  • The tolerance window (breachToleranceMinutes, default 30 minutes per location) is how long a location may stay continuously out of range before the background sweep escalates it.

Common workflows

These map to the real cold-chain procedures. They become usable once the Capability is enabled through a Pack.

1
Set the safe range for a location

Give a location its minimum and maximum °C (for example a freezer at -18°C, or a dairy chiller at 2°C–8°C) and, if you want, a tolerance window in minutes. One threshold per location — saving again updates the existing one.

2
Record a reading

A reading comes in two ways. A manual reading is typed in with the temperature and an optional photo or note. A sensor reading is pushed in automatically by a connected logger. Every reading is checked against that location's threshold.

3
A breach opens by itself

When an out-of-range reading lands and there is no breach already open for that location, the system opens one immediately — no manual step. It records the start time and starts tracking the peak and trough temperature.

4
Acknowledge the breach

Open the breach and acknowledge it with a note saying you have seen it. This moves it from open to acknowledged — your record that someone is on it.

5
Resolve the breach

Once you have decided what to do with the affected stock, resolve the breach with the action taken (write-off, sell-with-warning, override). This moves it from acknowledged to resolved and stamps how long the breach ran.

Role notes

Only Owner is tagged on this Capability. When the Owner installs the Dairy Pack, the Owner can open and read the cold-chain log at /dairy/cold-chain.

The direct cold-chain controls — set thresholds, record readings, acknowledge and resolve breaches — are owner-tier by design. But these permissions are not yet wired into the live app's permission catalogue, so even the Owner does not hold them in the running product today. They land when the Capability's own screen ships. For now, treat the read-only Dairy Pack log as what the Owner can actually see.

Tips & time-savers

Tip
Set one threshold per location once — for example 2°C–8°C — and every reading after that is checked against it automatically. The 30-minute tolerance window is a sensible default, so you rarely need to touch it again.

You don't have to hand-key readings forever. Cold-chain supports sensor loggers (Temptale and Roambee are live; BlueDart and Logmore are registered for later). Once the sensor feed is connected for your tenant, a logger streams temperatures in on its own, so the trail keeps building even when nobody is at the warehouse.

Gotchas

Warning
A breach moves open → acknowledged → resolved in that order — there is no shortcut. You cannot resolve a breach that hasn't been acknowledged first, and once a breach is resolved it is final: you can't reopen it or change its state. Acknowledge it, decide on the stock, then resolve with the action you took.

One more thing to watch: a location with no threshold set will still store its readings, but no breach will ever be raised for it, however warm it gets. If a fridge matters, give it a threshold — otherwise the log is just numbers with nothing checking them.

Related