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

pod pending

Juniper Pet Nutrition · Kansas City, MO → Omaha, NE

TMS source record

TMS · TMS-24039

Dispatcher / owner

Tessa Morgan

Carrier / driver

Lakeside Carrier Group · Jordan Brooks

Equipment

Dry van · (555) 016-3139

Origin

Kansas City, MO

Destination

Omaha, NE

Pickup appointment

6:00 PM

Delivery / current ETA

6:00 AM / 4:00 AM

Operational timeline

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

BOL received

4:00 PM · 41h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

Driver dispatched

12:00 AM · 57h ago

Jordan Brooks assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

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