Glossary · Equipment & tracking
IoT container tracking for produce
Also known as Smart container, IoT tracker, and Container IoT.
A device on or inside the container reporting position and condition on its own. The one feed that is genuinely about your box rather than about the ship.
Published
IoT container tracking means putting a connected device on the container itself: cellular or satellite radio, GPS, and usually sensors. The box then reports its own position and condition, instead of having them inferred from the ship carrying it. It is the only feed in container shipping that is genuinely about your container.
Everything else is inference. AIS tells you where a vessel is; carrier milestones tell you what the line did and when it got round to publishing it. A device on the box answers directly, including in the gaps where the other two say nothing.
Two kinds, and they are not interchangeable
Carrier-fitted devices are reefer telematics: the line’s own hardware, wired into the refrigeration controller, feeding the line’s monitoring product. You do not choose it and you may not receive it, because the data follows whoever holds the booking.
Shipper-fitted devices are trackers or data loggers you put in with the cargo. You own the data, and the trade-off is that somebody has to place the device, retrieve it, and accept that a battery in a steel box under forty other steel boxes reports unevenly at sea.
What it is good at
Surviving a transshipment. The device stays with the container, so it keeps answering at the point where a vessel feed stops being about your cargo.
Covering inland legs. A container crossing Panama by rail or running north out of Rotterdam has no AIS at all.
Shock, tilt, door openings on the sensor packages that carry them — the events nobody reports and everybody argues about afterwards.
What it is not
It is not cheap per container, which is why it is normal on high-value cargo and rare on a routine programme. It is not continuous — connectivity mid-ocean is the constraint, and readings arrive in bursts. And it is not a substitute for the carrier’s milestones, because free time starts at a discharge event the line records, not at a position your device reported.
For most importers the practical answer is layered: the carrier’s data for the clocks and the milestones, a tracking platform to watch every line at once, and a device where a specific consignment justifies one. Trackberry sits in the middle layer and does not read devices, which is worth knowing before you plan around it.
FAQ
Is IoT tracking better than AIS?
For your container, yes — it reports the box rather than the ship, and it keeps working after transshipment and on the road. For knowing whether a voyage is progressing normally, AIS is cheaper and covers every vessel.
Do I need a device to track a reefer properly?
No. Most avoidable cost on perishable cargo comes from time — a missed connection, a discharge nobody noticed — and those are visible from carrier milestones. A device earns its cost where condition or custody is genuinely disputed.
Why does my tracker go quiet mid-ocean?
Because it has to reach a network to send. Cellular units go silent as soon as the vessel is offshore, and satellite ones are constrained by power and by where the container sits in the stow. Gaps of days are normal rather than a fault.