Tour Booking Software Compared: What Small Operators Should Check

A small tour operator should choose the booking software whose rules fit their tours, whose fees stay sensible at their monthly volume, and whose channel sync stops double-bookings. Check booking rules, payouts, OTA sync, waivers and total cost per booking. Trial two systems on the same ten real bookings, not on a demo.

Review sites rank software on feature counts, which suits large operators with a dedicated systems person. A three-guide business has a narrower problem: one wrong rule, such as selling a seat on a full boat, costs a guest and a review. So judge each system first on whether it can enforce your rules, then on what it costs per booking at your volume, and only then on the extras.

Follow me on Instagram@sagnikteaches

Write your booking rules before you open a demo

Software is only as good as the rules you can tell it. Write them first, because they decide which systems can even be considered. An illustrative sheet for a small walking-tour company with three tours looks like this.

Connect on LinkedInSagnik Bhattacharya

TOUR: Old Town walk     capacity 12, 10 am and 2 pm daily
 - minimum 2 guests, else cancel 24 h before and refund or move
 - cut-off: no online bookings inside 3 hours of start
 - child (under 12) half price, under 5 free, not counted in capacity
TOUR: Evening food trail   capacity 8, Tue-Sat 6 pm
 - private hire allowed at 8 guests flat rate $480
 - dietary notes mandatory at booking
TOUR: Day trip   capacity 14, Sat only, minibus
 - 2 guides when more than 10 guests
 - deposit 30% at booking, balance 14 days before
Seasonal: prices +15% from 1 July to 31 August
Blackout: 25 Dec, 1 Jan, and any day with a private booking

Now each line becomes a test. Can the system apply a minimum number and auto-cancel? Can it block bookings inside a cut-off? Can children be free and excluded from capacity? Can one departure need two guides at a threshold? Can a private booking close a public slot? A system that cannot handle two of these is a poor match, whatever its review score says.

Subscribe on YouTube@sagnikteaches

What the main systems state about themselves

These are snapshots from vendor pages read in October 2026. Prices move, so confirm them on the day.

Rezdy. Three plans are listed: Foundation at $49 a month, Accelerate at $99 and Expansion at $249, each with a 3 per cent online booking fee that the operator can absorb or pass to guests. Offline or agent bookings carry a per-booking fee instead: $1.00, $0.85 and $0.70 across the three plans. The page says all plans include unlimited connections to OTAs, agents and resellers, offers a Stripe-powered payment gateway, and starts with a 21-day trial. The page shows dollar signs but does not name the currency, so confirm the currency before you compare it with another vendor's dollar price. It does not mention waivers on the page I read.

Checkfront. The page I read shows one plan at $99 a month plus a 3 per cent online booking fee, which can be absorbed or passed on, and notes that prices may vary by region and currency. It lists connections to Viator, GetYourGuide and Google Things to do, says there are no additional fees on OTA bookings beyond the OTA's own commission, and describes built-in customisable waivers with no extra fee, though third-party add-ons may charge.

Bookeo. Its tours and activities plans are flat monthly fees with no commission on payments: Solo $14.95, Small $29.95, Standard $39.95, Large $79.95 and X-large $119.95 a month, with your payment gateway's processing fee on top. Its digital waiver add-on is priced by volume, from $9 a month for 200 waivers to $249 for 10,000. Check which plan size fits your booking volume, because the tiers are capacity-based.

FareHarbor. Its pricing page returned an error when I checked it in October 2026, and no published rate card turned up. Several comparison sites report no subscription fee and a booking fee of about 6 per cent paid by the guest, but those pages are competitors' or aggregators', and they disagree on operator-side costs and card processing. Treat it as "ask for a written quote".

That is four systems and four different fee structures: flat fee plus percentage, one plan plus percentage, flat fee with add-ons, and guest-paid. You cannot compare them by headline price. Compare by cost per booking at your own volume, which is next.

Worked example: what each fee model costs at 120 bookings a month

Illustrative operator: 120 online bookings a month, average booking value $85, so $10,200 in monthly sales. Ignore card processing for a moment, because most systems charge it separately and it is similar across them.

