Odoo Fleet: Vehicles, Contracts, Services, and Costs

Introduction

Odoo Fleet centralizes employee data, time off, recruitment, and HR documents so managers and HR work from one file per person instead of parallel folders and tools.

People processes affect every department, yet leave balances, contracts, and hiring status are often unclear until someone escalates a problem.

The Fleet apps connect HR events to the org chart, approvals, and, where relevant, payroll or expense flows, giving leadership a live view of headcount and availability.

HR business partners, office managers, and executives planning workforce changes will find practical patterns to compare with their current setup.

Fleet is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Fleet: Vehicles, Contracts, Services, and Costs states the storyline for stakeholders approving budgets while.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Fleet.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Fleet is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

HR sends a leave approval by email. Payroll finds out late. The manager on site has no idea who is available Tuesday. Everyone trusts HR, but the data is always one step behind reality.

HR processes touch every employee, yet leave, recruitment, and contracts often sit in separate tools. Managers lack a single place to approve requests and see team availability.

Sound familiar? Teams usually hit these walls:

• Leave balances disputed because requests live in email
• Recruitment status unclear across hiring managers
• Contracts signed without a central employee file

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Fleet, and measure what changes.

Top 10 Fleet Use Cases

10 use cases for Odoo Fleet, ranked from Level 1 (easy, do it this afternoon) to Level 10 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Register your first company vehicle and assign it to a driver Level 1 — Easy

Level 1 is the simplest possible Fleet action: one manager, one car, one driver. No contracts, no costs, just a vehicle that finally lives in Odoo instead of a shared Excel tab.

Here's how you'd do it in Odoo:

1. Install the Fleet app, then go to Fleet, Configuration, Settings and confirm Fuel and Service options are enabled.
2. Open Fleet, Vehicles, New, and fill Model (brand and model), License Plate, First Contract Date and Last Odometer.
3. Set Driver to the employee or contact who actually uses the car day to day.
4. Pick the right Tags such as Company Car or Pool Car, save, and confirm the vehicle status becomes In Service.
5. Open Fleet, Vehicles, Kanban view to see the new car appear in the right column with the driver photo.

What you get: You stop debating who drives which car. One record holds plate, driver and start date, and every future cost will attach to that same vehicle automatically.

2. Log an odometer reading and a fuel refill on a vehicle Level 2 — Easy

Level 2 is the daily Fleet routine. Drivers or fleet admins record fuel logs and odometer values so the car has a real mileage history instead of a guess at year-end.

Here's how you'd do it in Odoo:

1. Open the vehicle record and use the Odometer smart button to add a new reading with the date and kilometers.
2. Go to Fleet, Fleet, Fuel Logs, New, pick the vehicle and enter Liter, Price per Liter and Total Price from the receipt.
3. Attach the fuel ticket to the chatter so the original invoice stays linked to the cost line.
4. Repeat for each refill of the week; the Last Odometer on the vehicle updates automatically from the highest reading.
5. Open Fleet, Reporting, Costs, group by Vehicle to see fuel cost per car this month at a glance.

What you get: Fuel cost per vehicle becomes a real number instead of a controller estimate, and the next service interval can be planned from accurate mileage.

3. Record a one-off service like an oil change or tire replacement Level 3 — Easy

Level 3 introduces the Services log, the Fleet feature that turns garage receipts into structured history records on the right car instead of a paper folder in the office.

Here's how you'd do it in Odoo:

1. Go to Fleet, Configuration, Service Types and confirm common types exist: Oil Change, Tires, Brakes, Technical Inspection.
2. From the vehicle, click the Services smart button, New, choose the Service Type and enter Date, Cost and Vendor.
3. Add a short note in the description: kilometers at service, next service due, parts replaced.
4. Mark the service as Done so it leaves the Running status and appears in the cost report.
5. Open Fleet, Reporting, Services, group by Service Type to see which maintenance line costs the most fleet-wide.

