Insights
Which hotel PMS connects to SiteMinder, and what happens to an OTA booking after it arrives?
Every hotel that sells on Booking.com, Agoda or Expedia has asked two questions of its PMS vendor: can it talk to our channel manager, and what exactly happens when a booking comes back? The first answer for WinX is short: yes, through SiteMinder. The second is the one that decides whether your front desk re-keys bookings at 11 p.m.
The pain: the channel manager is connected, the work is not
The booking arrives as an email. Many "integrations" stop at availability and rates going out. The reservation itself lands in an inbox and someone types it into the PMS: name, dates, rate, often with a typo, always with a delay. Until it is typed, the room is still for sale.
The hotel sells from allotments. Each channel is given a block of rooms. Too small and the OTA shows sold out while rooms sit empty; too large and the hotel oversells its last weekend. Someone spends every afternoon moving rooms between buckets.
Nobody can say what the OTAs cost. Commission is paid from a statement weeks later, so the share of business by channel, and what it costs, is a spreadsheet nobody trusts.
Why it happens: a PMS that was never built to be the master
Channel managers do one thing well: they take one set of availability and rates and push it to many OTAs, then collect the bookings. Everything depends on what feeds them. A PMS designed around nightly batches cannot offer a live room count, so it offers an allotment instead. A PMS that stores bookings but not guests cannot create a profile from an OTA booking, so it creates a reservation with a masked email and nothing else. The channel manager is blamed for problems that start a layer below it.
How WinX does it: mapped once, then it is just the room pool
- SiteMinder is the channel manager WinX connects to. It is the only one, and WinX says so plainly on its integrations page. SiteMinder then reaches Booking.com, Agoda, Expedia, Trip.com and the other channels it supports; you switch channels on and off in SiteMinder without touching the PMS.
- Three mappings, set up once. Each WinX room type is mapped to a SiteMinder room code, each rate code to a rate plan, and each OTA to an agent code. That last one is what lets WinX report business by source and cost per channel later.
- Availability goes out from the live room pool. WinX has no allotments. When the front desk, the group desk or your own booking engine sells a room, the count that SiteMinder distributes is the same count, at the same moment. The last room can be on every channel at once because only one of them can sell it.
- A booking lands complete. It arrives in WinX flagged as a channel-manager reservation with its OTA agent code, a folio and a guest profile. Nobody types it. The reception board shows it as an arrival with the source visible.
- Direct bookings share the pool. The WinX booking engine on your own domain sells from the same live availability, which is what makes growing direct share safe: no "sold out" on your site while the OTA still sells.
- Channel mix is a report, not a spreadsheet. Because every reservation carries its agent code, revenue by channel and the commission it attracts are queries on live data.
Where it matters
The mapping pays off most where the room pool is busiest. Petronas Pengerang runs more than 1,000 rooms on one WinX installation; at that scale a stray allotment is a fleet of empty rooms. At the other end of the spectrum, Batu Batu, a 29-villa private island, chose to sell entirely through its own WinX booking engine with no OTA at all. Both run on the same live pool; the channel strategy is the owner's choice, not the software's constraint.
Common questions
- Does WinX connect to Booking.com, Agoda and Expedia?
- Yes, through the SiteMinder channel manager. WinX maps room types, rate codes and OTA agent codes to SiteMinder, which distributes to the channels you enable and returns their bookings into WinX. There are no direct OTA connectors in WinX; SiteMinder is the distribution layer.
- Which channel managers does WinX support?
- SiteMinder. It is the only channel manager WinX connects to today, and it covers the major OTAs and metasearch channels. If your property is on another channel manager, that is a migration conversation, not an integration one.
- Do I need to give each OTA an allotment?
- No. WinX distributes availability from its single live room pool, the same count the front desk and the booking engine use. Allotments exist to protect a PMS that cannot offer a live count; WinX does not need the protection.
- What does the front desk see when an OTA booking arrives?
- A reservation on the reception board, flagged as a channel-manager booking with its OTA source, a folio ready for check-in, and a guest profile that will recognise the guest next time. Nothing is re-keyed.
- Can I see how much business comes from each OTA, and what it costs?
- Yes. Every reservation carries its OTA agent code, so revenue by channel and the commission it attracts are reports on live data rather than a reconciliation against the OTA statement weeks later.
Bring your SiteMinder room and rate plan list. We map it in the demo.
Request a WinX demo