Which Bookeo tier a 120-booking operator needs depends on its plan limits, so treat that row as the shape of a flat-fee model and confirm the tier. Two points follow. First, percentage fees scale with success: at 300 bookings a month the 3 per cent fee on the same average booking would be about $765 on top of the subscription, so a flat-fee plan gets cheaper by comparison as you grow. Second, "free to operator" fee models are not free. The guest pays, and a guest comparing your tour with a rival's sees the higher total. Either way, ask each vendor for a written example: "For 120 bookings at $85, what will I pay and what will the guest pay?" A good vendor answers in numbers.

Now add what these sums leave out: OTA commissions are separate in every system, since the OTA charges them whatever software you use. Payment processing is a per-transaction cost. Add-ons such as waivers, SMS credits or extra users sit outside the headline. Your real monthly figure is the headline plus these.

Payouts: when does the money reach you?

Payouts get less attention than features and cause more cash-flow stress. Ask each vendor five direct questions.

1. Who processes guest card payments, and do I need my own merchant account? (Rezdy describes a Stripe-powered gateway, for example.)
2. How many days from the guest paying to the money in my bank?
3. For OTA bookings, does the OTA pay me or does the system collect and pass it on?
4. If I refund a guest, do I get the processing fee back?
5. Do deposits and balances use the same payment link, and can I hold the money until the tour runs?

A realistic mistake: an operator takes a 30 per cent deposit for a day trip in March for a trip in September. The system pays out immediately. If the trip is cancelled for weather, the operator has already spent the deposits and must refund from the next month's income. A cautious owner holds deposits in a separate account until the tour runs, which is a habit rather than a software feature, but the payout timing is what makes it necessary.

OTA sync: the double-booking test

When you list on Viator, GetYourGuide or Google, each booking anywhere should reduce capacity everywhere. A sync that is delayed or partial lets two guests book the last seat. Here is how to test before you commit.

1. Connect one channel in a trial, even a test listing if the vendor provides one.
2. Set a departure to capacity 2.
3. Book 1 seat on your own site and watch the remaining capacity on the connected channel. Note the time it takes to update.
4. Book 1 seat through the channel and watch your own calendar.
5. Try to book 2 seats on both at the same moment, if you can.

If it takes minutes, ask what happens in the gap. Many systems close a departure on all channels when it fills, and some reserve seats while a guest completes checkout. Rules differ and the vendor's help pages will say. Also ask about edits: does changing a price or a time in your system update the OTA listing, or only capacity? Rewriting titles and descriptions for those channels is a separate job; Viator and GetYourGuide listings: rewrite titles with AI covers that side.

Waivers and guest information

If your tours involve bikes, water, climbing or anything that needs a signed form, check three things. First, is the waiver built in, capped, or a paid add-on? The sources above show the full range: Checkfront describes waivers with no additional fee, Bookeo prices waivers by volume, and Rezdy's page I read did not mention them. Second, can the guest sign before the day, on a phone, so the guide is not collecting paper at the meeting point? Third, can you require it, for example blocking check-in until a waiver is signed for each guest? For two worked examples of this on rentals, see AI for bike rental: availability, waivers and weather rebooking.

The same fields cover dietary notes, mobility needs and emergency contacts. Make anything you need mandatory at booking rather than hoping guests reply to an email. A food trail operator who finds out about a nut allergy at the meeting point has a problem that a mandatory field would have prevented.

Small-operator limits nobody lists

• Guide and resource handling. A day trip that needs two guides when more than ten book may need a resource rule. Rezdy's features page refers to assigning staff and equipment and to printable manifests. Check the exact assignment rules in a trial. Scheduling people is its own subject; see tour guide scheduling software for freelance guides.
• Private tours and custom quotes. Can you send an invoice for a bespoke group without creating a public slot?
• Multi-currency and languages. If guests book in several languages, check the booking page and confirmations, not just the dashboard.
• Reports. Can you export bookings by channel, with commission, to a spreadsheet for your accountant?
• Contract terms. Minimum term, notice to cancel and what happens to your data on leaving.
• Weather and cancellations. Bulk-cancelling a departure and offering a rebooking link to every guest saves an hour on a bad morning. Weather cancellations for tours with AI shows the messages.

