How does the system detect freight disruptions in the first place?

Three feeds are ingested continuously: GPS pings, carrier API status updates, and active weather alerts. Each signal is scored against a shipment’s estimated transit time, and events crossing the configured fifteen percent severity threshold become a ranked DisruptionEvent that the rerouting engine can act on.

What counts as a disruption — and can the threshold be tuned?

The default severity threshold is fifteen percent of the shipment’s estimated transit time. Below that the pipeline logs the signal without alerting; above it an in-app alert fires and a reroute recommendation is queued. The threshold is configurable per fleet during onboarding, so a fast-parcel fleet and a heavy-haul fleet can run different baselines.

How autonomous is the response, and what stays human?

Detection, scoring, and recommendation generation happen without a human in the loop. The approval step is the deliberate human check — the planner accepts the reroute from the dashboard or overrides it with a reason. The platform never auto-executes carrier book-and-go without the team’s sign-off.

What does pricing look like for a team adopting this?

Two tiers, both billed monthly through Stripe: a Pilot for live-lane validation and Pro for production rollout with priority support. Cancel any time from the Stripe billing portal — no lock-in. Custom rollouts (multi-region fleets, dedicated ops contact) are scoped on request.

What does ongoing support look like once the pipeline is live?

Pilot customers reach the team by email during business hours, with first response inside one business day. Pro customers get a named technical contact and priority support. Both tiers include onboarding tuning of the threshold and a quarterly review of the fleet’s disruption patterns.

Freight disruption response automation, from alert to approved reroute

Sensing

The Sensing stream watches every shipment in flight — GPS pings every few minutes, carrier API status events, and active weather alerts that overlap the lane’s bounding box. Each signal is scored against the shipment’s estimated transit time so that only events crossing the configured fifteen percent severity threshold generate an alert. This collapses three noisy feeds into one ranked event the reroute engine can act on without a dispatcher asking for it.

Negotiating

The Negotiating step is where freight disruption response automation earns its name. A lane rate is requested for the top three candidate paths to the destination, scored on cost, transit time, and confidence, and presented to the on-call planner as a single recommendation rather than a pile of options. The planner either accepts the recommendation in one click or overrides it with a reason that trains the next one — closing the loop between detection and approval on the same lane.

Self-healing

The Self-healing stage is what makes every accepted reroute a quieter one on the next disruption. Carrier reliability scores, corridor weather baselines, and per-lane confidence thresholds update in the background as recommendations get approved or overridden. The pipeline is not auto-dispatching without sign-off — it is steadily narrowing its own noise floor so the next reroute recommendation arrives with a tighter reasoning chain.

See it on a real lane

Both pricing tiers run the same autonomous disruption pipeline on your real fleet — pick the depth and keep the engine.

Start a Pilot — 14 days free See a real outcome story

Freight disruption response automation, from alert to approved reroute

Sensing

Negotiating

Self-healing

See it on a real lane

Related reading

Frequently asked questions