Ocean Shipment Tracking: Technologies, Data Standards, and Predictive Visibility - Yenra

The ship, cranes, and stacked containers in this port scene represent three different tracking problems. The vessel can report its own position, the port can record operational events, and individual containers may carry connected devices. A useful shipment view has to associate all three with the booking, transport documents, cargo, and inland journey.

Ocean shipment tracking has evolved from periodic carrier milestones into a data-fusion problem. Modern systems combine vessel broadcasts, satellite reception, carrier and terminal events, container-mounted sensors, port community data, weather and congestion feeds, customs and document status, and predictive models. The result can be much more informative than a dot on a map—but only when the system identifies what is actually being tracked, how fresh the evidence is, and where predictions begin.

One shipment, several things to track

The phrase “track my shipment” can refer to several distinct objects:

• Commercial shipment: the booking, bill of lading, purchase order, or house shipment managed by a shipper, carrier, forwarder, or logistics provider.
• Cargo: the individual goods, lots, pallets, or packages inside equipment.
• Container: the physical intermodal unit that moves by truck, rail, barge, terminal equipment, and vessel.
• Seal: the numbered mechanical or electronic device used to show whether the container doors may have been opened.
• Vessel: the ship carrying the container for one ocean leg.
• Voyage and port call: the scheduled and operational movement of a vessel between named locations.
• Documents and permissions: bills of lading, customs filings, verified gross mass, delivery orders, holds, release status, and arrival notices.

A vessel position is not a container position unless the container is known to be aboard that vessel. A container gate event is not proof that the cargo inside is intact. A predicted vessel arrival does not reveal when a specific container will be discharged, cleared, available, and delivered. Good platforms preserve these distinctions while linking the records.

The modern visibility stack

Automatic Identification System: the vessel-tracking foundation

The Automatic Identification System (AIS) is a VHF radio system created primarily for navigation safety and traffic awareness. A shipborne transponder broadcasts identity, position, course, speed, navigational status, and other information to nearby ships and shore stations. Under SOLAS regulation V/19, AIS carriage applies to passenger ships and defined categories of cargo ships, including ships of 300 gross tonnage and above on international voyages. The International Maritime Organization describes the carriage rules and AIS functions.

Shore receivers provide frequent updates near coasts and ports. Satellite AIS extends reception across oceans and remote regions, where Earth curvature prevents coastal antennas from hearing VHF transmissions. Satellite constellations, improved receivers, and data processing have made broad ocean coverage practical, but satellite reception is not continuous surveillance of every vessel. Message collisions in dense traffic, satellite revisit patterns, equipment faults, antenna conditions, and data-provider processing can create latency or gaps.

AIS also depends on reported identity and GNSS position. Values can be entered incorrectly, equipment can be switched off under limited security circumstances, and signals can be manipulated. The IMO recognizes falsified AIS data as a maritime fraud tactic. For commercial tracking, the permanent IMO ship number is a more durable identity key than a vessel name, call sign, or flag, because it remains with the ship throughout its life. IMO explains the integrated ship and company identification scheme.

LRIT and coastal surveillance are not customer tracking feeds

Long-Range Identification and Tracking (LRIT) is a regulated global ship-identification and tracking system used by entitled governments for maritime security, safety, search and rescue, and environmental protection. It transmits ship identity, GNSS position, and time through controlled data centers. It should not be confused with public AIS websites or a shipper's commercial visibility service. IMO's LRIT overview describes its architecture and purpose.

Authorities can also combine AIS and LRIT with coastal radar, optical satellites, synthetic-aperture radar (SAR), radio-frequency detection, aircraft, and remotely piloted systems. SAR can detect vessels through clouds and darkness; optical imagery can provide visual detail; RF detection can locate transmissions. Correlating those detections with self-reported positions helps identify “dark” or suspicious vessels. These methods improve route-risk and sanctions analysis, but they do not normally provide routine, continuous positions for individual containers. The European Maritime Safety Agency's Copernicus service demonstrates how satellite imagery is fused with vessel identity and behavior data.

Smart containers bring tracking down to equipment level

A smart container has a device attached to the equipment or integrated into the reefer machinery. A typical dry-container device combines a GNSS receiver, cellular modem, battery, accelerometer, and sensors for temperature, door or light events. More advanced units may monitor humidity, shock, tilt, pressure, or tamper conditions. Reefer systems connect to the refrigeration controller and may add cargo probes, power-state monitoring, atmosphere data, and two-way operational commands.

