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

in transit

Harbor & Pine Home Goods · Dallas, TX → Atlanta, GA

TMS source record

TMS · TMS-24040

Dispatcher / owner

Maya Chen

Carrier / driver

Blue Mesa Freight · Elena Rodriguez

Equipment

Reefer · (555) 016-3140

Origin

Dallas, TX

Destination

Atlanta, GA

Pickup appointment

1:00 AM

Delivery / current ETA

5:00 AM / 5:00 AM

Operational timeline

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

Exception created: Delivery appointment risk

12:00 PM · 21h ago

Current ETA is trending past the delivery appointment.

Operational event · FreightFlow event layer

Driver dispatched

7:00 AM · 26h ago

Elena Rodriguez assigned to the load.

Operational event · FreightFlow event layer

Exception created: Carrier non-response

2:00 AM · 31h ago

Carrier has not acknowledged the last two outreach attempts.

Operational event · FreightFlow event layer

TMS record synchronized

1:00 AM · 56h 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.