Cold Chain

Cold Chain Logistics — Why Temperature Excursions Cost More Than You Think

A temperature breach destroys product value and creates a compliance problem, and the reading that proves it is usually already in your own sensor data. Why the gap between the reading and somebody acting on it is where the loss sits.

Updated 11 September 2026 · first published 9 June 2026 · 7 min read

Runink Logistics Operations Team

Cold Chain Logistics — Why Temperature Excursions Cost More Than You Think

What are the Key Takeaways from this Executive Summary?

Quick answer

A temperature excursion is a period when a load goes outside the range it is allowed. In almost every case a sensor recorded it while it was happening. The loss comes from the gap between that reading and somebody acting on it. In many operations that gap is days, and nobody has ever measured it.
  • One excursion costs more than the product. Add the disposal, the replacement freight, the investigation and the customer’s response to a rejected load. Most operations only count the product.
  • Paper loggers and USB recorders tell you afterwards. By the time the data is read, the only decision left is accept or destroy.
  • Reading the data as it arrives changes what is possible — but only if somebody is ready to act on it. The fix is a named owner and a response, not only a better sensor.

How Large Is the Cold Chain Logistics Market — and What Is Really at Stake?

Quick answer

Enough of the world’s medicine and food now moves under a temperature rule that cold chain is a core capability rather than a specialism. According to IQVIA, global pharmaceutical spending passed $1.48 trillion in 2022, and a growing share of it moves in temperature-controlled lanes. The ranges run from cryogenic, around -196°C, up to controlled room temperature at 15-25°C.

Cold chain is no longer just vaccines and frozen fish. It covers biologics, cell and gene therapies, speciality chemicals and fresh produce.

The handling is harder than it was. A load that travels by sea, then air, then road changes hands several times, and each handover is a point where the temperature record can break.

IATA’s rules for perishable cargo require a continuous temperature record across every mode. Many shippers still use monitoring that goes blind at exactly those handover moments. A pallet of insulin or a container of fresh fish left standing on a hot apron is losing value while nobody is watching.


What Does a Single Temperature Excursion Actually Cost?

Quick answer

More than the product on the pallet. Count five things: the value of the goods, the cost of disposal, the replacement shipment, the time your quality and compliance teams spend on the investigation, and whatever the customer does about a rejected load. Most operations only count the first.

Here is how to work out your own figure. It is a better number than any industry average, and you can build it from records you already hold.

Direct losses. Take the wholesale value of an affected load, the disposal and handling fees, and the cost of the replacement shipment. Replacements usually go by air at short notice, so price them at the expedited rate rather than the contracted one. Your finance ledger has both.

Regulatory cost. A documented breach can start an investigation. The WHO sets out cold chain requirements for vaccines and essential medicines. In the United States, FDA 21 CFR Part 211 requires detailed temperature records for drug products, and gaps invite warning letters or import alerts. Food shippers under FSMA must hold continuous monitoring and corrective action records. Estimate this as the hours your quality and compliance teams spent on last year’s breaches, because that is the part you can count.

Customer and brand cost. This never appears as a line in the ledger. A retailer receiving a rejected load has empty shelves and a fill-rate problem of its own. Count the chargebacks you paid, and note which accounts have since reduced volume.

Add the five together for last year’s breaches and divide by the number of breaches. That is your cost per excursion, and it will be specific to your products and your lanes.


Why Do Traditional Monitoring Methods Leave Dangerous Gaps?

Quick answer

Because they report after the fact. Paper loggers, USB recorders and manual checks give you a history, not a warning. By the time anyone reads the data, the window in which the load could have been saved has closed.

The problem with the old methods is delay.

An indicator strip on a pallet tells you a breach happened. It cannot tell you when it started, how long it lasted, or whether the product is still within its allowed total exposure. A USB logger records in fine detail, but nobody reads it until the load arrives. At that point the only choice is accept or destroy.

Manual checks have a different weakness. Someone reading reefer temperatures every few hours on a night shift is not continuous monitoring. Waiting time at a cross-dock, a delay at a port, a cooling unit failing on a trailer — all of these open a window that a round of manual checks will miss.

The result is a quality team that spends its time investigating losses instead of preventing them, and a compliance team rebuilding temperature histories from several sources for a regulator. That is not managing a cold chain. It is examining the remains of one.


How Does Reading Telemetry as It Arrives Change the Equation?

Quick answer

It changes three things. A drift can be raised while the load can still be saved. The compliance record is built from the readings themselves rather than reassembled later. And lanes or sites with a history of breaches become visible before you tender the next shipment.

Modern sensors are small, battery powered and connected. They can send temperature, humidity and location throughout a journey.

But the sensor is the easy part. What matters is what happens to the reading in the minutes after it arrives.

Raising a drift early. Read the readings against the load’s own limits as they come in. A cooling unit losing ground in a hot yard looks different from a door being opened. If the reading is checked on arrival rather than on delivery, there is still time to move the load or get a unit repaired.

Building the compliance record as you go. Every reading, alert, acknowledgement and corrective action is kept in order, against the load it belongs to. When an auditor asks, the record exists already. Nothing has to be reconstructed, and nothing depends on one person’s memory.

Choosing lanes on your own history. If a particular cross-dock runs long in July, that is in your data. So is the carrier whose reefer units fail most often. Both can be read before the next load is tendered rather than after it is lost.

Before any of this, get your own baseline. For last year’s breaches: how many hours passed between the reading and anyone acting on it, and how many of those loads could still have been saved at that point? Operations that have never counted it usually find the answer uncomfortable. It is also the only honest figure against which a later improvement can be claimed.


Conclusion

Quick answer

Cold chain failures are not bad luck. They are a measurement and response problem. The reading almost always exists; what is missing is somebody reading it in time and a rule about what to do next.

Excursions will keep happening on long multimodal journeys. The question is whether you find out in time to act, or find out when the load arrives and the regulator writes.

Moving from reading afterwards to reading as it arrives is an operations decision before it is a software one. Decide who is told, what that person may do without asking, and when a load is past saving.

Runink FACE is built for that reading. It checks sensor data from refrigerated units as the stream arrives. A drift comes out with the unit named, the load on it, the reading that breached, and a corrective dispatch drafted for a person to approve. That is an illustration of a mechanism rather than an account of a deployment — the scenario has not been run against a customer’s telemetry, and there are no figures here for what it would save.



Sources

Cold Chain Temperature Control Pharma Logistics Food Safety IoT Runink

All articles

Runink: Data You Can Trust. Decisions You Can Defend.

Runink FACE reads the logistics records you already hold, compares them against the rules that govern them, and drafts an action for the person who owns the decision. It runs on infrastructure you control.