Where AI fits once the system is chosen

None of the pages I read described AI as the reason to pick a booking system, and that is the right way round: rules first, language second. Once the rules work, AI earns its keep on wording around the bookings. Three jobs are worth trying.

Turn your rules into test cases. Paste your rules sheet into a chat assistant on a plan that does not train on your content, and ask it to find the awkward cases.

Here are the booking rules for a small tour company.
List 12 edge cases a booking system could get wrong, such as
conflicting rules, rounding of child prices, or a private hire
overlapping a public departure. For each, say what the correct
outcome should be under my rules. If my rules do not decide
the outcome, say so instead of guessing.

[paste rules sheet]

An illustrative item from the answer: "A family of 2 adults, 1 child aged 4 and 1 child aged 11 books the Old Town walk. Under your rules the 4-year-old is free and excluded from capacity, the 11-year-old pays half price and counts, so 3 seats are used and the total is 2.5 adult fares. Your rules do not say whether a child can book without an adult." That last line is the useful part. The AI has found a gap in your rules, and you can fix it before a guest finds it. Check every outcome against your own rules, because the model can slip on arithmetic.

Draft the confirmation and reminder wording. The system sends the message; AI helps you write the template once. Give it the meeting point, what to bring, the cancellation terms and your tone, then paste the result into the system's template field. Do not let it add details you did not supply, such as an opening time or a toilet stop.

Answer repeat questions. "Is it suitable for a pushchair?" and "Where do we meet?" arrive daily. Keep a one-page facts document and let AI draft replies from it for a person to send.

A double-booking that the demo never showed

A realistic failure shows why the sync test matters. An operator runs a 12-seat evening trail and lists it on two channels plus their own site. On a busy Saturday, the last four seats are bought within the same few minutes on two channels. Both bookings are accepted because the second channel had not yet been told the first had landed. The operator now has 16 guests for 12 seats, two angry customers and a review risk. The cause was not the software being bad. It was a setting: capacity updates on that channel ran in batches, and the operator had not asked how often. The fix was to ask the vendor for the update interval, hold back a buffer of two seats on each OTA, and close a departure on all channels once it passed 10 bookings. A buffer costs some sales and prevents the worse outcome.

Put a line in your trial script for this. If you cannot test live, ask the vendor to explain in writing what happens in the gap, and ask a current customer of similar size.

Refund and cancellation wording to set up in the system

The system can only apply a policy you have written down. Keep it short and enforce it with the system's settings, not goodwill. An illustrative version:

Cancellation policy
- Free cancellation up to 48 hours before the tour starts.
- Inside 48 hours, 50% refund or a free move to another date.
- Weather: if we cancel for safety reasons you choose a full refund
  or a new date.
- Minimum numbers: if fewer than 2 guests book, we tell you at least
  24 hours ahead and offer a refund or another date.

Test each clause in the trial. Cancel a booking at 49 hours and at 47 hours and see what the guest is offered and what the system does with the payment. If the system can only refund in full, you will be issuing manual part-refunds, which takes time and invites mistakes.

A quick scoring grid for the final two

Once two systems survive the trial, score them on the five things that cost you most when they fail: how many rules from your sheet it enforced without a workaround (weight 30), whether the OTA sync test passed (25), the monthly cost at your volume from the sum above (20), the payout timing and refund handling (15) and waivers and guest fields (10). Multiply each score from 0 to 5 by its weight, add them and divide by 5. A system that scores 80 against 68 has earned the contract, and the gap shows you which area to ask the loser about if it matters. If the totals are within three points, choose the one with the shorter minimum term.

What switching later will cost

Pick with an exit in mind. Ask how you export customers, bookings and payment history, and whether reviews and OTA listings stay with you. A system that holds your data in a form you cannot take away is cheap to join and costly to leave. Keep a quarterly export in a spreadsheet, which takes five minutes and covers you against a vendor changing terms. The minimum term matters too: a 12-month contract signed in March, before the season has proved the system, is a bigger commitment than it looks. If a vendor will not offer a short term, ask for an extended trial instead.

