A GPS dot may show where a truck is, but it does not confirm whether all packages were collected, whether cargo entered the warehouse or is still waiting at the gate, whether it was loaded on the main carriage or rolled, whether documents will arrive before ETA, or whether customs clearance is blocked. When tracking is reduced to location, a business may receive many updates yet still be unable to answer three operational questions: what stage the shipment is in, what risk remains open, and who must take the next action. This article presents shipment tracking as a management system built on milestones, documents, compliance status, exceptions and ownership—particularly for B2B machinery, components and commercial cargo moving by road, sea or air.

B2B logistics operational reference | Updated: 20 July 2026 | Subject to actual documents and source data

QUICK FACTS

Good tracking answers “which stage?”

Location is only one data layer; status must be supported by a milestone and evidence.

Cargo and documents move in parallel

On-time physical movement cannot compensate for late or inconsistent documents.

Exceptions matter more than routine updates

Early notice of a rolled shipment, missing document or inspection is more valuable than repeated “in transit” messages.

Every status needs an owner and next action

Tracking supports decisions only when it identifies responsibility, deadline, ETA impact and closure criteria.

Illustration for Shipment Tracking Is More Than Checking a Vehicle’s Location — Illustration of the logistics topic, document or operation discussed in the article.

SCOPE

This article applies to B2B export/import shipments, especially machinery, equipment, spare parts, industrial components and palletised/crated commercial cargo moved by road, sea, air or multimodal transport.

Coverage runs from supplier Ready Date through physical delivery, exception handling, document completion and basic reconciliation.
FCL, LCL, air, road, DG, OOG, reefer and project cargo require different milestone sets and controls.
Carrier or GPS data is only one source and should be reconciled with bookings, transport documents, warehouse/terminal status and customs records.

Important limitation: Tracking is not an absolute delivery guarantee. ETA, status and responsibility must be read together with the contract, booking, transport document, SOP and live source data.

TERMS AND DEFINITIONS

TERM	MEANING	OPERATIONAL ROLE
Tracking	Monitoring the shipment’s current status and completed events.	Explains the operational stage, confirmed source and next milestone.
Tracing	Reconstructing historical movements, handovers and status changes.	Supports incident investigation, custody identification and evidence review.
Milestone	An operational event with explicit completion criteria, such as pickup completed, gate-in, customs released or delivered.	Replaces vague labels such as “in progress” or “in transit”.
Event Timestamp	The actual time an event occurred, including time zone and source.	Supports accurate transit-time, dwell-time and event-sequence analysis.
Update Timestamp	The time the event was entered, synchronised or received by the system.	Reveals reporting latency and prevents update time from being mistaken for event time.
ETA / ETD	Estimated Time of Arrival / Departure.	A forecast rather than a guarantee; it should state assumptions and confidence.
Exception	An event that deviates from plan: missing documents, missed cut-off, inspection, waiting truck, rolled cargo or wrong address.	Requires an impact assessment, owner and resolution deadline.
Dwell Time	Time cargo or equipment remains waiting at a location.	Reveals bottlenecks that a GPS position alone cannot explain.
POD	Proof of Delivery.	Closes physical delivery but may not close claims, document collection or cost reconciliation.

NATURE AND OPERATING MECHANISM

1. Tracking manages status, not just a map

A complete tracking system links the cargo object to a milestone, timestamp, evidence source and responsible owner. Vehicle location matters only when cargo is confirmed on that vehicle and the operational stage is known.

2. Two flows must be tracked in parallel

The physical flow includes packing, pickup, warehouse receipt, gate-in, loading, discharge, pickup and final delivery. The data/document flow includes Invoice, Packing List, booking, SI/VGM, B/L/AWB, pre-alert, manifest, origin/permit documents where applicable, Arrival Notice, D/O and customs files. Either flow can become the bottleneck.

3. A status needs completion criteria

“Picked up” needs package count, receipt time and evidence; “departed” must identify feeder, main carriage or transfer truck; “arrived” does not mean available; “customs cleared” does not necessarily mean D/O, local charges and final transport are ready.

4. Tracking must prioritise exceptions and impact

A useful update explains not only what happened but whether ETA, cost, cargo integrity or documentation changed. Each exception should state a preliminary cause, mitigation, owner and next update time.

5. ETA is a multi-condition forecast

Warehouse-delivery ETA depends on Ready Date, pickup capacity, cut-off, connection, carrier schedule, terminal dwell, customs, free time, D/O and last-mile capacity. It should therefore include confidence and assumptions.

A decision-ready status line: Current milestone → evidence/source → exception → ETA/cost impact → owner → next action → update deadline.

