If you run a tour, an experience, or an adventure business in Australia, your website almost certainly uses FareHarbor or Rezdy as the booking layer. The choice between them was the central technology decision for most Australian operators between 2015 and 2020, and the choice held up because both products solved a real problem — they put a working booking widget on a website that didn't have one.

That was the right call in 2018. In 2026, the trade-offs have shifted. The widgets have got slower. The commissions have gone up. The visual quality has stagnated. And the alternative — a properly built booking flow native to your own website — has got dramatically cheaper than it was. I'm not going to tell you that every operator should rip out their FareHarbor account tomorrow. But I am going to tell you that the default assumption that "you need FareHarbor or Rezdy" is a 2018 assumption, and it deserves an actual review in 2026.

The case for both platforms first. Then the case against. Then a structural look at when each option is the right one.

What these platforms actually do

FareHarbor and Rezdy are both Reservation Management Systems. They do four things:

Inventory and availability — calendar of dates, time slots, capacity per slot
Booking flow — guest details, pricing, add-ons, waivers
Payment processing — credit card capture, refunds, settlements
Connectivity — sync to Online Travel Agencies (OTAs) like Viator, GetYourGuide, Klook, TripAdvisor Experiences

That fourth piece is the one most operators undervalue. Building an inventory system isn't trivial. Building inventory that syncs across 6–12 different OTA channels in real time without double-booking is genuinely hard. Both FareHarbor and Rezdy did this well enough, early enough, that they became the default.

The booking widget that sits on the operator's website was, historically, the surface you mostly saw. It was free. It worked. You embedded an iframe and you were live. That was a strong proposition for a small operator without a developer.

What FareHarbor and Rezdy now cost

The pricing changed since most operators signed up.

FareHarbor is structurally a commission play. In Australia, the commission sits at 5–8% per direct booking depending on negotiation, with 6% being typical. There's no separate payment processing fee — that's bundled into the commission. There's no monthly fee for the basic platform. If you want them to build you a website on top of the booking layer, that's around $499/month or ~$5,000/year for their managed site service.

For a tour operator doing $400,000 a year in direct online bookings, 6% commission is $24,000/year. That's the cost of having FareHarbor as the booking layer.

Rezdy is structurally a subscription with a small booking fee. Plans start around $49/month plus a 2% direct booking fee. For the same $400,000 operator, that's $8,000 in booking fees plus around $600 in subscription, so roughly $8,600/year — about a third of the FareHarbor cost at that volume.

Checkfront sits closer to Rezdy — around $99/month plus a 3% booking fee. Bookeo starts at $14.95/month with no booking fees, which is appealing on paper but usually requires significantly more setup.

The pricing alone tells a story. If you're an Australian operator with a meaningful volume of direct bookings, the FareHarbor commission is real money — money that, at higher volumes, justifies building something custom.

The case for keeping FareHarbor or Rezdy

The honest case for staying.

Channel connectivity is genuinely hard

If 60% of your bookings come through Viator, GetYourGuide, and Klook, you need a system that manages inventory across those channels in real time. Both FareHarbor and Rezdy do this well. Rebuilding that integration from scratch is expensive and slow, and the OTAs aren't always cooperative with smaller bespoke integrations.

For OTA-heavy operators, the booking layer is doing serious work that isn't visible on the website. Ripping it out means rebuilding it. That's rarely worth it.

Payment processing and compliance are non-trivial

Both platforms handle PCI compliance, fraud screening, refunds, and chargebacks. Building this yourself means picking a payment processor (Stripe, usually), implementing the booking flow, handling 3D Secure, building a refund interface, and accepting the support load when a payment fails at 9pm.

This is doable. It's not free. For an operator without an in-house developer, it's a real consideration.

The widget works

A FareHarbor iframe drops onto any website. It works. It doesn't fall over. The conversion rate is acceptable. For an operator whose website strategy is "have a website and let the booking widget do the work", that's the right level of investment.

The case against — the actual problems

These are the issues I keep finding on operator sites in 2026.

The widget destroys page performance

A FareHarbor iframe adds around 600KB–1.2MB of JavaScript and CSS to the page, depending on configuration. On a 4G mobile connection in regional Victoria, that translates to 2–4 additional seconds of load time. The widget is rendered separately from the rest of the page, which means a working website often shows a spinning loader where the booking flow should be for the first few seconds of the visit.

We've audited operator sites with Lighthouse performance scores of 32 on mobile, where the rest of the site would have scored 85+. The widget is the load-time killer. On a page where the booking widget is the conversion mechanism, slow load on that widget directly reduces bookings.

Google's Core Web Vitals are now part of the search ranking signal. A page that loads slowly because of the booking widget ranks lower for the queries you most want to rank for ("Great Ocean Road tour", "Sydney harbour cruise"). The widget is hurting both conversion and discoverability at the same time.

The visual quality is stuck in 2018

Both FareHarbor and Rezdy let you customise colours and fonts in the widget. That's the extent of the visual control. The layout, the spacing, the form patterns, the date picker UI — none of that changes. Every FareHarbor widget looks like every other FareHarbor widget.

For an operator selling a $90 day tour where the booking is a 90-second decision, this is fine. For an operator selling a $4,500 multi-day adventure where the booking is a research project, the widget feels cheap relative to the rest of the brand. The friction at the booking step undermines the premium positioning every other element of the site is trying to build.

