Route planning software · SolutionsERP

Route planning software from CRM addresses —
not Excel round-robin.

Delivery route planner for UK field teams: select Address or Lead records in CRM, run Create Route, and send an optimised KML to engineers — planned visits instead of Friday-morning guesswork.

Field route optimisation runs on SolutionsInc servers — customer postcodes stay in your ERP, not a commercial maps API. Ideal for B2B service, sales rounds, and multi-stop deliveries.

See pricing

Delivery route planner — optimised stops on SolutionsERP map

Route cycleSolutionsERP

Select

Route

Optimise

KML

Field

Tick Address or Lead rows in CRM — postcodes and titles collected for routing.

Create Route

Route planning software — Create Route from CRM.

From the Address list (pincode) or Lead list (custom_post_code / Route Postcode), the dispatcher selects at least two records and chooses Actions → Create Route.

Source

Address: Customer and supplier sites already in ERP — ideal for maintenance visits and deliveries.

Optional Route description (route_note) — e.g. “B2B service — North region — 12 May”. Backend trigger_route_generation collects postcodes and titles, checks read permissions per record, and sends the payload to automation.

Business benefit: Routes built from live ERP data — no retyping postcodes from Maintenance Schedule exports.

Route planning software — team planning delivery route from CRM

Field route optimisation — postcode-based route strategy

Strategies

Field route optimisation — depot-aware strategies.

In SolutionsInc Route Settings set the default route_strategy sent with every optimisation — not just “order of selection”.

Strategy

from_home: Start at your configured base address (home or company depot in Route Settings) and finish at the furthest stop from that point.

far_first_home_last is the reverse: begin at the furthest postcode on the route and end back at your home or company address. legacy_first_stop keeps the first selected row as the start point — for teams used to manual ordering.

Business benefit: Fewer wasted miles and fewer SLA breaches caused by zig-zag routing.

CRM sync

Delivery route planner — postcodes stay in sync.

The app extends CRM with custom_post_code on Lead (install/migrate). sync_lead_postcodes_from_address copies pincode from linked Address via Dynamic Link on every save.

Fetch All Postcodes on the Lead list bulk-updates from related addresses. Dispatchers plan a day from Leads (prospecting + service) or Addresses (Customer delivery visits) with consistent postcodes — no manual copy-paste.

Business benefit: Field sales and service share one postcode source of truth for routing.

Delivery route planner — customer addresses on optimised map

Logic mascot recommending Customer Service

“Maintenance Schedule tells you which visits are due — Route Planner sorts the driving order for that day. Pair both in Customer Service for planned rounds, not fire-fighting.”

Explore Customer Service

Field route optimisation — KML route file emailed to technician

KML delivery

Route planning software sends KML to the field.

After optimisation (via n8n in your architecture), the KML file arrives at target_email or the requesting user’s inbox — with source_name, route_note, and stop list in the payload.

Engineers import into Organic Maps, OsmAnd, or Google Maps — offline-capable navigation without logging into ERPNext in the van. Remove stops after each visit; log work done back in Maintenance Visit at the office.

Business benefit: Lightweight field workflow — email in, drive out, ERP updated when back at base.

Privacy

Delivery route planner — no Google Maps API.

Route optimisation runs on SolutionsInc servers — our infrastructure, not a third-party map provider. Customer addresses (Lead, Customer, Address) stay in your ERP; postcodes are used for routing without sending client data to services such as Google Maps or other commercial map APIs.

No per-query fees to Big Tech map vendors — scale many daily routes for many technicians within the SolutionsInc environment. Built for ERPNext 16 with a dedicated Route Planner workspace and doc_events hooks on Address.

Business benefit: GDPR-friendly B2B routing — client data in your ERP, calculations on SolutionsInc, zero dependency on external map subscriptions.