Unified dispatch & route planning

Stop Planning. Start Delivering.

The first unified logistics workspace combining AI-driven route optimisation, live execution and eCMR compliance on a single platform.

See pricing
Illustration of a drag-and-drop stop list beside a map with numbered pins connected by an optimised dashed route and a delivery van
Planners drag stops into sequence and the optimiser rebuilds the route, drive time and ETAs instantly.

One engine instead of three disconnected tools

Mapping software, manifest spreadsheets and a driver chat group cannot agree on the truth. Depot2Door runs intake, planning and execution against the same record.

Tab 1

Order intake & manifest ingestion

Orders arrive by spreadsheet import, API or manual entry and land in a date-grouped queue with fleet KPIs — no separate manifest tool, no re-keying.

Tab 2

Planner & optimisation engine

Drag stops between vehicle lanes, optimise a sequence, balance the fleet, and watch distance, ETAs, load and legal-shift warnings recalculate on every move.

Tab 3

Live operations & eCMR tracking

The published plan becomes the live board: stop status, delays, proof of delivery and a structured consignment log you can export per route.

A plan built in Tab 2 is the same object the driver opens, the same object the eCMR log exports and the same object the audit trail versions. No exports, no copy-paste, no "which version are you looking at?".

Tab 2 — planner with drag-and-drop vehicle lanes, live map rendering and real-time drive, shift and load metrics.

Advanced planning capabilities

Everything a European planner needs between the order landing and the wheels turning.

Staged sandbox planning

Test, reorder and simulate route variations in a local draft state. Save named scenarios side by side and reset to the live plan in one click — drivers in the field see nothing until you say so.

Smart fleet load balancing

Distribute unassigned stops across vehicle lanes automatically while respecting box and rail capacity limits, shift length and each driver's remaining hours.

Built-in compliance & rest rules

Driving-hour ceilings, mandatory breaks and a configurable midday pause (12:00–14:00) are scheduled into the plan, not bolted on afterwards.

One-click fleet deployment

Publish verified routes instantly — per-route selection, an optional note to the driver, exactly one synchronized update alert, and an acknowledgement handshake back from the device.

Publish only when the route is locked in

A sandbox your drivers never feel

Dispatch is iterative: you try a sequence, move a customer, balance the load and try again. Depot2Door keeps all of that in a private draft, then bundles the final result into a single, clean deployment — so drivers get one clear update instead of a stream of half-finished changes.

  • Named scenario variations saved per planning day
  • Before-and-after diff of moved, re-sequenced and re-timed stops
  • Choose which routes to publish and whether to alert the driver
  • Optional note delivered alongside the driver's update alert
  • Acknowledgement handshake logged for every published route

Route planning FAQ

Does publishing a route disrupt my drivers while I'm editing?

No. Dispatchers work in a private draft workspace — every drag, re-sequence and optimisation run stays local. Drivers only receive an update when you press Publish to fleet, and even then you choose which routes go out and whether an alert is sent.

Does it account for mandatory rest breaks?

Yes. The engine schedules around driving-hour limits, mandatory breaks and your tenant's custom pause window (for example 12:00–14:00), and flags any lane whose shift length would break the rules before you publish.

How does the planner decide the stop order?

It sequences stops with a distance-and-time-window optimiser (2-opt improvement passes), then re-times the whole lane so every ETA reflects travel time, service time and inserted breaks.

Can I test several plans for the same day?

Save as many named variations as you need, switch between them instantly and reset to the live plan at any time. Nothing leaves the sandbox until you publish.

What happens on the driver's phone after publishing?

The driver app raises a single route-update alert with the new sequence and ETAs, and returns an acknowledgement handshake so dispatch can prove the change was received.

Want the dispatcher's full control room? Explore TMS & fleet management .