How hotel software is priced: per room, per module, per user and the costs outside the quote
Hotel software pricing models vary widely, but the quoted fee is rarely the total cost. This guide explains per room, module, and user pricing, and shows how to calculate the true three-year expense.
Contents
Key takeaways
- A hotel software quote is a starting figure, not a total: setup, interfaces, training, support hours and the annual increase decide the year-three number.
- Per-room pricing is predictable but punishes expansion; per-module pricing lets you start small but often leaves housekeeping, reports or the guest app outside the base fee.
- Per-user pricing turns front desk turnover and seasonal staff into a recurring cost, so ask whether accounts are named or simultaneous.
- Two quotes can only be compared on the same room count, the same module list, the same support level and the same contract term, added up over three years.
- The increase formula belongs in the contract, not in an email, and the data export terms belong there too.
Hotel software pricing models are the rules a vendor uses to set its recurring fee: per room, per module, per user, or a flat platform fee, often mixed. The quoted figure is rarely the total cost, because setup, interfaces, training, support hours and annual increases usually sit outside it.
Two vendors quote the same room count and the same module list, and the monthly figures look close. By year three one costs noticeably more, because the difference was never in the monthly fee: it was in setup, two interfaces, training and an index clause nobody read. This article explains the common pricing models, what quotes usually leave out, and how to put two offers side by side so the comparison is real. If terms like PMS or channel manager are new, the hotel technology glossary covers them first.
What are the main hotel software pricing models?
There are four common models: per room, per module, per user and a flat platform fee, and most quotes mix two or three of them. The model matters more than the number, because it decides what happens to the price when the hotel changes. A cheap-looking quote under the wrong model can be the expensive one by year three.
Per room
The recurring fee is multiplied by a room count. The questions that matter are which rooms count and when: all rooms or only sellable rooms, banded or exact, and whether the count is fixed at signature or checked at each renewal. A hotel that adds a floor or opens a second property pays for it under this model, immediately or at the next renewal.
Per module
A base fee plus a line for each module. The base often covers reservations, front desk and billing only, while housekeeping, reports, restaurant sales, channel connections and the guest app are priced separately. This model lets a small hotel start narrow, but the day-one list and the year-two list are rarely the same, and the difference is where the cost hides.
Per user
A fee for each account. Named accounts charge for every person who ever needs one; simultaneous sessions charge for how many people are logged in at once. Front desk turnover and seasonal staff make this the model to read most carefully, because a hotel that doubles its team in July can pay for the peak all year if accounts are named.
Flat or revenue-based
A flat platform fee is predictable at low volume and expensive at high volume; a fee tied to revenue or booking volume rises with the hotel's own success. Ask what counts as revenue, who measures it, and when it is checked. The same model behaves differently at different sizes: a per-room fee is stable for a 40-room hotel and heavy for a 200-room one, while a flat fee is the reverse.
| Model | What the fee follows | Where it hurts as the hotel grows | What to ask |
|---|---|---|---|
| Per room | Room count | Adding rooms or a second property | Which rooms count, and when is the count checked |
| Per module | Scope | A base that excludes modules you need by year two | The full module list, with prices |
| Per user | Headcount | Seasonal staff and turnover | Named or simultaneous accounts |
| Flat or revenue-based | The platform or your revenue | A good year | What counts as revenue, and who measures it |
Most quotes combine models: a per-room base, three modules, ten users and a setup fee. Write down which model applies to each line before you compare totals, otherwise the comparison is between two different shapes of price rather than two prices.
What does a hotel software quote usually leave out?
Setup, interfaces, training, support hours, hardware and third-party subscriptions are the usual gaps, and each one is a real cost line rather than a detail. Ask for every one of them in writing, with a one-time or recurring label. The items below are what to demand before signature.
Checklist
- A setup scope with deliverables and dates
- Every interface listed, with its one-time fee and its monthly fee
- The number of training days included, and the price of extra ones
- Support hours, out-of-hours rate, response time and resolution time
- The hardware list the system assumes
- Third-party subscriptions the hotel pays directly
- Minimum term, notice period and the annual increase formula
- The data export format, cost and timeline at exit
Setup and migration
Setup covers configuration, migration of rate plans, guest history and open balances, and a period of running the old and new systems side by side. Ask for a written scope and for what happens if the project runs late. A milestone schedule, where part of the payment follows delivery, protects the hotel when a project slips.
Interfaces and who holds the credentials
The channel manager, door locks, restaurant points of sale, fiscal devices, the e-invoice integrator and the payment provider may each carry a one-time connection fee plus a monthly line. Each also needs credentials that someone holds, and that someone may be the vendor rather than the hotel. Ask what happens to each connection if you change vendor, because a connection you cannot take with you is an exit cost.
Training and support hours
Training is priced per session or included in a fixed number of days, and the question that matters is who pays for training the staff hired in month eight. Support has two numbers that are often confused: the hours included and the rate outside them, and the commitment, which may be a response time or a resolution time. These are different promises, and the support and uptime terms in hotel software contracts are worth reading before you accept either.
Hardware and network belong on the same sheet: key card encoders, printers, tablets for housekeeping, and the Wi-Fi coverage the system assumes. None of it is software, and all of it is on the invoice. Third-party subscriptions the hotel pays directly, such as the e-document integrator or a payment provider, usually do not appear on the software vendor's quote, so budget for them separately.
How does growth change the price?
Growth changes the price through the model you signed: room counts, user counts and module scope each move the fee, and the contract decides whether that happens immediately or at renewal. Ask for the year-three number at three growth scenarios before you sign, not after.
More rooms
Adding rooms mid-term: is the fee recalculated at once and prorated, or only at renewal, and does the room count move in bands that step the price up sharply. A band that jumps at fifty rooms behaves very differently from a per-room line when you add the fifth.
More modules
A module bought later is often priced at the rate in force at activation, not the one published at signature. A module that costs little on day one can cost more in year two. New outlets follow the same pattern: a spa, a beach bar or a second restaurant can add a module and a fiscal device connection, and each connection may carry its own line.
A second property
A second property may be priced as a new installation, at a group rate, or under a per-property minimum, and the contract should say which. Ask also whether both properties run from one login or need two contracts, because that decides whether your group rate is real.
Watch outThe base fee is the advertisement; the modules are the price
A base fee that excludes housekeeping, reports, the channel connection or the guest app is not a cheap quote, it is a partial one. Ask each vendor to price the module list you expect to run in year three, not the list you need on day one, and put both figures in the comparison.
Under per-user pricing, growth also means people: seasonal headcount and turnover turn every new hire into a recurring line if accounts are named. Ask the question before July, not during.
What should you check in the currency and index clauses?
Check which currency the fee is set in, which currency you pay in, and the exact formula that raises the fee each year. Those three lines decide more of the year-three cost than the monthly figure does.
Which currency
A fee set in one currency and paid in another carries a conversion that someone absorbs. Write down who, and at which rate and date. A vendor that sets the fee in a foreign currency and invoices in yours may pass the movement to you at each invoice, at each renewal, or never; the contract decides, and the wording is usually one sentence long.
The increase formula
The index may be a fixed percentage, a consumer price index, a producer price index or a foreign index. Ask whether there is a floor below which the increase never falls, and a cap above which it never rises. Check the date the increase applies, the contract anniversary or the calendar year, and how much notice you get and how you object. Multi-year terms often take the shape of a locked first year and a capped second and third: ask for the cap in numbers, not in principle.
Payment terms and milestones
Payment may be monthly in advance, quarterly, or tied to implementation milestones. A milestone schedule protects the hotel when a project slips, because the money follows the delivery rather than the calendar.
TipPut the formula in the contract
Ask for the increase formula as a clause in the contract, not as a sentence in an email. A clause survives a change of account manager; an email does not.
Confirm the final wording of the currency and index clauses with your accountant or legal adviser before signature, since the contract, not this article, decides your case.
How do you compare two hotel software quotes like for like?
Put both quotes on the same room count, the same module list, the same support level and the same contract term, then add up three years. Anything not on that sheet is not being compared.
Normalize the scope first: send both vendors the same written module list, room count, user estimate and support expectation, and ask each to price exactly that. Split one-time from recurring on every line, so setup does not hide inside a monthly figure and support does not hide inside setup. Add a unit column, per room per year, per user per month, per interface per month: units expose which vendor is expensive at your size rather than at the size in the brochure.
The three-year total
Total three years, including the increase formula from the previous section, and show year one, year two and year three separately. The comparison table below is the shape to use.
| Line | Quote A one-time | Quote A recurring | Quote B one-time | Quote B recurring |
|---|---|---|---|---|
| Licence or subscription | ||||
| Setup and configuration | ||||
| Data migration | ||||
| Each interface | ||||
| Training days | ||||
| Support level and out-of-hours rate | ||||
| Third-party subscriptions paid directly | ||||
| Year-two and year-three increase | ||||
| Data export at exit |
The exclusion list
List what each quote excludes, side by side. The shorter exclusion list is often worth more than the lower monthly fee, because exclusions are where the year-three surprises live. Compare the support commitment as its own line: hours, out-of-hours rate, response time and resolution time.
The exit line
Add the exit cost: data export format, fee and timeline, and the notice period you must respect to leave. A quote without an exit line is a quote with an unknown at the end of it. To turn the three-year sheet into a longer plan, see building a five-year hotel IT budget from devices and licences.
What should you ask each vendor before signing?
Ask for the year-three number in writing and for the list of what is not included. A vendor who answers both clearly is telling you how the contract will feel in year two. Send the questions in writing and keep the answers.
Checklist
- What is in the base fee, module by module?
- What is the price if we add twenty rooms?
- What is the price for a second property?
- Which subscriptions do we pay directly?
- What is the increase formula and the notice period?
- Who trains new staff in month eight?
- What is the response time, and what is excluded from it?
- How do we export our data, in what format and at what cost?
- Who holds the interface credentials?
The scope questions expose the partial base fee. The contract questions expose the increase and the minimum term, quoted from the contract text rather than from an assurance. The leaving questions, export format, cost, timeline and data ownership, are the ones vendors answer most reluctantly, which is exactly why they belong in writing before signature. The same discipline applies when you commission anything from a website to a full system, as covered in comparing quotes and the contract when commissioning hotel software.
What to do next
Build the three-year sheet before you compare anything: same scope, same room count, same support level, one-time and recurring split, increase formula and exit cost included. Then ask each vendor to confirm the year-three figure in writing, and treat the answer as part of the offer rather than as a courtesy.
Frequently asked questions
Is per-room or per-module pricing cheaper for a hotel?
Neither is cheaper in general; it depends on room count and on how many modules the hotel actually runs. Per-room is predictable but rises with every room added, while per-module lets a small hotel start narrow but often leaves housekeeping, reports or the guest app outside the base. Compare both on a three-year total with the same module list.
Should a hotel pay a setup fee?
Setup covers real work: configuration, migration of rate plans and guest history, and a period of parallel running. The question is not whether to pay it but what it buys. Ask for a written scope with deliverables and dates, tie part of the payment to milestones, and agree what happens if the project runs late.
Who pays for the channel manager and door lock connections?
Interfaces are usually separate from the software fee and can carry both a one-time connection charge and a monthly line. Ask which of them the hotel pays directly to a third party, who holds the credentials, and what happens to each connection if the hotel changes software vendor.
Can a hotel get the software price fixed for three years?
Sometimes, and it is worth asking for a locked first year with a capped increase in years two and three. Read the index clause for a floor as well as a cap, and check the date the increase applies and the notice needed to object. Confirm the final wording with an accountant or legal adviser.
What happens to the hotel's data if it leaves a software vendor?
That is decided by the contract, not by the software. Ask for the export format, the cost, the timeline and the notice period before signature, and confirm who owns the data while the contract runs. A vendor who answers this clearly is also telling you how the rest of the contract is written.