ANALYSIS: SEVEN LAYERS OF SHIPMENT TRACKING

TRACKING LAYER	QUESTION TO ANSWER	PRIORITY DATA SOURCE	RISK SIGNAL	MANAGEMENT OUTPUT
Physical position	Where is the cargo/equipment? Is the position direct cargo data or only the tractor/vehicle position?	GPS, AIS, flight status, terminal/depot gate event, warehouse confirmation.	Vehicle moved without cargo; container in yard but not loaded; lost signal.	Position with update time and source.
Operational milestones	Which leg is completed and is there evidence?	Pickup note, warehouse receipt, FCR, EIR, carrier event, POD.	“Picked up” without package count; “departed” without transport document or load confirmation.	Confirmed milestone, verifier, timestamp and evidence.
Documents	Are documents keeping pace with the physical shipment?	Invoice, Packing List, SI, VGM, B/L/AWB, pre-alert, Arrival Notice, D/O.	Cargo nearing destination while pre-alert, consignee data, C/O or permit remains unresolved.	Document status, owner and deadline.
Customs and compliance	Is the shipment filed, selected for inspection, released or waiting for a regulatory result?	Declaration status, system response, permit, inspection record.	“Arrived” is mistaken for “ready to deliver” while clearance is not ready.	Procedure status, missing item and next action.
Exceptions and risk	Has anything changed ETA, cost or cargo integrity?	Carrier/terminal notice, warehouse report, photos, escalation email, booking amendment.	Late roll notice, shortage, seal discrepancy or emerging DEM/DET exposure.	Exception log with cause, impact, option, owner and deadline.
Responsibility and action	Who owns the issue and what happens next?	TMS/WMS, task log, confirmed email, SOP/RACI.	Everyone is “checking” but no one has a deadline or decision right.	Single owner, action, due time and closure criterion.
Delivery forecast	Is the ETA still credible and what assumptions may change it?	Carrier schedule, cut-off, free time, dwell, document and customs status.	Forecast based only on driving/sailing time.	Scenario-based ETA and confidence level.

DOCUMENTS AND DATA TO CHECK

Tracking is reliable only when system data matches shipment documents. Minimum fields should include shipment reference, PO, shipper/consignee, commodity, packages, weight, dimensions, container/seal or AWB/B/L, pickup location, POL/POD, voyage/flight, ETD/ETA, free time, document status, customs status, delivery address and receiver.

MILESTONE	MINIMUM DATA	EVIDENCE	TYPICAL UPDATER	STATUS CLOSURE RULE
Cargo ready	Ready Date, packages, weight, dimensions, pickup address and contact.	Draft Packing List, cargo photos, supplier confirmation.	Supplier / Buyer / origin Forwarder.	Ready means packed, minimum documents available and pickup is operationally possible.
Pickup completed	Arrival/departure time, vehicle, packages received and packaging condition.	Pickup note, photos, signature, GPS if available.	Trucker / agent / origin warehouse.	Vehicle location cannot replace the receipt evidence.
Warehouse receipt/gate-in	Package/container ID, measurements, yard location, seal and time.	Warehouse Receipt/FCR/EIR.	Warehouse/CFS/terminal.	Reconcile against booking and pre-alert; record discrepancies immediately.
Main-carriage loaded	Flight/voyage, actual departure and transport-document number.	B/L/AWB, carrier event, manifest/pre-alert.	Carrier/Forwarder.	Separate booked, received, loaded and departed.
Arrival at destination	ATA, discharge status, Arrival Notice and free time.	Carrier/terminal event, Arrival Notice.	Carrier/destination agent.	ATA does not equal cargo availability.
Customs/release	Declaration, channel, additional request and result.	System response, declaration, permit/inspection record.	Customs Broker / Importer.	Separate filed, cleared, released and ready for pickup.
Final delivery	Truck release, address, packages, receiver and exception.	D/O, delivery note, POD, photos.	Trucker / receiving warehouse.	Physical delivery may close while claims/documents/costs remain open.

PROCESS FOR MANAGEMENT-GRADE TRACKING

Step 1 – Map milestones before booking

Define mandatory events for the transport mode and delivery term, with completion rules, source and owner.

Step 2 – Lock one shipment reference

Use a single identifier linking PO, booking, packages, container, B/L/AWB, declaration and POD.

Step 3 – Set source hierarchy

Prioritise direct warehouse, terminal, carrier and customs events; label automatic data, manual confirmation and forecast separately.

Step 4 – Capture event time and update time

Record the actual event time, later update time, time zone and source to measure dwell correctly.

Step 5 – Track document workflow separately

