By Pablo Revale
June 24, 2026 · 5 Minutes
Adapted from Originally published in Unstoppable Hospitality on LinkedIn.
We say hospitality is fragmented. But what does that mean? A condition? Is it fixable? At a data session at HITEC, Luis Segredo and Dr. Rik van Leeuwen put words to something every hospitality leader complains about. The fragmentation isn’t a tech glitch. It’s structural. It’s built into how this industry is owned, operated, and sold. Most people use the word to mean "too many systems." That’s the smallest version of it. Ownership: one hotel can be owned by one company, branded by a second, and run by a third. Three parties, one building, three sets of priorities. The guest sees a single front desk. Stack: a property runs a PMS, a CRS, a POS, an RMS, a booking engine, a channel manager, a loyalty platform, plus spa, golf, and the app. Dozens of vendors. None of them built to agree with the others. Guest: the same person is scattered across every one of those systems, under different IDs, different spellings, different "last known" values. One human, forty fragments.
There is a common confusion between these two systems, the same way people confuse channel managers and CRS. I confused it when I started working, and it took me a long time and real implementation to understand the difference. A CRM manages relationships and actions. Campaigns, segments, the email that goes out Tuesday. It assumes you already know who the person is. A CDP manages identity. It pulls every fragment of a guest from every system and decides that this masked email, this misspelled name, this second loyalty number all belong to one human being. That is identity resolution. It’s the act of defragmenting the guest. A CRM doesn’t do that. It stores what you hand it. Hotels keep buying a CRM and expecting a CDP outcome, and the other way around.
This is the heart of the fragmentation. The lack of a defined source of truth for every piece of information. The PMS is the system of record for the stay: what room, what nights, what folio. The CRS owns reservations, rate plans, and inventory: what was sold, at what price, under what conditions. The guest, the actual person across time and properties, should live in the CDP. It’s the one layer built to hold an identity instead of a transaction. That’s the irony. The same CDP sitting in the fragmented stack above is the only system designed to defragment it. But most hotels buy it and never finish wiring it in, so it ends up as one more silo instead of the layer that unifies the rest. The fix becomes part of the problem.
When we built the Sandals mobile app and rebuilt the TA portal, the hard part was never the interface. It was the data underneath. We were pulling from several sources at once. For every piece of data, we had to map which source owned the truth, display the correct value, and check for inconsistencies. Who owns the email, the PMS or the guest portal platform? Who wins when two systems show different loyalty balances? You don’t answer that with code. You answer it by understanding each source, what it was built to hold, and where it lies. Then you clean. Defragmenting a guest is slow, manual, and unglamorous, and there’s no shortcut around it.
A single, continuously correct view of the guest. Everyone draws it as one clean circle in the middle of the architecture diagram. It’s the opposite of fragmentation, which is exactly why it’s so hard to reach. In practice it’s a daily fight against typos, masked emails, name changes, duplicate records, and systems that update at different speeds. Accuracy and consistency are not a setup step. They’re an operating discipline. The profile is only golden on the day you stop maintaining it, and that’s the day it starts to rot back into fragments.
Anyone can rent the same model you can. The model is not the edge. The edge is the last-mile information. The on-property behavior, the real interactions, the unified profile that only your systems can produce once you’ve defragmented them. That is the data you fine-tune on. That is what turns a generic model into one that performs for your guests instead of for everyone’s. For years, fragmentation was a cost you could absorb. Reports came out late. Personalization was generic. Everyone lived with it. AI changed the math. The same fragmentation that produced poor emails now produces a confident, wrong agent talking to your guest in real time. The hotels that win will be the ones who treated fragmentation as the real problem and did the slow work of stitching the guest back into one piece. AI didn’t remove the need for clean, unified data. It raised guests’ expectations.
