Choosing a hotel PMS: 10 rooms vs 100 rooms

A PMS (Property Management System) is the operational core of a property: reservations, room assignment, check-in and settlement all handled in one place. The catch is that there is no absolute "best" PMS. A 10-room property run by one person and a 100-room property run by rotating staff need opposite things from the same feature set.

Start with your operating structure, not your room count

Room count is only a proxy. Three numbers actually determine what you need: how many tasks require a human touch each day, how many people perform them, and how many sales channels you sell through. Write these down first and the feature list sorts itself.

• Solo operation, 10-20 rooms: nobody is at the desk all day, so automation is the point. Reservations must land automatically, guest messages must send themselves, and everything must be checkable remotely.
• Small team, 20-50 rooms: handover becomes the bottleneck. You need a record of who changed what and when, plus a single screen that brings the next shift up to speed.
• Larger team, 50+ rooms: permissions and settlement accuracy come first. Front desk, housekeeping and management need separate access scopes, and revenue must aggregate by channel and period automatically.
• Two or more properties: check that per-property management and consolidated reporting both work. If each site runs its own system, consolidated settlement collapses back into manual work.

Channel integration: count your update points

Manual channel management is simple arithmetic. With n channels, one rate change means n update points, and one booking means n-1 inventory decrements. Workload scales linearly with channels, and every gap between updates is a window for overbooking. Double bookings are structural, not careless.

So the question is not whether a PMS "integrates" but how. Check three things: which channels are supported, whether reservations and inventory sync in both directions (one-way sync still leaves manual work), and whether you are alerted when a connection drops. That last one is often missing, and a silently broken integration is more dangerous than no integration.

Settlement: you need to see the gaps, not just the revenue

What eats time in settlement is not adding revenue up. It is finding the entries that do not match. Channel-reported amounts differ from deposits, commission rates vary by product, cancellations and refunds land the following month. If the PMS holds per-channel commission and payment status alongside the booking, reconciliation finishes on screen. If not, you are back in a spreadsheet every month.

• Is the channel commission attached to each booking? Without it you compute net revenue by hand.
• Are cancellations, no-shows and partial refunds kept as distinct states? If they are handled as deletions, you lose the audit trail.
• Can you aggregate by period, channel and room type? This is the data that justifies rate decisions.
• Can you export? A screen-only system forces re-entry when the data goes to accounting.

Rate management: is manual still viable?

Rates move with season, weekend, local events and nearby supply. Three room types across five channels is 15 combinations a day, several hundred over a month. Past that scale it is more accurate to keep human judgement but hand the calculation to a system. That is what an RMS does; and since automatic changes without a stated rationale are risky, check that you can see why a price was set.

Questions to ask before you commit

• Will you migrate our existing reservation data? What is included, and how long does it take?
• Can you show the actual list of connected sales channels? What is the process for adding one?
• What is the support path and response time during an outage? Does it hold at night and on weekends?
• What does the monthly fee include, and how does pricing change as room count grows?
• If we terminate, in what format do we get our data back?
• Do extensions like kiosks, smart locks and AI response attach to this same system, or are they separate contracts?
• Has the company that built this system ever operated a property itself?

That last question separates vendors more than you would expect. Systems built without operating experience often have plenty of features but miss the one action you need at 3am in peak season.

The order is: write your operating structure as numbers, filter candidates with the channel/settlement/rate checklists, then pin down contract terms with the question list. Following that order reduces failure risk far more than comparing feature counts.