Real-time shipment visibility: how it works, what to build
· 5 min read · By YLinkTech
Real-time shipment visibility is the ability to see where a shipment is, what state it is in and when it will arrive, using data that updates as the freight moves. Visibility platforms do this by collecting position and milestone data from carriers, vehicles, vessels and devices, matching it to your shipments, predicting arrival times and raising alerts when a plan is at risk. Most companies buy the carrier connectivity and build the parts that touch their own orders, customers and decisions.
Where the data comes from, by mode
“Real time” means different things in each mode, because the underlying sources update at very different rates.
| Mode | Main sources | What to expect |
|---|---|---|
| Truckload and less-than-truckload | In-cab telematics and electronic logging devices, driver mobile apps, carrier system APIs and EDI status messages | Frequent positions when the truck is connected and the carrier has consented. Gaps with small carriers, brokered loads and trailer swaps |
| Ocean | Vessel positions from AIS, plus container milestones from carriers and terminals | Vessel position is frequent. Container events such as gate in, loaded and discharged arrive only when they happen |
| Air and parcel | Carrier scan events through APIs | Milestone based. Reliable at scan points, silent in between |
| Rail and intermodal | Railroad and terminal event feeds | Milestone based, with handoffs between parties as the weak point |
| Any mode | IoT trackers travelling with the cargo | Location and condition data such as temperature that follows the goods, at the cost of devices, batteries and returns |
Two of these sources are worth understanding in more detail. In US trucking, the Federal Motor Carrier Safety Administration explains that an electronic logging device synchronizes with the vehicle engine to record driving time automatically for hours-of-service compliance. The rule was mandated by Congress as part of the MAP-21 law. Because that hardware is already in the cab, the telematics systems around it became a practical source of truck positions, subject to carrier permission.
At sea, the US Coast Guard describes the Automatic Identification System (AIS) as a shipboard broadcast system that works like a transponder in the VHF maritime band and can update as often as every two seconds. It carries the vessel’s identity, course and speed. Note what it does not carry: any information about which containers are on board. Linking a container to a vessel depends on carrier booking and milestone data.
How a real-time shipment visibility platform works
Whether you buy or build, the pipeline has the same stages.
- Connect. Establish feeds from each carrier, telematics provider, terminal and device. Each connection needs onboarding, consent and monitoring.
- Normalize. Convert each source’s codes, time zones, location names and identifiers into one event model.
- Match. Tie incoming events to a shipment using references such as the bill of lading number, container number, carrier tracking number or truck and trailer assignment. Matching errors are the most common cause of “missing” tracking.
- Enrich and predict. Compare progress against the plan and calculate an estimated time of arrival using route, traffic or port conditions and historical transit times.
- Detect exceptions. Apply rules: late pickup, long dwell, route deviation, temperature out of range, ETA after the delivery appointment.
- Act and share. Send alerts to the people or systems that can respond, and publish status to customers, warehouses and planning systems.
Stages one to three are plumbing, and they are where most of the cost sits. Stages four to six are where the value shows up.
Standards that reduce custom mapping
Two open standards are worth knowing, because they shrink the normalization work.
The Digital Container Shipping Association publishes a Track and Trace standard for container shipping. It organizes visibility into five event types, covering shipment, transport, equipment, IoT and reefer events, in one shared structure that carriers and their customers can exchange through APIs.
GS1’s EPCIS standard describes events about products and assets in terms of what, when, where, why and how. Its 2.0 release added sensor data, a JSON syntax and a REST API, which makes it easier to use in modern applications.
Neither standard is universal across all carriers and modes. Still, modeling your own internal event schema on them means fewer translations later.
What to buy and what to build
The carrier network is hard to reproduce. Each connection is a small integration project with its own onboarding and upkeep, and a visibility provider spreads that cost over many customers. For most shippers, forwarders and third-party logistics providers, buying connectivity is the sensible default.
The parts worth building are the ones that depend on your own data and processes:
- Integration with your systems. Shipment creation from your TMS or ERP, and status and ETA written back to orders, appointments and inventory plans.
- A consolidated event store. One place that combines events from one or more providers, direct carrier feeds and your own warehouses, so you are not tied to a single supplier’s data model.
- Exception workflows. Rules, ownership and escalation that reflect your service commitments, not generic alerts.
- Customer-facing tracking. Branded status pages, notifications and APIs for your customers.
- Analytics. Carrier and lane performance, dwell time and ETA accuracy over time.
The build vs buy decision framework gives a general method for drawing that line.
Questions to ask before you commit
- What share of your own loads, by mode and carrier, can actually be tracked today? Ask for a test on your shipment list, not a network total.
- How fresh is each source, and how is that shown to users?
- How is ETA accuracy measured, and can you see it for your lanes?
- Can you export every raw event through an API, and who owns that data?
- What happens to tracking when a load is brokered or changes equipment?
- Which identifiers must your systems supply for matching, and are they reliably captured at booking?
The last question often leads back to paperwork. Reference numbers usually enter your systems from shipping documents, which is why freight document automation tends to sit close to visibility projects.
How YLinkTech helps
YLinkTech builds the software around visibility data for logistics and supply chain teams. Our Digital Product Engineering practice handles the API and systems integration between visibility feeds and your TMS, ERP and warehouse systems, and builds event stores, exception workflows and customer tracking portals. We are independent of visibility vendors and work with the provider you choose. To review your current tracking coverage and gaps, contact us.
Frequently asked questions
What is real-time shipment visibility?
It is the ability to see a shipment's current location, status and expected arrival using data that updates during transit, instead of waiting for a carrier to report after the fact. The data comes from vehicle telematics, vessel tracking, carrier milestone events and cargo sensors, and is matched to your shipment records.
How accurate is real-time shipment tracking?
It depends on the mode and the source. Truck telematics and vessel AIS can update frequently, while container, air and rail tracking rely on milestone events that arrive only at scan or handoff points. Accuracy also depends on correct matching between events and shipments, so clean reference numbers at booking matter as much as the feed.
Should we build our own shipment visibility platform?
Usually not the whole thing. Carrier and telematics connectivity is costly to build and maintain, so most companies buy it. It often makes sense to build the integration with your order and transport systems, your exception rules, customer-facing tracking and analytics, since those depend on your own processes and data.
Sources
- FMCSA: Electronic logging devices
- US Coast Guard Navigation Center: Automatic Identification System overview
- DCSA: Track and Trace standard
- GS1: EPCIS and CBV
This article is general information, not professional advice. See our Disclaimer.