HVAC companies live in a gap that Odoo core never fully closes. You install and service physical equipment at customer sites, run recurring maintenance agreements with scheduled visits, dispatch technicians against SLAs, and need the full history of every rooftop unit, chiller, and split system you touch. Out of the box, Odoo gives you Sales, a generic project/field-service surface, and Repairs — but none of them model an installed-equipment register with warranty and refrigerant-charge history, none of them auto-generate the next preventive-maintenance visit from a signed contract, and none reconcile technician time and parts back to a per-asset profitability view. Teams end up stapling spreadsheets to the side of Odoo, and the field data never makes it back into the ERP cleanly.

This is a demo service-business configuration app that we design specifically for HVAC operations and then build to your scope. At the data layer we add an installed-equipment model (models.Model with fields.Many2one links to customer, site, and the original sale order) plus a maintenance-contract model whose recurrence engine uses an @api.depends-driven compute and a scheduled ir.cron automated action to spawn the next service order before it falls due. Service jobs are modeled as a first-class order type that rolls up technician timesheets, consumed stock moves (refrigerant, filters, compressors), and checklist results, with compute fields exposing labour cost, parts cost, and margin per visit and per asset. Everything is wired through proper access control — ir.model.access.csv for group rights plus record rules so a subcontractor crew sees only its own assigned jobs.

On the presentation side we ship dedicated views (list, form, kanban dispatch board, and calendar) built in XML with OWL components where interactivity warrants it, plus QWeb service-report and maintenance-certificate templates the technician can generate on site. Optional automated actions send appointment reminders and contract-renewal notices, and the whole schema is reachable over the XML-RPC/JSON-RPC API so your booking site or a technician mobile app can create jobs and read equipment history programmatically. We target Odoo 17.0, 18.0, and 19.0, and we scope Community vs Enterprise honestly up front — where a capability (such as advanced Field Service routing or the studio-built dashboards) only exists in Enterprise, we tell you before you commit, and we build a Community-compatible equivalent when that is the right call.

Build-to-order means exactly that: after a short scoping call we confirm the models, workflows, and reports your operation actually needs, then design, build, and test the module on a staging database before installing it on yours. Typical delivery is 2–4 weeks from confirmed scope, and you receive the installable source, documentation, and a support window. Pricing starts from $349 (indicative, single-company base scope); multi-company rollouts, extra integrations (payment, telematics, or a mobile technician app), deeper localization, and migrating large volumes of legacy equipment and contract data increase the quoted scope.