A tracker that records only ETD, ETA and “in transit” is rarely sufficient to manage imports. The business must know where each update came from, whether a date is planned, estimated or actual, which function owns the next task, which document remains incomplete, what may cause delay and when the next action is due. When everything is placed in a free-text note, the file becomes a diary rather than a decision tool. This article presents a Shipment Master – Milestone – Document & Compliance – Exception & Action structure, designed primarily for FCL/LCL ocean imports and adaptable to air, road and multimodal shipments.

Operational reference for Import, Procurement, Logistics, Customs, Finance, Warehouse and Project Operations | Updated 20 July 2026

QUICK FACTS

One shipment, one stable ID

A Shipment ID links the PO, booking, transport document, container, customs file, costs and delivery evidence.

Separate plan from reality

Each milestone should distinguish planned/estimated time, actual time, source and last update.

Track work, not only location

Owner, next action, due date and exception status make the tracker operational.

Do not overload one sheet

Use a one-row shipment summary plus detailed milestone, document and exception tables.

Illustration for How to Build an Import Shipment Progress Tracker — Illustration of the logistics topic, document or operation discussed in the article.

SCOPE

This article covers commercial imports by FCL/LCL ocean, air, road, rail and multimodal transport. Users include procurement, import/export, logistics, customs brokers, finance, warehouses, project teams and management.

The tracking window runs from cargo readiness or booking to delivery, empty return and shipment closure.
Regulated cargo should include separate permit, inspection or quarantine milestones and owners.
An internal tracker does not replace official carrier, terminal, customs or source-document data.

KEY TERMS

Term	Meaning	Role in the tracker
Shipment ID	A unique internal identifier for a shipment or delivery flow.	Links PO, booking, B/L/AWB, container, declaration, cost and evidence.
Milestone	A meaningful operational event or stage.	Examples: cargo ready, booking confirmed, loaded, arrived, released and delivered.
Planned Time	A company plan or internal commitment.	Measures adherence to plan; it is not the carrier’s ETA.
Estimated Time	A forecast updated by carrier, forwarder, terminal or operating system.	May change and must carry source and update time.
Actual Time	The time an event occurred, supported by evidence.	Used to calculate lead time, SLA and completion.
Event Time	The timestamp associated with an event together with a Planned, Estimated or Actual classifier.	Shows whether the milestone is a baseline, forecast or completed occurrence; it is not the data-entry time.
Update Time	When data was entered or synchronised into the tracker.	Indicates freshness.
Exception	A deviation requiring attention or decision.	Needs severity, cause, owner, action and deadline.
Next Action	The next task required to move the shipment forward.	Turns tracking into execution management.

THE TRACKER MUST ANSWER SEVEN QUESTIONS

Question	Minimum fields	Common mistake
Which shipment?	Shipment ID, PO, supplier, importer, mode and commodity.	Using supplier name or invoice as the only key.
Which stage?	Current stage, current milestone and status.	Leaving “in transit” unchanged for weeks.
What is completed?	Actual time, evidence and event source.	Marking complete without ATA, EIR, D/O or POD.
What comes next?	Next milestone and planned/estimated date.	No preparation for documents, truck or warehouse.
Who owns it?	Owner, supporting party and contact.	Only naming a department.
What can go wrong?	Exception code, severity, impact and free-time exposure.	Long notes that cannot be filtered.
What must be done?	Next action, due date and escalation.	Tracking location without tracking decisions.

Principle: each event record should state what happened, when, where, which source confirmed it and who acts next.

FOUR-BLOCK TRACKER ARCHITECTURE

Data block	Row unit	Purpose	Core fields
1. Shipment Master	One row per shipment.	Dashboard and current status.	Shipment ID, PO, supplier, mode, booking, B/L/AWB, ETA, stage, owner and risk.
2. Milestone Log	One row per shipment milestone.	Stores plan, forecast, actual and source history.	Milestone code, planned, estimated, actual, location, source and update time.
3. Document & Compliance	One row per document/requirement.	Tracks document, customs and regulatory readiness.	Document, required status, version, issuer, reviewer, due date and issue.
4. Exception & Action	One row per exception/action.	Controls risk and escalation to closure.	Exception, severity, cause, impact, action, owner, deadline and evidence.
Optional: Cost & Free Time	One row per charge or charging milestone.	Tracks estimate/actual, Free Time, DEM/DET and storage.	Charge code, amount, free-time end, payer and dispute status.

Small teams may keep these blocks in four sheets. Larger operations can migrate the same model into a TMS, ERP, database or BI platform without redesigning the logic.

CORE DATA FIELDS

