Resolving Real-Time Tracking Discrepancies in International Freight Shipping

International Freight Visibility Guide

A tracking discrepancy does not always mean that a shipment is lost or delayed. It often means that two systems are describing different objects, event types, locations, or moments in the same journey. The correct response is to rebuild the shipment timeline from reliable evidence, identify the operational consequence, and communicate what is confirmed without presenting an estimate as a completed event.

“Real-time tracking” is often a combination of event updates, estimated times, system messages, sensor data, and partner reports. Some information may be transmitted immediately, while other data arrives only after a terminal, carrier, broker, airline, or warehouse completes and publishes an operational event.

International freight passes through several organizations that do not necessarily use the same software or terminology. A single movement may involve an exporter, pickup carrier, freight forwarder, terminal, airline or ocean carrier, transshipment facility, customs broker, government authority, destination warehouse, and final-delivery provider.

Each party sees only part of the journey. The carrier may know that a vessel arrived, while the terminal knows that the container has not yet been discharged. The customs broker may know that a declaration was released, while the depot knows that the equipment is not yet available for pickup.

How three apparently conflicting statuses can all be correct

Carrier portal

“Arrived”

The vessel or aircraft reached the destination location. This does not necessarily confirm discharge, breakdown, customs release, terminal availability, or pickup readiness.

Customs system

“Released”

A required customs action may have been completed. Other government, carrier, terminal, document, payment, or operational holds may still remain.

Terminal system

“Not available”

The cargo or container may still be onboard, awaiting breakdown, blocked by another hold, or not yet placed in a position where collection can be arranged.

The problem is not always that one source is wrong. The sources may be reporting different milestones. Resolving the discrepancy begins by identifying the exact meaning of each event rather than comparing only the words shown on the screen.

A reliable tracking message should answer four questions: What object is being tracked? What event occurred? Where did it occur? Is the time planned, estimated, requested, or actual?

Why tracking discrepancies happen

Different event definitions

“Departed,” “received,” “available,” and “delivered” may refer to different operational moments depending on the provider and transport mode.

Different tracked objects

One source may track the vessel, another the container, another the house shipment, and another the customs declaration or final-delivery vehicle.

Update latency

An event may occur physically before it is entered, transmitted, processed, accepted, mapped, and displayed by downstream systems.

Incorrect identifiers

Mistyped container numbers, reused references, incorrect air waybill numbers, missing check digits, or wrong house-to-master links can attach events to the wrong record.

Changed transport plans

Rolled bookings, transshipment changes, vessel substitutions, split shipments, route changes, and new appointments may not reach every platform at the same time.

Estimated times recalculated differently

Providers may use different schedules, historical models, traffic data, weather inputs, terminal assumptions, and cutoff rules when calculating an ETA.

Manual operating gaps

Missing scans, delayed data entry, incorrect status selection, unreadable labels, and unreported exceptions can create an incomplete timeline.

Integration or mapping errors

A technically successful API or EDI message may still be interpreted incorrectly if locations, event codes, timestamps, or reference fields are mapped poorly.

Do not treat planned, estimated, and actual events as equivalent

One of the most common sources of confusion is the mixing of future information with completed operational events. A dashboard may display all times in a similar format even though they have very different meanings.

Time classification	Meaning	Appropriate use	Main risk
Planned	A time defined in the intended schedule or transport plan.	Capacity planning, bookings, appointments, and expected sequence.	The plan may remain visible after operations have already changed.
Estimated	A forecast based on currently available information.	Operational preparation, customer updates, and risk monitoring.	The estimate may change as new events or conditions appear.
Actual	A recorded event that has already occurred.	Timeline confirmation, performance measurement, billing, and investigation.	The event can still be late, incomplete, duplicated, or attached to the wrong object.

A completed vessel arrival does not automatically prove container discharge. An actual customs release does not automatically prove terminal availability. An estimated final-delivery time should not be communicated as a confirmed appointment.

Map each source to the event it can truly confirm

Carrier or airline

Booking status, schedules, transport events, equipment milestones, shipment events, and transport-document activity within the provider’s service.

