NOTES — 2026-10-03
Homestay direct bookings vs OTAs in Malaysia
A homestay direct booking website gives guests an owned place to learn about your accommodation and contact your team. It does not, by itself, bring enquiries, check every booking channel or confirm a payment.
That distinction matters when comparing direct enquiries with online travel agencies, usually called OTAs. The decision is not simply whether to keep or remove an OTA listing. It is how guests find you, how they decide to enquire and how your team handles the booking afterwards.
I built a guest-facing website and a team booking ledger for Pulau Chekas, a homestay in Raub, Pahang. The project provides a concrete example of the work on both sides. It does not provide evidence for a claim that direct bookings replaced OTAs or increased revenue.
Compare the whole booking journey
An OTA listing puts your accommodation inside someone else's platform. Your own site lets you decide how to explain the place and how to guide the enquiry. Neither description tells you the actual cost of acquiring a guest.
Before comparing costs, check the terms of your particular OTA agreement. Commission, promotional arrangements, payment handling and cancellation rules should come from that agreement, not a generic percentage found online.
For direct bookings, include your own work. Someone must answer questions, confirm dates, explain payment instructions and keep records. A direct enquiry is not cost-free just because it does not arrive through a platform.
A website helps explain what guests are choosing
A list of room names may not tell guests enough about a property. They may need to understand where accommodation sits, what facilities are nearby and how the setting fits their stay.
At Pulau Chekas, an illustrated 3D map connects accommodation listings with rivers, paths and facilities. Guests can explore the setting rather than only scroll through a list of rooms. It is an illustrative layout, not a survey or a guarantee of exact distances.
This is the role of the guest-facing website: help people understand the offer before they ask. It is not evidence that an interactive map is necessary for every homestay. If your property is straightforward, clear photographs and useful accommodation information may be the more appropriate starting point.
The booking record is a separate problem
An enquiry can arrive through your site, WhatsApp or a telephone call. If each conversation remains separate, your team still needs a way to bring the information together.
Buku Lejar, the Pulau Chekas booking-management app, brings website enquiries and manually entered WhatsApp or telephone bookings into one interface. It supports booking status and deposit tracking with staff confirmation.
It also has separate admin and operator access, plus a record of who changed what and when. These are documented functions of the build. I am not claiming that it automatically imports OTA reservations, synchronises external calendars or processes payments. Those would be different capabilities requiring their own scope and testing.
An enquiry is not a confirmed stay
The Pulau Chekas workflow is staff-managed. It is not a promise of instant availability or automatic payment processing. That boundary should be clear to the guest as well as the operator.
For your own homestay, agree what each status means before buying a system. Is a new request waiting for a reply? Has the team checked the dates? Has a deposit been confirmed? When does the business regard the booking as accepted?
Do not let a button label answer these questions accidentally. “Send enquiry” and “Confirm booking” describe different commitments. The public wording should match what the team actually does.
Keeping both channels needs an operating rule
If you take bookings from more than one source, decide where the team checks the final record before accepting a stay. Also decide who updates it when a guest changes dates or cancels.
A website cannot prevent conflicting reservations unless the relevant channel information and operating rules are part of the solution. A manually maintained ledger depends on staff entering and checking the records. Automated channel synchronisation is a separate purchasing decision.
Ask a prospective developer to show how a telephone booking enters the system. Then ask how a correction is recorded. These ordinary tasks tell you more about day-to-day usefulness than a polished booking screen alone.
Direct enquiries still need a route to the website
An owned website is somewhere to send interested guests. You can use its address in your business materials and conversations, subject to any platform rules that apply. But publishing the site is not a guarantee that people will discover it through search.
Separate building the website from bringing visitors to it. Ask what search preparation is included and what ongoing promotion remains your responsibility. Do not accept guaranteed occupancy or ranking claims as substitutes for a clear plan.
Keep the accommodation information current too. An enquiry journey becomes confusing if the photographs, terms or contact details no longer match the business.
What to request in a proposal
Describe your accommodation, how enquiries arrive and who confirms bookings. Explain whether you need a public website, an internal record, or both. These are related but distinct deliverables.
Ask the proposal to name exclusions. If OTA integration, online payments or live availability are not included, that should be written down. If they are included, ask how they will be demonstrated before handover.
Include maintenance and access responsibilities. Who can change public information? Who can update records? What happens if a staff member leaves? How can you recover your data? You do not need technical jargon to ask these questions.
Choose around your actual bottleneck
If guests cannot understand the property, improve the public information. If staff cannot follow the bookings, look at the internal workflow. If external channel coordination is the problem, do not assume a contact form will fix it.
The useful lesson from Pulau Chekas is that hospitality has a guest side and a team side. Buying the right solution means considering both, while staying honest about which parts remain staff-managed.