TL;DR

  • Direct bookings still matter. The HOTREC European Hotel Distribution Study 2026 reports that direct channels take 51.3% of European hotel bookings, but that share is down 6 percentage points since 2013 while reliance on online travel agencies (OTAs) has risen from 19.7% to 29.9%.
  • Most hotels do not face a clean "build or buy" choice. The practical answer for many UAE, Singapore and UK properties is a hybrid: buy the commodity parts (rate and inventory sync, channel connectivity, payment processing) and build the parts that shape your guest experience and your data.
  • A booking engine is only as good as its integrations. The PMS connection, the channel manager, the payment gateway and the consent layer decide whether it is reliable, not the logo on the vendor's brochure.
  • Compliance is part of the design, not a final checkbox: PCI DSS 4.0.1 for payment pages, consumer-law rules on price display, and data protection (UK GDPR, Singapore PDPA, UAE PDPL) for guest data.
  • Use the decision framework and the scoring table below to decide where your property or group sits. If you want a second opinion, you can book a consultation.

Why direct booking is back on the agenda

Every hotelier knows the arithmetic of intermediated distribution. Rooms sell, but a slice of every sale goes to someone who also owns the guest relationship. What has changed over the past couple of years is how much leverage independent properties and small groups think they have to do something about it.

The HOTREC European Hotel Distribution Study 2026, as reported by TRAVEL Extra, gives a useful snapshot of one major market. Direct channels still account for 51.3% of hotel bookings in Europe. Within the OTA segment, Booking Holdings has 68.8% and Expedia Group 16.6%, a combined 85.4%. Booking.com alone holds 66.1% of OTA portal bookings. The same report says 51% of hoteliers saw OTAs undercut their rates without prior agreement.

Two caveats before you quote those numbers in a board paper. They describe Europe, not the Gulf or Singapore, and the underlying study covers a particular set of hotels. For a UAE or Singapore property the mix of corporate, inbound-tour and walk-in demand will look different. Treat the figures as evidence that the pressure is real, not as a forecast for your own P&L.

The legal backdrop has also moved. On 19 September 2024 the Court of Justice of the European Union ruled in case C-264/23 that Booking.com's price parity clauses, both the "wide" and the "narrow" versions, cannot in principle be treated as ancillary restraints under EU competition law (CJEU press release). That is an EU competition ruling, so it does not rewrite your contracts in Dubai or Singapore, and the referring Dutch court still had to apply it. Read your own agreements, take advice, and do not assume a parity clause has disappeared from your contract because a court in Luxembourg had doubts about it.

None of this means OTAs stop being useful. They bring demand you would not otherwise reach, especially for new markets. The strategic question is how much of your revenue you want to own the relationship for, and what it takes to make the direct channel as easy as the one you are paying commission on.

What a direct booking engine actually does

"Booking engine" is shorthand for several jobs that tend to be sold as one product:

  1. Availability and rate presentation. It reads inventory and rates from your property management system (PMS) or central reservation system and shows the guest what they can book.
  2. Basket and checkout. Room selection, extras, taxes and fees, promo codes, guest details and payment.
  3. Payment handling. Taking a deposit or full payment, storing a card token, handling refunds and failed payments.
  4. Writing the reservation back. Creating the booking in the PMS, updating inventory, and pushing availability changes to channels via the channel manager so you do not oversell.
  5. Guest communication. Confirmation emails, pre-arrival messages, modifications and cancellations.
  6. Measurement. Attribution, conversion funnels, abandoned baskets.

Most of the pain in hotel technology sits in item 4. We have written before about why PMS integrations fail and how to build a more reliable property tech stack, and the same lesson applies here: the interface between the engine and the PMS is where double bookings, rate mismatches and missing guest data come from. A beautiful front end on top of a shaky sync is a liability.

The three options: buy, build or hybrid

Buy: an off-the-shelf booking engine

This usually means a module from your PMS vendor or a standalone engine from a distribution technology provider, configured with your branding.

Where it works well

  • You run a single property or a small number of similar ones.
  • Your PMS vendor already offers a certified engine and your needs are standard: room types, rate plans, packages, promo codes.
  • You need to be live quickly and do not have an in-house technology team.

Where it starts to hurt

  • You need booking flows the template does not support: multi-room family stays, combined room-and-experience baskets, member pricing that depends on a loyalty tier, group blocks or corporate negotiated rates.
  • You run several brands or properties on different PMS platforms and want one guest-facing experience.
  • Your guest data ends up inside the vendor's system with limited export options, which makes it hard to build a single customer view.

