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

at delivery

Juniper Pet Nutrition · Harrisburg, PA → Newark, NJ

TMS source record

TMS · TMS-24029

Dispatcher / owner

Tessa Morgan

Carrier / driver

Silver Oak Freight · Priya Shah

Equipment

Dry van · (555) 016-3129

Origin

Harrisburg, PA

Destination

Newark, NJ

Pickup appointment

4:00 PM

Delivery / current ETA

6:00 PM / 6:00 PM

Operational timeline

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

BOL received

2:00 AM · 31h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

Driver dispatched

10:00 PM · 35h ago

Priya Shah assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

4:00 PM · 65h 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.