CargoTrax Shipment Tracking

RoRo Customer Timeline

Customer-facing shipment status timeline for CargoTrax RoRo export workflow. This screen connects customer submission, document review, title verification, carrier booking, AES/ITN, dock receipt, port delivery, vessel loading, and destination arrival.

Current Status
Documents Pending

CT-RORO-DEMO-001

Customer-visible tracking active
CargoTrax Status Strip

Color-coded shipment, document, title/cargo, booking, AES/ITN, payment, dock receipt, and tracking status.

Green = ready/complete · Blue = active · Orange = pending/action needed · Red = hold/blocked · Gray = future/not started
Shipment
In Progress

Customer RoRo packet is open.

Documents
Action Needed

Required customer documents are pending.

Title/Cargo
In Review

Title and VIN review pending clearance.

Booking
Pending

Carrier booking not confirmed.

AES/ITN
Pending

ITN required before dock receipt release.

Payment
Payment Needed

Customer release may be blocked until payment clears.

Dock Receipt
Locked

Blocked until packet gates pass.

Tracking
Active

Customer-visible timeline started.

Source: Fallback static packet view

Backend Shipment Timeline

Source: Fallback static timeline

Fallback Mode
1
Shipment Submitted

Customer RoRo packet has been started in the CargoTrax sandbox.

Pending backend event
2
Documents Pending

Required customer documents, title/cargo checks, booking, AES/ITN, payment, and dock receipt gates are being tracked.

Pending backend event
3
Dock Receipt Locked

Dock receipt release remains locked until the required gates pass.

Pending backend event

This tracking timeline is for SIA sandbox validation. Final customer-facing production tracking belongs to the NVOCC public website/domain.

Customer

Demo Export Customer

RoRo Vehicle Export

Vehicle / Cargo

VIN-DEMO-001

Destination: Nigeria

Booking / AES

Booking: Pending

ITN: Pending

Dock Receipt

Locked

Available after readiness gates pass.

Shipment Timeline

IntakeDocumentsAES / ITNDock Receipt
1
Submitted

Customer

Customer shipment submission started

CargoTrax opened the RoRo shipment workspace and generated the required document checklist.

COMPLETE
2
Documents Pending

Customer + Internal

Required documents in progress

Vehicle title was received. Bill of sale, customer ID/business document, and conditional export authorization are still pending.

ACTIVE
3
Title Review

Internal

Title and cargo verification under review

VIN, title, lien status, ownership, and vehicle details must clear before booking/AES/dock receipt release.

ACTIVE
4
Booking Pending

Customer

Carrier booking pending

Carrier, booking number, vessel/voyage, terminal, and cutoff date will be added after document and title review advance.

WAITING
5
AES / ITN Pending

Internal + Customer after accepted

AES/EEI and ITN pending

AES packet is prepared after booking and document readiness. ITN unlocks dock receipt readiness after acceptance.

WAITING
6
Dock Receipt Locked

Customer

Dock receipt not yet available

Dock receipt becomes available after documents, title/cargo review, carrier booking, AES/ITN, and hold checks pass.

WAITING
7
Port Delivery Pending

Customer

Port delivery / scan verification

CargoTrax will later show delivery, port scan, and vessel loading events.

FUTURE
8
Destination Pending

Customer

Destination arrival

Arrival and destination notice events will appear when carrier or internal updates are posted.

FUTURE

Customer Notices

Missing document notice ready for customer email
Carrier booking notice will be sent after booking confirmation
AES/ITN notice will be sent after accepted filing result
Dock receipt availability notice will be sent after dock receipt generation
Carrier notice posting will update tracking and customer notifications

Next Automation Target

CargoTrax should automatically post timeline events when documents are uploaded/reviewed, title status changes, carrier booking is confirmed, AES/ITN is accepted, dock receipt is generated, customer email notices are sent, and carrier/port/destination notices are posted.

Customer-visible events stay separate from internal-only compliance, exception, hold, correction, and audit events.