Three steps from a disrupted shipment to a resolved reroute.
FlowSync agents do the in-between work your ops team cannot scale — detecting the disruption, generating a reroute recommendation, and reporting on the outcome — so your team approves the call rather than making it under pressure.
Detect & classify
GPS pings, carrier status events, and active weather alerts are correlated per shipment in near-real-time. The pipeline scores each signal against the shipment’s estimated transit time and raises a DisruptionEvent the moment a signal crosses the 15% threshold — with type and severity attached so downstream steps know what they’re handling.
Negotiate & plan
For each new DisruptionEvent, the routing engine receives the shipment context and returns a scored reroute recommendation: a primary route plus alternatives, with cost and SLA tradeoffs side by side. Pricing is sourced from current spot-market rates so the recommendation is a real call, not a placeholder.
Execute & report
The recommendation lands in your ops dashboard the moment it’s generated, and a corresponding Alert record is written into the in-app alert feed. Your team approves from there, and the post-event report closes the loop — feeding the model so future recommendations for your network are sharper.
Your team still owns the call.
FlowSync generates the recommendation and keeps the alert log; executing with a carrier is your team’s approval. The pipeline’s job is to surface the right reroute at the right moment — not to skip the decision your team is paid to make.
For the live picture — top disrupted lanes, current reroute rate, and recent anonymized reroutes — see the trends digest →