All solutions

Know which shipments a disruption actually touches

Record disruptions by type and severity, automatically match the shipments they affect, alert the owners, and capture the alternative routing decision.

Auto-matched
affected shipments per disruption
8 types
weather, congestion, strike, geopolitical and more
Alerts
to the owners of exposed shipments

Risk & Disruption Monitoring

When a port congests or a route is disrupted, the question is never "is there a problem" - it is "which of my shipments are exposed, and what do we do". QueChains records each disruption with its type, severity, location and window, then matches your active shipments moving through the affected area and lists them.

Affected-shipment owners are alerted through your notification rules, and the response - reroute, expedite, hold - is captured against the disruption so the decision and its rationale are not lost.

What's included

01
Disruption register
Log disruptions with type, severity, location, description, start and expected resolution.
02
Affected-shipment matching
Active shipments moving through the disruption's country or lane are identified and attached automatically.
03
Owner alerts
The people responsible for exposed shipments are notified through your alert channels.
04
Alternative routing
Capture the alternative route, added cost and added time considered for the disruption.
05
Severity-driven triage
Critical and high-severity disruptions are surfaced first so attention goes where it matters.
06
Tenant-scoped
Disruptions and their affected shipments are isolated per organisation - no cross-tenant leakage.

From setup to daily use

1
Record the disruption
Enter the event: type, severity, where and when. This can be manual or driven by an integration.
2
See exposure
QueChains lists your active shipments passing through the affected area, scoped to your organisation only.
3
Alert and decide
Shipment owners are notified; the team decides to reroute, expedite or hold.
4
Capture the response
The alternative routing and its cost/time impact are recorded against the disruption.

Why teams use it

Targeted response
Effort goes to the shipments actually exposed, not a blanket panic.
Faster decisions
Exposure and owners are known immediately, so the reroute conversation starts sooner.
Institutional memory
What you did last time this port congested is on record.
Clean tenant isolation
A disruption in your account never exposes another organisation's shipments.
  • Control towers and supply chain risk teams
  • Operations managers responsible for on-time delivery
  • Forwarders keeping clients informed during disruptions
  • Businesses with concentrated exposure to specific ports or lanes

Common questions

How does it know which shipments are affected?

It matches your active shipments whose origin or destination country falls within the disruption's location, scoped strictly to your organisation. The matched shipments are attached to the disruption record.

Can disruptions come from an external feed?

The disruption register is API-driven, so a weather or geopolitical risk feed can create records automatically. Manual entry is also supported.

Does it suggest alternative routes?

It captures the alternative routing you decide on, with added cost and time. Automated route optimisation is not in scope.

See Risk & Disruption Monitoring in your operation

Start free, or talk to our team about a pilot for your logistics operation.