What a hotel's technology actually needs to talk to

A guest experiences a hotel as one service. Behind it, that service usually runs on half a dozen systems from different vendors, each designed to do its own job well and to say as little as possible to the others. Most guest-experience problems — the rate that differs between channels, the request that never reaches housekeeping, the preference forgotten on the second stay — are integration problems in disguise.

The core: property management

The property management system holds reservations, rooms, rates and folios. It is the system of record, and almost every other integration either reads from it or writes to it. The first design decision is which events the PMS publishes — a new reservation, a modification, a check-in, a room-status change — and how reliably other systems can subscribe to them.

Distribution: channels and booking engines

Availability and rates flow out to the booking engine, online travel agencies and, increasingly, B2B partners and agents. A channel manager keeps them aligned, but only if inventory updates are pushed promptly and conflicts are handled explicitly. Overbookings and rate disparities are almost always symptoms of a slow or one-way integration.

Money: payments and finance

Payment gateways handle deposits and pre-authorisations; the finance system needs the resulting postings, refunds and commissions. Designing this flow carefully — with tokenised card data and clear reconciliation — removes a large share of month-end manual work.

Relationships: CRM, messaging and feedback

Guest profiles, preferences and history should reach marketing, front office and service teams without exporting spreadsheets. Messaging platforms send pre-arrival and in-stay communication; feedback tools close the loop after check-out. Each needs a consistent guest identity, which is easier to design at the start than to reconcile later.

Insight: the data layer

Once these flows exist, occupancy, average rate, channel mix and service metrics can be modelled in one place. That is where revenue and operations decisions improve — and where AI assistants for guests and agents get the context they need to be useful.

The practical lesson: design the event flows and the guest identity first. The applications on either side can change; a well-designed integration layer is what lets them.