Industry · Transportation and logistics

Fleet and dispatch on Odoo Community: a practical guide

Which Odoo apps cover fleet, maintenance and dispatch, when Community is enough, how a driver app connects, and how to move off legacy fleet software.

By Octagotech Team5 min readUpdated

Key takeaways

  • Fleet, Maintenance, Inventory and Purchase run on Community. Field Service and full Accounting need Enterprise.
  • Choose Community or Enterprise by the apps you will use, not by the sales conversation.
  • A driver app can sit directly on Odoo's API, under a dedicated user with limited access.
  • Migrate history as read-only archives and re-enter only live records at cutover.
  • Map every workflow before you configure anything.

A common starting point for a fleet operator is a patchwork: dispatch in one tool, maintenance work orders in another, fuel cards feeding a third, and driver pay reconciled by hand at the end of the week. Odoo can cover much of that on one database, and for operations-heavy fleets Community Edition can be enough. This guide covers which apps do what, when Enterprise earns its cost, how a driver app connects, and how to bring legacy data across.

Start by mapping the workflows

The first step on any implementation engagement is a structured discovery. For a fleet, that means talking to dispatch coordinators, fleet maintenance supervisors, and the finance team that handles driver settlements and fuel reconciliation. Write down how check-ins, proof of delivery, work orders, fuel cards and mileage-based pay really run today, including the phone calls and spreadsheets.

Document every workflow in a process map before writing a single line of configuration. Odoo is flexible enough to model almost anything, but you have to know exactly what you are modeling. Skipping discovery is how projects end up with a technically correct Odoo installation that nobody uses because it does not match how the team works.

Community or Enterprise for a fleet

The answer is not always Community. Odoo Enterprise adds value in specific scenarios, particularly when you need the full accounting suite with multi-company consolidation, payroll, or the Odoo IoT box for shop-floor integrations. For those cases the Enterprise licence cost is often the right call.

The fleet-specific apps sit mostly on the Community side. Fleet (vehicles, contracts, service log and costs), Maintenance (preventive schedules and breakdown requests), Inventory and Purchase (parts and tires) are all in Community. Field Service and the full Accounting suite need Enterprise.

Key decision point. If your primary need is operations (dispatch, inventory, fleet maintenance, document attachments) and your accounting and payroll run elsewhere, Odoo Community is often the right choice. Enterprise licensing adds cost without adding value to the apps you will actually use.

Community also changes the hosting model. You self-host or pick a third-party cloud provider, so there is no vendor lock-in on infrastructure and no per-user licence cost as the team grows. The trade-off is that hosting, backups and upgrades are yours to run, or to hand to a partner.

A driver mobile app on Odoo's API

The biggest operational gap in many legacy setups is driver workflow. Dispatchers end up as information relays: calling drivers for status updates, logging check-ins by hand, and chasing proof-of-delivery photos. A driver app can remove those touchpoints.

The app talks to Odoo through its external API: on Odoo 19 and later the JSON-2 API with an API key, on older versions JSON-RPC or XML-RPC. Create a dedicated Odoo user for the app with only the access it needs. Our guide to integrating a mobile app with Odoo covers the options in detail. A typical driver app handles:

  • Driver check-in and trip start. The driver taps "Start trip" and the app writes a status change to the trip or delivery record in Odoo, which dispatch sees on a kanban board.
  • Load confirmations. At pickup, the driver confirms load details against the dispatch order, so discrepancies flag to the dispatcher before delivery.
  • Proof of delivery. Photo capture sits inside the delivery confirmation flow, and the image uploads as an attachment on the delivery order, with no shared drives and no manual uploads.
  • Status events. The app pushes a structured status at each stage (en route, arrived, loaded, delivered, returning), which can feed a live fleet view in Odoo.

A cross-platform framework such as React Native lets one codebase cover iOS and Android. Budget for the Odoo-side configuration of the models the app writes to, as well as the app itself.

Migrating data from the legacy system

Dispatch records, maintenance logs and driver history usually have to come across. Check what your contract says about data export and portability before you need it, because vendors do not always make a full export easy. Negotiate those terms before you sign any enterprise software contract.

One pattern that works is to migrate in three phases. First, a read-only analytical load: historical data goes into Odoo as archived records, queryable but not active in any workflow, so the operations team can confirm the history is intact before go-live. Second, load the active vehicle and driver roster and validate it against the physical fleet manifest: every truck, every driver profile, every open maintenance work order. Third, re-enter the open dispatch orders in flight at cutover on day one rather than migrating them, which avoids a class of data-state edge cases that plague ERP cutovers.

For the wider picture, see what actually takes the longest in a legacy ERP migration.

What to know before starting

We built a TMS on Odoo Community for three trucking companies. Spice Logistics, Raj Transport and Avalon Transport, each a broker and a carrier, replaced McLeod, QuickBooks and spreadsheets with it and went live in October 2026. Its driver app texts drivers a tracking link, logs GPS on Google Maps and writes stop times back to the load, and each company owns its code. The freight TMS case study has the details. The lessons below apply to any logistics or fleet operator evaluating Odoo.

First: invest in discovery. Time spent mapping workflows before configuration saves rework after go-live.

Second: let the apps you need drive the Community vs Enterprise decision, not the sales conversation. If your accounting is external and your payroll is outsourced, you may be paying for Enterprise features you will never use.

Third: custom mobile apps built on Odoo's API are tractable. The API is documented and covers the models of the apps you install. You do not need Odoo Studio or Enterprise to build a capable field app on Community.

Fourth: data migration is where projects go wrong. Negotiate data portability terms before you sign any enterprise software contract. And when you plan the cutover, consider migrating history as read-only archives and re-entering only live records. It removes a large category of risk.


If you are running a fleet on legacy software with a licensing cost that no longer feels justified, or if you are evaluating Odoo for logistics operations, we are happy to walk through what a realistic engagement looks like for your situation. Book a discovery call.

Octagotech Team

Certified Odoo Ready partner · San Francisco, New York, Ahmedabad and Rajkot

We write from live Odoo engagements: 20+ implementations over 5+ years. About Octagotech.

Evaluating Odoo for your fleet?

A scoping conversation about your dispatch, maintenance and data.

Book a discovery call

Running a fleet on legacy software?

The first call takes 30 minutes.

Or email sales@octagotech.com