A booking system on your website: integrate, build or refer out?
Many businesses sell their time or their places through a marketplace, and their own website politely sends visitors off to that platform. It works, until you add up what the commission costs over a year and realise you do not have the customer data.

Why direct bookings make the difference
Marketplaces are good at being found and at being trusted. They are also good at keeping your margin and your customer relationship. Commission in this category typically runs into double digits per booking, and you pay it even for the customer you brought in yourself, who simply clicked the button that felt safest.
Direct bookings give you three things back: the margin, your guest's email address, and the freedom to design your own experience. Examples of our work are in our cases.
The marketplace does not have to go. The healthy end state is a mix, in which your own channel takes the largest share and the marketplace tops it up.
Three routes to bookings on your own site
Route one is a ready-made calendar you place on your page. Route two is a booking flow you design yourself, on top of that system's calendar. Route three keeps availability, prices and capacity in your own platform. The table shows what mainly drives the cost of each route; an actual price belongs in a quote for your situation.
| Route | What drives the cost | When it fits |
|---|---|---|
| Booking system widget | A subscription with the provider, little build work | You want direct bookings this month |
| Integration via API | One-off design and integration work, plus the subscription | The booking is your most important conversion |
| Your own booking layer | The most build work, and the maintenance is yours | Complex capacity, multiple locations or your own logic |
For most businesses, our honest preference is route two. The widget is quick, but it rarely looks like your brand, and you are stuck with the steps the provider came up with. Building your own booking layer only makes sense if your availability genuinely works differently from what every system can already do. That route is in effect a custom platform, with the cost and the maintenance that come with it.
Eight things to settle before you go live
- One source of truth for availability. Not your site and your calendar side by side: one of the two leads, and the other follows.
- A temporary hold during checkout, or you sell the same place twice.
- Time zones and daylight saving time, especially if your guests come from abroad.
- Deposit or full payment, and what happens when a payment fails.
- Cancellation and no-show terms, visible before payment and repeated in the confirmation.
- An automatic confirmation plus a reminder, with everything the guest needs to know.
- Self-service changes and cancellations, or your inbox becomes the booking system.
- Capacity per time slot and per person, including groups and children where that applies.
The mistake we see most often
A contact form is not a booking. Yet many sites have a form with a date field that sends an email. The guest thinks they have booked, you find out three hours later that you are full, and you start the day with a disappointment you organised yourself.
If your system cannot say no, it is not a booking system. It is a waiting list in a nice coat.
The second mistake is the opposite: a seven-step booking flow that asks for everything you might ever want to know. At the booking stage, ask only what you need to secure and confirm the place. Ask for the rest in the confirmation email.
What it really costs
Plan for three items. The booking system itself usually charges a monthly fee, sometimes with a fee per booking on top; the current price is on the provider's site. The payment provider charges a fixed rate or a percentage per transaction. And connecting it to your site is one-off work, its size set by how much of the flow you want to design yourself.
Set that against what you pay in commission today. At a few hundred bookings a year, the sum often adds up within a season. At ten bookings a year it does not, and then a tidy widget is the right answer.
Measuring whether it works
One number counts: the share of direct bookings in your total. Beneath that, you measure the flow itself, step by step: date chosen, details entered, paid. The step where most people drop off tells you exactly what to change, and it is almost never the colour of the button.
If the rest of your site feels sluggish too, look first at the five signs your website is costing you customers. A booking system will not fix a site that loads too slowly. If you want route two or three built, that falls under having a booking or reservation system built.
Frequently asked questions
Can I keep my existing booking system?
Usually, yes. The question is whether it has a public API or a decent embed. If it does, we can design the flow on your own site while the calendar stays where it is, along with your existing way of working and your reports. If it does not, that is a reason to switch, not to leave things as they are.
What if I have several locations, guides or rooms?
Then capacity is the core of the design. You define what a bookable unit is, which resources rule each other out and which can be shared. This is exactly where widgets fall over, and where an integration or your own layer earns its keep.
Will I lose visibility if I rely less on marketplaces?
Not if you do it in phases. Keep the marketplace while you build up your own channel, and only adjust once you see direct bookings coming in consistently. Meanwhile, you build visibility with findable pages for each destination, activity or room.
