+
Sensors that see it.
Workflows that fix it.
ConnectedFresh monitors the conditions your brand standards depend on and turns real problems into structured events CMX1 can act on — corrective actions, SOPs, and audit-ready records, in the platform your quality team already runs.
ConnectedFresh and CMX1 have been partners since 2023.
Wireless sensors watch coolers, freezers, cook-and-chill, water systems, and equipment 24/7 — with escalation logic that separates real failures from noise.
The enterprise quality, risk, and compliance platform where your checklists, corrective actions, SOPs, and audit records already live.
A confirmed sensor event can hand CMX1 a corrective action on the right asset, with the readings attached — so the condition and the response live in one record.
A checklist is a snapshot.
Conditions are continuous.
Your quality program can be perfectly designed and still miss what happened between check-ins — because the record only exists when someone writes it.
Conditions drift between checks
A checklist proves the walk-in was 38°F when someone opened the door with a clipboard. It says nothing about the nine hours in between. The failures that cost you product and audit points happen in the gaps a scheduled check can’t see.
Corrective action waits on a human
Even with a great quality platform, the workflow only starts once a person notices the problem, decides it matters, and logs it. That’s how a real failure becomes a late entry — or never becomes a record at all.
ConnectedFresh measures. CMX1 acts.
ConnectedFresh doesn’t do checklists or corrective actions, and CMX1 doesn’t put sensors on your equipment. That’s the whole point of connecting them.
Three steps, one direction
Data flows out of ConnectedFresh and into CMX1. Designed so the integration work lands on our side, not on your quality team’s roadmap.
Capture
Sensors report continuously from the equipment and spaces that matter — no one has to walk over and look.
Qualify
Escalation logic decides what’s real. A compressor failing for 40 minutes is an event; a defrost cycle isn’t.
Act
The qualified event is pushed to CMX1, where it can open a corrective action against the right asset with your SOP attached.
ConnectedFresh pushes to a CMX1 endpoint. Nothing has to sit there asking whether anything happened yet.
CMX1 defines the payload it wants. The transformation happens on the ConnectedFresh side before it ever arrives.
Send every reading for continuous records, or only criticality-based events. Configurable per deployment.
Operators stay in CMX1. There’s no second system for the field team to learn or log into.
A failed cool-down
shouldn’t need a witness.
Cool-down is one of the most demanding records in the FDA Food Code — two stages, six hours, and a window that closes whether or not anyone was watching. ConnectedFresh watches the whole curve.
When a stage fails, that’s not a note in someone’s memory — it’s a structured event that can land in CMX1 as a corrective action, mapped to the asset, with the temperature timeline attached and your SOP already on it.
What you can put sensors on
Pre-configured, out-of-the-box sensors covering food temperature, energy consumption, restroom cleanliness, and more — all feeding the same workflows.
Temperature and time, recorded continuously
Cold holding, hot holding, and cook-and-chill monitored around the clock — so the record exists whether or not anyone was standing there with a probe.
Where the integration matters
ConnectedFresh is measurement, and CMX1 is where the response already runs. Connecting them changes four things that matter.
The record writes itself
Instead of a log entry that depends on someone remembering, the condition is captured as it happens and carried into your compliance record with its timestamp intact. Audit prep stops being an archaeology project.
Detection and response in one place
A sensor alert that lives in a separate dashboard is one more thing to check. Routed into CMX1, it becomes a corrective action with an owner, an SOP, and a due date — inside the system your team already works in.
Your CMX1 configuration stays yours
Checklists, workflows, escalation paths, asset hierarchies, reporting — everything your team built in CMX1 keeps working exactly as designed. ConnectedFresh feeds it better inputs; it doesn’t replace any of it.
Nothing new for the field team
Operators keep one login. The sensors run in the background and the work shows up where they already look for it — which is the difference between a program that gets adopted and one that gets ignored.
The most labor-intensive record,
handled automatically
“ConnectedFresh took the manual labor and potential for human error out of the process. What used to take an average of 20 minutes per cooled ingredient now takes less than 5 minutes, saving us thousands of hours across our restaurants.”
average time to manually log one cooled ingredient
the same log, once ConnectedFresh automated the capture
of hours saved across their restaurants
Luna Grill is a ConnectedFresh customer that also runs CMX1. These are ConnectedFresh cool-down monitoring results. Read the full story