Can each property keep its own rates and room types?

Yes. Properties operate independently with their own rooms, rates and teams. What is standardised at group level is the definitions that need to be comparable — how occupancy is counted, how booking sources are categorised, what each room status means.

Can group management see everything without disrupting properties?

Access is by role. A group operations role can see occupancy, bookings and open items across the portfolio without operational access to any individual property, so reviewing performance does not mean interrupting a GM.

How many properties does WingPMS support?

WingPMS is built for growing groups in the range of two to roughly a dozen properties. Beyond that, central reservations, brand standards and enterprise distribution usually become the dominant requirement, which is a different category of system — and we would say so rather than stretch.

Can a guest record be shared across properties?

Guest records can be recognised across the group so a guest who has stayed at one property is not a stranger at another. Whether you want that is partly a data protection decision, and it is worth deciding deliberately during implementation.

For multi-property groups

Multi-Property Visibility Without Taking Control Off the Properties

A hotel group needs two things that pull against each other: consistent standards across properties, and enough local control that each general manager can run their own day. WingPMS handles both — each property operates independently, while group management sees occupancy, bookings and open items across the portfolio in one view.

Typical property profile

Properties: 2 – 12
Rooms per property: 20 – 150
Decision made by: Group operations or director
Common situation: Different systems per property

The operating problem

Three properties, three systems, and one monthly reconciliation.

Groups rarely grow into a single system. They acquire properties that already run on something, or open new ones and pick whatever was quickest at the time. Within a few years there are three ways of recording a booking and no way to compare them without a spreadsheet at the end of the month.

The instinctive fix — one central system with everything standardised — often fails in the other direction. Properties differ in room mix, market and staffing, and a configuration built for the largest tends to be awkward everywhere else. General managers then work around it, and the group is back to inconsistent data.

The workable position is narrower: standardise the things that need comparing, and leave the rest local.

Who owns this decision

Group operations director, or the owner across properties

The decision is made centrally but adoption happens locally. A group rollout that ignores the general managers produces compliance rather than use — which is exactly what makes group-level reporting unreliable.

Usually also involved

General managers at each property
Group finance, for consistent reporting
Whoever handles distribution across the portfolio

What changes

What is different three months in

Before

With WingPMS

Each property reports occupancy its own way.

One definition, applied consistently, comparable across properties.

Group figures are assembled monthly by hand.

A portfolio view reading from live property records.

A guest who stays at two properties is two records.

Guest records can be recognised across the group.

Standards exist in a document nobody opens.

Standards are how the system is configured at each property.

A new property takes months to bring into reporting.

It is set up from the group template and reporting from week one.

The workflow

How the group and the property divide

Properties operate independently
Each runs its own reservations, front desk and housekeeping, with its own rooms, rates and team.
Standards are configured, not documented
Room status definitions, booking source categories and occupancy method set once at group level.
Access follows role
Property staff see their property. Group roles see the portfolio. Owners see what they need without operational access.
Group reporting reads live records
Occupancy, bookings, source mix and open items across every property, without a monthly assembly step.
New properties inherit the template
A property opening or joining is configured from the group standard rather than from scratch.

Onboarding

One property first, then the template

Rolling out to every property simultaneously is the most common group mistake. The pattern that works is to implement one property properly, learn what the group standard should actually be, and then use that as the template for the rest.

Choose a property with a general manager who will engage honestly rather than the easiest one. The value of the first implementation is the problems it surfaces, and a property that quietly works around difficulties teaches you nothing.

01
WingPMS property
One property implemented fully, with its GM closely involved.
02
Group standard
Definitions, categories and configuration agreed from what the first implementation showed.
03
Template build
The standard configured as a template for subsequent properties.
04
Rollout
Remaining properties, sequenced by season rather than by size.
05
Group reporting
Portfolio view enabled once properties are reporting consistently.

Where to start

The parts of WingPMS that matter most here

Hotel analytics

Property-level and portfolio reporting.

Hotel PMS

What each property runs on.

Hotel operations software

Consistent operational standards across sites.

Guest CRM

Guests recognised across the group.

Direct booking

Direct business across multiple properties.

Pricing

How pricing works across a portfolio.

Can each property keep its own rates and room types?: Yes. Properties operate independently with their own rooms, rates and teams. What is standardised at group level is the definitions that need to be comparable — how occupancy is counted, how booking sources are categorised, what each room status means.
Can group management see everything without disrupting properties?: Access is by role. A group operations role can see occupancy, bookings and open items across the portfolio without operational access to any individual property, so reviewing performance does not mean interrupting a GM.
How many properties does WingPMS support?: WingPMS is built for growing groups in the range of two to roughly a dozen properties. Beyond that, central reservations, brand standards and enterprise distribution usually become the dominant requirement, which is a different category of system — and we would say so rather than stretch.
Can a guest record be shared across properties?: Guest records can be recognised across the group so a guest who has stayed at one property is not a stranger at another. Whether you want that is partly a data protection decision, and it is worth deciding deliberately during implementation.

Page last reviewed September 2026

A resort pool at golden hour with palms around the terrace

Technology for a kinder hospitality industry.

Hotel-specific assessment

Start With One Property, Properly.

We will work through a single property's operations in detail and show what the group standard would look like built from it.

Get My Free Hotel Digital Audit See WingPMS in Action