Walk-In Cooler Temperature Monitoring: Sensors, Alerts and Logs

A walk-in that fails at 11 p.m. on a Saturday can warm up all night before anyone opens the door. A temperature monitoring system is the difference between a service call and a dumpster full of product. It also gives you the records that decide what you can keep after a failure.

Why monitoring matters for food safety

Three parts of the food safety rules make monitoring valuable:

• Cold holding. The FDA Food Code (the model most states adopt; the 2026 edition is current) requires cold TCS food (time/temperature control for safety food) to be held at 41°F or below.
• After a failure, the record decides. The Conference for Food Protection's emergency plan, referenced in the Food Code, allows refrigerated TCS food to be held for set periods depending on the highest temperature it reached, but only with a written plan prepared in advance and monitoring. Without monitoring, if food may have gone above 41°F, its guidance is to discard TCS food: "When in doubt, throw it out!" See food safety when a walk-in fails.
• New in Food Code 2026. With approval, an establishment may cool cooked TCS food in shallow pans (no more than 2 inches deep, uncovered) in a unit that holds 41°F or less and has "an electronic system that continuously monitors time and ambient air temperature." If you want to use that method, continuous monitoring is part of the requirement.

Your local health department decides which Food Code edition and rules apply. Check with it before relying on any of these.

What the thermometer rules require

The Food Code sets a baseline that every walk-in should meet, with or without a remote system:

• At least one thermometer that is built in or permanently attached, with its display easy to see.
• In the warmest part of the unit, measuring the air temperature or a simulated product temperature.
• Accurate to ±3°F for air thermometers scaled only in Fahrenheit (±1.5°C for Celsius or dual scale).
• A food thermometer (accurate to ±2°F) with a small-diameter probe for checking thin foods.

A remote monitor adds to these; it doesn't replace the permanent thermometer.

What a monitoring system does

Most systems share the same parts:

• Sensors in each walk-in, reading temperature (and sometimes door position, humidity or power) every few minutes.
• A gateway or hub that collects readings and sends them out over Wi-Fi, a wired network or a cellular connection.
• A software dashboard that stores the log, sets alarm limits and delays, and sends alerts.
• Alerts by text, phone call, email or app notification, often with escalation to the next person if the first doesn't respond.

Some refrigeration controllers can also feed a monitoring system. Heatcraft's Smart Controller, for example, closes a set of dry alarm contacts (rated 125 VAC / 1 A) during an alarm, which a technician can wire to a monitor or building system. An independent sensor is still worth having, because it keeps watching if the controller itself fails.

Sensor placement

Placement is the most common mistake. A sensor in the wrong spot either alarms constantly or misses a real failure.

Buffered probes. Air temperature swings every time the door opens and during every defrost. A probe sitting in a small bottle of liquid, glycol or a solid buffer responds more slowly, a bit like real product. The Food Code allows measuring "a simulated product temperature," and buffered probes are a common way to do it. They cut nuisance alarms without hiding a real failure.

Large walk-ins, boxes with several doors, or combination cooler/freezer boxes need a sensor in each space.

Setting alarm limits and delays

Getting the delay right is what makes people trust the alerts.

• Know what normal looks like. Box air temperature rises during defrost and after deliveries. Heatcraft's factory defaults, for example, run coolers on air (off-cycle) defrost 2 times a day and freezers on electric defrost 4 times a day. See walk-in cooler temperature fluctuating.
• Set a delay long enough to ride through a defrost and a normal delivery, but short enough to leave time to act. Refrigeration controllers do the same thing; Heatcraft's Beacon II defaults to a 60-minute high-temperature alarm time.
• Use a buffered probe so you can keep delays shorter.
• Freezers: the Food Code only says frozen food must stay frozen, with no set temperature. Set freezer limits from how cold your freezer normally runs and your food safety plan.
• Add an early warning. Some systems allow a warning level and an alarm level. A slow upward drift over several days often shows a failing system, such as a refrigerant leak, before it becomes an emergency.

Who gets alerted

An alert that goes to one phone is an alert that gets missed.

1. List at least three people in order, with a second and third contact who get called if the first doesn't acknowledge.
2. Include someone who can get to the store at night and on weekends.
3. Put your refrigeration contractor's after-hours number in the alert message or the response plan.
4. Write a one-page response plan: check the box with a thermometer, keep doors shut, record temperatures, call the technician, follow the emergency plan for product. See walk-in cooler stopped working.
5. Test it. Trigger a test alert every quarter and after any staff change.

Power-loss and connectivity alerts

A monitoring system has to keep working in the exact situations that cause failures.

• Power loss. Choose a gateway with battery backup that can send a power-loss alert. Heatcraft's Beacon II and Smart Controller also have a power failure alarm. See power outage and your walk-in.
• Wi-Fi vs cellular. Wi-Fi systems depend on the store's router and internet connection, which usually go down with the power. A cellular gateway with battery backup keeps reporting through a power outage, as long as the cellular network is up.
• Offline alerts. Make sure the system alerts you when a sensor or the gateway stops reporting. Silence is not the same as "all normal."
• Sensor batteries. Wireless sensors need battery changes. Put them on a schedule.

Logging and records

A good system replaces or supports the paper temperature log.

• Keep logs for the period your health department and food safety plan require.
• Record corrective actions next to alarms: what happened, what was done with the product, and when the system was repaired.
• After a failure, save the temperature history. It supports food decisions under the emergency plan and may be requested by the regulatory authority or an insurer.
• Review weekly trends, not just alarms. See walk-in cooler temperature log.

Food safety: Monitoring data supports your decisions but doesn't make them for you. Whether food can be kept after a failure follows your written plan, the rules above and, in the end, your local health authority.

Checking the monitor itself

• Compare each sensor with a calibrated thermometer placed beside it every month or so. A sensor that drifts undermines every record.
• Check that sensors haven't been moved, covered or knocked loose.
• Confirm alert contacts are current.

If a monitor and the walk-in's controller disagree, trust neither until you've checked with a calibrated thermometer. See thermostat and temperature controller and walk-in controller alarm codes. The daily and weekly checks in the walk-in cooler maintenance guide pair well with a monitoring system.