How hotel software is priced: licences, subscriptions and the costs around them
Hotel software has no list price because vendors charge in different units. Learn to compare licences and subscriptions, spot hidden costs, and evaluate total ownership over the full term.
Contents
Key takeaways
- Hotel software has no list price because vendors price different units, and the unit decides how the total moves when the hotel changes.
- A licence buys the right to use a version of the software; a subscription rents a running service, and hosting and updates usually come with the subscription only.
- The recurring fee is only part of the cost: setup, data migration, training, interfaces, hardware and the e-document integrator usually sit on separate lines.
- Two quotes can only be compared as total cost per room per month over the full term, with every third-party charge on its own line.
- The price that matters is the one in the renewal clause, not the one on the first invoice.
Hotel software has no list price because vendors charge in different units: per room, per property, per user or per module. A PMS, the property management system that runs reservations, rooms and bills, is only part of the total. Setup, migration, training, interfaces, hardware and renewal terms decide the real cost.
For example, two vendors quote the same forty-room hotel. One sends a monthly figure per room; the other sends a single fee per property plus a setup charge. Neither number tells you which is cheaper, because the two are counting different things. After reading this article you will be able to take any hotel PMS pricing quote apart, name every cost around the recurring fee, and put two competing quotes on one sheet where they can actually be compared.
Why is there no list price for hotel software?
Because vendors price different units, and the unit decides how the total moves as the hotel changes. A published price would only be true for one size of property with one set of modules, so vendors quote instead of listing.
The four units vendors use
The four common units are per room, per property, per named user and per module. A per-room quote grows with the building: add twenty rooms and the fee rises. A per-property quote does not, which makes it attractive for large properties and expensive for small ones. A per-user quote grows with staffing and shift patterns, so a hotel running three shifts pays for more users than one running a single desk.
Each unit also hides a step structure. Ask whether the unit price steps down in bands as room count rises, and where the steps sit. A banded price is not a straight line, so extrapolating from a small hotel to a large one gives the wrong answer. Ask also whether there is a floor: a minimum monthly charge that applies even when the property is small or partly closed for the season.
What the unit hides
The unit is only half the quote. Ask which modules sit in the base price and which are added: reservations, front desk, housekeeping, billing, restaurant and bar sales, reports, compliance, channel manager, guest app. A quote that looks cheap may simply carry fewer modules, and the missing ones may be exactly what your property needs.
Term length interacts with the unit. A per-room price over three years and a per-property price over one year are not comparable until both are converted to the same denominator. For a small property, the unit matters less than the floor and the module list; a pension or a boutique hotel often pays for capacity it will never use. If you run a small property, what a small hotel really needs from software is a shorter list than the market's average quote implies.
Key pointThe only comparable number
Total cost of ownership over the full term, divided by rooms and by months, with every third-party charge included. Everything else is a headline.
Before comparing prices at all, work through the questions to ask hotel PMS vendors; scope questions come before price questions, because a quote for the wrong scope is not a price at all.
Licence or subscription: what is the difference?
A licence buys the right to use a version of the software; a subscription rents a running service, usually with hosting and updates included. The difference shows up in cash flow, in updates and in what happens when you stop paying.
What a licence does not give you
In hotel software, a licence is a right to use, not ownership. You cannot modify the code or resell it. A licence is normally perpetual and paired with an annual maintenance and support fee; major version upgrades may be charged separately, and hosting, servers and backups are your responsibility. A subscription is recurring: hosting, updates and support usually sit inside the fee, and the software stops when the payments stop.
Some vendors use the words loosely and call a subscription a licence fee. The test is what happens on the last day of the term: does the software keep running, and in what form? Ask that question in writing. Also ask what you may export and keep at the end of the relationship, because your guest history and financial records are yours regardless of the model.
Comparing the two over one horizon
Compare the two over the same horizon, for example three years, and put the licence purchase, the annual maintenance and your own hosting cost on one side against the subscription on the other. Ask your accountant how each is treated in your books; the accounting and tax treatment is their call, not the vendor's. Hosting location and who operates the servers change the support and risk picture too, so read this choice together with the cloud versus on-premise trade-off.
| Licence | Subscription | |
|---|---|---|
| Payment shape | Large first payment, annual fee after | Even monthly or annual payments |
| Updates | Major versions may cost extra | Usually included |
| Hosting and backups | Your responsibility | Usually the vendor's |
| Support | Annual maintenance fee | Inside the fee |
| Fault at 22:00 | Depends on maintenance terms | Depends on coverage hours |
| If you leave | Software may keep running | Software stops |
| Ask your accountant | Depreciation treatment | Operating expense treatment |
What costs sit outside the monthly fee?
Setup, data migration, training, interfaces, hardware and the e-document integrator usually sit outside the recurring fee, and they are where two quotes for the same hotel diverge most.
Setup or implementation covers configuration of room types, rate plans, taxes, outlets, user roles and reports. It is charged as a fixed fee or as days, so ask which days are included and what happens when the work runs longer. Data migration is its own line: what moves, what is deliberately left behind, and who checks the result before the old system is switched off. What to move, check and leave behind in a PMS migration is a decision worth making before the quote arrives, not after.
Training is charged on-site or remote, per session or per role. Ask whether retraining is included when staff turnover brings new people to the front desk, because in most properties that happens every season.
The interface question: who invoices it
Interfaces are the quiet cost. Door locks, restaurant and bar points of sale, the channel manager, the e-document integrator and the guest identity notification each have their own provider. Ask who charges for each one: the PMS vendor, the other provider, or both, and who supports it when it breaks. Electronic invoices are issued through a licensed integrator, which is a separate commercial relationship from the PMS contract and is usually billed on its own terms. How PMS integrations work in plain words explains the mechanics behind these lines.
Hardware and the physical layer
Hardware covers key card encoders, printers, payment terminals, network equipment, plus installation and cabling. Hardware is often the largest line nobody puts in the first email. Ask for every line itemized in writing, with the name of the company that invoices it. A bundled figure cannot be compared, and it hides who to call when something fails.
ChecklistDemand these as separate lines on any quote
- Setup and configuration
- Data migration and validation
- Training per role
- Each interface named individually
- Hardware and installation
- E-document integrator
- Go-live support days
- Annual maintenance or renewal
- Price increase clause
- Data export at exit
What does a support level actually include?
A support level is defined by coverage hours, channels, response time and what the vendor will not do, not by the word priority. Ask for those four in writing.
Response time versus resolution time
Separate response time from resolution time. Most contracts commit to when a human replies, not to when the fault is fixed; a fast reply on a fault that takes two days is still two days. Coverage hours matter more: business hours only, extended hours, or round the clock. A hotel's difficult moments are evenings, weekends and public holidays, so check the calendar, not the slogan. Channels and language matter too: phone, email and ticket systems, and whether support answers in a language your night team speaks.
Escalation between vendors is the part nobody reads until it hurts. When the channel manager and the PMS disagree about availability, whose ticket is it, and who owns the path between the two providers? Also ask what is billable inside the support contract: new reports, changed rate logic, custom exports and extra training days are usually chargeable work even for supported customers.
The gap between two vendors
Go-live support is a separate question: how many days around cutover, on site or remote, and whether the first month after launch is covered. Ask for the last two support agreements as references, or at least for the escalation matrix in writing; the answer tells you more than the tier name.
NoteThree questions that separate support levels
What are your coverage hours on a public holiday? What is your committed response time for a fault that stops check-in? Who owns a fault that sits between your system and the channel manager?
How do renewals, price increases and minimum terms work?
The number that matters is the price in the final year of the term, not the first invoice, so read the renewal clause before you read the fee.
Indexation and caps
Check the minimum term and notice: how long you are committed, how many days' notice to cancel or renegotiate, and whether the contract renews automatically if nobody acts. Price increases come as a fixed annual step or an index-linked one. Ask which index, whether the increase is capped, and whether it applies to modules added later. Module creep is its own trap: adding a module mid-term, at what price, and whether adding it restarts the term or the increase schedule.
What happens when the hotel changes size
Room count changes cut both ways. A renovation that adds rooms, or rooms taken out of service for a season: ask whether the fee steps up automatically and whether it ever steps down. If a second property is on the horizon, ask whether the same terms apply or whether each property is negotiated from scratch. Exit terms belong in the same reading: notice period, final invoice, data export format, and how interfaces are handed over so the door locks and the channel manager keep working after the switch. Write the renewal terms into your comparison sheet in the same units as the fee, so the year-three number sits next to the year-one number.
Watch outUncapped increases
A multi-year term with an uncapped annual increase is a price you have not been quoted. Ask for the cap, the index and the notice period in writing before signing.
How do you compare two quotes on the same hotel?
Put both quotes on one sheet, in the same units, over the same term, with every third-party charge on its own line. Then compare totals and risk, not headline fees.
One sheet, two vendors
Fix the scope first: number of rooms, outlets, interfaces, named users, properties and term. Two quotes with different scopes are not two prices for the same thing. Convert both to cost per room per month over the full term, with setup, migration, training, hardware and third-party fees spread across the same months. Mark every line as included, extra or unknown, and write the name of the company that invoices it; unknown lines are the ones that decide the outcome.
| Line item | What to ask each vendor | Why it changes the total |
|---|---|---|
| Recurring fee | What unit, what floor? | Sets the base of the comparison |
| Setup | Fixed fee or days? | Diverges most between quotes |
| Migration | What moves, who validates? | Scope hides or adds weeks |
| Training | Per role, retraining included? | Recurs with staff turnover |
| Interfaces | Who invoices each one? | Third-party fees sit outside |
| Hardware | What must be replaced? | Often the largest hidden line |
| Support | Coverage hours, response? | Defines real risk |
| Renewal | Index, cap, notice? | Decides the final-year price |
| Exit | Export format, handover? | Sets the cost of leaving |
Reading the result
Score the non-price lines the same way: coverage hours, response commitment, migration scope, exit and export rights. Then send both vendors the same sheet and ask them to fill it in and return it in writing; a vendor who will not fill a sheet has told you something useful. For example, a hotel comparing two systems might find that one carries a lower recurring fee but a larger setup and two interfaces billed by third parties, which reverses the ranking once both are spread over the term. Decide on total cost plus the risk you can see.
Build the sheet before the next quote
Build the one-page comparison sheet for your own property before you read another quote: rooms, outlets, interfaces, users, term, and a column for who invoices each line. Then ask every vendor to fill the same sheet. The parts of this article fit together through that sheet: the unit explains why list prices do not exist, the licence or subscription choice sets the shape of the payment, the surrounding costs and support terms fill the rows, and the renewal clause decides the number you will actually be paying in the final year.
Frequently asked questions
Is per-room pricing cheaper for a small hotel?
Not automatically. The unit matters less than the floor and the module list: a small property may pay a minimum charge that makes the per-room rate irrelevant, or pay for modules it will never open. Ask for the total over the term, the minimum monthly charge, and what happens if the room count changes.
Do I own the software if I pay a licence fee?
No. A licence is a right to use a version of the software, not ownership of the code; you cannot modify or resell it. What you should secure in writing is the right to export your own data at any time, in a usable format, and a clear answer on what happens to your access if the vendor stops supporting the product.
What should a data migration line in the quote contain?
It should name what moves, such as in-house reservations, guest history, open balances, and company and agency records; what is deliberately left behind; who validates the result and when; and what the fallback is if the cutover does not complete. A migration quoted as a single figure without a scope list cannot be compared with another vendor's.
Why is the channel manager priced separately from the PMS?
Because it is a separate service with its own provider relationship, even when the two are tightly connected. Ask who invoices it, who supports it when availability and rates disagree, and what the escalation path is between the two companies. The interface existing does not mean one contract covers both.
Can we change systems in the middle of the season?
It is a risk decision, not a pricing one. Ask each vendor what go-live support is included, how many days the old system stays readable, and how open balances and in-house guests are carried across. Plan the switch for a low-occupancy window and keep the old system read-only for a period afterwards.