Back to queue Live shipment record

King of Freight · Concept prototype

The TMS remains the system of record for loads, contracts, customer master data, and accounting. This fictional demonstration shows how FreightFlow could surface what needs attention, who should act, and whether it was resolved.

Synthetic data · fixed Sep 8 scenario · saved in this tab

FF-24022

delivered

Vantage Retail Group · Memphis, TN → Nashville, TN

TMS source record

TMS · TMS-24022

Dispatcher / owner

Elena Rodriguez

Carrier / driver

Canyon State Logistics · Maya Chen

Equipment

Dry van · (555) 016-3122

Origin

Memphis, TN

Destination

Nashville, TN

Pickup appointment

5:00 PM

Delivery / current ETA

11:00 PM / 11:00 AM

Operational timeline

Imported TMS milestones alongside FreightFlow work, communications, documents, and exceptions.

Tracking checkpoint

8:00 AM · 1h ago

Last location reported near Memphis, TN.

Automated tracking · FreightFlow event layer

Customer notification

7:00 AM · 2h ago

EMAIL · Checkpoint update sent with current ETA and next action.

Human communication · FreightFlow event layer

Carrier communication

3:00 AM · 6h ago

PORTAL · Driver reports clear roads and steady progress.

Human communication · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to delivered.

Operational event · FreightFlow event layer

Exception created: BOL missing

8:00 PM · 13h ago

Bill of lading is not attached to the shipment record.

Operational event · FreightFlow event layer

POD received

11:00 AM · 22h ago

POD attached to the shipment record.

Document event · FreightFlow event layer

Driver dispatched

11:00 PM · 58h ago

Maya Chen assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

5:00 PM · 88h ago

Authoritative load and appointment data received from TMS.

Operational event · FreightFlow event layer

Operations notes

Keep handoffs clear for the next broker or dispatcher.