TL;DR — Key Takeaways
- ✓ Hotel booking engine pricing comes in three models: SaaS subscription, revenue share, and one-time custom build.
- ✓ Revenue share feels cheapest at launch — but the percentage taken on every booking can quietly outgrow a flat SaaS fee as volume rises.
- ✓ A custom build can run $100K–$300K+ upfront plus ongoing maintenance — viable only for large, funded OTAs.
- ✓ The right model depends on your booking volume and growth stage, not the headline price.
- ✓ Use the 3-year cost calculator below to compare models on total cost, not sticker price.
Ask three booking engine vendors what they charge and you will get three completely different answers — a monthly fee, a cut of every booking, or a six-figure build quote. That’s because hotel booking engine pricing isn’t one number; it’s three different models, each of which wins at a different stage of an OTA’s life. Pick the wrong one and you either overpay upfront or bleed margin on every booking for years.
This guide breaks down all three pricing models, shows the real three-year cost of each, and reveals the margin trap that catches fast-growing OTAs. The stakes are bigger than they look: with the global OTA market projected by Skift to reach $107 billion by 2026, even a one or two percent difference in platform economics compounds into serious money as you scale.
The 3 Hotel Booking Engine Pricing Models
Almost every booking engine pricing structure falls into one of three models. Here’s how each works and what it really means for your cost.
1. SaaS subscription
You pay a fixed monthly or annual fee for the platform, regardless of how many bookings you process. Predictable, easy to budget, and — crucially — your per-booking cost falls as volume rises. The more you sell, the cheaper each booking effectively becomes. This is why most scaling OTAs end up on SaaS.
2. Revenue share
The vendor takes a percentage of each booking (or a fixed fee per booking) instead of a subscription. Little or no upfront cost, so it’s attractive when you’re starting out. The trade-off: your cost rises in lockstep with your success — every booking you win, the vendor wins a slice of too.
3. One-time custom build
You commission a bespoke booking engine — large upfront cost, full ownership, and you carry all ongoing maintenance. A custom build commonly runs $100,000 to $300,000+ before launch, plus the engineering cost of maintaining every supplier integration forever after. Only viable for large, well-funded OTAs. We break this down in our in-house vs outsourcing analysis.
The Margin Trap: Why Cheapest Isn’t Cheapest
Here’s the mistake that catches growing OTAs. Revenue share looks like the obvious choice at launch — almost no upfront cost, low risk, pay only when you book. So you sign up. Then you grow.
The problem is that a percentage-of-booking model scales with your revenue, not with the vendor’s cost to serve you. Processing your 10,000th booking costs the vendor essentially the same as your 100th — but under revenue share, you pay vastly more for it. At low volume the percentage is trivial. At high volume, that same percentage can quietly exceed what a flat SaaS subscription would have cost you many times over.
The rule of thumb:
Revenue share is cheapest while volume is low; SaaS becomes cheaper once you cross a break-even booking volume. The moment you’re confident your volume will grow, model both — because the cheapest option at launch is frequently the most expensive at scale. Find your break-even point before you sign, not after.
A worked example: how the trap plays out
Picture two OTAs that launch on the same day. Both expect to grow. One picks a flat SaaS subscription; the other picks revenue share at a small percentage of booking value because it has almost no upfront cost.
Year one — revenue share wins. Volume is modest, so the percentage taken adds up to less than the SaaS fee. The revenue-share OTA feels clever; the SaaS OTA is paying for capacity it isn’t fully using yet.
Year two — they converge. As bookings climb, the percentage-based bill grows every month while the SaaS fee stays flat. Somewhere in here the two lines cross. That crossing point is the break-even volume, and it’s the single most important number in the whole decision.
Year three — SaaS wins decisively. The SaaS OTA’s per-booking cost has fallen the whole time, because a fixed fee divided by more bookings keeps shrinking. The revenue-share OTA is now paying a slice of every single booking at full volume — and that slice has quietly become far larger than a flat subscription ever would have. Same growth, very different platform bill.
The takeaway:
The right answer flips entirely based on where your volume lands relative to the break-even point — which is exactly why you should run your own numbers before signing. The downloadable calculator below does this in seconds: enter your bookings, growth rate, and each vendor’s terms, and it shows which model costs least over three years at your volume.
🧮
Free Download · Excel Calculator
Booking Engine 3-Year Cost Calculator
Plug in your booking volume and compare SaaS vs revenue share vs custom build over three years. Find your break-even point and see which model actually costs you least at scale.
The Hidden Costs Nobody Quotes
The headline price is never the full price. These are the costs that don’t show up in the sales deck but hit your P&L anyway:
- Supplier integration & maintenance — if the engine doesn’t come with inventory, every supplier you add is a separate integration to build and maintain. This is where a hotel API aggregator changes the math entirely.
- Setup & onboarding fees — some vendors charge separately to get you live.
- Per-transaction or payment-gateway fees — sometimes layered on top of the core model.
- Customisation & support tiers — premium support or feature unlocks priced separately.
- The cost of slow performance — a cheaper but slower engine loses bookings at checkout, which never appears on the invoice but shows up in revenue.
Want predictable pricing AND inventory built in?
ZentrumHub’s booking engine bundles 100+ hotel suppliers through one API — so you skip the per-supplier integration costs that inflate every other quote. White-label, sub-1-second, live in days.
See the Booking Engine →
What Drives Booking Engine Pricing Up or Down
Two OTAs can get wildly different quotes from the same vendor. These are the variables that move the number — knowing them lets you predict your cost and negotiate from a position of understanding.
Booking volume
The biggest lever. Higher volume strengthens your hand on SaaS pricing but inflates revenue-share bills. Always quote your projected volume, not just today’s.
Number of suppliers & integrations
If each supplier is billed or built separately, cost climbs fast. A platform that bundles many suppliers through one connection collapses this line item — the core reason aggregator-based pricing often beats piecemeal integration.
Customisation & white-label depth
Off-the-shelf is cheapest. Heavy UI customisation, bespoke workflows, and deep branding all add cost — decide what you genuinely need versus what’s nice to have.
B2B + B2C from one platform
Running consumer and agent channels on one engine usually costs less than two systems — but confirm whether the vendor charges per channel. See our
B2B vs B2C software guide.
Support tier & SLA
Standard support is usually included; guaranteed response times, a dedicated manager, or uptime SLAs are often priced as premium tiers.
What to expect at each stage (qualitatively)
Exact figures vary too much by region, inventory, and vendor to quote reliably — but the shape of pricing by stage is consistent:
- Startup / launching: lowest total outlay on revenue share or an entry SaaS tier. Prioritise getting live cheaply and validating demand over locking in long-term rates.
- Growing OTA: moving onto SaaS as volume becomes predictable; the focus shifts to protecting margin and negotiating volume terms.
- Established / enterprise: negotiated SaaS with custom SLAs, or selectively building proprietary pieces. The conversation is about control and total cost of ownership, not sticker price.
Pricing Red Flags to Watch in a Contract
The model matters, but so does the fine print. Watch for these before you sign anything:
Per-supplier integration charges
If every new supplier triggers a fee or a build, your inventory growth is taxed. This quietly becomes one of the largest costs over time.
Annual price escalators
Automatic yearly increases buried in the contract can outpace your growth. Ask for the escalation clause in writing and cap it.
Long lock-in with no exit
Multi-year commitments with steep termination penalties trap you on the wrong model as your volume changes. Favour flexibility, especially early.
Stacked transaction fees
A low headline rate with per-transaction or payment-gateway fees layered on top can cost more than a higher all-inclusive price. Always ask for the all-in number.
Which Model Fits Your Stage
Just launching / unproven volume → Revenue share
Minimal upfront risk while you validate the business. Accept the per-booking cost as the price of starting cheap — but set a calendar reminder to re-evaluate once volume climbs.
Steady or growing volume → SaaS subscription
Once bookings are consistent, a flat fee protects your margin and makes each additional booking cheaper. This is the sweet spot for most growing OTAs.
Large, funded, unique needs → Custom build
Only when you have the engineering team, the capital, and a product requirement no platform can meet. For everyone else, the build cost and maintenance burden outweigh the control. See our
white-label launch guide for the faster path.
Questions to Ask Any Vendor
Before signing any booking engine contract, get clear answers to these:
- Is inventory included, or do I pay separately to integrate each supplier?
- Under revenue share, what’s my cost at 10×, 50×, and 100× my current volume?
- Are there setup, onboarding, or per-transaction fees on top of the headline price?
- What’s the total three-year cost at my projected volume — not just year one?
- Can I switch models later (e.g. revenue share → SaaS) as I grow?
- Who maintains supplier integrations, and is that cost included?
Frequently Asked Questions
How much does a hotel booking engine cost?
It depends on the pricing model. SaaS subscriptions charge a fixed monthly or annual fee. Revenue-share models take a percentage of each booking with little upfront cost. Custom builds commonly run $100,000 to $300,000 or more upfront, plus ongoing maintenance. For most OTAs, SaaS or revenue share is far more cost-effective than building. The key is to compare total cost over three years at your projected booking volume, not just the year-one or headline price.
Is SaaS or revenue share better for a booking engine?
It depends on your booking volume. Revenue share is cheaper at low volume because there’s little upfront cost — you only pay when you book. SaaS becomes cheaper once you cross a break-even volume, because the flat fee doesn’t rise as you sell more, so your per-booking cost falls. Early-stage OTAs often start on revenue share, then move to SaaS as volume grows. Model both at your projected volume before deciding — the cheapest at launch is often the most expensive at scale.
Why is revenue share more expensive at scale?
Because the vendor’s cost to serve you barely changes as you grow, but a percentage-of-booking fee rises directly with your revenue. Processing your ten-thousandth booking costs the vendor roughly the same as your hundredth — yet under revenue share you pay far more for it. At low volume the percentage is negligible; at high volume it can quietly exceed many times what a flat SaaS subscription would have cost. That’s the margin trap fast-growing OTAs fall into.
Should I build my own booking engine to save on fees?
Rarely. A custom build commonly costs $100,000 to $300,000 or more upfront, takes 12+ months, and leaves you maintaining every supplier integration forever. The fees you save are usually dwarfed by the build cost, the delay to launch, and the ongoing engineering burden. Building only makes sense for large, well-funded OTAs with dedicated engineering teams and a genuinely unique requirement. Most OTAs save far more by using a SaaS or white-label platform with inventory already included.
Does booking engine pricing include hotel inventory?
Not always — and this is the biggest hidden cost to check. Some booking engines are just the front-end software, leaving you to integrate and maintain each hotel supplier separately, which adds significant engineering cost. Others, like ZentrumHub, bundle the engine with 100+ hotel suppliers through one API, so inventory and deduplication are included. Always ask whether supplier connectivity is part of the price or a separate cost, because it can change the total dramatically.
Why do two OTAs get different booking engine quotes?
Pricing moves with several variables: booking volume, how many suppliers and integrations you need, depth of customisation and white-label branding, whether you run B2B and B2C on one platform, and your support tier or SLA. The biggest swing is usually supplier integrations — if each supplier is billed or built separately, costs climb fast, whereas a platform that bundles many suppliers through one connection collapses that line item. When comparing quotes, make sure each vendor is pricing the same scope, including inventory.
Pricing that scales with you — not against you.
ZentrumHub’s booking engine bundles 100+ suppliers, 900K+ hotels, and sub-1-second performance into one platform — no per-supplier integration bills, no margin trap. 3M+ room nights booked. 99.99% uptime.
