Logistics and Mobility

RouteWise, Dispatch control and exception handling

RouteWise built a dispatch platform that prioritizes exceptions, supports dispatcher overrides, and keeps drivers productive when connectivity is unreliable.

L0Edge / CDN
L1API gateway
L2Tenant runtime
L3Data plane
L4Observability

01Challenge

What was in the way.

Legacy dispatch treated every alert equally. Drivers lost proof-of-delivery captures offline, and customers received ETAs that dispatch could not explain when routes changed mid-shift.

02Strategy

How we chose to proceed.

Codeaxes designed an event-driven routing core with a dispatcher-first UI, mobile apps with offline queues, and notification templates tied to geofence and scan events.

03Solution

What shipped.

A control tower surfacing delayed stops and capacity conflicts first, plus driver mobile flows that sync POD photos and signatures when back online.

  • Exception-prioritized dispatch board with override audit trail
  • Dynamic re-routing triggers based on configurable delay thresholds
  • Driver app with offline action queue and barcode scanning
  • Customer notification templates tied to milestone events
  • Partner API for shipper visibility and document retrieval
  • Replay tooling to simulate routing rule changes

04Stack

Technologies on the critical path.

  • TypeScript
  • Go
  • PostgreSQL
  • Kafka
  • React
  • Mapbox
  • GCP
  • Kubernetes

05Outcomes

Operating change the work targeted.

Dispatcher focus

Exceptions surfaced before routine stop noise

Field capture

POD sync after connectivity gaps without re-entry

Customer updates

Notifications matched to operational timestamps

“Our dispatchers work exceptions first now, and drivers trust the app when the signal drops between stops.”

Marcus Webb, COO, RouteWise Mobility

If this resembles your constraint, start a project.