The cold you load is the cold you keep: the pre-cool gate

It's 5 a.m. at a Fraser Valley packhouse and the blueberries came out of the field yesterday afternoon warm. The reefer has been running at the dock for twenty minutes, the driver wants to make his window, and the box air already reads 2 °C on the display. Everything looks ready. Three days later the receiver in the DC calls: the fruit arrived soft, there's leakage in the bottom layer, and they're opening a claim.

Nobody did anything obviously wrong — and that's the trap. A reefer is a thermostat, not a chiller: it holds the temperature the load enters with, and it has almost no capacity to pull heat out of warm fruit. So the last cold decision you fully control happens before the doors close. Get it wrong there and no amount of transit runtime rescues it — you're just circulating cold air around a warm pallet core for three days.

This post is about that moment: what to actually check at load-out, and why the reefer's own display is the one number that will mislead you.

The reefer holds; it doesn't rescue

Produce leaves the field carrying field heat, and it keeps making more of it. Fresh fruit and vegetables are alive in the box — they respire, and respiration throws off heat. The rate climbs steeply with temperature: under the Q10 rule in USDA's Agriculture Handbook 66, the deterioration rate roughly doubles for every 10 °C. Warm fruit isn't just warm; it's warming itself faster.

Pre-cooling is the step that removes that field heat before transport. UC Davis and USDA postharvest guidance is to bring most produce close to its storage temperature — for many commodities within a couple of degrees of 0–4 °C — within two to three hours of harvest, in a system built to do it: forced-air, hydro, or room cooling.

A transport reefer is none of those. It's sized to maintain a pre-cooled load against ambient heat leaking through the walls, not to chill a trailer full of warm pallets. Ask it to do the cooling and it can't — the air near the evaporator gets cold, the display looks great, and the core of the pallet stays warm for the whole trip.

That's the gap the dock display hides. The supply-air sensor reads the air the unit is blowing; it does not read your fruit. A pallet loaded warm can sit several degrees above the air around it, deep in the stack, for days — and the only place that shows up is the pulp.

The pre-cool gate: four checks before the doors close

Treat load-out as a gate, not a formality. Four things have to be true before the trailer leaves, and only one of them is on the reefer's display.

1. The unit is at setpoint and holding — not just switched on. A reefer that hit 2 °C ninety seconds ago is not the same as one that has held 2 °C steadily. Cold air is necessary, but it's the easy half.
2. The pulp is inside the corridor — not just the air. Probe the fruit, in the core of a pallet, and compare it to the commodity's target. This is the check the dock display can't make for you, and it's the one that decides the trip.
3. The load plan isn't choking airflow. Conditioned air has to move through properly stowed cargo and back. A pallet blocking the return, a solid wall of boxes with no channel, or an overloaded nose turns a working unit into a warm pocket.
4. The record is already running before departure. If your temperature log starts halfway down the highway, you've got no evidence for the part of the trip that decides a dispute — the beginning. Best practice from the industry's Fresh Produce Transportation working group is explicit: the Bill of Lading should carry pulp temperature at loading and the serial numbers of the recorders on the load.

Pass all four and the reefer is doing the job it's actually good at: holding a cold load cold. Fail any one and you've loaded a problem that transit will only preserve.

Why the gate is also your defense

There's a second reason to run the gate, and it shows up weeks later. In Canada, produce trade disputes go to the Fruit and Vegetable Dispute Resolution Corporation (DRC) in Ottawa — the single dispute-resolution body for the fresh fruit and vegetable trade, handling claims from shipping point through arrival, including transportation, against its published Guidelines for Good Delivery. When a load arrives short of good delivery, the question is always the same: whose cold broke, and where?

That question is answerable only if you have the record. Under DRC trading standards a receiver has to request a destination inspection within eight hours of arrival by land to preserve a claim — a tight window that produces a snapshot at the end.

What decides who pays is the continuous story from load-out to arrival: was the pulp in the corridor when the doors closed, did it stay there, and where exactly did it move. A shipper who can show a clean pulp-at-loading reading and an unbroken series has a short conversation. One who can only show the reefer's supply-air trace has a long, expensive one.

It's worth being honest about the limits here. A good record doesn't win every dispute, and it certainly doesn't prevent one — the DRC weighs condition defects, contract terms, and inspection results, not just temperature. What the record does is remove the argument you shouldn't be having: the one about whether your cold chain held at all.

A quick self-audit for your next load-out

• Do you probe pulp, in the core of a pallet, or do you read the reefer display and call it cold?
• Does your unit have to be holding setpoint before "loaded," or just running?
• Does anyone check the load plan for airflow, or is stacking left to whoever's on the dock?
• Does your temperature record start at the dock, with a pulp reading on the paperwork — or somewhere on the road?
• If a receiver opened a claim tomorrow, could you produce a continuous series from load-out in minutes, the way SFCR traceability expects records to be retrievable?

If any answer is soft, that's where the next lost load is coming from — and it's fixable before the doors close, not after.

How Navixy does it, without overpromising

None of this needs a particular vendor — the gate is a discipline you can demand of any operation. To be concrete about how it gets instrumented: Navixy runs the pre-cool gate as an IoT Logic rule. It ingests the reefer's own data alongside a BLE or wired pulp probe in the load, and gates "ready to depart" on the conditions that actually matter — the unit holding setpoint and the pulp inside the corridor, tied to a geofence at the dock — instead of a single air reading.

It also watches the gap between supply air and pulp on the road, and flags the sharp change that betrays an open door or a blocked return while you can still act on it.

The record starts where it should. IoT Query assembles the continuous series — pulp and air from load-out to arrival, time-out-of-range, and mean kinetic temperature — and exports it through an open API in a form a receiver or the DRC can read; the gate is how you make sure it starts clean.

Navixy produces the record the trade and the regulator expect; it does not certify compliance. The platform is delivered alongside certified partners, and both answer for your operation.

Your next step

Don't re-engineer your cooling this week. Just run the pre-cool gate on your next load-out: unit holding, pulp in the corridor, airflow clear, record running. If the reefer's display is the only sensor you're trusting at the dock, you're measuring the air — not the fruit that has to arrive.