Shipment Visibility vs Tracking Explained

Shipment visibility vs tracking

The two terms are often used interchangeably, but they describe different things:

	Tracking	Visibility
Question answered	Where is this shipment, or where was it last reported?	Is it on plan, and what needs attention?
Scope	One shipment, usually one carrier's data	Many shipments, across carriers, modes and legs
Typical output	A status page or a list of scans	Exceptions, estimated arrival, position age and who holds the goods
How you use it	Look it up when asked	Act on alerts before someone asks

Visibility is built on tracking data. Its value depends on whether each fact on the screen is labeled for what it is, which is what the rest of this guide is about.

Three kinds of "where is it?"

Kind	Where it comes from	What it really means
Measured position	A GPS or cellular tracker on the goods, trailer or container; vehicle telematics	The device was here at the time of the fix. It says nothing about where it is now if the fix is old.
Milestone	A scan or status event from a carrier, terminal or warehouse	Something happened at this place at this time: loaded, departed, arrived, released. Between milestones there is no information.
Estimate	Calculated from milestones, schedules or vessel and flight positions	Where the goods probably are if everything went to plan. Useful for planning, dangerous for proof.

All three are useful. The mistake is to show them the same way. A map that draws an estimate with the same confidence as a fresh measurement invites wrong decisions.

How old is too old?

Every measured position should carry its age: the time since the fix, not the time the screen refreshed. What counts as stale depends on the mode:

Road freight moves quickly, so a fix more than a short while old may already be many miles out.
Ocean containers often lose signal at sea or inside stacks. Gaps of hours are normal, and a position from the terminal may be the last until arrival.
Air cargo trackers are often switched off or restricted in flight, so milestones from the airline carry more weight.

Set a staleness threshold per mode and show clearly when a position has passed it.

Building visibility you can act on

Model the journey as legs. A shipment is a sequence of movements with different carriers and data sources, not a single location field.
Use what you already have. Many operators already run telematics or trackers. Connect those before buying more hardware.
Import carrier data idempotently. Carrier feeds repeat and correct themselves. An import that creates duplicates on every re-run makes the history untrustworthy.
Draw the difference. Show measured fixes, milestones and estimates distinctly, with the age of every measurement.
Alert on exceptions, not on movement. People need to know about a missed milestone, a stale tracker or an unplanned stop, not every ping.

Visibility is not custody

Knowing where the goods are does not tell you who is responsible for them. A container can stand still for days while responsibility passes between a carrier, a terminal and a trucker. For disputes, the position history matters less than the handover record: see chain of custody. For security, a tracker that goes silent or a stop that was not planned is often the first sign of cargo theft, and for temperature-controlled freight, a reading's age matters as much as a position's; see temperature excursion records.

Data sources compared

Source	Strengths	Limits
Carrier milestones and portals	No hardware; official status	Gaps between scans; formats differ by carrier
Vehicle telematics	Frequent positions; often already installed	Tracks the truck, not the goods once they leave it
Trackers on goods or containers	Follow the cargo across legs	Signal loss; battery life; restrictions in flight
Vessel and flight positions	Broad coverage	Show the vessel, not whether your container is on it

Exceptions worth alerting on

A milestone that should have happened by now and has not.
A tracker that has not reported within its expected interval.
A stop that was not planned, or a route that deviates from the plan.
An estimated arrival that moves past the delivery appointment.
A temperature or door event on sensitive freight.
A container still at the terminal as free time runs out, before demurrage starts to accrue.

A quick self-check

Can you tell, for any position on your map, whether it was measured or estimated?
Does every measured position show how old it is?
Can you find a shipment from any party's reference?
Do people hear about exceptions before customers ask?

If any answer is no, fix that before adding more data sources.

How Cargovate approaches it

In Cargovate, tracking positions come from your own devices or the telematics you already run, and each position carries the age of its fix. On the operational map, a measured tracker fix is drawn apart from positions estimated from status. Imports from the systems you already use are idempotent, so a re-run never duplicates history. See how shippers use it.

Common questions

What is the difference between shipment visibility and tracking?

Tracking reports where a shipment is or was. Visibility combines tracking data across carriers and legs to show whether shipments are on plan and which need action.

Why does my tracking position look wrong?

It may be old, estimated rather than measured, or from a device on the trailer rather than the goods. Check the age and source of the position before acting on it.

Is an ETA a measurement?

No. An ETA is a forecast built from schedules, milestones and positions. It is useful for planning but not evidence of where the goods were. See the glossary.

Do I need new trackers to get visibility?

Not always. Many operators already have telematics, carrier feeds and trackers. Connecting and labeling those sources is usually the first step.

Shipment visibility: what a position really tells you