IoT temperature monitoring in the kitchen: paperless HACCP, waste under control
A paper log records temperature three times a day, while a compressor can stop at two in the morning. IoT temperature monitoring closes that gap: sensors measure every 15 minutes, the system alerts your team within minutes of a limit breach, and records cannot be edited after the fact. Below you will find a payback model with open assumptions, a BLE vs LoRaWAN comparison, sensor placement rules, alarm scenarios and a 90-day rollout plan.
The price of a blind spot: what you actually lose
According to UNEP (Food Waste Index Report 2024), the world wasted 1.05 billion tonnes of food in 2022, of which 290 million tonnes came from foodservice, about 28%. Some of that loss is unavoidable, but a significant share is raw material spoiled by a temperature deviation that was noticed too late.
For a restaurant, the blind spot looks very specific: a compressor stops at 02:00, nobody is looking at the display, and at 08:00 the team opens a chamber full of product that spent half the night in the danger zone. International benchmarks (FDA Food Code): cold holding at no more than +5 °C (41 °F), hot holding at no less than +57 °C (135 °F), and food that has gone more than four hours without temperature control must be discarded. The limits in your HACCP plan may be stricter, and your sensors and alarm rules should follow them.
Power cuts: why failures happen at night
Switching to a generator or an industrial battery takes anywhere from a few minutes to half an hour, and even a short pause starts dangerous thermal processes inside the chambers. Inrush currents during switchover can damage compressor control boards. If that happens at night without monitoring, the team finds out in the morning, when the medium-temperature counter has already reached room-level +20 °C and the prepped food, seafood and sauces must be thrown away. A battery-powered sensor with a gateway on backup power raises the alarm within the first 15–30 minutes, while product can still be moved to a working chamber.
Paper log vs sensors: what really differs
Manual restaurant temperature monitoring across 15 control points, at three rounds a day, produces 16,425 entries a year. A system with a 15-minute interval collects 525,600 measurements, 32 times more, including nights and weekends when nobody walks the kitchen. Beyond data density, paper has a structural weakness: entries can be filled in just before an inspector’s visit, and when six months of lines are all in the same handwriting and the same pen, the log’s credibility is open to question.
Paper log
Zero startup cost, clear to every cook, independent of the internet.
Three entries a day miss overnight failures, values can be backfilled, and 30 minutes of a sous chef’s time every day is about 180 hours a year. Keep it only as a fallback for electronics failure.
IoT monitoring
Measurements every 15 minutes around the clock, alerts via Telegram, SMS or phone call, and a log that cannot be edited.
Needs a subscription, correct installation and calibration; without tuned alarm rules it turns into noise.
There is a human effect too: the daily checking round wears a sous chef down like any other paperwork. We covered how this affects the team and the P&L in our article on mental health in HoReCa.
Architecture and technology choice: sensors, gateway, cloud
A system has three tiers: wireless temperature sensors measure, a gateway collects and forwards the data, and cloud software stores the log, draws charts and sends alarms. The weakest tier defines the reliability of the whole system, so evaluate them separately.
BLE, Wi-Fi, LoRaWAN, NB-IoT: comparison
Mistake number one is buying consumer Wi-Fi sensors: their batteries drain quickly, and the metal bodies of refrigerators and the stainless steel of the kitchen shield the 2.4 GHz signal like a Faraday cage. The values below are guidelines; exact figures depend on the manufacturer and the measurement interval.
| Technology | Range and penetration | Sensor battery life | Best suited for | Weak spot |
|---|---|---|---|---|
| Wi-Fi 2.4 GHz | Depends on the router; metal and stainless steel attenuate the signal heavily | 3–6 months | Short pilots, display cases near the router | Battery drain and dependence on the local network |
| BLE | 15–20 m in line of sight, gateway needed in the kitchen | up to 2 years | Cafés, bakeries, restaurants up to 25 points | A load-bearing concrete wall needs a repeater |
| LoRaWAN (EU868, 863–870 MHz) | Hundreds of metres indoors, kilometres in the open; passes through floors well | 3–5 years | Hotels, underground storage, sites with 50+ points | Needs a base station, low data rate |
| NB-IoT / LTE-M | Mobile operator coverage, no gateway needed | 3–10 years | Remote storage and points without local infrastructure | Depends on operator coverage and tariff |
Sensor and accuracy: what to put in the specification
For chambers and counters a built-in sensor is enough; for freezers and blast chillers you need a remote probe (Pt100/Pt1000 or thermistor) with the transmitter mounted outside. The tolerance of platinum sensors is set by IEC 60751:
At −18 °C: ±0.39 °C (class B) and ±0.19 °C (class A)
Do not simply pinch the probe cable in the door: use a flat cable designed for door gaskets, or a service penetration. Otherwise the door loses its seal, and the chamber loses cold and electricity.
Gateway: autonomy matters more than port count
A gateway must keep working during a power cut and without wired internet. A simple calculation: a 2,000 mAh battery holds only about 7.4 Wh, which is 1–1.5 hours at a 5 W load (a gateway with an LTE modem). A small UPS gives an order of magnitude more:
Make the communication channel redundant as well: two SIM cards from different operators in addition to wired internet. Good systems store data locally, from a few days up to 30 days depending on the model, and upload it to the cloud without losing chronology once connectivity returns. Verify the buffer size during a pilot, not from a brochure.
Where to mount a sensor: installation without false alarms
The physics inside the chamber matters more than the sensor brand. The two most common mistakes:
- Near the door. Every opening produces a spike to +22…24 °C around the sensor, although the product itself cannot change in 10–15 seconds because of thermal inertia. The result is false alarms and a habit of ignoring them.
- Under the evaporator. The sensor is blasted by the coldest air, so it reads low, while in the far corner with boxes of greens it can be 4–5 °C warmer than the norm.
The most accurate approach is temperature mapping:
- Place 3–5 temporary loggers for 24–48 hours: centre, far corner, near the door, under the evaporator, upper and lower shelves.
- Find the warmest spot without a direct draught: that is where the permanent sensor goes. If mapping is not possible, choose the geometric centre at about 1.5 m height.
- To measure the product rather than the air, put the probe in a thermal buffer, a small container with glycol or food-grade glycerin that mimics meat or fish in thermal inertia and smooths out door-opening swings.
- Set the alarm delay with evaporator defrost cycles (short peaks several times a day) and stock deliveries in mind.
- Record a baseline: a week of normal operation shows the real range of each point.
Enclosure requirements: IP65 as a minimum for the kitchen, IP67 for freezers and the dishwashing area. Without moisture protection, contacts oxidise, batteries drain and the device fails within the first months. Every sensor drifts over time, so annual calibration against a reference thermometer with a certificate (a laboratory accredited to ISO/IEC 17025) is part of the system, not an option. If your equipment fleet is old or second-hand, start with the oldest units; we covered equipment choice separately.
Alarms people do not ignore: limits and escalation
Take limits from your HACCP plan and the manufacturer’s labelling. Below are working benchmarks you can use as starting settings.
| Equipment | Working range | Warning | Critical |
|---|---|---|---|
| Refrigerated chamber, counter (chilled food) | 0…+5 °C | above +6 °C for over 30 min | above +9 °C for over 45 min, or a sharp rise |
| Freezer | −18 °C or lower | above −15 °C for over 30 min | above −12 °C for over 45 min |
| Hot line, bain-maries | from +60 °C (per HACCP plan) | below +60 °C for over 15 min | below +57 °C for over 30 min |
For rapid cooling of cooked food, the international benchmark (FDA Food Code) is from +57 to +21 °C within 2 hours and down to +5 °C within 6 hours in total. This is a control point, so a blast chiller should be monitored against the cooling curve rather than a single threshold.
Three escalation levels
- Warning. A 30-minute limit breach: a Telegram message to the sous chef. The most common cause is a door left open during a delivery.
- Critical. A prolonged deviation: the alert is duplicated to the head chef and the technical service, plus a voice call if not acknowledged within 10 minutes. The likely cause is the compressor or a refrigerant leak.
- Emergency. No data from a sensor or the gateway for more than 20 minutes, especially at night: an alert to the venue manager and security, and an immediate power check.
Payback: an honest TCO model
Below is an illustrative three-year model for a venue with 15 control points, not a commercial offer. Prices are assumptions: replace them with your suppliers’ quotes and your own write-off statistics. We covered the broader logic of operating costs in our articles on Food Cost and the state of the HoReCa market in 2026.
| Parameter | Assumption | Amount |
|---|---|---|
| Sensors | 15 pcs × UAH 2,500 | UAH 37,500 |
| Gateway with backup power and 4G | 1 pc | UAH 12,000 |
| Installation, mapping, training | one-off | UAH 10,500 |
| Upfront cost (CapEx) | total | UAH 60,000 |
| Software subscription (OpEx) | UAH 150 × 15 sensors × 12 months | UAH 27,000/year |
| Manual rounds | 30 min/day ≈ 180 h × UAH 250/h (incl. payroll tax) | UAH 45,000/year |
| Labour saved after rollout | −60% of manual rounds | UAH 27,000/year |
The 70% share is the loss you can prevent thanks to an alarm within the first 15–30 minutes; the rest is unavoidable (the product has already warmed up, or the failure happened during delivery).
| Scenario | Failures per year × loss | Net effect per year | Payback |
|---|---|---|---|
| Conservative | 1 × UAH 45,000 | UAH 31,500 | ≈ 23 mo. |
| Base | 1.5 × UAH 90,000 | UAH 94,500 | ≈ 8 mo. |
| Optimistic | 2 × UAH 135,000 | UAH 189,000 | ≈ 4 mo. |
A UAH 90,000 loss is roughly 300 kg of product (meat, fish, dairy, prepped food) at UAH 300/kg. In the base scenario, manual control costs UAH 540,000 over three years (labour and expected losses), while IoT costs UAH 316,500 including upfront costs, a difference of about UAH 223,500. The calculation excludes calibration, battery replacement, fine risk and energy savings from door sensors.
Do you supply or implement IoT temperature monitoring for HoReCa? Tell us about your solution.
Contact usHACCP and inspections: what counts as evidence
Food safety in a venue rests on documented control, not good intentions. Ukraine’s Law No. 771/97-VR “On the Basic Principles and Requirements for Food Safety and Quality” (Article 20) obliges food business operators to develop, implement and apply procedures based on HACCP principles and to keep the related records; for small facilities the requirement has applied since 20 September 2019. Of the seven Codex Alimentarius principles, IoT directly covers monitoring of control points (principle 4) and record keeping (principle 7), supports corrective actions (principle 5) through a log of staff responses, and verification (principle 6) through calibration certificates.
The evidence pack for an inspector should contain:
- the HACCP plan with control points and critical limits;
- a temperature graph for the chosen period with a 10–15 minute step;
- a sensor-to-equipment mapping with serial numbers;
- a log of deviations and corrective actions with name and time (for example: “Chamber defrosted, products moved to backup fridge No. 3”);
- calibration certificates and a change history that cannot be edited (audit trail).
On format: the law requires evidence-based control, and HACCP digital temperature logs with an immutable history serve that goal well. However, the exact format and inspection practice (including under martial law) have changed over time, so agree it with a food safety consultant and check the current guidance of the State Service of Ukraine on Food Safety and Consumer Protection (Derzhprodspozhyvsluzhba).
Standards worth writing into your specification
| Standard | Scope | How to use it |
|---|---|---|
| EN 12830 | Temperature recorders for storage and transport of food | Ask the vendor for compliance or test reports |
| EN 13485 | Thermometers for measuring air and product temperature | For probe thermometers used at goods receipt |
| EN 13486 | Periodic verification of recorders and thermometers | Basis for your calibration schedule |
| IEC 60751 | Tolerances of Pt100/Pt1000 sensors (classes A and B) | Specification of remote probes |
| ISO 22000 | Food safety management systems | If you plan certification |
A 90-day rollout plan
- Weeks 1–2. Inventory of points. List refrigerated and freezer chambers, counters, display cases, blast chillers, the hot line and the receiving area. For each one, note the limit from your HACCP plan, the responsible person and the value of the stock.
- Weeks 2–3. Specification and requests. Choose the technology using the table above, define autonomy requirements (longer than a typical outage), data export and audit trail. Collect 2–3 commercial offers.
- Weeks 3–5. Pilot on 3–4 points. Take the most expensive stock and the oldest equipment, run mapping and collect a week of baseline data.
- Weeks 5–8. Rollout and escalation. Set up a “who, when, through which channel” matrix and run a 30-minute briefing for cooks and managers: what to do at each alert level.
- Weeks 8–10. Audit pack. Prepare a test report, calibration certificates and a written action procedure; run a practice night-time alarm.
- Weeks 10–13. KPI review. Compare temperature-related write-offs, average alarm response time (target: under 15 minutes), share of false alerts and manual-round hours against pre-rollout data.
Monitoring is one link in the kitchen automation chain that takes load off the team; we wrote about the others in our article on automation as a response to staff shortages.
Choosing for your venue format, and questions for vendors
| Format | Points | Technology | Gateway and autonomy | Software and calibration |
|---|---|---|---|---|
| Café, pastry shop, bakery | up to 5 | BLE | One compact gateway in line of sight and a minimal UPS | Telegram/Viber alerts for 2–3 people; manufacturer certificate |
| Full-service restaurant | 10–25 | BLE + remote probes for freezers and blast chillers | Gateway with an 8+ hour UPS and backup 4G from two operators | Access rights, escalation cook → sous chef → head chef → manager, PDF/Excel reports, annual verification |
| Hotel, chain, dark kitchen | 50+ | LoRaWAN (NB-IoT where needed) | Own base station and a backup channel (4G or satellite) | API integration with ERP/PMS, door sensors, one dashboard across sites |
Nine questions to ask a vendor
- What is the sensor accuracy and class, and is there a calibration certificate for every sensor?
- How many days of data does the gateway keep without connectivity?
- Is there a change log that cannot be edited (audit trail)?
- How fast does an alert arrive and which channels are supported (Telegram, SMS, call)?
- Is there a “no data” alarm and mains-power monitoring?
- Where is the data stored and in what format can it be exported?
- Is there an API for POS, ERP or PMS?
- What is the sensor battery life at your measurement interval?
- What happens to your data and archive if you end the contract?
Choosing a monitoring system for your venue? Tell us how many control points you have and we will suggest where to start.
Get in touchFAQ: short answers
Author: Ruslan, independent HoReCa analyst, technology expert at eeat.com.ua.
Author: Ruslan, Independent HoReCa Analyst, Expert Technologist at eeat.com.ua
