The Challenge
Cargopath Logistics was operating a fleet of 340 vehicles across three states with a patchwork of six different tools — a route planner, a separate GPS tracker, WhatsApp groups for driver communication, Excel for proof-of-delivery logging, a third-party ETA tool and a manual dispatch board. None of these systems talked to each other. Dispatchers were spending four to five hours per day manually reconciling data between systems and fielding calls from drivers who had received conflicting instructions. The result was predictable: fuel waste from suboptimal routes, missed delivery windows, and a dispatcher team that was burning out. The operations director calculated that the tool fragmentation was costing the business approximately ₹18 lakh per month in avoidable fuel, overtime and failed-delivery penalties.
Our Approach
We built a unified dispatch intelligence platform with three interconnected surfaces: a web dispatcher console, an Android driver app and a customer-facing ETA tracking link. The route optimisation engine ingested live traffic data from the Google Maps Platform, vehicle load data from the ERP integration and historical delivery performance by route — producing optimised multi-stop route sequences that saved an average of 2.3 hours of drive time per vehicle per day. The geo-fencing system automatically triggered status updates (departed, arrived, delivered) as drivers crossed digital boundaries, eliminating the need for manual check-ins.
How We Built It
Dispatcher and driver research (weeks 1–2)
We shadowed dispatchers for three days and rode along on two delivery routes to understand the actual workflow before designing anything. The research revealed that 60% of dispatcher calls came from drivers asking for the next stop — a problem the app solved by making the route self-evident.
Web dispatcher console (weeks 3–9)
Built the real-time dispatch map, route assignment workflow, live vehicle tracking and the historical analytics dashboard. Load tested against 340 simultaneous vehicle location updates to verify the WebSocket architecture could handle peak fleet size.
Android driver app (weeks 8–14)
Flutter-based app with offline-first architecture — routes and customer details cached locally so drivers could continue working in warehouse dead zones. Proof-of-delivery capture with photo, signature and geo-tagged timestamp, synced to the console the moment connectivity returned.
ERP integration and rollout (weeks 15–18)
Integrated with Cargopath's existing Tally-based ERP for order import and delivery confirmation. Rolled out to 10 pilot vehicles, then 100, then the full fleet — with dispatcher training sessions at each stage.
