Choosing a booking engine for an independent hotel

A hotel can spend a year and a serious budget on a website, and the guest still finishes the journey inside a piece of software the hotel did not design and rarely chose deliberately. The booking engine usually arrived bundled with the property management system, or was inherited from the previous owner, or was picked a decade ago on price. It is the last thing a guest touches before paying, and for most independents it is the least examined part of the whole journey.

This piece is deliberately not a league table. Products change, pricing changes, and the right answer depends on your property. What does not change is the set of questions that separates a good engine from an expensive leak.

Commission or licence fee, do the arithmetic

Compare the full cost, including fixed fees, booking commission, payment processing, setup and paid add-ons. As an illustrative calculation, £400,000 in annual bookings at a 3% engine fee costs £12,000 before other charges. Compare that with a fixed-fee quote on the same scope, rather than assuming either model is cheaper.

The subtler trap is that percentage pricing quietly taxes the thing you are trying to grow. Every pound you move from the OTAs to your own site earns the engine a margin, which is a strange incentive to fund once you notice it. Percentage deals make sense for a property starting from very low direct volume. They stop making sense precisely when your strategy starts working.

The design cliff

The most common failure is visible in one click. A considered, characterful website, and then the check availability button drops the guest onto a page that looks like airport car hire: different typeface, different colours, a URL with somebody else's name in it. The guest may not articulate it, but they feel handed to a stranger, and the drop-off data says a measurable share of them leave at exactly that seam.

Engines differ enormously here. Some allow real control of type, colour, photography and language. Some offer a logo upload and call it branding. Judge this with your own eyes on your own phone, not from the sales deck, and treat the transition from site to engine as one continuous room a guest walks through, because that is how the guest experiences it.

Can it sell what you actually sell

Every engine can sell a standard room for a Saturday night. The differences appear at the edges, which is where an independent property actually lives. Dinner, bed and breakfast rates. A three night stay where the middle night is discounted. A voucher for afternoon tea bought by someone's daughter in Australia. A dog supplement, a cot, a late checkout, a bottle of something waiting in the room.

If the engine cannot represent the offers that make your property distinctive, the website ends up flattening you into a room-only grid, and the interesting revenue either dies or turns into phone calls your team has to handle by hand. Bring your five oddest real offers to every demo and ask to watch them being built.

It has to talk to the rest of the stack

The engine sits between the website and the property management system, usually with a channel manager alongside. If availability and rates do not flow cleanly in both directions, someone ends up retyping bookings, and eventually a double-booked suite teaches the lesson expensively. Before any decision, list what you run today, the PMS, the channel manager, the payment provider, the EPOS if packages touch the restaurant, and get the integration confirmed in writing for your exact versions, not as a logo on a partners page.

Whose guest is it afterwards

A direct booking can give you a closer guest relationship, but it does not automatically give you permission to send marketing. Check how the engine records consent or another applicable permission, and how records can be exported or deleted. Ask how you would migrate future bookings and unredeemed vouchers if you changed suppliers.

Ten minutes with a phone tells you most of it

Ignore the feature matrix for a moment and book a room at a property that already runs the engine, on a phone, on mobile data. Count the steps from check availability to confirmation. Count the fields the form demands. Notice whether prices include everything or grow at each step, whether the room photographs survive the journey, whether paying feels reassuring or improvised.

Somewhere around two thirds of hotel website traffic is on a phone, and the mobile checkout is where direct bookings actually die. An engine that is merely adequate on mobile costs you real revenue every night, invisibly, which is the most expensive kind of cost.

Choosing, in practice

Shortlist three. Do the arithmetic on your own numbers for each pricing model. Test the guest journey on a phone at a live property. Bring your strangest offers to the demo. Confirm the integrations in writing. Ask the exit question. A day of this work protects the most valuable click on your website for the next five years, and it is a day most properties never spend.

How we build direct booking journeys

A checklist for the supplier demo

Use the same examples with every supplier and record the answer, any extra fee and who is responsible for delivery.

• Book a real room for two adults and a child, including any occupancy limits.
• Build a dinner, bed and breakfast package with the restaurant allocation you need.
• Check how rates, restrictions and availability move between the PMS and engine.
• Change dates on a phone without losing the room or offer already selected.
• Confirm when the total price, deposit and cancellation terms appear.
• Ask for a complete first-year and renewal quote, including payments and add-ons.
• Demonstrate consent recording, reporting, booking exports and the exit process.
• Agree who tests the integration, handles failures and supports the team after launch.

If a supplier needs to follow up, ask for a written answer before choosing. A documented limitation is easier to plan around than an assumption.

Further reading: ICO guidance on electronic mail marketing.