On land, devices usually communicate through cellular networks using roaming SIMs or eSIM profiles. Low-power wide-area technologies such as LTE-M and NB-IoT can reduce energy use where networks and roaming agreements support them. At sea, data may pass from the container to a gateway on the vessel and then through the ship's satellite connection. Some devices use direct satellite IoT. Bluetooth Low Energy can connect nearby sensors or support short-range reading at gates, depots, and warehouses.

The newest cellular standards are bringing satellite and terrestrial IoT closer together. 3GPP Release 17 introduced work for NB-IoT and enhanced machine-type communication over non-terrestrial networks, creating a standards path for low-power logistics devices to use satellites where cellular coverage ends. 3GPP's non-terrestrial-network overview explains the progression through Releases 17 and 18. Commercial coverage, roaming, device power, antenna view, and regional authorization still determine what works on a particular lane.

Why “real time” still has gaps

A container inside a dense stack is a difficult radio environment. Steel walls block or reflect signals, antennas may not see enough sky for a GNSS fix, vessel gateways may be temporarily unavailable, and devices conserve battery by sleeping between reports. Some systems store measurements locally and forward them when connectivity returns. Therefore, a responsible interface shows:

• the time the measurement was made and the time the platform received it;
• whether the position came from the container, vessel, truck, terminal event, or inference;
• the age and expected accuracy of the last observation;
• device battery, connectivity, and sensor-health status;
• whether an alert is based on one reading, a sustained threshold, or a model.

“Last reported position” is more honest than “live location” when a device has not communicated for hours.

Reefer tracking: location plus cargo condition

Cold-chain visibility asks whether the equipment is maintaining the environment specified for the commodity, not merely where the container is. Modern reefer telemetry can include controller set point, supply-air and return-air temperature, humidity, ventilation, O2 and CO2 levels for controlled-atmosphere cargo, defrost cycles, alarm codes, power interruptions, and readings from inserted cargo probes.

Those signals need context. A brief off-power interval during a planned terminal move is different from an unexplained outage at a depot. Return-air temperature responds differently from pulp temperature. Defrost cycles can create expected changes that look alarming without controller-state data. Rules and machine learning can suppress noise, recognize sustained excursions, and route an actionable alert to a terminal, vessel crew, depot, carrier operations center, shipper, or insurer.

Large-scale deployments show how quickly the technology is changing. In July 2026, Maersk reported that it had started replacing reefer IoT devices with a new generation across its fleet, with about 30 percent upgraded and a new connectivity platform being completed aboard 450 vessels. The stated direction is a move from displaying data toward recommending actions. Read the July 2026 Maersk connectivity update.

Dry-container tracking is moving from add-on to fleet infrastructure

Dry-container tracking was once used mainly for high-value cargo or temporary deployments. Carriers are now equipping large portions of standard fleets with permanent devices. Hapag-Lloyd's Live Position provides container-level location across ocean, rail, and truck legs for equipped dry containers, while MSC's smart-container services combine position with temperature, door, and shock events. These deployments illustrate a broader shift: the container itself is becoming a persistent source of journey data rather than a passive object located only when it crosses a gate.

Permanent devices also create new operational uses. Fleets can identify idle equipment, reduce searches and misroutes, measure depot dwell, detect unauthorized movement, prioritize maintenance, and compare planned versus actual equipment flows. The same data can support customers, carriers, lessors, terminals, insurers, and security teams, but each party needs appropriate permissions and a common interpretation of events.

Operational events remain essential

Sensor location alone cannot tell whether a container has been accepted by the carrier, loaded below deck, discharged, placed on customs hold, made available, or released to the correct trucker. Those are business and operational events produced by carrier systems, terminal operating systems, depots, rail operators, truck platforms, customs agencies, and port community systems.

Traditional ocean data exchange relies heavily on electronic data interchange (EDI) messages and carrier portals. APIs increasingly provide on-demand or subscription access with structured fields, faster updates, and clearer versioning. The hard part is semantic consistency: one provider's “arrived” might mean arrival at pilot station, port limits, anchorage, berth, terminal, or inland facility.