What you get: Every garage bill lives on the car that consumed it, and you can finally answer the only question that matters at renewal: is this vehicle still cheaper to keep than to replace.

4. Track leasing and insurance contracts with renewal alerts Level 4 — Medium

Level 4 activates the Contracts layer. Leasing, insurance and assistance contracts are stored on each vehicle with start and end dates so renewals stop being a last-minute fire drill.

Here's how you'd do it in Odoo:

1. From the vehicle, click the Contracts smart button, New, and pick Type Leasing (or Insurance, Assistance).
2. Fill Start Date, Expiration Date, Vendor and Recurring Cost (monthly fee) plus the contract reference.
3. Attach the PDF contract to the chatter so the document is one click away from the car record.
4. Set Activity Alert: schedule a To-Do for the fleet manager 60 days before expiration to start the renewal review.
5. Open Fleet, Fleet, Contracts and filter Expires in the next 90 days each Monday to anticipate every renewal.

What you get: No more uninsured vehicle on the road and no more auto-renewed lease at a worse price, because every contract has a real owner and a real deadline.

5. Organize the fleet with tags, statuses and categories Level 5 — Medium

Level 5 turns a list of vehicles into a structured fleet. Tags, vehicle statuses and categories let finance, HR and operations slice the same data with their own filters.

Here's how you'd do it in Odoo:

1. Go to Fleet, Configuration, Tags and create Company Car, Pool Car, Commercial, Workshop, Electric, Diesel.
2. Open Fleet, Configuration, Vehicle Status and define the real lifecycle: Ordered, In Service, To Downgrade, Sold, Scrapped.
3. On each vehicle, tag the car correctly and set its current Status so the Kanban view becomes a real pipeline.
4. Create Categories (Light, Van, Truck, Electric) via Fleet, Configuration, Vehicle Models, Categories to enable cost grouping.
5. Save a custom filter Pool Cars Available and pin it to your Vehicles Kanban for the dispatcher.

What you get: Finance sees cost by category, dispatch sees available pool cars, HR sees company cars per employee, all from one shared fleet database.

6. Plan a driver change with Future Driver and a clean history Level 6 — Medium

Level 6 uses the Future Driver feature, specific to Fleet. A planned handover keeps the current driver active until the swap date and writes a real assignment history on the car.

Here's how you'd do it in Odoo:

1. Open the vehicle of an employee who is leaving or changing role and set Future Driver plus Plan To Change Car date.
2. Add a chatter note with the agreed swap context: end of contract, role change, end of leasing.
3. On the swap date, open the vehicle and click Change Driver: the future driver replaces the current one in one click.
4. Check the Drivers History tab on the car: the previous assignment is logged with start and end dates.
5. Schedule a Service activity Vehicle Cleaning and Inspection so the car is ready for the new driver.

What you get: Handovers stop being a back-and-forth between HR and the fleet manager, and every car keeps a clear chain of custody for HR, insurance and tax audits.

7. Build a Total Cost of Ownership report per vehicle and category Level 7 — Hard

Level 7 turns the fleet from a cost center into a measured one. The Reporting view of Fleet aggregates fuel, services and contracts to surface a true cost per vehicle and per category.

Here's how you'd do it in Odoo:

1. Open Fleet, Reporting, Costs and switch to Pivot view with rows Vehicle and columns Cost Type (Contract, Service, Fuel).
2. Add a measure Total Amount and a second Total Kilometers to compute cost per kilometer in a custom column.
3. Group by Category (Light, Van, Truck, Electric) to compare TCO between fleet segments over the last 12 months.
4. Save the favorite as TCO by Vehicle and pin it to the Fleet dashboard for the monthly fleet review.
5. Export the pivot to spreadsheet and share it as a recurring report to the CFO and the COO.

What you get: The fleet conversation moves from gut feeling to numbers, and the next vehicle replacement is decided on cost per kilometer instead of habit.

8. Automate fleet service purchasing via Purchase and approved vendors Level 8 — Hard

