Every lodge and guesthouse owner knows the deal they've made with the booking platforms. The OTAs — Booking.com, Airbnb and friends — bring you guests, and in exchange they take a commission on every single booking, forever. Not on the first booking. Every booking. Including the family who loved their stay and came back three times — if they book through the platform again, you pay the toll again.
That's not a partnership. That's renting your own customers.
To be fair to the OTAs: they're genuinely good at one thing, which is discovery. A traveller in Germany who has never heard of you can find you there. The mistake isn't being listed. The mistake is letting a listing be your only way to take a booking — because then the commission isn't a marketing cost, it's a tax on your entire revenue.
The quiet cost nobody calculates
Commission percentages look small on paper. But run the thought experiment across a year: every confirmed stay, multiplied by your average booking value, with a slice taken off the top of each one. For a lodge with healthy occupancy, that slice typically adds up to more than the cost of building and running your own booking system — and the OTA cost repeats every year, while a booking engine is built once and maintained cheaply.
And the commission is only the visible cost. The invisible ones bite harder:
- You don't own the guest relationship. The platform controls the communication, and the guest is their customer in the data that matters.
- You're a row in a list, displayed directly next to your competitors, sorted by an algorithm you don't control.
- Their rules, your business. Cancellation policies, payment timing, dispute outcomes — decided elsewhere.
"Book direct" only works if booking direct is actually good
Here's the uncomfortable part. Most lodge websites say "book direct for the best rate" — and then offer a contact form that disappears into an inbox, answered whenever someone gets off the quad bike. The guest, meanwhile, gets instant confirmation from an OTA. Guess where they book.
If you want direct bookings, the direct experience has to be at least as smooth as the platform's. That doesn't mean copying the OTA. It means building the flow that fits how a real lodge actually operates.
What a real booking engine looks like
We built this for Rocking Giraffe Bush Lodge — a premium lodge website with a booking and admin workflow behind it, not just pretty pages. The full case study is at /work/rocking-giraffe. The shape of it transfers to almost any lodge or guesthouse:
- A website that sells the stay. Accommodation, experiences, location, story, menus — presented at the level of the actual product. This is the part guests judge you on before any price comparison.
- A request-to-book flow. Guests pick dates and submit a booking request with their details and any special requests. No dead-end contact form, no risky instant-confirmation logic.
- Owner approval. You confirm or decline each request from an admin dashboard. You stay in control of availability, special cases and who's sleeping on your property.
- Payment on your terms. In South Africa that often means EFT and manual payment steps with human confirmation — which a custom flow handles natively instead of fighting against. An online payment gateway can be added later when the volume justifies it.
- An admin calendar and booking dashboard. Requests, approvals, rejections and the calendar in one place, instead of scattered across email, WhatsApp and a paper diary.
- Automatic transactional email. Guests get professional confirmations and updates without anyone typing them at 9pm.
Why request-to-book, not full automation
This is a deliberate design opinion, and we'll defend it: most lodges should not start with fully automated live payments and instant reservations. Owners legitimately need control — over availability quirks, special requests, group bookings, and payment steps that don't fit a rigid checkout. Request-to-book gives guests a modern, smooth experience while keeping a human hand on the final confirm.
Start there. Automate the steps that prove themselves repetitive. That's how you get a system the team actually trusts, instead of an automated machine everyone quietly works around.
What it costs to run
Honesty section: your own booking engine isn't free to operate. There's hosting, a backend, transactional email, and a domain — modest, predictable monthly costs. The difference is structural: those costs are flat, while commission scales with your success. The better your lodge does, the more an OTA-only setup punishes you — and the better the owned engine looks.
The strategy that works isn't OTA or direct. It's OTA for discovery, your own engine for everything else: returning guests, referrals, people who found you on Google or Instagram, and everyone who should never have paid a platform toll in the first place.
FAQ
Should I delist from Booking.com and Airbnb entirely?
No. OTAs are excellent at reaching travellers who've never heard of you — keep them for discovery. The goal is to stop them being your only channel: convert returning guests and direct enquiries to your own booking flow, so commission applies to new-guest acquisition instead of your whole revenue.
What does a custom booking engine actually include?
At minimum: a premium public website, a request-to-book flow with dates and special requests, an owner admin with approvals and a calendar, and automatic confirmation emails. Payment handling fits your reality — EFT and manual confirmation are first-class citizens, with gateway payments as a later addition.
Do I need online card payments from day one?
Usually not. Most South African lodges run perfectly well on request-to-book plus EFT with human confirmation — that's how many owners prefer to operate anyway. Build the workflow first; add a payment gateway when booking volume makes the admin worth automating.
Tired of paying rent on your own guests? Talk to us — we'll scope what your own booking engine would involve.