The Digital Container Shipping Association (DCSA) publishes vendor-neutral data models and APIs for cross-carrier visibility. As of July 2026, its tracking family includes Track & Trace 3.0 Beta, IoT Events 1.0 Beta, and Reefer Events 1.0 Beta. These standards create common definitions for equipment, transport, shipment, and sensor-related events. DCSA's Track & Trace overview links the current documentation.

Outside container shipping, GS1 EPCIS 2.0 provides a broader supply-chain event model for the “what, when, where, why, and how” of products and assets. It supports sensor data, certifications, JSON/JSON-LD, REST APIs, and the relationships among items, cases, pallets, and containers. EPCIS can connect ocean milestones to manufacturing, warehouse, food-safety, pharmaceutical, and retail traceability.

Ports are becoming real-time data platforms

A port call involves far more than crossing a geofence. Berth availability, pilot boarding, towage, mooring, cargo moves, bunkering, tides, draft restrictions, labor, cranes, yard capacity, customs, and onward transport all affect the actual timeline.

DCSA released Port Call Standard 2.0 in December 2025. It provides a shared API and event structure for carriers, terminals, port authorities, and service providers to exchange estimated, requested, planned, and actual times, along with operational data such as forecast cargo moves. The goal is a shared operational picture that supports just-in-time arrival instead of ships racing to port and waiting at anchor. DCSA describes the Port Call 2.0 changes.

Government reporting has also become more digital. Since January 1, 2024, the IMO Facilitation Convention requires public authorities to establish, maintain, and use maritime single windows for electronic information exchange when ships arrive, stay, and depart. The IMO Compendium aligns data models from IMO, UNECE, the World Customs Organization, and ISO so systems can share data with consistent meaning. IMO explains the mandatory maritime single window.

AI changes ETA from a timestamp into a forecast

A carrier schedule is a plan. A predictive ETA is an estimate calculated from current evidence. Modern models may combine:

• current and historical AIS tracks, vessel speed profiles, and route behavior;
• weather, waves, currents, ice, tides, and canal or strait restrictions;
• port congestion, anchorage queues, berth plans, and terminal productivity;
• previous and downstream port calls in the vessel rotation;
• cargo-move counts, draft, vessel class, and service pattern;
• transshipment dependencies and inland rail or truck schedules;
• historical dwell, customs, release, and equipment-availability patterns.

Machine-learning systems can update a forecast whenever evidence changes, detect an abnormal route or speed, and estimate the probability of a missed connection. A port or carrier digital twin—a continuously updated computational representation of vessels, infrastructure, constraints, and plans—can test alternatives before they are executed. The Port of Rotterdam reported in 2025 that its fairway-planning model uses AIS, vessel-visit data, restriction rules, and weather to predict actual arrival and departure times and advise the harbor master. See the Port of Rotterdam case study.

Prediction quality depends on the target. “Arrival at port,” “all fast at berth,” “container discharged,” “cargo available,” and “final delivery” are different outcomes. Interfaces should label the milestone, show a forecast range or confidence, keep the source and model version, and preserve earlier predictions for performance measurement. A precise-looking time without uncertainty can be less useful than an honest window.

Geofencing and event inference

Geofences convert position into business context: entered port approach, reached anchorage, arrived at terminal, departed rail ramp, or deviated from an authorized corridor. Modern systems use polygons rather than simple circles and add speed, heading, dwell, map-matched road or rail position, and facility schedules to reduce false events.

Inference becomes necessary when direct events are absent. If a container device enters a terminal, later stops transmitting, and the assigned vessel departs while carrier records show a load event, a platform may infer that the container is aboard. That can be useful, but it should remain distinguishable from an explicit terminal load confirmation. Derived events need confidence scores and explainable source links.

Electronic seals and chain of custody

A high-security mechanical seal provides evidence of physical tampering when the seal number and condition are checked at custody changes. ISO 17712:2013, confirmed current in 2023, establishes classification and acceptance procedures for mechanical freight-container seals.

Electronic seals and smart locks can add time, identity, location, and open-close events. Door sensors, internal light sensors, and accelerometers can provide additional evidence. No single sensor proves theft or cargo integrity: doors can be opened lawfully, sensors can fail, container walls can be breached without opening the door, and event data can be delayed. Strong chain of custody combines physical inspection, unique identifiers, device identity, signed records, user access control, and exception investigation.

Electronic bills of lading add document visibility

