Claims and Recovery

Cold-Chain Claims: Turning a Temperature Excursion into a Claim That Holds Up

A load that drifts warm is a claim only if the evidence is gathered in time. What a cold-chain claim needs, and why most excursions end as write-offs.

17 October 2026 · 3 min read

Runink

What is a cold-chain claim?

Quick answer

A cold-chain claim is a demand for money after a temperature-controlled load was spoiled or put at risk because it left its required temperature range in transit or in storage. It is made against the carrier, the warehouse or an insurer, depending on who had the goods and what the contract says.

The event behind it is called an excursion: a period when the load sat outside the range it was meant to stay in. A reefer unit that failed overnight. A door left open at a cross-dock. A pallet that waited on a warm dock before loading.

An excursion is not always a loss. Some goods tolerate a short one. That is exactly why the claim has to show what happened, for how long, and against which limit.


What evidence does a cold-chain claim need?

Quick answer

Four things, read together: the temperature range the shipment was meant to stay in, the temperature records for the whole journey, the condition of the load at delivery, and the documents that show who had it when. A claim that shows only one of them is easy to dispute.
  • The required range, from the order, the bill of lading or the carrier instructions. If the range was never written down, the claim starts weak.
  • The temperature log, from the reefer unit or a logger in the load, covering pickup to delivery without gaps.
  • The condition at delivery: photos at the door, the receiving notes, and any exceptions written on the proof of delivery.
  • The chain of custody: the bill of lading and handover records that show who held the load during the excursion.

Each of these usually lives in a different system. The log is in a telematics portal, the photo is on a handheld, the range is in the order, and the handover is on paper.


Why do most temperature excursions end as write-offs?

Quick answer

Because the evidence is scattered and goes stale fast. By the time somebody pulls the log, finds the photo and checks the range, the load has been thrown away and the dock team has moved on. Without the four pieces read together, the claim is easier to drop than to argue.

There is also a quieter reason. Many teams treat an alarm as the end of the job. The monitoring system flags the excursion, someone takes the load off the line, and the record stops there. Nobody turns the alarm into a claim.

To see this in your own operation, take one month of temperature-controlled deliveries. Count the excursions your monitoring flagged. Count how many led to a claim. The gap is your own figure.


How can a team file more cold-chain claims, faster?

Quick answer

Read the evidence together as soon as the load arrives. If the photo at the door, the temperature log and the required range are compared automatically, a person can see the excursion, the pallet it touched and who held it, and decide on the claim the same day, while the evidence is fresh.

Runink FACE: Fulfilment Autonomous Claims Engine reads the photo from the door beside the consignment papers. It checks the image first, reads it on machines your plan names rather than at an outside AI service, and ties what it saw to the exact frame. It compares the observation with what the documents say the load should be, names the pallet that differs, and drafts the claim with the evidence attached.

Where a record says nothing about a condition, FACE reports it as not evidenced, never as kept. A named person approves the claim before it is filed.

See the cold-chain case worked through on the logistics page, or send one month of deliveries and we will walk it with you.

Cold Chain Temperature Excursion Reefer Cargo Claims Claims Recovery Runink FACE

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 your own servers or cloud account, or on Runink's shared machines to start, with no outside AI service.