A ten-booking trial script

Instead of clicking through a demo, run the same ten bookings through each system. Use your real tours and your rules sheet.

1. A standard booking for two adults.
2. A family with a child under 5 and one under 12.
3. A booking inside the cut-off window, which should be refused.
4. A booking that would exceed capacity.
5. A private hire that should close the public slot.
6. A deposit booking, then payment of the balance.
7. A cancellation inside and one outside your refund window.
8. A booking from a connected channel, if available.
9. A guest with a dietary note and a signed waiver.
10. A date change after booking, with a price difference.

Score each line pass, partial or fail, and write a one-line note on what you had to do by hand. At the end the system with fewer manual workarounds usually wins, even if it costs a little more. For the wider picture of where AI fits around bookings, how small tour operators use AI for bookings and itineraries is the overview.

If you would like help turning your tours and channels into a trial script, that is part of what my AI implementation consultation covers; see the contact page. Whichever you choose, keep a copy of your rules sheet, because it is the document you will need when you switch systems again in a few years.

Questions small tour operators ask before choosing a system

Which tour booking software is best for a small operator?

There is no single best. A small operator should pick the system whose booking rules match their tours, whose fees stay low at their volume, and whose OTA sync stops double-booking. Run two shortlisted systems through the same ten real bookings in a trial and compare what each did with them.

Who pays the booking fee, the operator or the guest?

It depends on the vendor and setting. Rezdy and Checkfront both state that an online booking fee can be absorbed or passed to guests. Some other systems charge the guest at checkout. Decide which you want, because it changes the price your guest sees against competitors.

How does OTA sync avoid double bookings?

The system updates remaining capacity on each channel when a booking lands anywhere. Delays or manual steps cause overbooking. Ask how quickly changes propagate and what happens if two guests book the last seat at the same moment, then test it.

Do I need built-in waivers?

If your activity carries physical risk, such as bikes, boats or climbing, yes, or you will use a separate tool and chase signatures by hand. Check whether waivers are free, capped or a paid add-on, and whether guests can sign before they arrive.

Further reads

• How to Price Tour Packages: Per-Person and Group Rates With AI — Helps set the prices your booking rules will enforce.
• Tour Descriptions in Several Languages: An AI Workflow — Booking pages and confirmations for guests in several languages.
• Reply to TripAdvisor Reviews as a Tour Company With AI — Handles the reviews that follow a smooth or a botched booking.
• 8 Examples of AI in Tourism From Guided Tours to Group Bookings — Eight other places AI fits around a small tour business.
• Kayak Rental Software: Bookings, Waivers and Weather Calls With AI — A set-up for a small kayak or paddleboard rental: booking system, waivers, written weather-call rules and AI-drafted rebooking messages.
• AI Marketing Booklet Creator: Print a Tour Brochure From Itineraries — Turn three tour itineraries into a print-ready booklet: AI-drafted copy, a pricing page, Canva layout, print specs and a proof checklist.
• How to Start a Bike Tour Business: Routes, Pricing and Bookings With AI — A staged plan for a first guided bike tour: ride-test the route, price per rider from real costs, check insurance and waivers, choose a booking tool.
• Walking Tour Software: Ticketing, Guide Rotas and AI Enquiries — How a small walking-tour company sets group caps, guide rotas, weather rules and private-group quotes, and which writing jobs AI can take on.
• Travel Industry AI Chatbot: What a Tour Operator Website Should Answer — What a tour operator's website chatbot should answer, look up and hand to staff: meeting points, cancellation wording, availability, refunds and safety.
• Can AI Handle Fishing Charter Bookings and Weather Call-Offs? — What AI can do for a fishing charter's seat bookings and weather call-offs, what stays with the skipper, with a decision log and message templates.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Rezdy, Checkfront and Bookeo (tours and activities) pricing pages checked in October 2026; FareHarbor's own pricing page returned an error, so its fees are described as reported and unconfirmed.