Optimize Delivery Routes. Reduce Fuel Costs. Deliver Faster.

From the Odoo apps grid, open Route Optimization (the compass/map icon). It sits beside the rest of the Delivro suite: Driver App, Fleet, and Field Service. If you open Route Planning instead, that's the old module; close it.

Apps grid, Route Optimization (top row) alongside Driver App and Fleet. (The amber top banner is just a license-renewal reminder on this staging server: the database is active.)

Every stop needs coordinates. Open the customer contact, set a valid Address, and confirm the map pin lands correctly. No coordinates = the job is dropped with reason bad_coords.

Contact with a real map pin: the optimizer reads this contact's latitude/longitude.

The outgoing delivery must be in the ready state with its scheduled date set to today. Orders dated before/after today, or with no date, are excluded.

At least one fleet. vehicle in Fleet state registered, with a start warehouse (or its own coordinates) and a Driver assigned.

Fleet vehicle with a driver set and state-registered.

In the app, Delivery Orders › Jobs is the work list. Every routable job is one row, grouped by Vehicle (filtered to Today by default: remove that filter to see other days). Pickings are pulled in automatically by a background job every 2 min.

A real route in the Jobs list — vehicle Volkswagen/Golf 8 (AUD-001), driver Beth Evans, 6 stops sequenced 1→6 with per-stop Status, Customer, Type, ETA (08:00→09:25), Drive and Dist; the group totals 86.95 min / 85.02 km.

The Jobs columns (Vehicle, Driver, #, Status, Customer, Type, ETA, Drive, Dist, Reason) with the default Today filter: a fresh day starts empty until you optimize.

The Optimize control lives on the Map Views screen, in the Summary / Filters panel: Optimize, Force Re-Optimize, and Confirm & Notify. Press Optimize: the plugin gathers today's ready deliveries, planned field-service tasks, and registered vehicles, sends them to the routing engine, and writes back one route. Unified Step per stop (vehicle, sequence, ETA, drive time, distance).

The Optimize / Force Re-Optimize / Confirm & Notify buttons in the Map Views panel, with the usage-credit counter and the Total Distance / Travel Time / Vehicles / Jobs summary tiles.

The Jobs list reloads: each vehicle group is a complete route in stop order, with ETA / drive time/distance per stop (see step 4). A banner confirms, "Unified route optimization complete. " Jobs that couldn't be placed stay in the None group with a reason.

A completed plan: jobs assigned to a vehicle and sequenced with ETAs.

The Map Views menu shows the whole plan on a map: each vehicle's route as a colored polyline, live stop positions, and summary tiles (distance, travel time, vehicles, and jobs). It's also where the Optimize controls live (step 5).

Map Views: the top menu (Jobs · Map Views · Reporting · Configuration), the summary tiles, the Optimize panel, and the map.

Reporting holds Delivery Orders, Field Service, Route Plan, and Route History. The Route Plan lists every stop (Day, Route, Seq, Customer, Stop, Type, Unassigned, Reason); Route History is a frozen snapshot of each optimize run.

Reporting › Route Plan: the same VW Golf route: 6 stops with Day/ETA, Seq, Customer, Stop (customer + WH/OUT reference), and Type.

Settings holds the plugin's config; Configuration › Route Skills defines vehicle skills. The Settings blocks are Route Polyline & Cost Control (polyline provider + optimize cache window) and Map View Tuning (map poll intervals + collapse threshold).

Route Polyline & Cost Control: Polyline Provider (VROOM free / Google Directions paid) and the No-Change Optimize Skip Window (60 min).

Map View Tuning: live-position poll (10,000 ms), partner-marker poll (5,000 ms), timeline collapse threshold (15).