Build: a custom booking engine

A custom engine is software designed around your business rules and connected to your systems through APIs.

Where it works well

  • You have distinctive products to sell (resort packages, villas, spa and dining bundled with stays, seasonal events) and the standard basket gets in the way.
  • You want full control over the checkout, the data model and the analytics.
  • You operate multiple properties and need one engine that can sit across PMS platforms.

What people underestimate

  • Maintenance. The build is the smaller commitment. Rate logic, tax rules, payment scheme requirements and browser changes keep moving.
  • Connectivity. You still need a reliable connection to your PMS and channel manager. Building the interface is feasible, but each PMS API has its own quirks and limits.
  • Compliance scope. Take payments on your own pages and you take on more of the security burden than if you redirect to a hosted payment page.
  • Peak-day reliability. A booking engine that is slow or down during a campaign or a major local event costs real revenue.

Hybrid: buy the plumbing, build the experience

This is where many mid-sized groups land. You keep proven components for what is common to every hotel, and you write custom software where it differentiates you.

A typical split looks like this:

LayerBuy / use existingBuild / customise
PMS and inventory source of truthUsually boughtRarely worth building for a few properties
Channel manager and OTA connectivityBoughtCustom only for unusual distribution needs
Payment gateway and tokenisationBought (hosted fields or hosted pages)Orchestration logic around it
Booking flow and UISometimesOften custom (packages, member rates, upsells)
Guest profile and consent storeRarely suitable off the shelfOften custom, feeding CRM and marketing
Analytics and attributionStandard toolsCustom data model tying booking, stay and loyalty

If you have already invested in separate systems for PMS, point of sale and CRM, our piece on unified hospitality platforms covers the integration patterns in more detail.

A scoring framework you can run in an afternoon

Gather your revenue manager, your IT lead and whoever owns the guest relationship. Score each statement from 0 (not true for us) to 3 (completely true).

StatementScore 0–3
We sell products or packages the standard basket cannot represent
We operate more than one PMS platform, or expect to within two years
We want guest and booking data in one place we control
Our direct channel conversion problem is in the booking flow, not in traffic
We have, or can hire, people to run production software
We have a roadmap of changes that a vendor's release cycle would delay
Our PMS vendor's engine cannot expose the data or APIs we need

How to read it: a low total points towards buying and configuring. A middling total points to a hybrid, where you keep the vendor engine at first and build selectively. A high total, especially if you operate several properties, makes a custom engine worth a serious scoping exercise. This is a conversation starter, not a verdict. The most useful part is usually the disagreement it surfaces between revenue, operations and IT.

What to get right whichever route you take

1. The PMS and channel manager connection

Ask how availability and rates are read, how bookings are written back, how failures are retried and who is told when a sync fails. Ask what happens when two bookings for the last room arrive within the same second. If a vendor or a team cannot answer that clearly, you have found your biggest risk. Our guide to channel manager and OTA API integration goes through the data drift problem in detail, and the checklist for integrating a PMS with OTAs and channel managers is a practical review tool.

2. Payments and card data

If your engine collects card details, PCI DSS applies. The PCI Security Standards Council notes that requirements 6.4.3 and 11.6.1 for e-commerce payment pages became mandatory on 31 March 2025 (PCI SSC). In plain terms, scripts running on your payment page need to be authorised and checked for integrity, and you need a way to detect tampering. That matters for hotels because booking pages tend to accumulate third-party scripts: analytics, chat, tag managers, review widgets.

The simplest way to shrink your scope is to use hosted payment fields or a hosted payment page from a PCI-validated provider, so card numbers never touch your servers. Your scope still includes the page that frames the payment, so confirm with your acquirer or a qualified assessor what applies to you. For deeper practical coverage see our PCI compliance checklist for hotel payment systems and the broader piece on protecting PMS and payment systems from integration risk.

Multi-currency deserves its own design pass in the Gulf and Singapore, where many guests pay in a currency different from the rate currency. Decide early which currency the rate is held in, who bears the conversion cost, and how refunds are handled when the exchange rate has moved.

3. Price display and consumer rules

Showing the full price early is both good conversion practice and, in some markets, a legal expectation. In the UK, the Digital Markets, Competition and Consumers Act came into force on 6 April 2025, and the CMA's published guidance on price transparency and "drip pricing" says mandatory charges must be included in the headline price (RPC summary). That summary does not discuss hotels specifically, so ask your legal adviser how it applies to resort fees, service charges, city taxes and similar items on your booking pages. For UAE and Singapore, confirm local rules on displaying taxes and service charges with local counsel. The practical point for the build is that your engine should store taxes and fees as structured data, not as free text, so the basket can show a correct total at every step.

