Compliance
HACCP requires that you monitor refrigeration temperature and can prove it. CoolTech records continuously, so the proof already exists before anyone asks for it — no clipboard, no gaps, no arguments about whose handwriting that is.
Why manual logs fail
It does not prove the cooler was cold. Inspectors know the difference, and so does an insurer reviewing a spoilage claim. The three failure modes are always the same.
Nobody walked the coolers during a Saturday rush. The one day the log is missing is the day it would have mattered.
Seven entries in the same pen, all within two degrees of each other, written on Friday. An inspector has seen this before.
It was written down at 44 degrees and filed. A record of a problem is not a response to a problem.
Readings for any date range, for a single unit or a whole group of them, formatted as the log an inspector expects to be handed.
Who changed which setpoint, when, and to what. The record that answers why a unit was running warm three weeks ago.
Every report exports for spreadsheets, auditors, insurers and your own archive. Nothing is locked inside the console.
Generated and emailed on a recurring schedule to whoever needs them, with nobody responsible for remembering.
A unit keeps recording with no connection and uploads the gap when the link returns. An internet problem never becomes a compliance problem.
Administrative and access events are recorded independently of the temperature record, so a change to the record is itself part of the record.
Before
After
A HACCP temperature log is the record showing that refrigerated food was held at a safe temperature over time. Under a Hazard Analysis and Critical Control Point plan, refrigeration temperature is a critical control point, so the log has to demonstrate both the readings themselves and that they were monitored at a defined frequency. Health inspectors, third-party auditors and insurers all ask for it.
In practice, yes, and inspectors generally prefer it. An automatic log records at a fixed interval regardless of staffing, so it has no gaps on busy days and no suspiciously identical entries. CoolTech generates the log for any date range and exports it to CSV, which can be printed or handed over directly. Requirements vary by jurisdiction, so confirm the accepted format with your local health authority.
Continuously. Each unit records its own readings and reports them to CoolTech Central, and the recorded history is what the HACCP report is built from. Because the unit keeps recording even when the connection drops and uploads the gap afterwards, an internet outage does not put a hole in the compliance record.
Yes. The setpoint audit report shows who changed which setpoint, when, and to what value, and configuration changes are kept as a dated revision history per unit. That is a separate record from the temperature log itself, and the two together answer the question an auditor actually asks.
Yes. Reports can be scheduled to generate and email on a recurring basis, to whoever needs them, without anyone being responsible for remembering. Most operators schedule a weekly or monthly log to a manager and a compliance address.
CoolTech provides the monitoring and the records. It does not write your HACCP plan or certify your food safety programme — requirements vary by jurisdiction and by the kind of operation you run. Confirm accepted record formats with your local health authority.
Twenty minutes and you will see the report generated against real data, for a date range you pick.
Talk to the people who build it. No call centre, no gatekeeping.