Shipment tracking in NetSuite, posted back to the order itself
Vessel milestones, ETA changes, and exceptions from GPS, AIS, IoT, and carrier feeds reported against the NetSuite item fulfillment, with only the events that break a rule reaching a person.
Tracking usually lives in a carrier portal, a forwarder's email, and a visibility tool the ops team watches. The NetSuite record says shipped and nothing else, so customer service leaves the ERP to answer a question the ERP should hold. Freightgate's NetSuite TMS integration posts milestones, ETA shifts, and exceptions back against the item fulfillment, and applies your rules to decide which of them need a person.
The order knows it shipped. It does not know where it is.
A visibility tool shows the container drifting. The ERP has no idea. The customer calls, the rep opens three tabs, and the answer that eventually goes back was never written to the order. Meanwhile every ETA change lands in the same inbox at the same priority, so the one that actually breaks a delivery commitment gets the same attention as the forty that do not.
Visibility shows you what happened. Governing what happens next is a different thing.
What posts back to the NetSuite record.
Milestones on the item fulfillment
Departure, vessel milestones, arrival, and delivery events are written against the NetSuite item fulfillment, so the record answers the question instead of a carrier portal.
All modes, one feed
GPS, AIS, IoT, and carrier feeds across ocean, air, land, and rail unified into one event stream, with no tab-switching between portals. For an ocean move, that includes the vessel the booking was made against.
Exceptions governed by your rules
Each event is checked against the ETA thresholds, routing, dwell, and temperature limits you already run on. On-track moves pass silently. Only a breach is flagged, re-routed, or held.
ETA shifts raised before they reach the customer
Predicted arrivals update as conditions change, and a shift that puts a delivery commitment at risk raises an exception against the order before the customer hears about it.
IoT and cold-chain conditions
Temperature, shock, humidity, and door events stream in alongside location, so a cold-chain breach raises an exception the moment a sensor crosses your threshold.
Audit trail on the shipment
Every event, rule decision, and re-route is logged in order against the shipment, so you can show what happened, which rule applied, and who resolved it.
From raw signal to a status on the order.
Shipment booked from the order
The booking Freightgate executed against the sales order or purchase order is the shipment the events attach to.
Signals ingested
GPS, AIS, IoT, and carrier feeds land in one live view across every mode.
Rules applied
Every event is checked against your policy. On-track moves flow through untouched.
Exceptions routed to an owner
A breach is flagged, re-routed, or held, and routed to the person who can resolve it with the context to act.
Status on the NetSuite record
Milestones, ETA, and exception state post back to the item fulfillment, so customer service answers from NetSuite. The same record carries the invoice audit when the bill arrives.
“We view Freightgate as a strategic technology partner. The net result of the relationship is a competitive advantage in the marketplace.” Nestlé Waters North America
What NetSuite teams ask first.
Does tracking write back to NetSuite?
Yes. Milestones, ETA changes, and exception state are posted against the item fulfillment record, so the order carries its own status.
Which tracking sources are covered?
GPS, AIS, IoT sensors, and carrier feeds across ocean, air, land, and rail, unified into one live view. Two decades of integrations mean most signal sources are already live.
What counts as an exception?
Whatever your rules say. ETA thresholds, routing deviations, dwell, and temperature limits are the policy. Freightgate flags only the events that break them, so the team sees signal rather than every alert equally.
Does an alert just notify us, or does something happen?
Something happens. A breach can be re-routed or held automatically, and what is left is routed to the owner who can resolve it, with the context to act.
Can it track cold-chain conditions as well as location?
Yes. Temperature, shock, humidity, and door events stream in alongside location, so a breach raises an exception the moment a sensor crosses the threshold you set.
Does this replace our visibility tool?
Freightgate ingests GPS, AIS, IoT, and carrier feeds directly, so the shipments it governs do not need a separate tracking tool. Where other systems are in place, Freightgate sits above them rather than replacing them.
Is this a validated SuiteApp?
Yes. Freightgate is a Built for NetSuite validated hybrid SuiteApp.
Pairs well with
Watch your own containers report back to the order.
Bring a handful of live shipments. We will show you milestones and ETA shifts posting to the NetSuite record and the one exception that actually needs a person.