How to Cap OTA Inventory Without Losing Channel Marketing Reach
The OTA commission ceiling is a real thing. Viator at 20–30% per booking. GetYourGuide at similar. Expedia for accommodation legs. Booking Holdings sitting upstream of FareHarbor for activity bookings. The percentages compound — and once an operator's revenue is OTA-dominant, the cost of every booking has been quietly priced in to the customer journey years before the operator notices.
The standard reaction is to "go direct" — push customers to the operator's own website, drop the OTAs, recapture the commission. Done at scale, this kills the marketing reach the OTAs were providing in the first place. The OTA might cost 25% per booking, but the OTA also brought the booking to your dock. Drop them entirely and the booking goes somewhere else — to a competitor still listed on the OTA, or to a customer who never finds you at all. (How transport operators lose revenue without realising it →)
The better question — the one the OTA-vs-direct debate keeps missing — is how much OTA capacity do you actually need? Once you know the answer, you can stop selling capacity to OTAs you don't need them for, while keeping them as a marketing channel for the capacity you do.
This is what channel mix optimisation looks like in practice. And it depends on a piece of booking-platform architecture most operators have never seen described clearly: capacity rules per channel, configured at the architecture level, not as a discount code stapled on after the fact.
The math of the channel mix shift
Pick a real example. A 200-pax ferry running a peak Saturday sailing. Two scenarios:
Scenario A — current state. The operator sells 200 seats. 130 go through Viator at 25% commission. 70 go direct at 0% commission. Average ticket $50.
Viator revenue: 130 × $50 × 0.75 = $4,875
Direct revenue: 70 × $50 × 1.00 = $3,500
Total revenue: $8,375
Effective commission: ~19%
Scenario B — capped channel mix. Same ferry. Same 200 seats. But Viator capacity capped at 80 seats; the remaining 120 reserved for direct.
Viator revenue: 80 × $50 × 0.75 = $3,000
Direct revenue: 120 × $50 × 1.00 = $6,000
Total revenue: $9,000
Effective commission: ~11%
Scenario B captures $625 more per sailing on the same physical capacity, with no marketing-reach loss because Viator still has the listing live — it just sells fewer seats per sailing.
Across a peak season with ~80 sailings, that's ~$50,000 in additional revenue. Across a year, it's six figures. Without changing the ferry, the staff, the timetable, or the marketing budget. The cost is purely architectural — the booking platform's ability to enforce a per-channel cap.
The math works the same for tour operators, cruise operators, and multi-modal packages. The capacity exists; the question is which channel sells it.
Why this requires the right inventory architecture
The capacity cap has to be enforced at the inventory layer, not the listing layer. That distinction is the whole game.
The wrong place: the OTA listing itself. The operator pushes 200 seats to Viator's listing, then manually pulls the listing down when 80 are sold. By the time the manual update propagates, sailings are oversold or the listing is offline for hours. Operations staff become the channel-cap mechanism. It doesn't scale.
The right place: the operator's inventory architecture. The platform tracks the capacity pool centrally. Every channel — website, mobile POS, agent portal, OTA connectors — draws from that pool, with rules per channel. Viator queries availability, the platform answers "80 seats from your cap" not "200 seats from the actual pool." When Viator's 80 are sold, the platform answers Viator's next availability query with zero, regardless of how full the actual sailing is. Direct bookings keep going.
The technical pattern (booking-platform agnostic) requires:
Channels modelled as distinct first-class entities — not just URLs the booking widget gets embedded in
Per-channel capacity rules per service — set on each sailing / departure / tour
Real-time synchronisation so OTAs and direct bookings can't oversell each other
Reservation/release logic — reserved capacity for one channel can release back to the general pool at a configurable time before departure
Without those four pieces, the channel-mix conversation stays theoretical. The operator can't actually enforce caps without burning operations hours doing it manually. (The true cost of generic booking systems for transport operators → covers the broader pattern of features that get described as bookable but only work with manual operator effort to back them up.)
What channel caps look like in practice
Three patterns operators use, each solving a different problem:
Pattern 1 — Hard cap on OTA capacity
Used when the OTA channel is the dominant one and the operator wants to shift to direct over time.
"Viator gets 40% of every sailing's capacity. Direct gets the other 60%. If Viator's 40% sells out, the listing returns 'sold out' to Viator while the website keeps selling. If direct sells out first, the website shows 'sold out' while Viator keeps selling its remaining cap. The operator never oversells; the channels stay balanced."
The 40% number isn't fixed by physics. It's the operator's call, informed by:
Historical conversion rate from OTA listings (if the listing converts 5% of viewers, you need fewer seats listed there)
Direct-channel marketing maturity (the smaller the direct funnel, the more OTA capacity you might still need)
Margin tolerance (lower cap = higher margin; higher cap = more total bookings at lower margin)
Pattern 2 — Reserve capacity for direct, release if unsold
Used when the operator wants the option to capture late-booking direct customers without sacrificing the OTA reach.
"Reserve 25% of capacity for direct bookings. Release that 25% to OTAs 24 hours before departure if it hasn't sold. The operator gets first crack at the high-margin direct sale, but doesn't lose the seat to an empty sailing if direct demand doesn't materialise."
The 24-hour release window is the operator's call. Some operators set it tighter (12 hours) to maximise direct upside; some looser (48 hours) to give OTAs time to actually convert the released seats.
Pattern 3 — Tier-locked pricing per channel
Used when the operator wants to keep the OTA channel but push it toward lower-margin segments.
"Direct bookings see all price tiers including peak. OTAs only see the standard and budget tiers — never the peak tier. When peak-price seats are available, only the website and agent portal can book them. The OTA listing returns 'sold out' for peak even when peak seats exist, because the OTA isn't authorised to sell that tier."
This pattern keeps OTAs busy at the operator-chosen price ceiling, while the website captures the peak-pricing upside.
Operators can combine all three patterns on the same sailing. The architecture composes — caps and reserves and tier locks are different facets of the same per-channel-rule model.
The decision framework — what cap should I pick?
Pick the cap based on three inputs:
What's your current OTA mix? Pull last month's revenue by channel. If OTAs are >70%, you have aggressive room to cap. If OTAs are <30%, the cap conversation is less urgent.
What's your direct-channel conversion rate? If your website converts 4% of visitors and the OTA converts 1.5%, capping OTAs and pushing visitors to direct genuinely captures the lost margin. If your website is 0.5% and the OTA is 3%, capping OTAs costs you bookings the website can't replace yet.
What's your marketing pipeline maturity? If you're investing in direct-channel marketing — SEO, paid social, partnerships, email — caps make the investment pay back faster. If you're not investing, capping just leaves OTA seats unsold.
The rough heuristic: start at 60% OTA / 40% direct if you're OTA-dominant. Move 10 percentage points per quarter toward direct as your direct conversion rate climbs. Don't try to flip overnight — sudden cap changes confuse OTA algorithms and can demote your listing visibility.
What this is not
Capping OTA capacity is not the same as fighting Viator. Most operators benefit from keeping OTAs live — the listing visibility, the international reach, the trust signal a brand-name OTA provides — particularly for the half of customers who book first through an OTA and only later discover direct. The point is to stop selling capacity through the OTA that the operator could have sold direct anyway.
This is also not the same as "raising prices." The base ticket price stays. What changes is which channel gets to sell that ticket, with which margin. The customer pays the same; the operator keeps more.
And it's not a one-time switch. Channel caps are configurable per service per departure. A Tuesday sailing in shoulder season might have 80% OTA cap (the operator needs the volume); a Saturday peak sailing might have 20% OTA cap (the operator wants the margin). Same fleet, same software — different rules per sailing.
What good looks like at six months in
An operator running mature channel caps usually sees:
Effective commission rate down 5–8 percentage points
Direct booking share up 15–25 percentage points
OTA listings still live and still bringing in marketing-reach bookings — just at smaller per-sailing volume
Customer database growing first-party (every direct booking captures the contact; OTA bookings often do not)
Peak-season chaos reduced because the operator controls which channels sell when
The investment isn't in marketing spend or staff hours — it's in the booking platform's architecture. Once the rules are configured, they run automatically every sailing. Channels stay synced in real time. Operations staff stop being the cap mechanism and go back to running the ferry.
How JetSetGo handles this
JetSetGo's inventory architecture models channels as first-class entities and supports all three patterns above — hard caps, reserved-with-release, tier-locked pricing per channel. The rules are configured per service in the operator's admin, not coded by an engineer. OTAs (Viator, GetYourGuide, Expedia) connect via the existing OTA connectors and respect the rules without any OTA-side configuration change.
The capability sits underneath the broader multi-modal booking platform, and is most useful for ferry operators and tour operators whose channel mix is currently OTA-heavy.
Book a demo → to see channel caps configured for your own operation.