What is a combined reservation set?

One booking that holds many stays: different check-in and check-out dates per room, different rates and packages per line, venue and banquet items in the same set, and named guest allocations per room — all managed, amended, and billed as a single booking context instead of a stack of unrelated confirmation numbers.

How does billing work across one reservation with many stays?

Through WinX's live billing structure: a master folio for the set, with charges routed, split, or transferred between folios in real time. The company pays the rooms, the guest pays their own minibar, the organiser pays the venue — decided while the stay is running, not untangled at checkout. There is no night-audit wait for any of it.

Can one reservation include venues and events, not just rooms?

Yes. A wedding or conference can hold its room block, the ballroom or meeting venues, and banquet/catering items in the same booking context, with event billing tied to the same structure. One organiser, one context, one bill — instead of a rooms system and an events system meeting in a spreadsheet.

Insights

One reservation, many stays: group bookings without the jigsaw

Real bookings are rarely one guest, one room, one date range. A family lands Tuesday, the grandparents join Thursday. A project team books eight rooms with staggered arrivals, a meeting room, and a farewell dinner. A wedding is a room block, a ballroom, and three different rate deals. Most systems answer all of this the same way: shred it into separate reservations and let the staff hold the pieces together.

The pain: a stack of confirmation numbers that don't know each other

Once a real-world booking is split into fragments, every later step inherits the fragility. The organiser calls to move the whole group by one day — someone must find and amend six reservations without missing one. A room posts its deposit against the wrong fragment. One guest extends, and their new night lands outside the group rate. At checkout, the front desk plays detective: which of these folios belong together, and who is actually paying for what?

The guest experience shows the seams too — the person who booked everything gets six confirmation emails and still has to explain the arrangement at the desk.

Why it happens: the reservation is the atom

In most PMSs, the reservation is the indivisible unit: one stay window, one rate, one room. Anything more complex than that has nowhere to live, so it's decomposed at booking time and reassembled by hand at billing time. Group modules bolt a "block" on top — but a block is a fence around inventory, not a booking: it holds rooms, not the dates-rates-venues-people structure of the actual arrangement.

How WinX fixes it: the combined reservation set

In WinX, one booking can hold the whole arrangement — this has been core to the platform since day one, not a bolted-on module:

Mixed dates in one booking — each room line carries its own check-in and check-out; staggered arrivals and extensions live inside the set instead of breaking out of it.
Mixed rates and packages per line — the couple on the honeymoon package, the team on the corporate rate, the late-joiner on best-available: one context, line-level pricing.
Venues in the same set — the ballroom, the meeting room, the banquet items (BDI) sit alongside the room lines, with event billing tied to the same structure.
Named guest allocations — who sleeps where isn't a sticky note; each line carries its guests, so registration, housekeeping, and in-house lists are right automatically.
One billing structure, live — a master folio with charges routed, split, or transferred in real time: rooms to the company, minibar to the guest, venue to the organiser. Decided during the stay, not untangled at checkout.
Amendments touch the set, not six fragments — move the group a day, and it's one operation on one booking context.

The shift: the system's data model finally matches the booking's real shape — so the complexity lives in the software, not in your front-desk team's memory.

Proven where bookings are genuinely complicated

Combined reservation sets have carried real complexity for years: Manila Ocean Park + Hotel H2O, where hotel stays and park visits belong to one arrangement; Petronas Pengerang, with 1,000+ rooms of long-stay and rotation patterns; I'M Hotel, mixing hotel, spa, and serviced-residence stays; and convention operations where the room block and the ballroom finally live on the same booking. The live routing and splitting that makes the billing work is the same engine behind one bill across hotel, park and spa.

Common questions

What is a combined reservation set?: One booking holding many stays — different dates per room, different rates and packages per line, venues in the same set, named guests per room — managed, amended, and billed as a single context.
How does billing work across one reservation with many stays?: A master folio with live routing, splitting, and transfers between folios: the company pays the rooms, guests pay their own extras, the organiser pays the venue — decided while the stay runs, not at checkout.
Can one reservation include venues and events, not just rooms?: Yes — room block, ballroom, and banquet items in one booking context with event billing tied to the same structure. One organiser, one bill.

Bring your most complicated booking — see it fit in one reservation.

Request a WinX demo