A direct booking engine collects personal data at scale: names, contact details, travel dates, sometimes passport or ID details, and marketing preferences. The three regimes your guests will most often be covered by are:

  • UK GDPR and the Data Protection Act 2018 for UK guests and UK-based processing.
  • Singapore's PDPA for organisations handling personal data in Singapore.
  • The UAE's Federal Decree-Law No. 45 of 2021 (PDPL), in which consent is the primary lawful basis. Free zones such as DIFC and ADGM have their own regimes, and the status of implementing regulations has moved over time, so check current guidance with counsel rather than relying on summaries.

Design implications that apply in all three: separate consent for marketing from the data needed to fulfil the booking, store the consent record with a timestamp and wording version, make withdrawal easy, and decide where data is hosted and which suppliers can see it. We summarise the operational side in our guest data privacy and consent checklist for hotels and look ahead at how rules shape hotel AI in guest data rules and the hotel AI roadmap for the UAE and Singapore.

5. Mobile experience and speed

A large share of hotel browsing now happens on phones. The sources that put a number on it are mostly vendor benchmarks that disagree with each other, so we will not quote one. What you can do is measure your own funnel: how many sessions are on mobile, where they drop, and how long the checkout takes on a mid-range phone on a mobile connection. Fix the biggest drop-off first. In many properties it is the date picker, the payment step or a slow rate-loading call.

Singapore: what the public programme tells you

If you operate in Singapore, the government's Hotel Industry Digital Plan is worth reading before you scope any project. It was launched in 2019 by IMDA and the Singapore Tourism Board with the Singapore Hotel Association, and was updated and announced on 1 September 2025 (TTG Asia). The update lays out business journeys and examples of AI-enabled solutions for guest experience and operations. Funding schemes change, so check eligibility and any grant conditions with IMDA and STB directly before building a business case around support.

UAE and UK: points to check locally

For the UAE, the practical issues are usually multi-currency payments, bilingual presentation if that is a requirement for your market, tax and service-charge display, and how guest identity data flows to your PMS and the relevant authorities. We have not verified every requirement in this article and these rules are changing, so work through them with your legal adviser and local partners. For the UK, price transparency, UK GDPR and the Privacy and Electronic Communications Regulations on email marketing are the first things to review.

Migration without breaking the business

Whichever option you choose, the riskiest moment is the switch. A sensible sequence:

  1. Map the current flow. Document every step from search to confirmation, including emails and back-office handoffs.
  2. Run in parallel. Launch the new engine for a subset of rate plans, a single property or a share of traffic.
  3. Reconcile daily. Compare bookings, inventory and payments between the new engine, the PMS and the channel manager until the numbers match for a defined period.
  4. Keep a rollback. Know how to send traffic back to the old engine within minutes.
  5. Plan the peak. Avoid cutover before a major local event, school holiday or festival period.

For multi-property groups, our zero-disruption migration playbook and the checklist for migrating from a legacy PMS to a cloud-based system lay out the steps in more detail.

Vendor and partner questions that separate good from risky

Whether you are buying a product or hiring a team, ask:

  • Which PMS and channel manager integrations are production-proven, and with which hotels you can speak to?
  • Who owns the guest data model, and can I export everything in a usable format?
  • How is the payment page secured, and who handles PCI evidence?
  • What are the uptime commitments and the support hours across Gulf, Singapore and UK time zones?
  • How do rate, tax and fee rules get changed, and by whom?
  • What does a rollback look like?
  • What happens to the system if the supplier relationship ends?

Our vendor evaluation scorecard for booking engine and channel manager providers and the buyer's guide to off-the-shelf versus custom hotel management software are useful starting points for shortlisting.

Where Syslabs fits

Syslabs builds custom software for hospitality, including booking engines and website kits, guest apps, F&B point-of-sale and multi-property analytics. Typical engagements start with the integration map (PMS, channel manager, payments, CRM) because that decides what is realistic. You can see the shape of the work on our hospitality industry page and the booking engine and website kit page. We do not publish price points, because the scope depends on how many systems are involved, which markets you sell in and what you already own. Costs are scoped properly on a consultation.

Conclusion

Direct booking is a systems problem as much as a marketing one. The guest experience on your site only works if inventory, rates, payments and consent flow cleanly behind it. Decide where you need control, buy what is commodity, and write down the integration contract before anyone writes code. If you want to talk through your property's situation, book a time with our team. The booking page shows slots in your own time zone.

References