Selling through other people
OTA bookings that behave like every other booking.
Most operators run their OTA sales through a channel manager or, worse, re-key them by hand. Either way those guests end up outside your reporting, outside your guest records and outside your gate. Ours land in exactly the same place as a booking taken on your own site.
An OTA connection
Connections → the OTA integration screen, showing the connected channel and which products are mapped.
Connected properly, not scraped or synced overnight
- GetYourGuide and Viator, live. They ask us for availability in real time, hold a place while the traveller pays, then confirm or release it. No nightly export, no allocation carved off and hoped over, no double-selling the last two seats.
- We tell them when something changes. A departure that fills up, a slot you cancelled, a time you moved — pushed to the OTA rather than waiting for them to ask again. That is the difference between a listing that is right and one that is right until tomorrow morning.
- Held, then booked. A reservation is a genuine hold on real inventory, released automatically if the traveller does not complete. The same seats your own checkout is protecting.
- Cancellations come back through the same door. An OTA cancellation frees the place immediately, so it can be resold — including to whoever is waiting on your waitlist.
The bit that actually saves you time
- An OTA booking is just a booking. It becomes an ordinary order in your system — so it appears in your reporting, counts toward the departure, shows on the manifest, and scans at the gate exactly like a direct sale. Nobody re-keys anything, and nobody is standing at the gate with a printout from somebody else's website.
- The guest is a guest. They land on your guest record like anyone else, so you can see that the family who came through an OTA in June booked direct in August. That is the whole point of doing this properly.
- Redemption is reported back. When an OTA ticket is scanned, the OTA is told — and that never sits in the way of your gate. If their service is slow, your queue does not know about it.
Keeping your own pricing safe
The main reason operators are nervous about connecting a channel is that the prices they give an OTA are not the prices they want on their own site.
- A trade price can be OTA-only. Mark a ticket type as channel-only and it never appears in your own booking page or at the till. Your commission-adjusted pricing cannot leak into direct sale by accident.
- Capacity is counted honestly on both sides. A family ticket that seats four is sent to the OTA as four places, not one — so a twenty-seat boat cannot be oversold through a channel any more than it can through your own checkout.
- You are not carving up your inventory. There is no separate OTA allocation to manage and rebalance. Everyone sells from the same pool, and whoever books first gets the seat.
Your own resellers, too
Hotels, concierges, tour desks and local partners are usually a bigger share of trade than people expect — and are almost always handled on paper.
- Give a partner their own booking page. On your system, with their own prices, so they can book a guest in directly rather than phoning you.
- Trade price lists per partner or partner type. The concierge desk and the coach operator do not have to be on the same terms.
- Payout statements from what they actually sold. Generated from real bookings rather than reconciled by hand at the end of the month — and reversed automatically when something is refunded or cancelled.
- Attribution that survives. Every booking knows which partner brought it, so commission and performance are answerable without anybody keeping a spreadsheet.
OTA bookings in your order list
Orders list filtered to OTA-sourced bookings, showing them alongside direct sales.
See it running on your own products.
Bring one activity, one ticket type and one price. We will show you what it looks like in a real checkout.