Industry and Supply Chain

Cold Chain Monitoring for Perishables

How temperature loggers and connected sensors track food and medicines in storage and transit, what the readings mean, and where monitoring falls short.

On this page
  1. Why temperature records matter
  2. How logging works
  3. Storage and transport differ
  4. What happens when readings go out of range
  5. Limits to keep in mind
  6. Making use of the data

Why temperature records matter

Some products are only safe or effective within a temperature range. Fresh and frozen food can spoil or become unsafe if held too warm. Many medicines, including most vaccines, are commonly stored in a refrigerated range, often described as roughly 2 to 8 degrees Celsius (about 36 to 46 degrees Fahrenheit), though the exact requirement is set by each product’s labeling. Frozen foods are commonly held at or below 0 degrees Fahrenheit (about minus 18 degrees Celsius).

The cold chain is the unbroken series of refrigerated steps from producer to final customer: cold storage, loading, transport, transfers and delivery. A weak link anywhere can undo the rest. Monitoring exists to show whether each link held, and to catch problems early enough to act.

How logging works

A temperature monitor has three parts: a sensor that measures temperature, a clock and memory that record readings at set intervals, and some way to get the data out.

The interval is a design choice. A reading every 10 minutes produces 6 per hour and 144 per day, which is plenty to show a trend without filling memory or draining the battery. Shorter intervals catch brief spikes, such as a door left open, but use more power and create more data.

There are two broad types:

  • Standalone loggers record readings and are read after the trip, either by plugging in or by tapping a phone or reader. They are inexpensive and simple, but they only tell you about a problem after the shipment has arrived.
  • Connected sensors send readings while the goods are moving or sitting in storage, through cellular IoT links, Wi-Fi in a warehouse, or a gateway that collects readings from many nearby sensors. They allow an alert in time to move a pallet, adjust a cooling unit or reroute a truck.

Between the two, there are loggers that store readings when out of coverage and upload them when connectivity returns, which relates to how well a device handles offline operation.

Storage and transport differ

In a warehouse or cold room, sensors are typically fixed to walls or shelves and wired or wirelessly linked to a central system. Temperature is not uniform in a room. Areas near doors, evaporator fans or the floor can differ from the middle, so a single sensor can give a misleading picture. Sites often map a room and place several sensors, with extra attention to the warmest and coolest spots.

In transit, the sensor travels with the load, either in the vehicle’s cargo space or inside the packaging. Readings in the air of a truck are not always the same as the temperature of the product inside a pallet, and a probe placed in or near the product tells a different story from one measuring air. Which is appropriate depends on what is being shipped and what the rules for it require.

Humidity matters for some goods too. For produce, pharmaceuticals and packaged items sensitive to moisture, humidity sensors are sometimes added to the same device.

What happens when readings go out of range

Systems usually define a limit and a duration: for example, an alert if the temperature stays above the limit for longer than a set number of minutes. A short blip when a door opens may be expected; a prolonged rise suggests a failing unit or a stalled truck.

When an excursion occurs, a typical response is to alert the responsible person, note the time and size of the deviation, and decide what to do with the goods. That decision belongs to people with the relevant expertise and rules. For food, that may involve food safety guidance; for medicines, manufacturer instructions and quality staff. The monitoring data supports the decision but does not make it.

Records also serve as documentation. Many businesses are expected to keep temperature records, and requirements vary by country, industry and product, so anyone handling regulated goods should check the rules that apply to them.

Limits to keep in mind

Monitoring reports; it does not cool. A sensor can show that a freezer has failed, but it cannot save the contents on its own.

Other practical issues include:

  • Calibration. A sensor that reads two degrees off can hide a problem or cause false alarms. Regular checks against a known reference, as covered under sensor calibration, are part of keeping records trustworthy.
  • Battery life. Frequent readings and frequent transmissions use more energy, and cold temperatures tend to reduce battery performance. Planning for battery life matters, particularly for devices that ride with a shipment for weeks.
  • Coverage gaps. Ports, tunnels, container stacks and rural routes can interrupt signals, leaving holes in live tracking until data catches up.
  • Alert fatigue. If alerts fire constantly for harmless events, people stop responding. Sensible thresholds and delays are as important as the hardware.

Making use of the data

Beyond individual alerts, stored readings form time series data that can show patterns: a cold room that slowly warms before each defrost, a route that is consistently warm at one stop, or a carrier whose trucks run closer to the limit. Simple dashboards and basic anomaly detection can highlight these, giving a business something to fix rather than only something to record.

A reasonable starting point is a small trial on one route or one cold room, comparing the logged readings with what staff already believed about it. Surprises in the first month are common and informative.

The complete guide to industry and supply chain

The Internet of Things: A Game-Changer for the Manufacturing Industry
Read the guide

Keep exploring

Guides from other topics

All topics →