Primary for carrier events

Port or cargo terminal

Gate activity, receipt, loading, discharge, terminal movement, availability, release conditions, and collection events within the facility.

Primary for terminal events

Customs broker or authority

Declaration submission, requests, examination status, customs release, and other messages within the relevant customs process.

Primary for customs status

Truck or drayage provider

Dispatch, pickup, vehicle movement, terminal arrival, appointment execution, delivery, and proof-of-delivery information.

Primary for road execution

Warehouse or consignee

Receiving appointment, gate arrival, unloading, quantity, visible condition, refusal, discrepancy, and inventory receipt.

Primary for receipt

GPS or IoT device

Device position, motion, temperature, door, shock, or other sensor observations, subject to device installation, coverage, power, and configuration.

Independent sensor evidence

AIS vessel data

Information about the vessel’s identity and movement. It can help explain a vessel’s position but does not directly prove the physical status of a particular container.

Vessel-level context

Always verify the tracked object. A vessel position, trailer position, device position, container event, shipment event, and purchase-order status are related but not interchangeable.

A three-level discrepancy triage model

Not every mismatch deserves the same operational response. Classify the discrepancy according to its likely impact and the time available to act.

1 Informational difference Two systems use different wording or one source is slightly delayed, but the current operational decision does not change.

2 Actionable uncertainty The mismatch affects an appointment, labor plan, customer promise, transfer, customs action, or pickup decision.

3 Critical exception The shipment may be missing, misrouted, blocked, damaged, exposed to temperature risk, or approaching a costly operational deadline.

A practical workflow for resolving a discrepancy

Confirm the shipment identifiers Verify the booking, bill of lading, air waybill, house reference, master reference, container, seal, trailer, purchase order, and internal shipment number as applicable.
Identify the exact tracked object Determine whether each status refers to the shipment, transport document, container, vessel, aircraft, vehicle, customs entry, package, pallet, or IoT device.
Normalize dates and time zones Preserve the original timestamp and time zone, then convert the information into one comparison standard. Do not compare local times without checking the zone.
Classify each event Separate planned, requested, estimated, and actual information. Record the event creator, event location, received time, and source system.
Rebuild the physical sequence Arrange confirmed events in operational order: pickup, terminal receipt, loading, departure, transshipment, arrival, discharge, release, availability, collection, and delivery.
Find the first missing or impossible transition Focus the investigation on the gap. For example, a pickup cannot be confirmed before availability, and delivery cannot be confirmed before collection.
Contact the source closest to the disputed event Ask the terminal about discharge or availability, the broker about customs release, the carrier about transport events, and the trucker about collection or delivery.
Assess the operational consequence Decide whether the discrepancy changes receiving labor, production, inventory, customer communication, demurrage exposure, delivery appointment, or replacement planning.
Publish one controlled status State what is confirmed, what remains unverified, which source is being checked, who owns the action, and when the next update is expected.
Correct the underlying data problem After the incident, repair identifier mappings, event definitions, integration logic, partner procedures, or alert thresholds that allowed the discrepancy to recur.

Use confidence levels without hiding uncertainty

What may increase confidence

High Confirmed actual event from the organization that physically performed or controlled the activity.

Medium Consistent event reproduced by several sources or supported by a reliable downstream event.

Low Unverified estimate, manually relayed message, stale portal status, or event that conflicts with the physical sequence.

Confidence should consider

Source proximity to the event
Actual versus estimated status
Age of the information
Identifier quality
Sequence consistency
Independent confirmation
Known source latency
Integration health

A confidence score should not become a false claim of certainty. Employees should be able to see why one source was prioritized and which evidence remains missing.

Do not silently overwrite conflicting events. Preserve the original source messages and record how the operational status was resolved. This supports later investigation, partner discussion, billing review, and system correction.

Mode-specific tracking differences

Ocean freight

Container, vessel, and terminal events

Vessel arrival, container discharge, customs release, carrier release, terminal availability, and gate-out are separate milestones. Transshipment and vessel substitutions can also change the expected timeline.