Use draft/checked/issued/received/corrected statuses for key documents, with owner and deadline before ETD/ETA.

Step 6 – Open an exception log immediately

Document cause, impact, action, owner, deadline and escalation point as soon as the plan changes.

Step 7 – Reforecast ETA

When a milestone or exception changes, update warehouse-delivery ETA and state assumptions and confidence.

Step 8 – Close against full criteria

Close only after POD, exception resolution/reservation, required documents, empty return where applicable and basic cost reconciliation.

RISKS AND COMMON ERRORS

COMMON ERROR	CAUSE	IMPACT	CONTROL
Sending only a map position	Tracking is reduced to GPS.	No proof that cargo was received, loaded or moved with that vehicle.	Link position to milestone, source and evidence.
Using “in transit/in progress”	No shared status taxonomy.	Stakeholders cannot forecast or identify the next action.	Use statuses with completion criteria and timestamp.
ETA without assumptions	Carrier ETA copied or theoretical transit time added.	Production, warehouse and cash-flow plans become unreliable.	Provide scenario ETA and change drivers.
Cargo moves ahead of documents	Transport is tracked but documents are not.	Cargo arrives but clearance cannot start; storage/DEM/DET exposure grows.	Track physical and document flows in parallel.
Exception without owner	Problem is announced but no task is assigned.	High information volume with no resolution.	Every exception needs one owner, action, deadline and escalation.
Event time confused with update time	Late manual updates or time-zone errors.	Dwell and delay responsibility are misread.	Store event time, update time, time zone and source.
Shipment closed at POD	Delivery is treated as full operational closure.	Claims, originals, invoices, empty return or reconciliation are missed.	Close only after delivery, exceptions, documents and costs are completed.

OPERATIONAL BASIS AND SOURCES

Shipment tracking is built from contracts, bookings, transport documents, carrier/terminal/warehouse events, customs files and internal SOPs. No single universal status vocabulary fits every route and provider.

Sales contract and Incoterms: identify named place, delivery responsibilities and required coordination data.
Booking, transport document and carrier terms: verify cut-off, voyage/flight, route, free time and event definitions.
Warehouse/terminal/carrier systems: confirm gate, loaded/discharged, release and equipment events.
Customs and regulatory files: confirm filing, inspection, additional requests and outcome.
Company SOP/TMS/WMS: standardise milestones, ownership, escalation, retention and closure.
DCSA Track & Trace: Standardises data definitions and event exchange for container whereabouts, gate events, load/discharge, transshipment and pickup/drop-off.
GS1 EPCIS: Provides an event-data framework for the what, where, when, why and how of status, location, movement and chain of custody.

Reference scope: DCSA and GS1 EPCIS are data standards and operational reference frameworks. They do not replace the governing contract, carrier terms, customs data or shipment-specific internal procedures.

Note: Before using tracking data for a customer commitment or liability decision, verify the data timestamp, source and governing contract.

FAQ

Does GPS mean the shipment is fully tracked?

No. GPS mainly shows vehicle location. Cargo presence, completed milestone and supporting evidence still need confirmation.

Why does a carrier say “arrived” while cargo is not collectable?

Arrived may refer only to vessel/flight arrival or discharge. Release, manifest, Arrival Notice, D/O, charges, customs and truck capacity may still be pending.

How often should status be updated?

Update by event and exception, not only by a fixed reporting interval. Critical exceptions should be reported immediately.

Is carrier ETA the warehouse-delivery date?

Usually not. It commonly refers to port/airport/terminal arrival; warehouse delivery depends on discharge, clearance, release and last mile.

Should tracking include C/O and permits?

Yes when they affect preferential duty or clearance eligibility. A complete system tracks cargo and documentation in parallel.

When is a shipment operationally complete?

Not solely at POD. Delivery, exceptions, required documents, equipment return and relevant cost reconciliation should be completed.

APPLICATION NOTE: Status names, update frequency and data sources should be designed for the actual mode, route, cargo, contract and system capability. Generic status labels do not replace documents or operational evidence.

TGIMEX IMPLEMENTATION SUPPORT

TGIMEX helps businesses turn the article into a shipment-ready checklist, covering input-data review, dossier preparation, milestone control, and coordination with the relevant parties.

Convert guidance into checks

Assign an owner and deadline to every operational control point.

Reconcile shipment data

Compare booking, transport, commercial, customs, and delivery evidence.

Manage operational risk

Record discrepancies, actions, and decision evidence to prevent recurrence.

Discuss your shipment dossier

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B

MACHINERY

HOUSEHOLD GOODS

COSMETICS – PERSONAL CARE