Report Finds Just 11% of Operators Run Fully Linked Tech

A joint paper from hospitality technology advisory firm TAG and guest-experience vendor Cendyn puts a number on something most property managers already feel in their daily workflow: only 11% of operators say their booking, payment and guest-data systems are fully integrated. The rest are running some mix of property management system, channel manager, payment processor and guest messaging tool that requires manual reconciliation, duplicate data entry, or both.

The figure comes from the two companies' own research and should be read as a claim, not an audited industry count. TAG advises hotels and resorts on technology procurement; Cendyn sells CRM, guest-data and payment tools built to plug that gap. Neither is a neutral party in an argument for more integration. That doesn't make the underlying problem imaginary - fragmented stacks are a routine complaint among multi-property operators - but it does mean the 89% figure deserves the same skepticism any operator would apply to a vendor's own market sizing.

What 'fully integrated' is actually describing

The paper's definition centers on three systems working off one shared data layer: the booking engine or channel manager, the payment processor, and the guest profile that carries preferences, stay history and communication threads across every channel a guest books through. In a short-term rental context, that means an Airbnb reservation, a Vrbo reservation and a direct booking all updating the same guest record, with payment capture and refund handling running through one ledger rather than three separate OTA dashboards and a standalone processor.

Most property management companies don't operate that way today. A manager running 40 units across Airbnb, Vrbo and a direct website typically reconciles payouts from each platform separately, keeps guest contact details wherever the booking happened to land, and logs refunds or chargebacks by hand when a guest disputes a charge. None of that is unusual. It's the default setup for operators who built their tech stack by bolting on tools as they scaled, rather than designing for integration from the start.

Why the gap matters more as fee pressure rises

Fragmentation gets more expensive as commission structures tighten. Vrbo moved to double its host commission this year, narrowing the gap with Airbnb's take rate, and operators are under more pressure to prove which channel actually delivers margin once fees and payment processing costs are netted out. That calculation is hard to run cleanly if payment data sits in three disconnected systems and nobody owns a single view of true revenue per booking.

Guest data fragmentation carries a similar cost on the experience side. A returning guest who booked through Airbnb last year and is inquiring directly this year shows up as a stranger if the two records never merge. Upsell opportunities, loyalty recognition and even basic things like knowing a guest's prior complaint history get lost in the gap between systems.

What this changes for a manager running a mixed portfolio

The practical question for most operators isn't whether to consolidate - it's how much consolidation actually pays for itself. Full-stack platforms exist that bundle booking, payment and guest-data functions under one vendor, but switching costs money and carries migration risk, particularly for operators with revenue management or dynamic pricing tools they don't want to give up. A more common middle path is integrating at the data layer: keeping existing point solutions but routing guest and payment data through a shared system of record, often via a property management system's native integrations or a third-party connector.

Operators already doing this in pieces offer a useful comparison. Beaumier, a European hospitality group, consolidated guest messaging and front-desk administration onto a single platform earlier this year specifically to stop staff from toggling between separate inboxes for each channel. That's a narrower version of the same bet the TAG-Cendyn paper is making at full-stack scale: that the cost of switching is lower than the cost of staff time lost to manual reconciliation.

What to watch before acting on this

Nothing in the paper obligates any operator to do anything by a given date - this is advocacy for a direction, not a regulation or a platform policy change. The more useful signal to watch is whether OTAs themselves start exposing richer data feeds that make third-party integration easier or harder. Booking.com and Airbnb both control how much guest and payment data flows out through their APIs, and any tightening there would blunt the case for building a unified stack around data those platforms don't fully release.

Operators considering a consolidation project should ask vendors for a specific accounting of integration costs, migration timelines and what happens to historical guest data during a switch, rather than taking an industry-wide integration percentage at face value. An 11% baseline is a useful provocation. It is not a benchmark any individual portfolio needs to hit on a fixed schedule.