Guide

Multi-property configuration

If you run a group of four to forty hotels on Profitroom Multi-Property, you already know that the sanity of your revenue team depends on how well the master versus property configuration is separated. Here is how our modules handle groups, and the setup we recommend after onboarding around 40 Polish hotel groups.

Groups on Profitroom — a quick recap

Profitroom Multi-Property sits above individual properties. A property has its own Establishment ID, rate plans and channel manager mappings. The group owns the roster of properties, sets central pricing policy, and lets you push shared campaigns. Every Suite Profit module can be enabled at group level, property level, or both.

Connect at group level first

Rather than generating one API key per property, ask your Profitroom admin for a group-level key with scoped access to every property in the roster. In the Suite Profit dashboard, open Settings, Connections, "Add Profitroom Multi-Property". Paste the key. The dashboard polls the group and lists every property with its city and star rating. You tick which properties should participate in each module.

Master rate grid

For rate-touching modules such as AutoPricer, we recommend defining a master rate grid at group level. The master grid holds:

  • The reference BAR by room class (standard, superior, suite).
  • A rate-plan skeleton — BAR, NRF, breakfast-included, weekly stay, corporate.
  • The floor and ceiling logic as a formula, not as absolute PLN values (see below).
  • Compset assignment rules — how compset members are chosen per property.

Per-property multipliers and offsets

Absolute PLN values almost never make sense at group level — a standard double in Sopot and one in Lublin should not carry the same floor. We use two per-property adjustments:

  • Multiplier — multiplies the master reference BAR. Sopot might be 1.35, Lublin 0.82. Applied first.
  • Offset — a fixed PLN nudge added on top, useful for one-off market corrections such as a temporary construction site next door.

Multipliers can be edited weekly by the revenue director; offsets are usually set by property GMs.

Override precedence

Every setting in a Suite Profit module resolves through a precedence stack, from lowest to highest priority:

  • Group default.
  • Regional default (optional layer for groups with a Warsaw cluster and a Tricity cluster, say).
  • Property override.
  • Rate-plan override.
  • Date-range override (a hard-coded value for the 24 December to 1 January window, for example).

The last matching layer wins. In the dashboard you can hover any setting and see which layer resolved the current value — no more "why is this rate showing this way" mystery.

Rolling out a change across the group

Say you want to lower every property's ceiling from 2.4x to 2.2x. Open the master grid, change the value once, click "Simulate impact". The dashboard runs the change against the next 90 days for every property and shows expected ADR change, RevPAR change and any breaches of local overrides. If the simulation looks clean, click "Publish to selected properties". If not, you can override the master change per property before publishing.

Reverting a bad publish

Every publish is versioned per property. If a master change goes wrong in only three of your fifteen properties, revert just those three — the audit tab lets you pick versions per property in the same view. Revert takes 60-120 seconds to reach Profitroom and syndicate to your channel manager.

Guest data across properties

The Guest module deduplicates guest profiles across the group when the email or the phone number matches. A guest who stayed in Wrocław last October will be recognised on booking at your Warsaw property. Deduplication respects data-minimisation defaults — we do not share stay history to a property the guest never booked into unless you tick "Share stay history across the group" in the module settings.

Reporting

Every metric — RevPAR, ADR, occupancy, WhatsApp response rate, direct booking share — is available at group level, at property level, and at a custom cluster level. Cluster grouping is manual: you name a cluster (Tricity, Silesia, Mazovia) and drag properties into it. Reports are exportable as CSV or piped into a Google Sheet through a signed webhook.

Onboarding order that works

  • Week 1 — connect the group, ingest the roster, no modules enabled yet.
  • Week 2 — configure the master rate grid and one pilot property.
  • Week 3 — verify pilot property numbers against a manual baseline.
  • Week 4 — roll out to the remaining properties in waves of five.

Access control across the group

Give property GMs a scoped role that lets them read group-level settings but only edit their own property overrides. Revenue directors get group edit rights. IT gets connection-management rights but not rate rights. All of this is configurable in Team settings.

Next steps

Open modules catalog Back to guides