Skip to Content

NexOR talks to your stack

The transport platform plugs into maps, EDI, telematics, accounting, HR and documents. The optimisation service is a REST API you can call from anything that sends JSON. Both fit the systems you already run.

What connects, and how

Everything below ships in the product unless the last column says otherwise.

Category Systems How it connects Status
Routing and maps Mapbox, OSRM, OpenRouteService, OpenWeatherMap configured in Settings shipped
Odoo apps Contacts, Accounting, Employees, Attendances, Documents, Discuss, Spreadsheet, Portal, Inventory, Fleet, Maintenance, Time Off, Planning native, one database shipped
Devices NexGo as a tracker, QR-paired GPS devices, Android TWA built in shipped
Optimization as a Service REST with signed webhooks, published JSON Schemas HTTPS from anything that sends JSON shipped
Data exchange customer and partner feeds scoped per customer on request

Open standards for distances, routes and tiles

Mapbox

Tiles, routing, and turn-by-turn directions. Configurable from Settings.

OSRM and OpenRouteService

Self-host or use a managed instance. Used for distances and optimisation fallback.

OpenWeatherMap

Weather widget on the NexGo driver dashboard. Configurable API key.

Built on Odoo. Already integrated with its apps.

Because NexOR is a set of Odoo modules, it shares one customer, one fleet, and one chatter with every other Odoo app you install.

Contacts

Customers, locations and drivers are ordinary Odoo contacts. One record, wherever you open it.

Accounting

Job-based invoices land on the accounting journal you pick. Customer balances stay in sync.

Employees and Attendances

Drivers link to HR employees. Confirmed routes create attendance entries on their own.

Documents

Per-asset workspaces for vehicles, trailers, drivers, customers, and locations.

Discuss

Driver and dispatch chat runs on Odoo channels. One Inbox, no third-party messenger.

Spreadsheet

Routing, fleet, and optimisation dashboards are live spreadsheets. Pivot and export.

Portal

Drivers, customers, and locations log into the same Odoo portal as everywhere else.

Inventory

Stock moves behind a shipment, so what leaves the warehouse and what leaves on the route are one line.

Fleet

Odoo's fleet costs and contracts beside the vehicles the planner is assigning.

Maintenance

Service plans and garage visits on the vehicle the routes are built against.

Time Off

Driver leave read before the planner hands anyone a route.

Planning

Shifts lined up with the day's routes instead of kept beside them.

Track the assets you already have

NexGo as a tracker

Every driver's NexGo phone is also a tracker. Battery, signal, and GPS quality monitored.

Bring your own tracker

Pair existing GPS devices by QR code with one-time auth tokens.

Android TWA

Distribute NexGo as a signed Android app, configurable from Settings.

Call the optimiser from anything that speaks JSON

One versioned REST API. Send one request, then take the answer from a signed webhook or the event stream.

REST and webhooks

A versioned HTTP API with signed, retrying webhooks and a server-sent event stream for when you cannot receive them.

Published JSON Schemas

Generated from the validators, so your client can validate before it sends and never drifts.

jumpy, the Python SDK

Write the model in Python and read the solution back as objects. The HTTP API is underneath, so anything the SDK does, your own client can do.

Feeds to 3PLs, carriers and customer systems

Nothing ships as a ready-made connector here. Each feed is a custom integration type, scoped and quoted with you before it is built.

  • Custom integration types scoped on request
  • Its own credentials, held per integration
  • Built on the same database, so no export step
  • Quoted separately from the subscription

Tell us the format and the cadence the other side needs and we scope it. Custom development is quoted separately under the subscription agreement.

Got a stack we should fit into

Send the list of tools you run. We come back with what is already supported and what we would build.