Mobile conversion is materially worse

The widgets work on mobile. They don't work well. The booking flow is a tab-by-tab series of steps, each requiring the user to scroll and re-orient. The date picker is small. The pricing summary frequently disappears off the visible area. The "add-ons" step is confusing.

For operators where 70%+ of bookings now come from mobile, this matters. The mobile conversion rate gap between a native mobile-first booking flow and a FareHarbor widget is around 1.5–3 percentage points in our experience. On $400,000 of annual revenue, that's $60,000–$120,000 left on the table per year.

The commission compounds against you

FareHarbor at 6% felt reasonable in 2018 when nobody was offering a real alternative. In 2026, with custom development cheaper and Stripe's APIs mature, the commission feels like a tax on direct bookings the operator built themselves.

The break-even math is straightforward. A bespoke booking flow built on top of Stripe costs $15,000–$40,000 depending on complexity. At a 6% FareHarbor commission and $400,000 in annual direct bookings, the build pays back in 5–12 months. At $1M in direct bookings, it pays back in 2–5 months. Operators below $200,000 in direct online bookings are typically still better off with FareHarbor or Rezdy.

The two structural options

Here's how I'd actually frame the choice for an Australian tour operator in 2026.

Option 1: Stay on the widget, fix the website around it

If you're under $300,000 in direct online bookings or OTA-dependent, keep the widget. Move from FareHarbor to Rezdy if the commission math hurts (it usually does). Don't rebuild the booking layer.

What you can do is fix the website around the widget. Optimise the rest of the page so the widget isn't the entire conversion experience. Make sure the page above the widget loads in under 1.5 seconds so the visitor stays engaged while the widget initialises. Use Rezdy's REST API rather than the standard iframe widget for at least the highest-converting tours — the API gives you control over the visual presentation while keeping the inventory connectivity.

This is the right answer for most small operators. It's also what most operators don't do — they take the widget, drop it in, and don't optimise the surrounding page.

Option 2: Native booking flow, channel manager separately

If you're over $500,000 in direct online bookings, or you sell experiences where the booking is a considered $1,000+ decision, the right answer is usually a native booking flow on your own site with a separate channel manager (still possibly Rezdy or Bokun) handling OTA distribution.

This means:

The booking flow on your own site is built specifically for your tours, your customer journey, and your brand
Payments go through your Stripe account directly
Inventory is the source of truth on your system, and the channel manager pulls availability from there
OTAs still get their bookings through Rezdy or Bokun; the OTA commissions still apply
You save the 6% on direct bookings and gain control of the user experience

The build is more expensive. The ongoing cost is dramatically lower. The conversion rate on the booking flow is materially better. The Core Web Vitals problem goes away.

The hybrid that often makes sense

There's a middle option that suits a lot of operators. Use Rezdy as the inventory and channel manager. Build a custom booking layer on top of Rezdy's API for your own website. Continue to use the standard Rezdy widget for any micro-sites, partner sites, or the agent network.

This gives you the channel connectivity Rezdy is good at, with a native-feeling booking flow on the website that actually carries your brand. The cost sits between the two options above — roughly $10,000–$20,000 build, plus the ongoing Rezdy subscription, but no FareHarbor commission.

For most operators in the $300,000–$800,000 direct booking range, this is the right structure. It's not the answer either Rezdy's sales team or FareHarbor's sales team will tell you to consider, because it splits the value across two layers — but it's usually the answer that produces the best operator economics over three years.

The Tourism Research Australia context

For context on whether any of this is worth doing — international visitor spend in Victoria hit $9.7 billion in the year to December 2025, up 7% on the previous year, with China alone spending $3.2 billion in the state (Tourism Research Australia data). Regional Victoria visitor spend grew 30%. The market for Australian tour operators is the strongest it's been in years.

That growth is the reason it's worth re-examining the booking infrastructure. The operators winning the next three years will be the ones whose websites convert international research traffic at the higher rates. The booking widget is the conversion mechanism. If it's costing you 6% on every direct sale and shaving 2 points off your conversion rate, that's a meaningful drag at exactly the wrong moment in the cycle.

The honest bottom line

FareHarbor and Rezdy aren't broken. They're good products that solved a real problem. The trade-offs in 2026 are different from the trade-offs in 2018 because the cost of building a bespoke booking layer dropped, the commissions on the widgets didn't, and the Core Web Vitals impact of a 1MB iframe started costing operators meaningful search rankings.

For small operators, the right answer is still a widget — but Rezdy at 2% rather than FareHarbor at 6%. For mid-to-large operators, the right answer is increasingly a native booking layer with a separate channel manager. For operators selling considered premium experiences, the widget is actively undermining the brand and should be replaced as soon as the development capacity is available.

Run the math on your specific commission against the cost of building the alternative. The break-even is usually less than 12 months. That's the conversation the next agency or developer should be having with you, not "do you want FareHarbor or Rezdy".

If you'd like an honest look at the booking infrastructure on your current site and what an alternative would actually cost, book a free audit. We'll review the widget performance, the commission cost, and what a bespoke booking layer would look like for your specific volume and tour mix.

FareHarbor vs Rezdy vs Custom: Real 2026 Cost