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-24037

at delivery

Redwood Office Products · Harrisburg, PA → Newark, NJ

TMS source record

TMS · TMS-24037

Dispatcher / owner

Elena Rodriguez

Carrier / driver

Highland Route Co. · Priya Shah

Equipment

Dry van · (555) 016-3137

Origin

Harrisburg, PA

Destination

Newark, NJ

Pickup appointment

6:00 PM

Delivery / current ETA

2:00 AM / 2:00 AM

Operational timeline

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

Driver dispatched

12:00 AM · 33h ago

Priya Shah assigned to the load.

Operational event · FreightFlow event layer

BOL received

6:00 PM · 39h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

TMS record synchronized

6:00 PM · 63h 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.