When a hotel guest is one person, but five systems hold the stay
In a joint essay, Cendyn and The Anything Group argue that the guest is still one person, while the hotel's systems often hold five fragments of the same stay.
A joint essay from Cendyn and The Anything Group, published on 20 October 2026, starts with a familiar stay. A couple books a suite, adds a spa treatment later, and pays the deposit and the bill on different cards. By checkout, five systems hold five pieces of that visit, and none holds the whole story.
This is not a single tool failing. It is what a hotel gets when the property management system, the booking engine, the payment processor and the CRM were each chosen separately, and never resolved into one guest record. Guests now judge that friction against the rest of their phone, not only against other hotels.
The essay cites figures, without naming an independent study, that only 11% of operators report a fully integrated stack, 27% spend more than eleven hours a week reconciling data, and only 15% have strong confidence in their own operational data. Read those as the authors' citations.
Cendyn argues that teams cannot work from the same guest until booking, loyalty and sales records sit in one profile. It points to Cendyn CRS and Cendyn Booking Engine for consistent rates and availability, to Cendyn Rate Match for rate agreement across channels, and to Cendyn CRM so folio spend can inform marketing without storing card credentials. Case studies in the piece are Cendyn's own figures.
The test is practical: how often the same guest is retyped, how long the team spends reconciling reports, and which system is the record of who that guest is.
What this means for hoteliers
- Map every point in a stay where a person still carries data from one system to another, and time that work in a normal week.
- Ask whether Cendyn CRM, or your current CRM, can see folio spend and the booking record without holding payment credentials.
- Before adding another tool, test whether it will write back to the same guest profile as the booking engine and the central reservation system.
- Treat vendor case-study figures as a prompt for your own numbers: direct share, time spent reconciling, and whether the desk still opens more than one screen to recognise a guest.
- Do not build an automation or AI plan on top of conflicting guest records. The data question comes first.
Links
- Original article: https://www.cendyn.com/blog/the-new-hospitality-stack/