A complete TMS. Everything between the order and the invoice.
Plan routes, optimise them, dispatch them to drivers on the NexGo app, track them live and invoice them. One product, on your own database, with no per-driver fees.
From order to invoice, in one loop
-
Capture demand
Jobs, shipments and recurring stops, entered by hand, imported from CSV, Excel or a database extract, or pushed in over the API. Each task lands on exactly one stop.
-
Optimise
The optimiser behind Optimization as a Service builds the routes: time windows, capacities, availability slots and depots, on real road distances, travel time and cost minimised. If the plan changes after submission, the drift is flagged before a stale solution can apply.
-
Dispatch
Confirmed routes reach drivers at once, in the NexGo app or on the driver portal. Changes made mid-route propagate live to both.
-
Execute
Per-stop arrival, operation and departure times, GPS positions, incidents and messages with dispatch, all threaded on the route.
-
Bill and analyse
Mark completed jobs billable, generate invoices in one batch, and read the dashboards on what actually happened.
Six surfaces, one set of records
Nothing is re-keyed between them. Everything ships in every quote.
Planner
The dispatcher's workspace: plans, routes, stops, jobs and shipments in list, kanban, calendar, Gantt and map views. Build routes, run the optimiser, confirm, dispatch.
- Views
- list, kanban, calendar, Gantt, map
- States
- Draft, Planned, Ongoing, Done, Confirmed
- Templates
- plans, routes, jobs
NexGo
A Progressive Web App with signed Android packaging. Live map, per-stop operations, messaging with dispatch, in-app manual. Writes queue on the phone and replay when the signal returns.
- Offline
- queued writes, replayed
- Languages
- EN FR NL PL
- Install
- browser, or Android TWA
The NexGo route screen: route R-02 ongoing, offline with three actions queued, the next stop is Wavre with a window of 08:00 to 09:00 and an ETA of 08:12.
Fleet
Vehicles, trailers and drivers in the same platform that dispatches them. Every coupling, odometer reading and driver assignment is logged and dated, with load-utilisation alerts, a Documents workspace per asset, a link to the HR employee, and driver attendance on a Gantt beside the routes it belongs to.
- Capacity
- volume and mass alerts
- History
- odometer, coupling, assignment
- Reports
- roster, odometer, trailer quantity
Live
Pair a tracking device by QR code and watch positions on the map, with every asset's trail kept as searchable history. Route progress maps reload on their own.
- Pairing
- QR code, one-time token
- Telemetry
- battery, storage, network, GPS accuracy
- Maps
- one route, or the whole plan
Portals
Drivers open their route on their own phone, in a browser with nothing to install, hours before the day starts. Locations see upcoming, ongoing and past visits with expected and actual times. Messaging with dispatch runs on the same portal.
- Driver portal
- routes by state
- Location portal
- visits, expected and actual
- Accounts
- no per-seat fee
Reporting and billing
Spreadsheet dashboards on routes, stops, fleet and the optimiser, graph reports on odometer and trailer use, and every list pivots and groups like any other Odoo model. Mark completed jobs billable and generate invoices in one batch from a wizard.
- Route KPIs
- completion, distance variance, incidents
- Stop KPIs
- on-time rate, wait time
- Billing
- batch, with date filters
On the record
- Route optimisation
- included, no bolt-on tier
- Driver and user seats
- unlimited, no per-driver fees
- Languages
- English, French, Dutch (Belgium), Polish
- Hosting
- EU, on Odoo's cloud platform, managed by NexOR
- Decisions
- the solver proposes, a dispatcher confirms
- Quote
- one number, usually within two business days
- Trial
- two to four weeks on your own fleet
- Go-live
- usually within the same month
- Data import
- CSV, Excel or a database extract
- Backups
- daily, point-in-time restore, on the platform
Native Odoo modules, one database
NexOR is a set of Odoo modules. They install into your Odoo and run beside your CRM, HR, accounting and inventory, on one database. Not five tools wired together by hope.
- Hosting
- EU, on Odoo's cloud platform
- Data
- yours, exportable
- Backups
- daily, point-in-time restore
-
- Routing
- Plans, routes and stops
-
- Optimisation
- Routes built to your constraints
-
- Transport Fleet
- Vehicles, trailers and drivers
-
- NexGo
- The driver app, offline first
-
- Driver portal
- A driver's route in a browser
-
- Location portal
- What arrives, and when it did
-
- Solve
- Any optimisation problem, over HTTP
-
- Helpdesk
- Tickets, SLAs, and the thread with the customer
-
- Planning
- Shifts allocated and published
-
- Contacts
- One customer record, used everywhere
-
- Discuss
- Messages threaded on the record
-
- Time Off
- Leave requested, approved, and in the plan
-
- Barcode
- Scan the move instead of typing it
-
- Purchase
- Requests for quotation to supplier bills
-
- Manufacturing
- Work orders against a bill of materials
-
- Maintenance
- Requests and preventive schedules per asset
-
- Timesheets
- Hours against the task that used them
-
- CRM
- Leads through to the won deal
-
- Accounting
- Invoices, bills, and the ledger under them
-
- Dashboards
- Spreadsheets over live data
-
- Inventory
- Stock, moves, and where each unit is
-
- Calendar
- Meetings, deadlines, shared diaries
-
- Attendances
- Clocked in, clocked out
-
- Fleet
- Vehicles, contracts, running costs
-
- Project
- Tasks, stages, and who has them
-
- Recruitment
- Applications through to the signed contract
-
- Payroll
- Payslips from the hours that earned them
-
- Sales
- Quotations, orders, and what shipped
-
- Employees
- The people record the rest points at
-
- Website
- Pages, forms, and the customer portal
-
- AI
- Drafts, summaries and extraction, on the record
-
- ESG
- The numbers a sustainability report needs
-
- Documents
- Files filed against their record
What Odoo is, and what one platform buys you
A business suite: one database, one interface, and an application for each part of a company. Around eighty ship with it, the core is open source, and it is Belgian, like us.
One record, not five copies
The customer in the CRM is the customer on the invoice and the customer at the stop. Nothing is synced, because there is nothing to sync.
One history, on the record itself
Messages, files and every change sit on the thing they happened to. You read the whole story in one place.
Nothing wired between the apps
No nightly export, no CSV bridge, no middleware to keep alive. One app reads another's tables in the same transaction.
Switch an app on when you need it
Start with transport. Add accounting, HR or maintenance later, on the same database, with no migration and no second login.
Inside the platform, not beside it
NexOR installs as Odoo apps, not as a connector. A route points at the same customer record as the invoice, with no mapping table between them.
Milk doesn't wait for a planner. NexOR builds the day's route each morning, pushes it to the drivers, and tells us where every truck is in real time. The history shows us what to fix the next time round. When we ask the team for something, they're on the phone the same day.
Kristof LambrechtsCEO, Transport Lambrechts NV
Out on the road
Have you spotted us on the back of our partners' trucks?
See it on your own stops
Bring a day of jobs. We build the first plan on your own stops, then walk through it with your dispatcher.