Hotel software contracts: clauses to read before you sign
A hotel software contract decides what happens when the system fails or when you leave. Read seven key clauses on service levels, data ownership, exit terms, and liability before signing.
Contents
Key takeaways
- A demo shows the system on a good day; the hotel software contract decides what happens at 23:00 on a full night and on the day you leave.
- An availability figure means nothing without its measurement window, its exclusions and the remedy you actually receive.
- Data ownership is one sentence; getting the data back is a format, a deadline and a price, so ask for all three in writing.
- Every interface in the contract is maintained by someone; find out who, and who pays when the partner changes its side.
- Liability caps and exclusions decide how much of a bad night the vendor shares, so read them before you discuss the price.
A hotel software contract is the document that decides what happens when the system fails and when you leave. Read seven things before signing: service levels and support hours in high season, data ownership and export format, exit and transition help, price changes and minimum term, interface maintenance, personal-data roles, and liability limits.
The sales call ends with a promise that the system will be there when the lobby is full at midnight. The contract is where that promise either becomes a duty with a number and a remedy attached, or stays a friendly sentence in an email. After reading this, you will know which clauses to find, which question to ask about each, and which parts to hand to your legal adviser before you sign.
What should a hotel software contract cover?
It should turn every promise from the demo into a written duty, and it should answer four questions: what the system must do, how fast help arrives, who owns the data, and how you leave.
The main agreement and its annexes
Ask for the whole package before you sign: the main agreement plus its annexes. The service description, the service levels, the data terms and the price schedule usually live in the annexes, and that is where the operational detail sits. Make the service description name the modules you bought, such as reservations, front desk, housekeeping, billing, restaurant sales, reports and compliance, rather than a product name alone, so the scope is readable without a salesperson.
Fix what you evaluated. If the vendor may change the system freely, the change process and the notice you receive should be written down. Ask what is not included: training, data migration, extra interfaces, additional properties, storage and after-hours support are commonly priced separately, and the first invoice is a bad place to discover this. Keep the vendor's written answers to your questions as an annex, so the promise survives the person who made it. If you are still selecting, our guide to questions to ask a hotel PMS vendor before you shortlist pairs well with this reading list.
Who reads which clause
Agree who on your side reads which part. The general manager reads service levels and support hours, finance reads price, indexation and payment terms, and your legal adviser reads termination, liability and personal data. Read the contract against the questions you asked during selection; a vendor that answers them in writing before signing is easier to hold to afterwards.
| Clause group | The question to ask | Why it decides a bad night |
|---|---|---|
| Service levels | What availability, measured over what window, and what do I get when it is missed? | A percentage without a window and a remedy is decoration. |
| Support hours | Who answers at 02:00 in August, and in which language? | Incidents arrive when the lobby is full. |
| Data | Who owns it, in what format, how fast, at what price? | Ownership without export is a slogan. |
| Exit | How much notice, what transition help, what access afterwards? | The cheapest time to negotiate exit is before you sign. |
| Price | How can it change, with what notice, and how long am I committed? | Indexation and renewal decide your five-year cost. |
| Interfaces | Who maintains each one, and who pays when the partner changes? | You do not control the other side. |
| Personal data | Who is controller, who is processor, where does processing happen, who do I call in a breach? | A legal question for your adviser. |
| Liability | What is the cap and what is excluded? | It decides how much of a bad night the vendor shares. |
What do service levels actually promise?
A service level is a measurable promise with a remedy attached. Without a measurement window, a list of exclusions and a remedy, an availability figure is marketing.
Availability, response and resolution
Availability needs a definition of what counts: the booking page, the front desk, billing and reporting may be measured separately, and a single headline figure hides which part failed. Check the measurement window, a month or a year, and the exclusions: scheduled maintenance, your own internet connection and events outside anyone's control are often removed from the calculation.
Response time and resolution time are different promises. A fast first reply that fixes nothing is still a bad night at the front desk. Severity levels should be defined by your operation, not the vendor's convenience: cannot check a guest in and a slow report are not the same event, and the clock should start when you report, not when someone picks it up.
Support hours in high season
Write support hours for your season. A weekday office-hours line is weakest exactly when you are fullest, so ask about nights, weekends and public holidays, and which languages the support team speaks. Ask who measures and what you receive: a monthly report, a dashboard, or nothing at all. Ask what the remedy is. Service credits are common and are usually a fraction of the monthly fee, so treat them as compensation, not recovery, and pair them with a written fallback procedure for your own team.
Watch outRead the small print with the figure
An availability figure is only as good as its small print. Find the measurement window, the excluded hours and the remedy in the same paragraph; if they sit in three different documents, ask the vendor to put them together in writing before you sign.
Who owns the data, and in what format do you get it back?
The contract should say the hotel owns its data, and then it should say how that data leaves: which records, in which format, within how many days and at what cost.
Ownership is a sentence, portability is a project
Ownership and portability are separate clauses. A sentence saying the data is yours is worth little if the only export on offer is a printed report. Name the records: reservations and their history, guest profiles, folios and invoices, rate and availability history, housekeeping and maintenance records, user accounts and the audit trail. Name the format. A common machine-readable format, for example one spreadsheet file per table, is portable; a proprietary backup file is not, unless the vendor also promises to restore it for you.
Ask for a sample export before you sign, on demo data if you are not yet a customer. A sample shows the columns you will actually receive, which is more useful than a description. Ask how fast and at what price: a self-service export you can run any day is a different promise from a paid project scheduled weeks ahead. Ask the receiving vendor what it needs, then check that the export you are promised can be read by it. The time to discover a format problem is before you sign, not during a cutover, so it is worth reading about what to move, check and leave behind in a PMS data migration.
Personal data inside an export carries duties of its own: who may receive it, how long you keep it and how it is deleted afterwards is a question for your legal adviser.
ChecklistExport questions to get in writing
- Which records are included, table by table
- Which file format, and can I open it without the vendor's software
- How many days after I ask
- Is it self-service or a scheduled project
- What does it cost
- Does it include history and the audit trail, or only current records
- What happens to the data after the handover, and how is deletion confirmed
What happens on the day you leave?
The exit clause should tell you how much notice you give, what help you receive during the transition, and what access you keep afterwards.
Notice, renewal and the calendar entry
Find the minimum term, the renewal rule and the notice deadline, then put the deadline in a shared calendar a quarter earlier than required. Most unpleasant renewals are a missed date, not a bad system. Check the form of notice: an email to a named address is easier to prove than a call to an account manager. Termination for cause should list what counts as a serious failure, for example repeated missed service levels, a data breach or insolvency, and whether you can then leave without penalty.
Transition help and read-only access
Transition help should be counted in days or hours, with a price and a named contact, and it should say what it covers: data handover, parallel running, and training the incoming team. Read-only access after termination is worth more than a promise of a full export: a period in which you can still open history and old invoices protects you during a dispute.
List what must be switched off or transferred: channel connections, payment settings, the e-invoice integrator, door-lock systems, domain names and email addresses. Ask what happens to guest-facing services, such as the booking page and any links you have published, and who shuts them down and when. Close the money: the final invoice, any prepaid amount left, and what happens to the data once the retention period ends.
Key pointNegotiate the exit before you sign
The best time to negotiate the exit is before you sign, when the vendor still wants the deal. Ask for transition help counted in days, read-only access counted in months, and a named contact, and have all three written into the contract rather than agreed by email later.
How can the price change, and how long are you committed?
Read the price schedule for what is fixed, what is indexed, how much notice an increase needs, and when the contract renews itself.
Indexation, notice and auto-renewal
Ask what the unit is: per room, per user, per property, per transaction or a flat fee. The same monthly figure behaves very differently as you add rooms, staff or a second property. An annual increase tied to a published index is a normal arrangement; an open right to change prices with short notice is a different thing, and it should be read as one. Ask what happens when the price rises: can you terminate without penalty, and by which date? A price clause without an exit is a one-way door. Find the auto-renewal term and the window in which you must give notice, and check whether the renewal price is stated or left open.
What sits outside the monthly fee
List what sits outside the fee: interfaces, extra modules, training, data migration, storage, support tiers, additional properties and after-hours cover. Compare total cost over the term, not the first-year price: multiply the fee by the term, add the increases you can predict, and add the one-off costs you were quoted separately. Check payment terms and currency, including which exchange-rate basis applies and what happens if the rate moves between invoice and payment. For background, our guide to how hotel software is priced covers the models behind these numbers.
TipPut three dates in a shared calendar on signing day
On the day you sign, put three dates in a calendar the general manager and finance both see: the notice deadline for renewal, the date a price increase must be announced, and the end of the minimum term. A contract you cannot find the dates in is a contract you renew by accident.
Who keeps the interfaces working when a partner changes?
Every interface has two sides, and the contract should say who maintains your side, who pays when the other side changes, and what notice you get when a connection stops working.
The interface annex
List the interfaces in an annex by name and purpose: booking sites or a channel manager, the payment provider, the e-invoice integrator, guest identity notification, door locks, fiscal devices, accounting, and restaurant or spa systems. Ask who maintains each one and what the vendor's duty is when the partner changes its side: a fix within a stated time, or a general best-efforts sentence. The difference shows up on the night the connection drops. Ask who pays: a one-off connection fee, a recurring per-interface fee, and development work for a new connection are three different costs.
When the other side changes
Ask what happens when an interface is discontinued: the notice period, the alternative offered, and whether you can leave without penalty if the alternative does not suit you. Read integration promises carefully: no vendor controls a booking site, a payment provider or a fiscal device maker, so a promise of a full integration describes work on one side, not a guarantee about the other. Ask for the interfaces that work today and for references you can call about them; a connection shown in a demo is not the same as a connection someone maintains. If the contract includes AI features or an assistant, the same questions apply, plus what it may do without a person and what is recorded when it acts. Our questions to ask an AI vendor before buying for your hotel covers that ground.
What do the personal-data and liability clauses leave to you?
These two clauses decide who answers to a guest or an authority, and how much of a loss the vendor shares. Both need your legal adviser, not a blog.
Controller, processor and processing location
On personal data, the contract should say who is the controller and who is the processor for guest data, what the processor may do with it, where processing happens, which subcontractors are involved, and how a breach is reported to you. Ask about retention and deletion: how long data is kept after the contract ends, and how deletion is confirmed in writing. Ask where data is stored and processed and get the answer in writing; if processing outside Türkiye matters to you, say so before signing, not after. Treat certifications as something to ask for and verify, never as a requirement or a credential: ask what was audited, by whom, for which scope and on what date.
Caps, exclusions and insurance
On liability, find the cap, which is often the fees paid over a period, and the exclusions, which often cover indirect loss, lost profit and lost bookings. Then ask whether the vendor carries insurance. Check the indemnities: who defends whom if a third party makes a claim, and for what. How these clauses apply to your hotel, and what the law requires of you, is a question for your legal adviser and your accountant. This article describes what to look for, not what your contract means.
NoteGeneral terms, not legal advice
This section describes clause types in general terms so you can ask better questions. It is not legal advice, it cites no articles, and it cannot tell you how a clause would be read in your case. Take the signed package to your legal adviser and your accountant.
Before you sign
Ask the vendor for the annexes, a sample data export and the interface list, put the renewal deadline in a calendar, and read the whole package with your legal adviser. The clauses above are one question in seven parts: what happens when the system, the price or the relationship changes, and who carries the cost when it does.
Frequently asked questions
How long should a hotel software contract be?
Length is not quality. A short agreement with thin annexes is worse than a longer one with a readable service description, service levels, data terms and an exit clause. Ask for the annexes first; if the operational detail is missing, the length of the main agreement will not help.
Can a hotel negotiate a software contract?
Yes, and the leverage is highest before signing. Transition help, read-only access after termination, notice periods, the interface list and the right to leave after a price increase are the usual places where a vendor can move. Ask in writing, and keep the answers with the contract.
What is a service credit, and is it enough?
A service credit is a reduction on a future invoice when a service level is missed, and it is usually a fraction of the monthly fee. It compensates for an outage but does not recover a bad night, so pair it with a written fallback procedure for your team and an exit right after repeated failures.
Do I need a lawyer to read a PMS contract?
For termination, liability and personal-data clauses, yes. A manager can check service levels, support hours and price mechanics, but how a clause applies to your hotel and what the law requires of you depends on your case. Have your legal adviser and your accountant read the signed package.
What should I ask about data export before signing?
Which records are included, in which file format, how many days after you ask, whether it is self-service or a paid project, what it costs, and whether history and the audit trail come with it. Ask for a sample export, and confirm with the receiving system that it can read that format.