Link every device ID, firmware version and calibration to the unit that left the factory.

An IoT device is a small board in a plastic enclosure with a device identity, a firmware image and usually a cellular or LoRa radio. Once thousands are deployed, the hard question is which unit runs which build, and which carries a suspect radio lot. A mislabelled batch is painful to recall.

Management software for device makers keeps the identifier, the firmware and the fixture result together for every unit, from the first programming step to the last courier label. Every returned unit points straight at the station that flashed it.

A hardware revision leaves engineering with its parts list, a firmware build and a test procedure, and purchasing buys the microcontroller, the radio module, the lithium cell and the enclosure. Boards arrive from a contract assembler or your own board assembly line, then units are flashed with firmware and given a device identifier. A test fixture then checks the radio, runs the sensor through its calibration points and writes the offsets back to the unit.

Units are provisioned with keys or certificates, activated on a SIM where needed and registered with the customer’s cloud account through a script run from the fixture PC. Some are burned in first. Later, firmware updates go out over the air and devices come back with a one-line note saying what went wrong, so support needs the version. Quick answers matter to the customer.