What should a multi-property hotel group demand from a PMS?

A multi-property group should demand five things before anything else: one login that reaches every property, per-property data isolation with group-level reporting on top of it, staff roles granted property by property, local tax and invoicing configured per property rather than once for the group, and pricing that doesn't change shape every time you add a room. Feature lists are easy to match between vendors; those five are structural, and a PMS that got them wrong cannot be patched into getting them right later.

"Multi-property" has to mean one account, not several

The cheapest way for a vendor to claim multi-property support is to sell you a second subscription and let you log in twice. That is two hotels on the same software, not a group on a PMS. The working version is one account that contains every property, where a manager switches between them without logging out and without a second password to rotate when someone leaves.

Ask directly: is a second property a new subscription, or a new property inside my existing one? The answer tells you which architecture you're buying.

Group reporting that doesn't end in a spreadsheet export

The reason a group buys a PMS instead of running each property on its own tool is the consolidated view — occupancy, revenue, and arrivals across the portfolio, in one place. If the only way to get a group number is to export three CSVs and add them up, you have three single-property systems sharing a login screen.

Two questions separate real group reporting from the export version: can I see revenue and occupancy for the whole group without leaving the system, and can I still drill from the group number down to the individual property and the individual reservation that produced it? A number you can't trace back to a booking isn't a report, it's an estimate.

Roles granted per property, not per group

A front-desk clerk at property A should not be able to open property B's guest list, and a regional manager should be able to open both. That's an access-control question, and it has to be answered at the property level or the group ends up with a single shared "manager" login that everyone uses — which is exactly the arrangement that makes a departing employee a security incident.

The same logic applies to any AI assistant in the stack. If your group runs an AI concierge, one property's knowledge base answering another property's guests is a data-isolation failure, not a quirk. FluxPMS's Aria answers from each property's own content only, and cross-property isolation is checked on every engine change rather than assumed.

Tax and invoicing configured per property

Groups tend to grow across borders, or at least across tax regimes, before they grow across continents. A PMS that hardcodes one country's tax logic forces the group either to run a second system for the outlier property or to reconcile that property's taxes by hand forever.

What to demand: tax rules set per property, and local e-invoicing handled as a per-property configuration. FluxPMS's taxation layer is country-pluggable for exactly this reason — Guatemala's FEL electronic invoicing is live today and further countries are added as demand appears, with each property holding its own configuration rather than inheriting the group's.

Pricing that doesn't move when you do

Per-room and per-booking pricing punish exactly the growth you're planning. A group adding a fourth property under a per-room model finds its software bill scaling with its room count in a straight line, which makes every capacity decision partly a software-cost decision.

Flat per-tier pricing removes that from the calculation. FluxPMS's Professional tier covers up to 3 properties and 50 rooms at $79/month, and Ultimate covers up to 10 properties and 150 rooms at $199/month — published numbers, no per-room or per-booking component. Annual billing is twelve months for the price of ten: $790 and $1,990 respectively. See the full pricing page and why fixed-price PMS pricing exists at all for the reasoning behind the model.

What to be skeptical about

Two claims deserve a follow-up question from any group-sized buyer. First, "unlimited properties" almost always means unlimited at a price negotiated after you've committed — get the number for your actual portfolio size in writing before the sales process ends. Second, a vendor claiming a two-way channel manager across all your properties should be asked which channels specifically, in which direction, and whether availability flows out or only in. Plenty of platforms — FluxPMS included today — do one-way iCal calendar import rather than a full two-way connection, and the distinction matters far more at four properties than at one. The difference between a PMS, a channel manager, and a booking engine is worth being precise about before comparing quotes.

The checklist to take into a demo

The short version

At group scale the deciding factors are structural, not cosmetic: one account, real consolidated reporting you can trace back to a booking, access control granted property by property, tax configuration that lives on the property rather than the group, and a price that doesn't reprice itself every time you add capacity. Run the five questions above in the demo rather than after the contract. FluxPMS's published tiers and a 30-day free trial let you test all five on your real portfolio before committing to anything.