Last-mile teams running ERPNext create Delivery Trips, attach Delivery Notes, and hand drivers a list of stops — but the native Delivery Trip doctype leaves the hard part to humans. Stops sit in whatever order they were added, ETAs are guesswork, and dispatchers eyeball a map to decide who drives where. As drop counts climb past a dozen per vehicle, that manual sequencing burns dispatcher time, wastes fuel on backtracking, and gives customers no reliable arrival window. ERPNext core has no optimization engine, no time-window or capacity constraints, and no driver-facing navigation — it tracks the trip, it does not plan it.

ECOSIRE builds a proper Frappe app (its own module, installed via bench get-app and bench install-app) that extends the standard Delivery Trip rather than replacing it. On save or on demand, a whitelisted server method calls a routing provider — Google Maps Directions/Routes API or Mapbox Optimization API, chosen per your account and region — geocodes each stop from the linked Address, and writes the optimized order back into the Delivery Trip stops child table. We wire this through hooks.py doc events (validate/on_update) plus explicit "Optimize Route" and "Re-sequence" buttons added by a client script, so optimization is deterministic and auditable rather than a black box. Time windows, per-stop service duration, and vehicle capacity are captured as custom fields on the stop and vehicle records and passed to the solver as constraints, so the sequence respects "deliver before noon" and "van is full" instead of just shortest distance.

Each stop gets a computed ETA and distance-from-previous, persisted on the child row and recalculated when the route changes. A scheduler event (or manual trigger) can push per-stop notifications — Email/SMS/WhatsApp via ERPNext's notification channels — with the customer's estimated arrival window. Drivers open a mobile-friendly route view (a Frappe web page / portal view scoped by role) that shows their stops in order, deep-links each address into Google Maps or Waze for turn-by-turn navigation, and lets them mark stops delivered — which updates the Delivery Trip status back in ERPNext through the REST API. A dedicated "Delivery Driver" role profile and permission rules ensure drivers see only their assigned trips, and all provider keys live in a single-doctype settings record, encrypted, never in code.

This is build-to-order: ECOSIRE builds, installs, and supports it — it is not an instant download from the Frappe marketplace. It starts with a short scoping call to confirm your routing provider, constraint rules, notification channels, and Frappe/ERPNext version (we support v15 and v16). We then deliver the app to a staging bench for UAT, run it against your real Delivery Trips, and cut over with a rollback plan. Typical delivery is one working week from confirmed scope depending on the number of constraints and integrations, and you receive the full git repository, install/config docs, and a post-go-live support window.