Running vehicle rentals inside standard Odoo means bending tools that were never built for it. The fleet app tracks your own vehicles, odometer logs and service costs, and sale/sale_rental can price a time-boxed line — but neither knows how to hold a car against overlapping reservation windows, block a double-booking, apply a tiered daily/weekly/monthly rate card, add mileage overage or a security deposit, or capture the fuel level and body damage at pickup versus return. Teams end up managing all of that in spreadsheets alongside Odoo, so availability is guesswork, deposits leak, and revenue per vehicle is invisible. That gap is exactly where a purpose-built rental layer earns its keep.

ECOSIRE builds a dedicated Fleet Rental Management module on top of your existing fleet.vehicle records so nothing is duplicated. The core is a fleet.rental.order model (with fleet.rental.line for multi-vehicle bookings) carrying reservation start/return datetimes, pickup and drop-off locations, a linked res.partner renter, and a stateful workflow (draft → reserved → checked_out → returned → invoiced) driven by @api.depends computes and state-guarded buttons. An availability engine uses an SQL overlap check plus @api.constrains to make double-booking a hard error rather than a warning, and a Gantt/calendar view gives dispatch a single board of what is out, due back, and free. Pricing runs off a configurable fleet.rental.pricing rate card — tiered by duration, vehicle class or season — with computed lines for mileage overage, late-return fees, deposits and taxes, so the quote is defensible and repeatable.

Around that core we wire the operational detail that makes rental real: a check-out / check-in wizard that records odometer, fuel level and a damage/condition checklist (with photo attachments) at both ends, so disputes are settled by data; deposit hold and release tracked against the invoice; and QWeb PDF reports for the rental agreement, pickup/return inspection sheet and final invoice, all on your letterhead. Access is governed by ir.model.access.csv plus record rules so a branch agent sees only their location's bookings while managers see the fleet, and automated actions/scheduled crons handle return reminders and overdue flags. Everything is reachable over the standard XML-RPC/JSON-RPC API for a booking website, mobile check-in app or downstream reporting. It targets Odoo 17.0, 18.0 and 19.0, and is built Community-first — if your database is Enterprise we reuse the full accounting and dashboard stack, and where it is Community we ship the equivalent without leaning on Enterprise-only dependencies.

Because this is build-to-order, you are not downloading a fixed app and hoping it fits. We start with a short scoping call, confirm your vehicle classes, rate structure, deposit and mileage rules, branch/multi-company layout and any booking-site or payment integration, then agree the exact scope in writing. Typical delivery is 2–4 weeks from confirmed scope: we build on a staging copy of your database, run UAT with your team, and only then install to production behind a rollback plan. Pricing starts from $249 (indicative, single-company base scope); added rate-card complexity, multi-company or multi-branch rollout, booking-website/payment-gateway integrations, localization depth and historical data migration increase the quoted scope. After the scoping call you receive a fixed quote — no surprise line items.