The logistics company conducted a temperature monitoring pilot that appeared flawless. Forty sensors, gateways, dashboards, two weeks of clean data from a bench in the office. They all entered. Then the unit went into the cold storage facility it was originally intended for, and within nine days, a third had stopped reporting. The battery has not failed; they were only ever mentioned to minus twenty degrees, and the adhesive mount came from the steel racking as soon as the condensation got involved.
The fix costs more than the pilot. New hardware, a second installation crew, and a quarter of the momentum lost when sponsors who had been enthusiastic in March asked pointed questions in June. No one is acting stupid. They have chosen the device in terms of features and price, which is exactly how most hardware decisions are taken, and the features were all real.
Sourcing hardware for a connected deployment is a different discipline than buying a laptop. The device is the cheapest part of the system and the most difficult to replace later, so the decision to make is one that cannot be undone by a software update.
Connectivity Defines More Than Devices
Instinct to choose the sensor and then know how to speak. Turn it around. Range, data volume, latency tolerance and power budget limit your hardware list more aggressively than any feature comparison, and the mis-message is how the deployment of devices that cannot reach the network it is purchased for.
The low-power wide area option is suitable for the classic case of small and sparse readings from hard-to-reach places. The LoRa Alliance describes LoRaWAN as reaching up to 15 kilometers in rural settings with a ten-year battery life in unlicensed spectrum, which tells you what’s good and what’s not: it’s not a technology for video or anything really important. Cellular gives you managed coverage and monthly billing, Wi-Fi gives you throughput in buildings you control, and satellite covers places where land doesn’t reach.
Write the decision down with the limitations attached. A sensor that reports every fifteen minutes from the basement requires penetration and battery life. Cameras in loading bays require bandwidth and electrical power. Both devices should rarely come from the same procurement conversation.
Compatibility Worth Paying For
Interoperability sounds like an abstraction until you open three vendor portals and write the glue code for reconciliation. Devices certified to published specifications save you the most, which is all the premise of the Connectivity Standards Alliance’s work in Matter: one IP-based protocol, devices certified from different brands that work together authentically, and certification marks that take the guesswork out of purchasing.
Ask the supplier specific questions and listen to specific answers. The specification version, the certification program, the firmware update mechanism, the API, and what happens when the cloud vendor is the only way to access data. Devices that can only be managed through a proprietary dashboard are devices that you lease rather than buy.
Firmware deserves its own line of questions. Over-the-air updates, signed drawings, documented support windows, and published deadlines are the difference between a fleet that can be maintained and a fleet that will be replaced in a panic.
Processing, Power, and Headroom You Can’t Increase Later
Computing is the easiest thing to buy. Edge filtering, local buffering during outages, encryption, and eventually some form of on-device inference all want memory and cycles that minimal modules won’t have. Buying tiers in processing and storage is usually cheap at the unit level and very expensive to convert two thousand installed devices.
Power is the constraint that quietly governs everything else. Reporting interval, radio selection, load size and ambient temperature all draw the same battery, and the vendor’s battery figures assume laboratory conditions that your site will not reproduce. The duty cycle model you actually plan to run, then consider worse, because changing the right cell of the fleet disperses labor costs rather than hardware.
The environment is included in the Specifications
The cold storage story is a specification failure dressed up as a hardware failure. Operating temperature range, ingress protection rating, vibration, dust, humidity, cleaning chemicals, UV exposure and mounting surfaces are all included in the requirements document before anyone requests a quote. The same goes for physical security, as devices in public places will be hit, sprayed and occasionally stolen.
Tests in real places, with real installations, take longer than necessary. A two-week bench pilot proved the software works. A six-week pilot in the worst location you have proves the hardware, and the only pilot whose results should be allowed to buy a fleet.
Finally, treat this as a sourcing exercise rather than a shopping trip. Lead times, second source availability, regional radio approvals, spare parts ownership and warranty requirements dictate that year three goes smoothly, and hardware procurement practices can be handled before volume commitments are made rather than after. Tracking what you spread, where it sits and when the support is finished is the same discipline, added to the objects that are outside the room.
No one is making hardware choices slow. It makes the order: barriers, connectivity, compatibility, capacity, environment, then vendor. Teams working in that sequence tend to run one pilot rather than three, and the pilots they run tend to be more or less spread out.
IoT Business News has a helpful companion to read about platform selection criteria, and the same logic applies to the following devices. Buy for a system you plan to operate for five years, not a demo you’ll have to go through next month.
Logistics companies have finally got the job of monitoring cold storage, with industrial sensors, magnetic mounts and deliberately chosen reporting intervals. It also gets a short requirements template that every future deployment needs to fill out, which can be more expensive than sensors.