Hotel Property Management System (PMS) Core

This is a real PMS living inside Odoo rather than a bolt-on. Room types, rooms, rate plans, folios, and reservations are modeled as first-class Odoo objects (models.Model with typed fields and @api.depends computes for nightly totals, occupancy, and balance), so front-desk operations, housekeeping status, and revenue all flow into the same database as your CRM, Inventory, and Accounting. Because it is built on the Odoo ORM, every screen is a standard Odoo view (list/form/calendar/Gantt-style planning boards in XML, with OWL components where a richer front-desk experience helps), and folio charges post straight to account.move in Accounting — no nightly export, no reconciliation spreadsheet.

The reservation engine handles both individual and group bookings. A single group booking can allocate a room block, and auto room assignment matches available inventory to each stay by room type, occupancy, and dates while respecting overbooking rules you define. Rate management ships with rate plans and a Best Available Rate (BAR) strategy: BAR is computed from your configured rules, and front-desk staff can apply a documented override on any stay, with the reason captured for audit. Cancellation and deposit policies are enforced as records — deposit due, cancellation windows, and no-show handling are driven by policy records and Odoo automated actions, not by staff memory.

Folios are the financial spine of the stay. Room charges, extras, city tax, and POS/restaurant postings accumulate on a guest folio, split-folio and company-billing scenarios are supported, and check-out generates a QWeb PDF folio/invoice. Access is governed the Odoo way — ir.model.access.csv plus record rules keep receptionists, night auditors, revenue managers, and finance in their lanes, and multi-property setups are isolated per property so one instance can run several hotels with correct company/property scoping.

Every deployment targets your chosen Odoo edition and version — the module supports Odoo 17, 18, and 19, on Community or Enterprise. You own the code (a clean, versioned addon with a proper __manifest__.py), the configuration, and the documentation. Integrations to channel managers, door locks, or payment providers are available via Odoo's XML-RPC/JSON-RPC API or automated actions and can be scoped as part of the build. Typical delivery is 2–4 weeks depending on scope, and every engagement includes a post-launch support window.