Smart Route Optimiser

Client

DLD

Problem

The problem: Manually planning routes across hundreds of addresses is slow and error-prone. Auto-optimisers sometimes skip side roads, cul-de-sacs, or estate branches — leaving obvious local sequencing errors on the map. Their envelope-stuffing machine needs to know whether each address gets a "customer" or "non-customer" insert — but that same address file is also used to print envelope labels, so words like "Customer/Non-Customer" must NOT appear on printed envelopes.

What we built

The solution (this app — "AllRoute"): Upload & map a spreadsheet of addresses (auto-detects columns like address lines, Eircode, Insert Type / Customer Status). Optimise into numbered routes with a configurable max stops per route, optional depot start/end, and address-aware sequencing (uses road/locality tokens, not just coordinates). Review on a map with numbered markers and route lines, plus a side list of stops. Manually fix local ordering directly on the map without re-running the optimiser or moving coordinates: Drag/reorder stops "Insert road/branch here" — pick a stop, detect a nearby connected branch (same road tokens + proximity), and splice it in after an anchor stop; existing stops shift down and renumber automatically. Move stops between routes, reset a route to the original optimised order, or recalculate a single route. Save/cancel edits; saved edits mark exports as needing rebuild. Download files that reflect the final saved order: SmartRoutes export (.xlsx / .csv) for the routing platform. Label Print File (.xlsx) — addresses only, safe for envelope printing. Machine Fulfilment File (.xlsx and .csv) — addresses + Insert Type column, for the envelope-stuffing machine.