Tracker telemetry joined to the shipment it belongs to.
Location, temperature, shock, light, and humidity readings from cargo and container trackers land on the same shipment record as the booking, the rate, and the carrier milestones. A threshold breach raises an exception in the workflow rather than a notification in a device portal nobody watches.
What device integration covers.
Condition on the shipment record
Temperature, shock, light, humidity, and tilt readings attach to the shipment, so condition sits beside cost and schedule instead of in a separate application.
Thresholds that raise exceptions
Set limits per lane or commodity. A breach raises an exception in the governed workflow and notifies the party who can act on it.
Device position against carrier milestones
Where the tracker says the cargo is and where the carrier says it is are compared. A disagreement becomes an exception rather than a discovery at delivery.
Device-agnostic by design
Freightgate integrates the feed rather than selling the hardware, including partner devices such as Tive, so the tracker choice stays a commercial decision.
Reading history retained for claims
The full reading series stays with the shipment, so an excursion or a shock event has a timestamped record behind it when a claim follows.
Data that never reaches a decision.
Trackers generate readings in their own application, on their own login, watched by whoever set them up. The alert arrives without the shipment context around it, and by the time someone connects the reading to the order, the cargo is already sitting at a door.
A reading that changes what happens next.
Freightgate joins the device feed to the shipment it belongs to. The threshold breach enters the same exception workflow that governs cost and schedule, so the reading produces an action rather than a chart.
What operations teams ask first.
Which trackers and IoT devices does Freightgate support?
Freightgate ingests telemetry from cargo and container tracker providers through API and web-service connections, including partner devices such as Tive. Where a device exposes a data feed, it can be joined to the shipment record.
What is the difference between this and carrier tracking?
Carrier milestones tell you where a shipment was reported to be. Device telemetry tells you where the cargo actually is and what condition it is in. Freightgate joins both to the same shipment, so a disagreement between them becomes an exception rather than a mystery. See Freightgate Pulse.
Can device readings trigger an exception?
Yes. Thresholds for temperature, shock, light, humidity, and dwell are set per lane or commodity, and a breach raises an exception in the same workflow that governs the shipment, with the responsible party notified.
Do we have to buy trackers from Freightgate?
No. Devices are sourced from whichever provider you prefer. Freightgate integrates the feed rather than selling the hardware, so the tracker decision stays yours.
Does telemetry reach our ERP?
Yes. Condition and location events post back to the ERP or TMS record through the same EDI, API, and web-service connections used for the rest of the shipment data, including the NetSuite SuiteApp.
Is device data retained for claims?
Yes. The reading history is kept against the shipment, so a temperature excursion or a shock event has a timestamped record behind it when a claim or a customer conversation follows.
Where telemetry gets used.
See a device reading turn into an action.
Bring one tracked lane. We will join the device feed to the shipment, set a threshold, and show you the exception it raises and who it reaches.