Delivery Route Optimization for ERPNext

Key Features

Extends the native ERPNext `Delivery Trip` doctype and its `stops` child table rather than replacing it, so existing Delivery Note linkage and trip status stay intact

Whitelisted server method calls Google Maps Routes/Directions API or Mapbox Optimization API to compute the optimal stop order and writes it back to the trip

Automatic geocoding of each stop from its linked `Address` doctype, with cached lat/long custom fields to avoid repeat API calls and control cost

Time-window constraints per stop (earliest/latest delivery) captured as custom fields and passed to the solver so sequences honor customer availability

Vehicle capacity and per-stop load constraints so a route stops adding drops when the van is full and splits across trips

Per-stop service-duration handling so ETAs account for time spent at each address, not just driving time

Computed per-stop ETA and distance-from-previous persisted on the child row, recalculated automatically whenever the route changes

`hooks.py` doc events (`validate`/`on_update`) plus explicit client-script buttons — Optimize Route, Re-sequence, Recompute ETAs — for deterministic, auditable optimization

Scheduler event for automated per-stop customer arrival-window notifications via Email, SMS, or WhatsApp through ERPNext's notification channels

Mobile-friendly driver route view (role-scoped Frappe portal page) listing stops in order with one-tap deep links to Google Maps or Waze for turn-by-turn navigation

Driver stop-completion updates the Delivery Trip status back in ERPNext via the REST API / whitelisted endpoints, keeping the office view live

Dedicated `Delivery Driver` role profile and permission rules so drivers see only their own assigned trips and no other operational data

Single-doctype encrypted settings for provider API keys, default region, distance units, and optimization mode — no secrets in source code

Built and tested against Frappe/ERPNext v15 and v16, packaged as a standard installable Frappe app compatible with your bench and CI

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2-4 weeks 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.

What you get

Installable source code for the Frappe app built to your confirmed scope and ERPNext version (v15 or v16)

Installation and configuration on your bench, including routing-provider key setup and constraint/notification configuration

Technical documentation: doctype/custom-field reference, hooks and whitelisted methods, and API-key/settings guide

User guide plus a live training session for dispatchers and drivers

UAT on a staging bench against your real Delivery Trips, with a documented cutover and rollback plan

Post-go-live support window for bug fixes and adjustments

Full git repository handover with commit history so your team owns and can extend the code

Handover notes covering upgrade compatibility and how to re-run optimization for future Frappe/ERPNext versions

Who this is for

Last-mile delivery operations manager

Runs daily dispatch on ERPNext Delivery Trips and needs stops auto-sequenced with realistic ETAs so dispatchers stop hand-planning routes and drivers stop backtracking.

Fleet dispatcher / route planner

Assigns drops to vehicles and drivers each morning and needs time-window and capacity constraints respected automatically so promised delivery windows are actually met.

ERPNext administrator / systems owner

Owns the ERPNext instance and wants a clean, version-safe Frappe app with proper roles, encrypted keys, and a git repo they can maintain — not a fragile customization glued into core.

Customer experience / support lead

Fields 'where is my order' calls and needs automated per-stop arrival-window notifications so customers get an ETA without a support agent looking it up.

How Delivery Route Optimization for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor
Route optimization engine	Google/Mapbox optimization wired into Delivery Trip	Whatever you build yourself	Basic distance sort, often generic
Time-window & capacity constraints	Modeled as custom fields, passed to solver	Possible but you design and test it	Rarely supported or fixed rules
Per-stop ETA & notifications	Computed ETAs + Email/SMS/WhatsApp windows	Build the calc and channels yourself	Sometimes ETA, notifications vary
Driver navigation view	Role-scoped mobile view, Maps/Waze deep links	You build the portal and links	May lack driver-facing view
ERPNext integration depth	Extends core Delivery Trip via hooks/clients scripts	Depends on your team's Frappe skill	Often bolt-on, weaker linkage
Version fit (v15/v16)	Built and tested to your exact version	You own version compatibility	Whatever the vendor last released
Ownership & code handover	Full git repo handover, you can extend it	You own it fully	Usually closed source
Support & scoping	Scoping call, UAT, post-go-live support window	Your team supports it	Ticket queue, generic responses

Frequently Asked Questions about Delivery Route Optimization for ERPNext

Is this a ready-to-download app from the Frappe marketplace?

No. This is build-to-order. ECOSIRE builds, installs, and supports the app for your specific ERPNext instance, routing provider, and constraint rules. There is no instant download — we scope it with you first, then deliver a Frappe app tailored to how your delivery operation actually runs.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. The exact timeline depends on the number of constraints (time windows, capacity, service durations), the notification channels you want, and any integrations. We confirm scope on a short call, then build, UAT on staging, and cut over.

How do updates and support work after go-live?

Every build includes a post-go-live support window for bug fixes and adjustments, and you receive the full git repository so your team can maintain and extend the code. Because it is a standard Frappe app, it upgrades with your bench; we can also quote ongoing support or upgrades to future ERPNext versions separately.

Which routing provider does it use?

We support Google Maps (Routes/Directions API) or Mapbox (Optimization API), chosen on the scoping call based on your region, existing accounts, and cost preference. You supply your own provider API key, which is stored encrypted in a settings doctype — never hard-coded — so billing and quotas stay under your control.

Which versions of ERPNext does it work with?

It is built and tested against Frappe/ERPNext v15 and v16. We confirm your exact version during scoping and package the app to match your bench, so it installs cleanly via `bench install-app` and passes your CI.

Will this break our existing Delivery Trips or Delivery Notes?

No. The app extends the native `Delivery Trip` doctype and its stops child table using custom fields, hooks, and client scripts — it does not replace core doctypes. Your existing Delivery Note linkage, trip statuses, and reports keep working, and we validate everything on a staging bench before cutover with a rollback plan.

Can drivers use it on their phones for navigation?

Yes. Drivers open a mobile-friendly, role-scoped route view that lists their assigned stops in optimized order and deep-links each address into Google Maps or Waze for turn-by-turn navigation. They can mark stops delivered, which updates the Delivery Trip in ERPNext in real time.