Air freight

Shipment, flight, and warehouse events

A flight may arrive while cargo remains onboard, awaits breakdown, requires document processing, or is not yet available from the cargo terminal. House and master air waybill relationships must also be correct.

Road and final delivery

Dispatch, location, and proof events

GPS location does not prove pickup or delivery. Appointment arrival, gate entry, unloading, signature, photo, quantity, and receiving confirmation may be needed to establish completion.

Multimodal shipments require a common view that connects events without removing their original meaning. International standards and shared data models can make this exchange more consistent, but every implementation still needs accurate identifiers, event mapping, permissions, and exception handling.

Hypothetical scenario: a container shown as arrived but unavailable

Illustrative case—not a reported company result An importer receives three different messages about the same container.

The carrier portal shows that the vessel arrived at the destination port. The customs broker reports that the entry has been released. The drayage provider says the terminal will not accept a pickup appointment.

Carrier event

Vessel arrival recorded as an actual transport event.

Confirmed

Customs event

Customs release confirmed for the relevant entry and shipment reference.

Confirmed

Terminal event

No discharge or availability event has been published for the container.

Pickup blocked

Initial conclusion

The container may have arrived at port onboard the vessel but is not yet physically available for collection.

Monitor discharge

The logistics team should avoid telling the warehouse that the cargo is ready. A controlled update could state:

“The vessel arrival and customs release are confirmed. Terminal discharge and pickup availability are not yet confirmed. The drayage appointment remains on hold, and the next review will follow the terminal’s availability update.”

Design alerts around business impact

Alerting every difference creates noise. A useful system should distinguish harmless data latency from discrepancies that affect an operational commitment.

An actual event appears before its required predecessor
The tracked identifier fails validation or changes unexpectedly
Two sources report different actual locations for the same object
A planned connection becomes impossible under the latest events
An ETA changes beyond an agreed operational threshold
A customs release exists but cargo availability remains blocked
A pickup is dispatched without confirmed release or availability
A delivery is reported without supporting receipt evidence
A high-value or temperature-sensitive shipment stops reporting
A transshipment event points to an unexpected vessel or facility
A partner feed becomes stale or incomplete
Multiple shipments are linked to the same supposedly unique reference

Thresholds should reflect the mode, lane, customer, cargo, delivery window, free time, inventory position, and recovery options. A two-hour difference may be insignificant for one shipment and critical for another.

Prevent discrepancies at the source

Standardize event definitions

Maintain a shared glossary defining the physical meaning of milestones such as received, loaded, departed, arrived, discharged, released, available, collected, and delivered.

Validate identifiers early

Check reference format, container identification, check digits, house-to-master relationships, shipment duplication, and equipment assignment before events begin flowing.

Preserve source timestamps

Store when the event occurred, when it was created, when it was received, and the applicable time zone. These times should not be collapsed into one field.

Use standard data models where practical

Standards from organizations such as DCSA, IATA, UN/CEFACT, FIATA, and ISO can improve consistency and interoperability across providers and transport modes.

Monitor integrations

Track rejected messages, stale feeds, duplicate events, missing fields, authentication failures, version changes, and mapping exceptions.

Record operational overrides

When employees correct or override an event, require a reason and supporting evidence instead of replacing the original information without explanation.

Assign data ownership

Define who maintains customer references, locations, carrier mappings, event rules, time zones, partner connections, and exception queues.

Review recurring patterns

Repeated discrepancies by provider, port, airport, terminal, lane, event, or integration should create a corrective action rather than permanent manual checking.

How to communicate an uncertain shipment status

Customers and internal teams need a useful answer, not a screen capture containing conflicting statuses. A good update separates facts, uncertainty, impact, action, and next review.

Communication element	What to include	Example
Confirmed fact	The latest actual event supported by a relevant source.	“The container was discharged at the destination terminal.”
Unconfirmed point	The missing, conflicting, or estimated information.	“Terminal availability for pickup has not yet been confirmed.”
Operational impact	The decision, appointment, cost, or customer commitment affected.	“The drayage appointment cannot be finalized until availability is posted.”
Action owner	The party investigating or completing the next step.	“The destination agent is checking the terminal release status.”
Next update	A time or event that triggers the next communication.	“We will update after the terminal response or by 3:00 p.m. local time.”

