A beverage brand with coolers in the field has a different problem from a food business with cold rooms. The product inside a cold drink cooler is not going to hurt anyone if it warms up for an afternoon. The cooler itself is the asset, and it is sitting in an outlet that belongs to somebody else.
That changes what is worth measuring, and it changes almost everything about who needs to see the result.
What the estate owner actually wants to know
Is it powered. The single most common failure on a placed cooler is that somebody unplugged it, for the socket or for the noise. Nothing else you monitor matters until this is answered, and it is answered by watching power state rather than by inferring it from a temperature that drifts slowly in a full cabinet.
Is it cold. Setpoint tracking, but on the load rather than the return air. A full cooler holds its temperature long after the compressor has stopped working, so return air will tell you everything is fine for hours after it is not.
Is anyone opening it. Door activity is the closest thing to an honest engagement signal the hardware can produce. A cooler that is powered, cold and never opened is in the wrong place, or behind a pillar, or facing a wall. It does not tell you what was taken. Any vendor implying that door events give you sales data is selling you an inference the sensor cannot support.
Is it still where it was placed. This one is worth stating carefully, because it is where equipment monitoring pitches usually overclaim. A cellular controller tells you the unit is alive and reachable. Treat presence and network behaviour as a weak signal that something has changed, not as asset tracking.
The reason these deployments stall
Not the sensors. The org chart.
A branded cooler estate typically involves a brand that owns the equipment, bottlers or distributors who place it, a service company that repairs it, and outlets that host it. Four parties, four different views of the same device, and no two of them should see the same thing.
The brand wants the whole estate. The distributor wants their region. The service company wants the units they are contracted to maintain, and nothing about anyone else’s commercial performance. Get this wrong and the system either leaks data between competitors who share a distributor, or becomes so locked down that the people who could act on an alert never receive it.
This is a tenancy requirement, and it arrives with the second distributor rather than the fiftieth. Accounts have to nest, roles need a ceiling so a parent cannot grant more than it holds, and a device has to belong to one account while being shared with another so the owner and the service company both see it without sharing credentials. The multi-tenant platform page covers how that is built.
Branding is a requirement, not a finish
A brand placing equipment under its own identity generally cannot hand its distributors an app with a hardware vendor’s name on it. That is not vanity. The distributor relationship belongs to the brand, and an app store listing under someone else’s name undermines it every time somebody installs it.
So the platform has to resolve its own identity per customer: name, logo and colour system from the hostname it is served on, and mobile apps published under your own developer account. We build that as a platform property rather than as a bespoke fork, which is what keeps a second brand from becoming a second codebase. The branded mobile apps page has the detail.
Specifying the hardware
The useful questions are about the estate rather than the sensor. How many units, in what kind of outlet, with what power reliability, and who has to see which ones.
On the device side, three things do most of the work: a temperature probe placed with the load, a door contact, and power sense. Genesis has four modular ports where every port takes any supported protocol, so one configuration covers all three without a different part number per variant, and cellular is the default because the outlet’s network is not yours to depend on. Where a site network is genuinely stable and owned, Genesis Lite has WiFi and Bluetooth built in with 4G LTE available.
One hardware detail worth insisting on regardless of vendor: a disconnected probe must produce a fault code rather than a plausible number. On an estate of hundreds, a sensor that fails silently into a believable reading is worse than one that stops reporting, because the daily summary keeps looking healthy.
If you are scoping a cooler estate, talk to us with the shape of it: unit count, who places them, who services them, and who is not allowed to see whom. That is the part that decides whether the deployment works.