Direct booking 29 July 2026, 7 min read
Choosing a booking engine for an independent hotel
The booking engine is where the website either earns its keep or quietly hands the guest back to the platforms. What genuinely separates the options, and how to judge them.
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
Engines charge in one of two ways: a monthly fee, or a percentage of every booking they process. Percentage pricing feels safe because it scales with success, but run the numbers on your own volume before accepting that framing. A hotel putting four hundred thousand pounds a year through its own website at three per cent is paying twelve thousand pounds for software, every year, forever. A flat fee often costs a fraction of that once direct volume is healthy.
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 is worth more than the commission it saves, because it comes with the guest's real email address and consent to stay in touch. Some engines treat that data as yours, exportable in full at any time. Some make leaving painful: history held hostage, addresses locked in, gift vouchers that cannot migrate. Ask the exit question while everyone is still being friendly. How do we take every guest record, every future booking and every unredeemed voucher with us if we go? The quality of the answer tells you a great deal.
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.