Avoid vague statements such as “the system is wrong” or “the shipment is delayed” unless the evidence supports them. Describe the exact mismatch and the operational effect.

Metrics that improve tracking quality

Event completeness Percentage of required milestones received for the relevant shipment type and lane.

Event latency Time between physical occurrence, event creation, system receipt, and user availability.

Identifier rejection rate Records rejected or quarantined because shipment, container, equipment, or document references are invalid.

Duplicate-event rate Repeated messages representing the same physical event without useful additional information.

Discrepancy resolution time Time from detection until a controlled operational status is confirmed.

Actionable-alert rate Alerts that led to a necessary investigation or operational decision.

False-alert rate Warnings caused by known latency, harmless terminology differences, or incorrect thresholds.

ETA stability Frequency and scale of ETA changes at defined points in the shipment journey.

Manual correction rate Events or references requiring employee intervention and the recorded reason for each correction.

These measurements should be reviewed by provider, lane, terminal, mode, customer, event type, and integration. A strong overall average can hide a persistent problem in one important trade route.

Frequently asked questions

Why does the carrier show arrival while the cargo is still unavailable?

The arrival may refer to the vessel or aircraft reaching the destination. The cargo may still require discharge, breakdown, terminal processing, customs or other releases, payment, document completion, or physical positioning for pickup.

Is GPS data always more reliable than carrier tracking?

GPS or IoT information can provide useful independent evidence, but it tracks the installed device and depends on power, coverage, installation, configuration, and data transmission. It may not confirm legal release, cargo condition, document status, or completion of a business process.

Can AIS prove where a container is?

AIS provides information about a vessel. It may help explain the route or position of the ship believed to be carrying the container, but it does not independently confirm that a specific container is onboard, discharged, or available.

Which source should be trusted when two systems disagree?

Use the source closest to the disputed physical or administrative event, then consider whether the message is actual or estimated, how recent it is, whether the identifier is correct, and whether the event fits the shipment sequence.

Should every discrepancy be reported to the customer?

Not every harmless system difference requires a customer alert. Communication should focus on uncertainty or changes that affect service, appointments, costs, inventory, delivery expectations, compliance, or customer decisions.

Can standardized APIs eliminate all discrepancies?

Standards can improve common definitions, structures, and data exchange, but they cannot eliminate incorrect source data, missing physical events, poor system mapping, stale integrations, or incomplete partner participation.

What should happen when the shipment cannot be located?

Escalate according to the shipment’s risk, value, cargo type, and contractual process. Confirm identifiers, contact the parties responsible for the last confirmed and next expected events, preserve evidence, and document every action and response.

Final perspective

Tracking discrepancies are a normal risk in international freight because many systems describe different parts of the same journey. The objective is not to force every source to display identical words at the same moment.

The objective is to create an understandable shipment timeline that preserves source information, distinguishes actual events from estimates, connects the correct identifiers, and directs employees toward discrepancies that can change an operational decision.

A strong resolution process combines standardized event definitions, source-specific authority, time-zone control, integration monitoring, human investigation, and honest communication. When uncertainty remains, it should be shown clearly rather than hidden behind a single confident-looking status.

Sources and further reading

Editorial note: This guide was prepared by the Samai Supply Tech Editorial Team using publicly available freight data-standard, container-identification, air cargo, multimodal transport, and maritime navigation resources. It provides general educational information and does not replace professional freight forwarding, customs, legal, cybersecurity, insurance, or transportation advice.

Samai Supply Tech Editorial Team

Samai Supply Tech Editorial Team creates practical, research-based content about supply chain management, freight technology, warehouse operations, and e-commerce logistics. Our goal is to explain complex industry topics in a clear and useful way, helping readers better understand modern logistics tools, processes, challenges, and opportunities. Each article is reviewed for clarity, relevance, and accuracy before publication.