Cleaning and facility-management companies live or die on recurring execution: dozens of sites, each with its own scope, frequency, assigned crew, consumables and SLA — repeating every week and month. In stock Odoo you can fake pieces of this with project, planning, maintenance and a subscription add-on, but nothing ties a physical site to its contract, its recurring visit calendar, the roster of staff who are supposed to show up, and the invoice that should follow. Schedules end up in spreadsheets, supervisors reconcile attendance by WhatsApp, and month-end billing becomes a manual reconstruction of "what did we actually deliver at each site." That gap is where margin leaks and SLA penalties appear.

ECOSIRE builds a purpose-fit Odoo module that models your operation directly. At its core is a facility/site registry (facility.site) linked to res.partner for the client, carrying location, contacted supervisor, assigned team and a one-to-many of on-site assets (facility.asset) — floors, restrooms, HVAC units, whatever you clean or maintain. A facility.contract model holds the commercial terms, billing frequency and the SLA definition, with a recurrence engine (an ir.cron job plus a @api.depends-driven next-visit compute) that generates the actual facility.visit occurrences — daily, weekly, or custom RRULE-style patterns — instead of you cloning tasks by hand. Each visit references the site, the planned crew shift, the consumables checklist and a completion state that supervisors close from the field.

On top of that we wire the day-to-day flows: staff rostering and shift assignment per site (integrating cleanly with hr employees and, on Enterprise, planning), an SLA tracker that stamps response/completion deadlines and flags breaches via automated actions, and a per-site consumables and equipment inventory backed by stock so restock and usage are real transactions, not notes. Security is proper Odoo — ir.model.access.csv for group-level CRUD plus record rules so a site supervisor sees only their sites while operations managers see the whole portfolio. Views are delivered as list/form/kanban/calendar XML (with OWL components where a richer field widget earns its keep), and month-end billing runs off delivered visits, either drafting account.move invoices directly or pushing billable lines so finance keeps one workflow. QWeb reports give you a site service sheet and an SLA-compliance summary, and every model is reachable over Odoo's XML-RPC / JSON-RPC API for integration with access-control hardware, client portals or a mobile check-in app.

Because this is build-to-order, nothing here is a shrink-wrapped download. We start from a short scoping call, agree the exact models, contract types, SLA rules and billing logic your business actually uses, then build against your target — Odoo 17.0, 18.0 or 19.0, Community or Enterprise (we tell you honestly which capabilities lean on Enterprise apps like planning and which we implement natively so Community stays viable). Typical delivery is one working week from confirmed scope. You get the installable source, a staging UAT round, and a support window after go-live — not a black box, but a module your own team can read, run and extend.