Cold chain · Temperature excursions

    Catch an excursion before the load is ruined.

    Most temperature excursions are discovered at delivery — or from a logger downloaded after the fact — when the whole load is already condemned. Navixy evaluates every packet against your limits and the rate of change between readings, so a failing reefer or an open door triggers an alert and escalation while you can still act.

    Get a deployment plan Cold-chain overview
    Per-packet evaluationRate-of-change alertsEscalation ladderOffline buffering
    A worker in an insulated jacket moving a pallet down a frosted cold-storage aisle, frost on the racking and vapor in the air
    Anatomy of an excursion
    Allowed band · −20 to −15 °C (frozen)
    Peak temp
    −12.8 °C
    Time out of range
    11 min
    Disposition
    Released

    Find it in five minutes, not at delivery

    An absolute threshold tells you the cargo is already gone. Watching how fast condition changes — and routing the alert to someone who can act — is what turns a loss into a save.

    Alert on the rate of change, not just the limit

    Navixy's IoT Logic compares each reading to the previous valid one. A steep rise — a door left open, a reefer that quit — trips an alert before the absolute limit is breached, while there's still time to intervene.

    Reading-to-reading delta
    2°4°6°8°8°C2°C+0.4 °C

    The same rule runs across 2,500+ device models with no firmware work — start from a downloadable flow and tune the threshold.

    0m2m4m6m8m10mevery packet

    Every packet, evaluated

    Each incoming reading is checked against your thresholds — not sampled or averaged away.

    0 minDriver app + SMS
    5 minDispatcher
    15 minOps manager

    An escalation ladder

    Route the first alert to the driver, then up the chain if it isn't acknowledged — every alert has an owner.

    no gaps

    No gaps in dead zones

    Devices log offline and store-and-forward on reconnect, so a cellular gap never hides an excursion.

    A worker in an insulated jacket moving a pallet down a frosted cold-storage aisle, frost on the racking and vapor in the air
    Excursion alertack 4 min
    5 min
    from first drift to the driver's phone
    On the dock and in the aisle

    The five-minute window is won on the floor

    An excursion alert is only worth the action it triggers. Navixy routes the first warning to the person nearest the load — the driver, the dock lead, the cold-store operator — with the context to act before the band is breached, instead of a post-trip report no one can undo.

    • Route the first alert to the owner nearest the load
    • Escalate automatically until someone acknowledges
    • Keep logging through dead zones and unhooked trailers
    Anatomy of an excursion

    A frozen load slips — and is pulled back before it's lost

    A −18 °C frozen shipment runs its corridor until a reefer stutter lets it drift. Watch the rate-of-change alert fire on the climb, the intervention, and the proof-of-condition record that closes the trip.

    Allowed band · −20 to −15 °C (frozen)live shipment telemetry
    -15 °C-20 °C
    Origin DCLine-haulReefer stutterRecovered
    Condition timeline
    • Departure — box at −18.4 °C, well in band
    • Rate-of-change alert: +1.1 °C between readings
    • Excursion: −12.8 °C — driver alerted, reefer reset
    • Back in band; time-out-of-range logged
    • Proof-of-condition record sealed
    Proof of condition
    Peak temp
    −12.8 °C
    Peak temp
    Time out of range
    11 min
    Time out of range
    Disposition
    Released
    Disposition
    How Navixy catches it

    From packet to intervention

    The detection mechanism, end to end — buildable on the hardware your lanes already run.

    1. 01

      Evaluate every packet

      Each reading off a BLE/1-Wire probe or the reefer's CAN feed is normalized and checked the moment it arrives.

    2. 02

      Test limit and rate

      IoT Logic checks both the absolute band and the delta from the last valid reading, with debounce so a single spike doesn't cry wolf.

    3. 03

      Alert and escalate

      The right owner is notified in real time and the alert climbs an escalation ladder until someone acts.

    4. 04

      Log the proof

      Time-out-of-range and the full curve are recorded for the condition report — whether the load is saved or not.

    FAQ

    Catching excursions in time

    Why isn't an absolute temperature threshold enough?
    Because by the time it trips, the cargo is already over the line. An absolute limit is a lagging signal. The rate of change between readings is a leading one — a fast rise reveals a door left open or a failing reefer minutes before the band is breached, which is the window where you can still intervene.
    Won't rate-of-change alerts create false alarms?
    Not with debounce and sensible deltas. Defrost cycles and brief door openings are expected; IoT Logic uses debounce windows and tunable thresholds so only a sustained, abnormal change escalates — and you start from a working flow rather than a blank rule.
    Does this work on product temperature or just the reefer's air?
    Both — and you choose which drives the alert. Navixy ingests the reefer's supply/return air over CAN and independent BLE/1-Wire probes placed in the load. For excursion alerting most teams trust in-box product probes; reefer air is used for early equipment warnings.
    What happens when the truck loses signal mid-excursion?
    The device keeps logging and backfills. Readings are stored on the device and forwarded on reconnect, so the excursion and its timing are reconstructed for the record even if the live alert was delayed by a dead zone.
    Does catching excursions in time actually pay for itself?
    One prevented loss usually covers a deployment. Industry estimates put the value destroyed by a single temperature excursion at roughly US$50,000–$500,000+ per incident — high-value biologic loads sit at the top of that range — against a pharmaceutical cold-chain loss pool estimated near US$35 billion a year. Turning one would-be write-off into a save, or defending one disputed claim with a record, typically pays for the monitoring many times over.

    Turn excursions into saves, not write-offs

    Tell us your products, lanes, and limits. We'll set up the threshold and rate-of-change flows, the escalation ladder, and the proof-of-condition reports for your cold chain — and show you how it's built.

    Get a deployment plan See how it's built