Hotel Property Management System (PMS) Core

Name: Hotel Property Management System (PMS) Core
Brand: ECOSIRE
SKU: hotel-pms-core

主な機能

Individual and group reservations, with group bookings allocating a room block and generating linked per-guest stays

Automatic room assignment matching available inventory by room type, occupancy, and date range, with manual override and drag-to-reassign on the front-desk board

Guest folios that accumulate room charges, extras, city/occupancy tax, and POS postings, with computed balance via @api.depends

Folios integrated directly with Odoo Accounting — check-out posts to account.move and generates the invoice with no export step

Rate plans plus Best Available Rate (BAR): rates computed from configured rules with per-stay overrides that capture the reason for audit

Cancellation, deposit, and no-show policies enforced as policy records driven by Odoo automated actions (deposit due, cancellation windows, penalties)

Multi-property from a single Odoo instance, with per-property company scoping and data isolation via record rules

Availability and occupancy calendar/planning view (Odoo calendar + Gantt-style board) showing arrivals, departures, and in-house guests

Housekeeping room status tracking (clean, dirty, inspected, out-of-order) tied to check-in/check-out events

Split-folio and company/OTA billing so charges can be routed to guest, company, or travel agent on the same stay

QWeb PDF documents: registration card, guest folio, and check-out invoice, all brandable to your property

Role-based security via ir.model.access.csv and record rules for receptionist, night auditor, revenue manager, and finance profiles

Night audit workflow that rolls the business date, posts room charges, and flags open balances and no-shows

XML-RPC/JSON-RPC API surface so channel managers, booking engines, door locks, or payment gateways can be integrated in later phases

Deposit and pre-authorization tracking on the reservation, linked to the folio balance and Accounting

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

Hotel Property Management System (PMS) Core is a build-to-order Odoo application that ECOSIRE designs, builds, installs, and supports for your property — it is not an off-the-shelf apps.odoo.com download. After purchase, our engineers scope your workflows, then deliver a native Odoo module engineered specifically for hotels, resorts, and hostels.

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.

得られるもの

Complete, version-controlled Odoo addon (source code with a clean __manifest__.py) targeting your chosen Odoo 17, 18, or 19 edition — you own the code

Installed and configured module on your Odoo instance (staging first, then production), including room types, rooms, rate plans, and policies set up to your property

Security configuration: ir.model.access.csv access rights and record rules mapped to your front-desk, night-audit, revenue, and finance roles

Accounting integration configured so folios post to the correct journals, taxes, and analytic accounts in your chart of accounts

QWeb report templates (registration card, folio, check-out invoice) branded with your property's logo and details

Admin and front-desk documentation plus a live training session (reservations, check-in/out, night audit, rate overrides)

Post-launch support window for bug fixes and questions, with a defined response commitment

Data-migration assistance for existing reservations, guests, and rate plans where source data is provided in a workable format

これは誰のためのものですか

Independent hotel & resort owner-operators

Properties running on Odoo (or moving to it) that want reservations, folios, and billing in the same system as Accounting and Inventory, instead of paying for a separate PMS and reconciling it every night.

Hostels and multi-property groups

Operators running several properties who need one Odoo instance with per-property isolation, group and block bookings, and consistent rate plans across sites — without a per-room SaaS bill for each location.

Odoo partners and in-house IT/revenue teams

Implementation teams and revenue managers who need a native, code-owned PMS they can extend — BAR strategies, deposit policies, and API integrations to channel managers — rather than a black-box third-party app.

Hotel Property Management System (PMS) Core の比較方法

基準	エコシエール	カスタムビルド	競合他社
Native to Odoo (folios post to Accounting, one database)	付属	部分的なサポート	部分的なサポート
Individual + group reservations with auto room assignment	付属	部分的なサポート	部分的なサポート
Rate plans + Best Available Rate with audited overrides	付属	部分的なサポート	部分的なサポート
Cancellation & deposit policies enforced via automated actions	付属	部分的なサポート	部分的なサポート
Multi-property from one instance with record-rule isolation	付属	部分的なサポート	含まれていない
Built, installed & supported for you (2–4 wk lead time)	付属	含まれていない	含まれていない
You own clean, version-controlled addon source	付属	付属	含まれていない
Fits your exact workflows without forcing a template	付属	付属	含まれていない
Supports Odoo 17, 18 & 19 (Community or Enterprise)	付属	部分的なサポート	部分的なサポート

Hotel Property Management System (PMS) Core に関するよくある質問

How long until the module is delivered and live?

This is a build-to-order module, not an instant apps.odoo.com download. After purchase we run a short scoping call to confirm room types, rate strategy, policies, and integrations, then build, install, and test on staging before going to production. Typical delivery is 2–4 weeks depending on scope (multi-property setups and channel-manager integrations sit at the longer end). You get a timeline in writing after scoping.

What support and updates are included after launch?

Every engagement includes a post-launch support window for bug fixes and usage questions, with a defined response commitment. Because you own the addon source, you're never locked out of your own code. We also offer optional ongoing support/maintenance plans covering enhancements, Odoo version upgrades (for example moving from 17 to 18 or 19), and new integrations after the initial window ends.

Which Odoo versions and editions does it support?

The module is built for Odoo 17, 18, and 19, on either Community or Enterprise. We target your exact running version so the addon installs cleanly against your instance. Accounting integration works with Odoo's standard accounting; if you're on Community we confirm the accounting configuration during scoping.

Can it run multiple properties from one Odoo instance?

Yes. Multi-property is a core design point. One instance can run several hotels or hostels with per-property scoping and data isolation enforced through Odoo record rules, so each property's staff see only their reservations, folios, and rooms, while group-level roles can see across sites. Rate plans and policies can be shared or set per property.

How does billing connect to Odoo Accounting?

Folios are native Odoo objects. Room charges, extras, taxes, and POS postings accumulate on the guest folio, and at check-out the folio posts to account.move and produces a QWeb PDF invoice using your journals, taxes, and analytic accounts. There's no nightly export or separate reconciliation — the PMS and your books share the same database. Split-folio and company/OTA billing are supported.

Can you integrate a channel manager, booking engine, or door locks?

Yes, as scoped add-ons. The module exposes its data through Odoo's ORM and XML-RPC/JSON-RPC API, and we can build automated actions and webhooks for two-way sync with channel managers (rates/availability/reservations), a website booking engine, payment gateways for deposits, or door-lock systems. These integrations are quoted based on the specific provider's API and are typically delivered as a follow-on phase.