Skip to content
my-iris
HACCP-readyEU data residency

The cold chain breaks in transit — and the one SMS goes unread.

A reefer warms on a weekend run. A single text goes to a single phone, and nobody sees it until the load is already compromised. The result: a product recall, a HACCP violation, and brand damage. my-iris escalates until someone takes the load — and records the corrective action for the investigation.

Illustrative industry scenario — not a specific client.

Cold-chain break in transit · cost of a missed alert
Primary cost
product recall
Regulatory exposure
HACCP violation
Lasting damage
brand + customer trust
With my-iris
reached · acknowledged · proven

Illustrative cost-of-failure categories

The problem

Three ways a cold-chain breach goes unanswered

The reefer reported the breach. The alert didn’t reach anyone who could divert the load — and there was nothing to show the recall investigation afterward.

  • Single SMS, single person

    One text to one duty manager. If the truck breaks cold chain on a weekend run and that one phone is missed, the load is already compromised before anyone looks.

  • No escalation

    No reply, no backup. Nothing climbs to the transport lead or the QA manager while the temperature climbs and the HACCP critical limit is breached.

  • No proof

    A recall investigation asks for the alerting record. “We sent a text to the driver” is not a defensible HACCP monitoring and corrective-action trail.

How my-iris maps

From breach to documented corrective action

The same stateful lifecycle behind pharma cold-chain monitoring — applied to your routes, your sites, your HACCP plan.

  • Escalation beyond one phone

    No answer in your window? my-iris goes from a push to a voice call to the next person — up to 20 attempts by default — until someone in the chain takes the load. Never one message to one person.

  • Voice/IVR for drivers on the road

    A driver who can’t read a push mid-route can take a call. The keypress that acknowledges the alert is captured and timestamped like every other step.

  • Cold-chain aware

    Transport reefers, cold stores and processing lines — my-iris sits on top of whatever monitors temperature and turns a breach into an escalating, acknowledged response.

  • Two-way acknowledgement

    Recipients acknowledge or skip in the my-iris app or on the call. The alert resolves only when a person has taken it — the corrective action HACCP expects.

  • Audit-ready event log

    Every notification, escalation, reply and resolution is logged append-only and tamper-evident — monitoring and corrective-action evidence for a HACCP plan or a recall investigation.

  • 7 languages on the call

    Each receiver group has its own call language, so the crews in each country hear the voice call in theirs.

Wired into your HACCP plan

Monitoring, corrective action and the recall trail

HACCP doesn’t just want a temperature log — it wants documented corrective action when a critical limit is breached, and evidence to defend a release or a recall. my-iris is that layer.

  • 01

    CCP breach → corrective action

    A breach at a critical control point becomes an escalating alert and a recorded response — notified, acknowledged, resolved — the corrective-action evidence the HACCP loop expects, not just a chart.

  • 02

    Fixed sites and moving reefers

    Cold stores, processing lines and transport reefers all post to one endpoint; the voice call reaches a driver mid-route when a push won’t, so a weekend load isn’t lost in silence.

  • 03

    Recall & retail-audit defence

    An exportable, timestamped trail answers the auditor’s “show me the alerting and corrective action” — the traceability a BRCGS or retail-customer audit asks for.

Audit-ready by design

Evidence for your HACCP plan and recall defence

my-iris produces the timestamped, EU-resident corrective-action trail a HACCP audit or recall investigation asks for — every notification, escalation, acknowledgement and resolution. We give you the trail and the residency posture; your food-safety system owns the HACCP study itself. We don’t claim certifications we don’t hold.

  • HACCP corrective-action export
  • EU data residency by architecture
  • Configurable retention · up to 5 yr
  • GDPR Art. 15 / 17 · DPA
  • Two-way acknowledgement proof
  • STOP/START opt-out · 7 languages

Built by MeshWorks Wireless Oy, which also runs Seemoto — pharmaceutical cold-chain monitoring across 5 EU countries, under regulatory scrutiny.

Its predecessor, AMS v1, delivered 1,431+ alerts in Seemoto production — the temperature-excursion escalation pharma demands is exactly what food and logistics need.

Read the Seemoto case study

Food & cold chain — frequently asked

How does my-iris support our HACCP plan?

A HACCP plan needs monitoring of critical control points plus documented corrective action when a critical limit is breached. my-iris is the layer that turns a temperature breach into an escalating alert and then records the corrective response — who was notified, when, who acknowledged, and how it resolved — as an exportable, EU-resident trail. my-iris supports your HACCP documentation; it does not replace your HACCP study or hold a food-safety certification.

Does it work for trucks and transport, not just fixed cold stores?

Yes. Any telematics or reefer monitoring system that can fire a webhook posts the breach to one REST endpoint. my-iris then escalates by push and voice call — the call matters for drivers on the road — and records who acknowledged and when, whether the asset is moving or stationary.

Where does our data live, and is opt-out handled?

On Cloudflare’s EU edge, with alert state in Durable Objects pinned to EU jurisdiction. STOP/START opt-out for calls and SMS end reports is built in across 7 languages, GDPR Art. 15 export and Art. 17 erasure are supported, retention is configurable, and a DPA is available.

Don’t let one missed SMS become a recall

Talk to us about cold-chain alerting across your sites and fleet.