The path
What a booking touches, in order
Seven hops between a guest choosing a room and the front desk knowing about it. Every one of them is a place the two sides can disagree.
01
Website or app
Rooms, content and the rate display. Owns the story and nothing else.
- CMS
02
Booking engine
Holds the transaction. Themed as far as the vendor allows, with language and currency carried across the handover.
- IBE
03
Availability check
Live before payment, never from cache. This is the step that stops a guest being refused at checkout.
- Channel manager
04
PMS
The reservation is written where the front desk will find it, with the arrival notes attached.
- PMS
05
Payment
Through the compliant path the engine already uses, so card data never reaches the site or a conversation.
- PSP
06
CRM
Guest profile and the marketing consent, recorded where it was actually given.
- CRM
07
Analytics and comms
One funnel across the domain boundary, and the confirmation sent on the channel the guest used.
- GA4
- Messaging
When a system is down
The site degrades honestly: last known rates marked as indicative, an enquiry or call-back offered, and no payment taken that the property cannot honour. Selling through an outage creates reservations nobody can find.
Ownership
Which system is authoritative for what
Most integration defects are an ownership question answered wrongly at build time. Settled here, the rest of the work is mechanical.
Availability
The property system, usually surfaced through the channel manager.
What goes wrong when the website asks elsewhere: A room shown as free and refused at checkout. The most damaging failure on the site, and the hardest to notice from inside.
Rates and restrictions
The revenue management or property system, never a copy on the site.
What goes wrong when the website asks elsewhere: A price the hotel will not honour, or a minimum-stay rule the site ignores and the desk has to enforce by phone.
Room descriptions and imagery
The website content model. This is the one thing the site should own outright.
What goes wrong when the website asks elsewhere: Engine-supplied descriptions written for a distribution feed appear mid-funnel and read like a different hotel.
The booking record
The booking engine, written through to the property system.
What goes wrong when the website asks elsewhere: A confirmation the guest holds and the front desk cannot find. Reconciliation work that lands on the duty manager.
Guest profile and consent
The CRM, with the marketing permission recorded where it was given.
What goes wrong when the website asks elsewhere: Marketing to a guest who never consented, or losing the repeat relationship the direct booking was for.
Caching
The trade-off nobody states out loud
Live availability calls are slow, and a search page that waits on them feels broken on a phone. So most sites cache. Caching is correct, and the question is what the cache is allowed to say: showing a cached price is defensible, showing cached availability at the final step is not, because that is where a guest is told the room they chose does not exist.
The workable design is a cached search, a live check before the payment step, and an honest message where the two disagree that offers the nearest real alternative rather than an error. Getting this right is worth more than any redesign of the pages around it.
Field notes
What integration projects actually run into
- 01
The vendor supports it, on a different plan
API access is frequently a commercial tier rather than a technical limitation. Establishing which contract you are on, before design, prevents a build that assumes an endpoint you are not entitled to call.
- 02
Rate plans mean different things in each system
A package in the property system, a rate code in the channel manager and a product on the site rarely map one to one. The mapping table is the deliverable everybody forgets to ask for and everybody needs.
- 03
Nobody owns the test property
Testing against production because there is no sandbox produces real reservations that have to be cancelled by hand. Asking the vendor for a test environment early is a two-week lead item, not a two-day one.
- 04
The analytics stop at the handover
Where the engine is a separate domain, sessions break and the funnel appears to end at the moment it matters. Fixing measurement across that boundary is usually the first thing worth doing.
Our role
What we do across the property stack
- 01
Establish what each system exposes
Before design, in writing, including the contractual tier. It constrains what the site can promise and it is cheaper to know first.
- 02
Build the mapping and the cache policy
Rate plans mapped across systems, and an explicit rule for what may be cached and what must be checked live before payment.
- 03
Instrument across the handover
One funnel from the first page to the confirmation, so drop-off is visible by stage rather than as a single conversion number.
Distribution strategy and rate parity terms are commercial decisions for you and your intermediaries; what we own is that the systems agree about what the guest is being shown.
Common questions
What buyers ask
Our booking engine is a vendor product. How far can you integrate it?+
In most cases yes, and keeping it is usually the cheaper path. What we establish first is how far it can be themed and what it exposes, because those two facts decide how much of the experience can be made continuous. Where a vendor genuinely cannot be styled or integrated, that is a procurement finding worth having in writing before a redesign is scoped.
How long does an integration take?+
Four to eight weeks for a single property with cooperative vendors, and the variable is almost always vendor response time rather than engineering. Group estates take longer because the mapping has to be reconciled across properties that have configured their rate plans independently for years.
What happens when the property system is down?+
The site should degrade honestly: show rates from the last known good state, mark them as indicative, and offer a call-back or an enquiry rather than taking a payment it cannot honour. Sites that keep selling through an outage generate reservations nobody can find, and the recovery costs more than the bookings were worth.
In this cluster
Map your property systems
An integration map naming which system is authoritative for each field, and the list of places the current site is asking the wrong one.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