The bill of lading can function as a receipt, evidence of the carriage contract, and—in negotiable form—a document of title. A shipment may physically arrive while cargo release is delayed because the document has not been properly endorsed or surrendered. Electronic bills of lading (eBLs) allow document state and control to move digitally alongside the physical shipment.

DCSA's Bill of Lading 3.0 standard, finalized in February 2025, includes digital-signature support. Its Platform Interoperability (PINT) API, legal framework, and Control Tracking Registry allow compliant eBLs to move among different platforms while recording which platform has control. In June 2026, DCSA announced that five eBL providers had implemented its Standard Annex v2 with International Group of P&I Clubs approval, building on the first standards-based interoperable transaction in 2025. Read the June 2026 interoperability update.

Distributed-ledger technology can support some eBL or provenance platforms, but it is not a substitute for legal recognition, reliable identity, governance, interoperability, or truthful source data. A digitally immutable false event remains false.

Arrival notices, customs, and cargo release

Physical arrival is only one step toward delivery. A full visibility platform may also track:

• shipping instructions and bill-of-lading approval;
• advance manifest acceptance and customs risk screening;
• verified gross mass submission;
• import holds, inspections, and releases;
• freight payment and original-document or eBL surrender;
• arrival notice, delivery order, and terminal availability;
• free-time expiration, demurrage, detention, and appointment status.

DCSA introduced Arrival Notice 1.0 in November 2025 to replace inconsistent emailed PDFs with structured, machine-readable data. Its Booking 2.0 and Bill of Lading 3.0 standards also added fields for the European Union's Import Control System 2 advance-filing requirements. These developments move shipment tracking beyond location toward the question that matters operationally: “What prevents the cargo from moving next?”

Tracking emissions as part of the shipment record

Modern visibility platforms increasingly associate movements with estimated greenhouse-gas emissions. Distance, vessel and service characteristics, speed, fuel, capacity allocation, port calls, and inland legs can feed shipment-level calculations. ISO 14083:2023 provides a common method for quantifying and reporting emissions from passenger and freight transport chains.

Operational data and regulatory emissions data serve different purposes. IMO's Data Collection System requires ships of 5,000 gross tonnage and above to collect annual fuel-consumption and related data, and since 2023 those data support operational carbon-intensity calculations. It is not a public, shipment-by-shipment tracking feed. Commercial shipment estimates should disclose methodology, allocation rules, data quality, and whether values are measured, modeled, or carrier supplied.

Emerging technologies to watch

VDES: higher-capacity maritime data exchange

The VHF Data Exchange System (VDES) extends the AIS ecosystem with Application Specific Messages and higher-capacity terrestrial and satellite data channels. It is designed to support e-navigation and digital ship-to-ship and ship-to-shore services without overloading AIS safety channels. IALA's 2025 seminar described terrestrial and satellite components and a potential data rate up to 32 times higher than AIS, but deployment is still developing and should not be presented as universal coverage. IALA maintains the VDES roadmap and technical guidance.

Authenticated and resilient positioning

GNSS jamming blocks satellite navigation signals; spoofing transmits false signals that make a receiver calculate an incorrect position or time. AIS, onboard navigation, container GNSS, and timestamped events can all inherit bad position data. In March 2025, IMO, ICAO, and ITU jointly warned that interference was increasing. Galileo's Open Service Navigation Message Authentication became freely available worldwide in 2025, allowing compatible receivers to verify that navigation data came from Galileo and was not modified. It improves spoofing detection but does not prevent jamming.

Resilient systems compare multiple GNSS constellations with radar, inertial sensors, terrestrial ranging, vessel motion, geofences, and other independent evidence. In 2026, IALA discussions emphasized multi-sensor integration, stronger AIS and VDES authentication, alternative positioning, and machine-readable interference reports. IALA's interference overview explains the risks and backup concepts.

Edge intelligence and action-oriented alerts

Instead of sending every sensor reading, edge software can filter noise, detect sustained threshold breaches, compress data, and retain evidence when connectivity disappears. Cloud models can combine device data with cargo rules and operational context, recommend an intervention, and learn which alerts led to useful action. The important progression is from telemetry to decision support—not merely from slower dots to faster dots.

Computer vision and high-precision port positioning

Port gates and cranes increasingly use optical character recognition to read container numbers, vehicle plates, and seal images. RFID, BLE, ultra-wideband, private 5G, cameras, and terminal equipment telemetry can locate assets within yards more precisely than public GNSS alone. These systems create strong local events, but integration with carrier, customs, and inland records is what turns a yard detection into end-to-end visibility.

