Temperature-controlled delivery carries a compliance obligation and a spoilage risk, and both are addressed by the same technology: sensors that record continuously and evidence that the chain was maintained.
What to monitor
| Sensor | Purpose |
|---|---|
| Compartment temperature | Core compliance and product safety record |
| Multiple probes per compartment | Multi-temperature vehicles, or verifying uniformity |
| Door open/close | Explains temperature excursions and evidences delivery events |
| Ambient temperature | Context for excursion analysis |
| Fridge unit status and run hours | Maintenance and fuel, and diagnosing failure |
| Humidity | Specific products — produce, flowers, pharmaceuticals |
| Load presence | Whether the compartment was empty during an excursion |
| Fuel level on the refrigeration unit | Preventing failures caused by running dry |
The combination of temperature and door status is what makes the data defensible. A temperature rise with a door-open event is a normal delivery; the same rise with the door closed is a unit failure.
For compliance purposes, what matters is not that the temperature was correct but that you can prove it was, for each consignment, with an unbroken record.
Alarm design
Badly designed alarms are worse than none — they train everyone to dismiss them.
- Threshold plus duration. Alarm on temperature outside range for more than N minutes, not instantaneously. Every door opening causes a transient rise.
- Suppress during door-open, with a maximum permitted duration.
- Escalate. Driver first, then depot, then a manager. Automatic escalation if unacknowledged.
- Pre-alarm. Warn at a margin inside the limit so intervention is possible before a breach.
- Distinguish equipment failure from operational excursion. A fridge that has stopped needs a different response from a door left open.
Document the alarm design as part of your food safety or quality system. Auditors ask how you would know about an excursion, and "we get an alert" is a weaker answer than a documented threshold, escalation path and response procedure.
Compliance context
Requirements differ by jurisdiction and product, but the common themes are consistent:
- Continuous monitoring during transport of temperature-sensitive food and pharmaceutical products.
- Records retained for a defined period — commonly one to several years depending on the regime.
- Calibrated sensors, with calibration records. Uncalibrated sensor data is challengeable.
- Documented corrective action when an excursion occurs, including the product disposition decision.
- Traceability linking the temperature record to the consignment and the customer.
Pharmaceutical distribution under Good Distribution Practice adds qualification of vehicles and equipment, mapping studies for temperature uniformity, and stricter documentation. If you distribute medicines, treat this as a regulated system rather than an operational nicety.
Integrating with delivery records
The temperature record has most value when it is attached to the delivery:
- Temperature at time of delivery printed or attached to the proof of delivery
- Excursion flags visible to the driver before they hand over
- Consignment-level records retrievable by customer, date or product
- Automatic hold on delivery where an unresolved excursion has occurred
Customers in food retail and foodservice increasingly require this evidence contractually, and the ability to produce it per consignment within minutes is a genuine commercial differentiator.
Practical deployment issues
Probe placement. Return air, discharge air and product-level readings differ. Place probes where your regulator or customer expects the measurement, and be consistent.
Wireless versus wired. Wireless probes simplify installation and allow flexible placement in multi-temperature vehicles, at the cost of battery management. Wired is more robust for permanent installations.
Trailer swaps. Where trailers are exchanged between tractors, the sensor system must belong to the trailer and report independently, or you lose the record on coupling changes.
Calibration cycle. Schedule and record it. An expired calibration invalidates the data at exactly the moment you need it.
Data continuity. In coverage gaps, data must be logged locally and uploaded later. A gap in the record is a gap in the evidence.
Driver workflow. Pre-trip checks that confirm the unit is running and at temperature before loading. Most excursions begin before the vehicle leaves.
Frequently asked questions
How often should temperature be recorded?
Frequently enough to demonstrate continuity and to catch excursions early — intervals of a few minutes are common in food transport, with tighter requirements in pharmaceutical distribution. Check the specific requirement that applies to your products and customers.
Do we need calibrated sensors?
For regulated products, yes, with documented calibration on a defined cycle. For general operational monitoring, calibration is still advisable, because uncalibrated data will be challenged in any dispute about spoiled product.
What do we do when an excursion happens?
Follow a documented procedure: assess duration and magnitude, decide product disposition against defined criteria, record the decision and the rationale, and investigate the cause. The record of the decision matters as much as the decision.
Can telematics devices handle temperature monitoring?
Many fleet telematics platforms support temperature probes and door sensors directly, which keeps everything in one system. Dedicated cold chain systems offer deeper compliance features and reporting; the right choice depends on how heavily regulated your products are.
How long should temperature records be kept?
Long enough to satisfy the applicable regulation, your customer contracts and your product shelf life — commonly a period of years. Set a documented retention policy and ensure the data is retrievable in a usable form for the whole period, including after a platform change.
