One inventory, every sales channel: how to stop the sync chaos

The problem isn't distribution — it's synchronisation

Most tour and activity operators in the UK and Australia are not short of sales channels. Viator, GetYourGuide, Airbnb Experiences, direct website bookings, DMC trade partners, inbound travel agents — the distribution options have never been broader. The bottleneck is not reach. It is keeping all of those channels looking at the same availability, in real time, without an ops team member manually updating each one.

When you sell the same departure slot through three channels and update availability in none of them automatically, you are one busy Saturday away from a double-booking and a refund conversation you did not need to have. At low volume, manual management feels survivable. At scale, it becomes the thing that caps your growth.

This article is about the architecture that solves it — what a connected inventory system actually looks like, where operators usually get stuck, and when it makes sense to build rather than buy.

Why the standard advice breaks down

The usual recommendation for operators is to sign up for a channel manager — a tool like Rezdy, Fareharbor or Bokun — that connects your booking calendar to the major OTAs. For many operators, that is exactly the right starting point, and if you have not yet read our guide on online booking systems for tour operators in Australia, it covers the fundamentals well.

The limitation appears when your product does not fit the standard mould. Off-the-shelf channel managers are designed for the common case: a fixed-capacity experience, a simple pricing tier, a supported OTA list. If you run multi-day touring with variable group sizes, dynamic pricing by lead time, a mix of trade and direct channels, or partner types that the major platforms have never heard of, you will quickly find yourself patching gaps with spreadsheets and Slack messages — which defeats the purpose.

The other limitation is partner connectivity. Viator and GetYourGuide have well-documented APIs. Many regional DMCs, inbound agents and corporate travel desks do not. Connecting to a trade partner who sends enquiries by email, expects an XML feed, or needs a white-label booking widget requires a level of custom integration that no off-the-shelf channel manager is going to handle for you.

What a connected inventory architecture actually looks like

At its simplest, the architecture has three layers.

1. A central reservation system (CRS) — the source of truth

This is where availability, capacity and pricing live. Every booking, regardless of which channel it originated from, writes back to the CRS and decrements the available slots. Nothing else is authoritative. If your booking engine, your OTA extranet and your ops spreadsheet all have different numbers, you do not have a CRS — you have three sources of uncertainty.

2. Channel connectors

These are the integrations that push availability from the CRS out to each sales channel, and pull confirmed bookings back in. For major OTAs, this means an API integration. For smaller partners, it might mean an iCal export, a webhook, or a custom XML feed. The quality of these connectors determines how real-time your sync actually is.

3. A booking surface for each channel

This might be your own website's booking widget, a Viator product listing, a trade partner portal, or a white-label page you've given to a hotel concierge desk. Each surface shows live availability pulled from the CRS. None of them hold local copies.

The failure mode operators most commonly hit is having layer 3 without layers 1 and 2 — a booking widget on their website that does not talk to their OTA listings. That is not connected inventory. That is two disconnected booking surfaces with a human in the middle.

OTA connectivity: what the major platforms actually offer

Viator (TripAdvisor) and GetYourGuide both offer API access for operators, though the onboarding process, documentation quality and support vary. Viator's Experiences API allows operators to manage availability and receive booking notifications programmatically. GetYourGuide's Supplier API covers similar ground. Both require technical resource to integrate — this is not a no-code configuration task.

For operators who do not have that resource in-house, the practical path is either an off-the-shelf channel manager that already has these integrations pre-built, or a development partner who can wire them up as part of a wider reservation system build.

The important thing to understand is that iCal-based sync — which many operators rely on as a stopgap — is not real-time. iCal exports are polled at intervals; a booking made at 10:03 may not be reflected on another channel until 10:30 or later. For high-frequency products (city walking tours, escape rooms, cooking classes), that lag is enough to cause oversells on busy days.

Trade and reseller connectivity: the harder problem

OTAs are the visible part of the distribution challenge. The harder problem, and the one that is most often solved with manual workarounds, is trade partner connectivity.

A DMC or inbound travel agent sending group bookings expects either a real-time availability check or an allocation they can draw down against. A hotel concierge programme needs a booking widget they can embed or a phone line with reliable availability information. A corporate travel platform may want an XML feed or a direct API. None of these are covered by the standard OTA integrations.

This is typically where operators with serious distribution ambitions find that their off-the-shelf channel manager runs out of road. It handles Viator. It does not handle the regional DMC who sends 40 pax per month but needs a live allocation portal.

Building that portal — a simple, white-label interface where trade partners can check availability, make bookings and manage their allocations — is one of the most common briefs we see from operators who have outgrown their current stack. It is also the kind of build that can meaningfully move the needle on trade volume, because it removes the friction that causes agents to stop selling you in favour of operators who make it easier. For more on what that procurement decision looks like, our build vs buy guide for tour booking platforms covers the decision framework in detail.

When to consider a custom reservation system

The build vs buy question for tour inventory connectivity comes down to three factors.

Complexity of your product rules. If your capacity logic, pricing tiers or group size handling is straightforward, an off-the-shelf system will cope. If you have rules that require custom configuration every time you add a product, the overhead of working around a generic platform accumulates.

Number and type of channels. If you distribute across more than five or six channels, including trade partners who need bespoke connectivity, the patchwork of integrations required to hold it together manually starts to cost more than building something that owns the integration layer.

Growth trajectory. A system that works at 500 bookings a month may not work at 5,000. The cost of migrating later — in ops disruption, re-integration work and potential data loss — is real. If you are planning to scale distribution seriously, the architecture decision is worth making once, properly, rather than incrementally.

AI-assisted development is increasingly useful in shortening the discovery-to-release cycle for custom reservation systems. It does not change the fundamental build vs buy calculus, but it can compress the time between scoping a custom integration and having it in test, which makes the build option more accessible for operators who previously could not justify the timeline.

What a well-built system handles automatically

When the architecture is right, the following happen without manual intervention: a booking on Viator decrements availability on GetYourGuide, your website and your trade partner portal simultaneously; a cancellation releases that slot back to all channels within seconds; your ops team gets a single consolidated manifest for each departure, regardless of which channel each pax booked through; and your yield management rules — close-out periods, minimum numbers, last-minute pricing — apply consistently everywhere.

The ops team stops managing channels. They manage the product. That is the shift that unlocks the growth that better distribution was supposed to deliver in the first place.

If you are at the point where manual channel management is the bottleneck, it is also worth reviewing how your post-booking communications stack works — automated reminders, waivers and pre-trip information are the next layer of ops that breaks under volume. Our guide on reducing no-shows with booking software covers that side of the picture.

The next step

If your current setup relies on manual extranet updates or iCal sync to keep OTAs and resellers in step with your real availability, the first honest question to ask is: how often does it go wrong, and what does that cost? The answer usually makes the case for doing something about it more clearly than any architecture diagram can.