A separate Odoo module
Installed like any other Odoo module. Odoo itself is left as it is, and your own changes stay yours.
Doroobi Fleet · Odoo and integrations
Doroobi Fleet comes from ITD Innovation, a team that also implements Odoo. Odometer, engine hours, fuel, trips and driver hours will flow into the Odoo apps you already run.
In many fleets the tracking system and the ERP never meet. Someone exports mileage to a spreadsheet, types it into the maintenance plan, and adds up driver hours by hand at month-end. Every copy is a chance for a mistake, and the numbers are already old by the time anyone uses them.
ITD Innovation builds Doroobi and also implements Odoo for companies across the region, so we know where fleet data belongs in it. Doroobi Fleet will connect through its own Odoo module, added beside your apps without changing Odoo’s core, and keep vehicles, odometer, engine hours, fuel, trips and driver hours up to date.
Installed like any other Odoo module. Odoo itself is left as it is, and your own changes stay yours.
Odometer and engine hours come from the tracker or the vehicle’s CAN bus, and update the vehicle’s record in Odoo Fleet.
Service plans in Odoo Maintenance fall due by the kilometres and engine hours the vehicles actually ran.
With workforce attendance, after launch, shifts and site hours checked by location go to Attendances and Timesheets, and hours signed off by a manager go to Payroll.
Fuel and maintenance costs land in Accounting and Expenses, against the vehicle and the project they belong to.
Not on Odoo? A REST API and webhooks will connect your ERP, dispatch or reporting tools, and push events such as alerts and zone visits as they happen.
We check which Odoo apps you use, your version, and how you name vehicles, drivers and projects.
Each tracked vehicle and driver is linked once to its record in Odoo.
You decide which Odoo apps receive fleet data, and who in Odoo can see it.
Data starts to flow, and during the pilot we check it with your team against the readings in the vehicles.
Odoo knows the job, the customer and the cost. Doroobi Fleet adds where and how the work happened, on Doroobi’s own map with live traffic and road reports from Doroobi drivers. When a technician runs late to a job, the dispatcher can see the jam or the closed road before updating the customer, and the proof of visit that reaches Odoo Field Service comes from the same map.
| Odoo app | What syncs |
|---|---|
| Fleet | Vehicles, odometer, drivers, contracts and expiry dates |
| Maintenance | Service due by real kilometres and engine hours |
| Attendances and Timesheets | Shifts and site hours checked by location |
| Field Service and Project | Job locations, travel time and proof of visit |
| Accounting and Expenses | Fuel and maintenance costs per vehicle and project |
| Payroll | Hours and overtime, once signed off |
No. The Doroobi Fleet module sits beside your apps and does not change Odoo’s core. We look at your version and setup first.
Fleet, Maintenance, Attendances and Timesheets, Field Service, Project, Accounting and Expenses, and Payroll. You choose which ones receive data.
Yes. A REST API and webhooks will let your own ERP, dispatch or reporting tools read fleet data and receive events.
No. Odoo receives the figures it uses, such as odometer, engine hours, fuel, trips and hours. The full position history stays in Doroobi Fleet for 12 months.
Yes. The same team implements Odoo, so the fleet link and any other Odoo work can be planned together.