Level 8 connects Fleet to Purchase. Services stop being one-off lines: they become Requests For Quotation sent to a short list of approved garages, with vendor pricing visible per service type.

Here's how you'd do it in Odoo:

1. In Purchase, Configuration, Vendors, mark each garage and tire shop as a fleet vendor with their contact and payment terms.
2. From a vehicle, schedule a service and click Create Purchase Order to issue an RFQ for the agreed amount.
3. Receive the vendor bill in Accounting, link it back to the Fleet Service Cost so the cost line is invoiced once.
4. Configure a recurring rule: every 15,000 kilometers, Fleet auto-creates a Service activity assigned to the fleet manager.
5. Open Purchase, Reporting and filter by Fleet vendors to negotiate frame agreements with the top three garages.

What you get: Fleet spend stops being scattered receipts. Every euro is purchased, billed and traced like any other vendor cost, with to renegotiate annually.

9. Post fleet costs to Accounting with analytic distribution per department Level 9 — Hard

Level 9 plugs Fleet into Accounting. Every fuel log, service and contract recurring cost is posted on the right account and distributed to an analytic plan so finance sees cost per department, project or cost center.

Here's how you'd do it in Odoo:

1. Create an Analytic Plan named Fleet with one Analytic Account per vehicle, plus a parent per department (Sales, Tech, Admin).
2. On each vehicle, set Default Analytic Account and define the recurring cost journal so contracts post automatically each month.
3. Map each Service Type to an expense account (Maintenance, Fuel, Insurance) under Accounting, Configuration, Chart of Accounts.
4. Validate the first monthly run: vendor bills, fuel logs and recurring contract costs all hit the right analytic line.
5. Open Accounting, Reporting, Analytic Items and group by Department to share fleet cost per team with the CFO.
6. Build a Spreadsheet pivot Cost per Driver to feed the next salary package review.

What you get: Fleet stops being an opaque cost center. Each department sees what its cars actually cost, and finance can defend the budget with one query instead of a manual Excel rebuild.

Designing the analytic plan, mapping every fleet cost to the right account, and wiring recurring postings into the monthly close is exactly the kind of Fleet plus Accounting plus Analytic setup Dasolo runs as a partner-led engagement.

10. Run a connected fleet with telematics, AI predictive maintenance, Field Service and live dashboards Level 10 — Expert

Level 10 is the full operating system: GPS telematics streams mileage and driving data into Fleet, AI flags vehicles before they break, Field Service dispatches a technician, and a real-time TCO dashboard shows the whole fleet in one view.

Here's how you'd do it in Odoo:

1. Integrate a telematics provider (Geotab, Webfleet, Verizon) via API: GPS position, kilometers and driving behavior land on each vehicle every night.
2. AI service consumes the telematics stream, scores risk per car and posts a predictive alert with confidence when a breakdown is likely within 30 days.
3. Critical alerts auto-create a Maintenance Request, then a Field Service task assigned to the closest mobile mechanic via Planning.
4. Driver behavior signals (harsh braking, speeding, idling) trigger a Discuss notification to the driver and a coaching activity for the manager.
5. Insurance and accident events open a Helpdesk ticket on the broker team, with telematics extract pre-attached for the claim file.
6. Marketing Automation sends an end-of-lease offer to drivers 90 days before contract expiration with a renewal vehicle suggestion.
7. A Spreadsheet Fleet Live dashboard tracks TCO, cost per kilometer, downtime, predicted failures and CO2 per category, refreshed in real time.

What you get: The fleet runs itself in the background: breakdowns are caught before they happen, claims are filed with evidence, and management opens one live dashboard instead of waiting for the monthly fleet report.

Designing the telematics integration, the AI predictive rules, the Fleet to Maintenance to Field Service handoff, and the live TCO dashboards is the architecture Dasolo designs as a partner-led connected-fleet engagement. Most teams need an outside team to assemble these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 6 fit your world, you can often succeed with standard Odoo Fleet, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 7 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Fleet includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo