Skip to Content
← Back to catalog
Vehicle Fleet Maintenance

Vehicle Fleet Maintenance

Open source

The mileage recorded on the vehicle triggers preventive maintenance, with no double entry.

Technical nameoski_fleet_maintenance
LicenseLGPL-3
AuthorOdooSkills
⬇ Download (20.0)

Vehicle Fleet Maintenance

The mileage recorded on the vehicle triggers preventive maintenance. One entry, two modules served. Open source.

"Oil change every 10,000 km" is the most ordinary maintenance rule of a vehicle fleet — and the most poorly kept. Yet the mileage exists: the fleet manager records it every month, and every fill-up carries one. But the maintenance management module waits for its own meter, on its own screen. Two entries for a single number: the second one eventually stops being done, and mileage-based preventive maintenance falls asleep. This bridge copies what the fleet already knows to the maintenance meter, at every reading, without anyone having to think about it.

What it adds

  • 🔁 Every fleet reading feeds the maintenance meter — whether entered by hand or created by a fuel fill-up. The "Odometer" meter is created automatically at the first reading, with the vehicle's unit.
  • 📅 Mileage-based preventive maintenance actually triggers — "every 10,000 km" becomes a plan that produces its work order at the right time, with the lead time you choose.
  • 🔮 A due date announced in days, not in kilometers — the maintenance module computes the actual pace of use and gives a likely date. You schedule the workshop before the threshold is reached.
  • ➡️ One direction, by design — the copy goes from the vehicle to maintenance, never the other way. The vehicle's odometer remains the source of truth for mileage: no discrepancy to settle.
  • 🔒 Never twice — each reading keeps the link to the one it created. Replaying an import duplicates nothing.
  • 💶 Maintenance cost flows into the cost per kilometer — the work done on the vehicle feeds its "cumulative maintenance", hence its actual cost per kilometer.
  • 🤝 Nothing to install, nothing to configure — the bridge installs itself as soon as the fleet and the maintenance module are both present, and has no effect if one of them is missing.

In screenshots

1. Preventive plans by mileage

Service every 20,000 km, tyre check every 10,000 km: vehicle plans sit next to the other equipment plans, with their next threshold and estimated date.

Preventive plans with mileage thresholds and estimated dates

2. The odometer feeds maintenance

Each odometer reading is copied into the vehicle's maintenance meter, once. No double entry.

Maintenance meter of a vehicle fed by the odometer readings

3. All odometer readings

Readings from fill-ups and manual entries, vehicle by vehicle.

List of odometer readings for the fleet

4. Work orders on vehicles

A finished repair with its parts: its cost is added to the vehicle's maintenance cost and to its cost per kilometre.

Finished work order on a vehicle with parts and cost

Why install it

  • Double entry disappears — and with it the reason mileage-based preventive maintenance always ended up going off the rails.
  • Maintenance is scheduled on an announced date, instead of being caught up once the threshold is passed.
  • A vehicle's cost becomes complete: fuel and maintenance, per kilometer.
  • No configuration, no risk of duplicates, no arbitration between two diverging meters.
  • Open source: it is the glue between two modules you already have, not one more product.

The Asset suite

This bridge is useless on its own: it connects two modules of the family.

  • 🚚 Vehicle Fleet (oski_fleet) — $49: required. License plate, odometer, fill-ups, drivers and cost per kilometer.
  • 🔧 Asset Maintenance (oski_maintenance) — $89: required. Work orders, routings, actual cost and meter-based preventive maintenance.
  • 🏢 Asset Management (oski_asset) — $49: required by both. The asset register and its log.

The Rolling Stock bundle (core + vehicle fleet + this bridge) is $79 instead of $98. The complete Asset family — eleven paid modules and eight open-source bridges — is $299 instead of $509. Details on apps.odooskills.com.

License LGPL-3 — compatible with Odoo 19.0 Community and Enterprise. Requires oski_fleet and oski_maintenance, and installs automatically as soon as both are present. Good to know: the copy only applies to readings created after installation; the history already entered in the fleet is not replayed. French interface. Support: apps@odooskills.com.

Discussion