Field group	Recommended fields	Suggested authoritative source	Control point
Identification	Shipment ID, PO, supplier, importer, Incoterms, mode and shipment type.	ERP/PO or approved master tracker.	Do not change Shipment ID when vessel or ETA changes.
Cargo	Commodity, SKU group, packages, weight, CBM and DG/OOG/reefer flags.	Approved packing list/cargo profile.	Separate planned from shipped cargo.
Transport	Booking, carrier/forwarder, B/L/AWB, container/seal, route and vessel/flight.	Booking confirmation, transport document and carrier portal.	Do not overwrite event history.
Time	Ready date, ETD/ATD, ETA/ATA, availability, gate-out, delivery and empty return.	Carrier, terminal, forwarder and delivery evidence.	Record location, time zone and update time.
Documents	Invoice, PL, B/L, C/O, permit, declaration and D/O.	Document repository and filing system.	Record version, status, reviewer and open issues.
Actions	Current stage, next action, owner, due date and escalation.	Operations owner.	Close only with result/evidence.
Risk	Exception type, severity, delay, cost exposure and mitigation.	Exception log.	Separate estimated and actual impact.
Closure	Delivery, POD, empty return/EIR, invoice reconciliation and closure date.	Warehouse, trucker, carrier/depot and finance.	Do not close at customs release alone.

STANDARD OCEAN-IMPORT MILESTONES

Phase	Milestone	Plan/estimate data	Actual evidence	Primary owner
Pre-carriage	Cargo ready confirmed	Ready date, quantity and packing data.	Supplier/factory confirmation.	Procurement/Logistics
Booking	Booking confirmed	ETD, cut-offs, route and equipment.	Booking confirmation.	Logistics/Forwarder
Origin	Cargo received / Gate-in	Closing time and terminal-delivery plan.	Terminal/CFS or carrier event.	Supplier/Forwarder
Origin	Loaded on transport	Loading date and intended service.	Carrier/terminal load event or on-board document where applicable.	Forwarder/Carrier
Departure	Transport departed / ATD	ETD and planned route.	Carrier transport-departure event.	Forwarder/Carrier
Transit	Transshipment / Rollover / Delay	Leg ETA and connection plan.	Timestamped carrier event/update.	Logistics
Destination	Transport arrived / ATA	ETA at the specified destination port/terminal.	Carrier/terminal actual-arrival event; an arrival notice is a planning document, not default proof of Actual arrival.	Carrier/Forwarder
Destination	Container/Cargo discharged	Discharge plan and terminal/CFS.	Carrier/terminal actual-discharge event.	Carrier/Forwarder
Availability	Container/Cargo available	Availability forecast, release and D/O readiness.	Carrier/terminal/CFS availability confirmation.	Logistics
Customs	Declaration registered	Planned filing, documents and tax data.	Registered declaration and corresponding processing status.	Customs/Compliance
Customs	Customs clearance/release status	Plan for duties, documentary check, physical inspection or specialist controls where applicable.	Official status/result appropriate to the actual procedure; one generic “Released” label should not replace all customs states.	Customs/Compliance
Pickup	Gate-out / Pickup	Truck, slot and receiving plan.	EIR or actual gate-out/pickup event.	Trucking/Logistics
Delivery	Delivered / POD	Delivery appointment.	POD/receiving report.	Warehouse/Trucking
Container close	Empty returned	Depot and Free Time end.	Empty-return EIR/depot confirmation.	Trucking/Logistics
Shipment close	Cost reconciled / Shipment closed	Invoice and reconciliation plan.	Approved cost sheet, archived records and closed/transferred exceptions.	Finance/Logistics

For LCL, replace container discharge/availability, gate-out and empty return with CFS arrival, cargo deconsolidated, cargo release, pickup and delivery. For air, keep flight arrived separate from cargo available; aircraft arrival does not mean the cargo is ready for collection.

DOCUMENTS AND DATA TO RECONCILE

Source	Issuer/updater	Fields to capture	Risk of copying without validation
PO/Contract	Procurement and supplier	Supplier, importer, Incoterms, quantity and required date.	Wrong shipment or business deadline.
Packing List/Cargo profile	Supplier/factory	Packages, weight, CBM, dimensions and cargo nature.	Wrong booking and truck/warehouse plan.
Booking confirmation	Carrier/forwarder	Route, ETD, cut-offs, equipment and booking number.	Outdated sailing or missed cut-off.
B/L/AWB and pre-alert	Carrier/forwarder	Document number, parties, ports, vessel/flight and cargo.	Manifest, D/O and customs mismatch.
Carrier/terminal tracking	Carrier, terminal and CFS	Estimated/actual events, location and availability.	Confusing estimate with actual or using stale data.
Customs/compliance file	Importer, broker and authority	HS, declaration, channel, permit, inspection and release.	Tracking transport but missing the clearance bottleneck.
D/O, EIR and POD	Carrier/depot/trucker/warehouse	Release, gate-out, empty return and delivery.	No proof of DEM/DET end or delivery.
Quotation/debit note/invoice	Service providers and finance	Scope, validity, estimate, actual and disputed amount.	No measure of delay-cost impact.

BUILD PROCESS