Cybersecurity and data trust

Tracking systems connect device firmware, radio networks, vessel gateways, cloud platforms, APIs, port operational technology, mobile apps, and user accounts. Compromise can expose cargo patterns, falsify positions or release status, suppress alarms, or interrupt port operations. The IMO's current maritime cyber-risk guidance emphasizes governance, identification of assets and threats, protection, detection, response, recovery, and operational resilience. Review IMO maritime cyber-risk guidance.

A trustworthy tracking program should use unique device and user identities, encrypted communications, signed software and documents, protected keys, least-privilege access, logging, anomaly detection, tested recovery, and vendor vulnerability management. API consumers should verify timestamps, signatures, identifiers, sequence, and source—not assume that data are trustworthy because they arrived through an API.

How to evaluate an ocean visibility platform

1. Define the object and decision. Do you need vessel ETA, container position, cargo condition, document control, release status, emissions, or all of them? What action should the data trigger?
2. Map the full route. Include origin pickup, inland rail or truck, transshipment, port dwell, final terminal, customs, and delivery—not just the main ocean leg.
3. Ask for source-level provenance. Every event should identify whether it came from a carrier, terminal, container device, vessel AIS, satellite inference, document platform, or predictive model.
4. Measure freshness and coverage. Review real reporting intervals by lane, port, vessel, container position in stack, and transport mode. Marketing “real time” is not a service-level metric.
5. Test identity resolution. The platform should reliably connect booking, bill of lading, equipment number, seal, vessel IMO number, voyage, port call, and inland references without duplicating or merging unrelated records.
6. Examine standards and APIs. Prefer documented, versioned interfaces and common semantics such as DCSA and GS1 EPCIS where they fit. Confirm subscriptions, retries, pagination, correction events, rate limits, and historical access.
7. Evaluate prediction honestly. Ask which milestone is predicted, what inputs are used, how often it is recalculated, how accuracy is scored, and whether confidence ranges and model history are available.
8. Design alert ownership. A temperature or delay alert needs severity, escalation, acknowledgement, responsible party, recommended action, and closure evidence.
9. Review security and governance. Cover device security, authentication, encryption, data residency, sharing permissions, retention, incident response, auditability, and vendor exit.
10. Pilot on difficult lanes. Test transshipments, remote ports, dense container stacks, rail handoffs, cellular roaming, weather disruption, and corrected carrier events—not only a simple direct voyage.

Common mistakes

• Equating a vessel dot with proof that a container is aboard.
• Showing a scheduled arrival as if it were a live prediction.
• Calling stale, store-and-forward telemetry “real time.”
• Triggering alarms without accounting for normal reefer cycles or planned power-off moves.
• Using proprietary event names without a mapping to shared definitions.
• Treating geofence entry as customs clearance or cargo availability.
• Assuming blockchain makes source data accurate or a document legally effective.
• Trusting AIS or GNSS without checking for impossible motion, duplicate identity, spoofing, or gaps.
• Buying a dashboard without planning API access, workflow integration, or alert response.

What changed since the 2017 Ocean ETA launch

This article began with Savi Technology's October 2017 Ocean ETA announcement. The service combined mobile and satellite communications, port geofences, historical and real-time data, machine intelligence, and transition alerts to predict ocean and land milestones. Those ideas anticipated the direction of the market.

The difference in 2026 is scale and interoperability. Container devices are being installed across major carrier fleets, reefers report rich condition data, satellite IoT is converging with cellular standards, port calls and arrival notices have standardized APIs, maritime single windows are mandatory, eBL platforms can exchange documents across systems, and AI models fuse operations, weather, congestion, and equipment data. At the same time, GNSS interference, AIS manipulation, platform cyber risk, and inconsistent event semantics make data provenance more important than ever.

The most mature tracking systems no longer promise a single perfect location. They assemble observations, business events, documents, and forecasts into an explainable timeline—and make clear what is known, what is delayed, and what is predicted.

Current technical references

• DCSA Track & Trace, IoT, and reefer event standards
• DCSA Port Call Standard
• GS1 EPCIS and Core Business Vocabulary
• IMO Automatic Identification System guidance
• IMO Facilitation and maritime digitalization resources
• IALA VHF Data Exchange System guidance
• UN Trade and Development Review of Maritime Transport 2025