Hotels running on Odoo quickly hit a wall: there is no native concept of a room's housekeeping state. Front office knows a guest has checked out, but housekeeping has no queue, no per-room clean/dirty/inspected/out-of-order status, and no way to see which rooms are ready to re-sell. Teams end up coordinating on WhatsApp groups, printed room lists, and whiteboards — and a room that is actually dirty gets sold because nobody updated a shared board. Odoo's Maintenance app tracks equipment, and Project/Field Service can model tasks, but none of them speak "room status," attendant assignment, or a housekeeping supervisor's inspection pass out of the box.

We build a dedicated housekeeping and engineering layer on top of your existing Odoo. At its core is a hotel.room model carrying a computed housekeeping_state selection (clean, dirty, inspected, out_of_order) plus occupancy, floor, and room-type fields, surfaced as a live kanban/room-rack board that supervisors and front desk share in real time. A hotel.housekeeping.task model represents each cleaning job — linked to a room, an assigned attendant (res.users/hr.employee), a cleaning program, and a checklist of line items your supervisors sign off. Cleaning programs are configurable records (e.g. stayover, departure, deep_clean, turndown) that seed the correct checklist and expected duration when a task is generated, so a departure clean and a stayover touch-up are never treated the same. Engineering requests live in a hotel.maintenance.request model — a guest-reported leak or a broken AC becomes a job ticket with priority, trade category, assignee, and an optional out_of_order flag that automatically pushes the room off the sellable board until the fix is closed.

Technically, room status stays honest because we wire it into your reservation events. Using @api.depends compute methods plus Odoo automated actions / server actions, a check-out flips the room to dirty and auto-creates a departure housekeeping task, while a completed-and-inspected clean flips it back to clean/inspected and makes it re-sellable — no manual board updates. Access is locked down with ir.model.access.csv groups (Attendant, Supervisor, Engineering, Front Office) and ir.rule record rules so an attendant sees only their assigned rooms and a supervisor sees their floor or property. Views are standard XML (list, kanban, form, calendar) with an OWL room-rack component where it helps; QWeb reports produce the printed housekeeping assignment sheet and a maintenance work order. Everything is reachable over Odoo's XML-RPC / JSON-RPC API so a housekeeping mobile app, a door-lock system, or your PMS integration can read and write room state programmatically. We target Odoo 17.0, 18.0, and 19.0 and build cleanly against Community or Enterprise — we confirm which edition-specific hooks (e.g. Enterprise Field Service linkage) apply to you during scoping.

Because this is build-to-order, you are not downloading a fixed app and bending your operation to fit it. We start with a short scoping call to map your room inventory, cleaning programs, inspection workflow, and how check-in/out fires in your setup, then deliver the installable module, install and configure it on your server or ours, and hand over the git repository. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window. You get a system shaped around how your property actually runs, on your own Odoo, with the source code in your hands.