Step	Input	Action	Output
1. Define the purpose	Users and decisions.	Separate management dashboard, daily operations and reconciliation needs.	Tracker scope.
2. Lock the identifier hierarchy	PO, delivery split, booking, transport document, equipment and actual shipment.	Create a stable internal Shipment ID; booking, B/L/AWB and container numbers are linked one-to-many identifiers and should not replace it.	Cross-table linkage.
3. Define milestones by mode	FCL, LCL, air, road or rail.	Select decision-relevant events and do not merge arrival, discharge and availability.	Milestone dictionary.
4. Separate planned–estimated–actual	Internal plan and carrier/terminal sources.	Add separate fields with event classifier, location, time zone, source and update time.	Measurable timeline.
5. Assign owner and next action	RACI/operating roles.	Every open item receives an owner and due date.	Actionable tracker.
6. Separate progress and health	Milestone lifecycle and risk condition.	Use Progress Status: Not started/In progress/Completed/Cancelled; Health Status: On track/At risk/Delayed/Blocked.	A dashboard that does not confuse completion with risk.
7. Set update rules	Sources, cadence, triggers and escalation.	Define who updates, when and with what evidence.	Update SOP.
8. Pilot on real shipments	Different modes and risks.	Remove unused fields and fix logic.	Adjusted tracker.
9. Measure data quality	Completeness, latency, overdue actions and milestone variance.	Fix root causes rather than add notes.	Quality dashboard.

ALERT AND ESCALATION RULES

Signal	Reference trigger	Priority	Action
ETA change	New ETA exceeds internal buffer or affects warehouse/production deadline.	Medium–High	Replan delivery, documents, cash, warehouse and stakeholders.
Documents incomplete before ETA	Required document not Approved/Available by internal deadline.	High	Assign owner, obtain draft/final and establish fallback.
No fresh update	Update Time exceeds the phase-specific threshold.	Medium	Verify with carrier/forwarder; do not infer status.
Milestone overdue	Actual is blank after planned/estimated time.	High	Open exception and obtain revised timing.
Free Time exposure	Forecast gate-out/empty return approaches Free Time end.	High	Lock D/O, customs, truck, warehouse and depot plan.
Action overdue	Due date passed while action remains open.	High	Escalate through RACI and quantify impact.
Conflicting data	B/L, tracker, portal or customs file disagree.	High	Identify System of Record before overwriting.

Thresholds must reflect route, lead time, cargo, Free Time, business criticality and recovery capability. No single number of days fits every shipment.

RISKS AND COMMON DESIGN ERRORS

Design error	Impact	Correction
All history in a Notes column	No filtering, lead-time measurement or open-action control.	Separate milestone and exception logs.
ETA without destination/location	Transshipment ETA is confused with final-port ETA.	Attach location and time zone.
Overwriting old ETA	Schedule-change history is lost.	Keep event/version history.
Status without owner/due date	The file reports but cannot drive execution.	Add owner, next action, due date and escalation.
Mixing estimated and actual	Lead-time and completion reports become wrong.	Separate planned, estimated and actual.
Manual colours instead of codes	Cannot filter or migrate.	Use code lists; colour is only presentation.
Email update without source	No traceability for decisions.	Store source, update time and evidence link.
Closing at customs release	Delivery, empty return and cost closure are missed.	Define complete closure criteria.
Mixing progress with risk status	One field contains both Completed and At risk/Delayed values.	Users cannot tell whether the milestone is finished or merely unhealthy; dashboards misstate the situation.	Maintain separate Progress Status and Health Status fields.

STANDARDS AND REFERENCE SOURCES

Source	Role for tracking design	Application
DCSA Track & Trace	Standardises container journey visibility and events such as load/discharge, gate-in/out, transshipment and pickup/drop-off.	Milestone and event-code reference for ocean shipments.
DCSA Standard Documentation	Organises the journey into pre-shipment, pre-ocean, ocean, post-ocean and post-shipment phases.	Prevents an ETA-only tracker.
UN/CEFACT Multimodal Transport Standards	Provides reference data models and multimodal exchange standards.	Identifiers, parties, documents and status reporting.
GS1 EPCIS & CBV	Describes events through what, when, where, why and how in a shared language.	Event time, location, object and business context.

These are technical and industry references. Internal tracking must still follow contracts, company procedures, official partner data and applicable regulations.

FAQ

One row per shipment or one row per milestone?

Use both: Shipment Master for overview and Milestone Log for history and lead-time analysis.

Should a changed ETA overwrite the old ETA?

Keep the current ETA in the master view, but retain each change with source and update time in the event log.

Is Excel enough?

It may be sufficient for limited volumes and users. More integrations, access controls, alerts and audit requirements usually justify a database, TMS or suitable platform.

How often should it be updated?

There is no universal cadence. Update on new events, near cut-offs/ETA and when actions become due; do not create cosmetic updates without a new source.

How many status values?

Enough to support decisions without excessive complexity. A practical set is Not started, In progress, Completed, At risk, Delayed and Blocked.

Should costs be in the same tracker?

Summary estimates/actuals may be in the master, while detailed charges should remain in a linked cost table.

When is a shipment closed?

After delivery and POD, empty return where applicable, document archive, key cost reconciliation and closure or transfer of all exceptions.

APPLICATION NOTE: A tracker is an operational aggregation layer, not the sole evidence of an event. Important Actual Times should link to sources such as carrier events, arrival notices, declarations, D/O, EIR, POD or terminal/warehouse confirmation. The structure must be adapted to cargo type, mode, route, Incoterms and available systems.

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