TL;DR
Integration pricing comes in four shapes: a one time connection fee, a monthly interface fee, usage charges, or a revenue share, and both sides of a link may charge.
Mews and Stayntouch publish free integrations, while Oracle bills OHIP partners per call, at approximately USD 20 per 10,000 calls above the plan.
Keep standard PMS and channel manager connections inside the subscription, because a fee taxes the reason hotels buy.
Charge one time build fees for custom interfaces and pass through metered upstream costs above a stated allowance.
Integration pricing is the decision every hotel tech vendor makes twice: what you charge hotels to switch on a connection, and what the platforms you connect to charge you. Get it wrong and you either give away real engineering cost or put a toll on the one thing hoteliers buy for. This post gives you the decision first, then the fee models named vendors actually publish, then the pros, cons and a charge if, don't charge if test.
Integration pricing is how a software vendor recovers the cost of connecting its product to other systems: a one time connection fee, a recurring interface fee, a usage charge, a revenue share, or nothing at all because the cost sits inside the subscription.
The decision in one table
If you only read one section, read this. It assumes you are a hotel tech vendor selling into hotels that already run a PMS, a channel manager and a payments stack.
Your situation | Recommended integration pricing | Why |
|---|---|---|
Standard connection to a major PMS, used by most customers | Include it in the subscription | It is table stakes and a fee reads as a penalty for using your product properly |
Custom or legacy interface built for one group | Charge a one time build fee | Real, unrepeatable engineering work the next customer will not pay for |
Connection where the upstream platform bills you per call or per event | Pass through usage above a fair included allowance | Your cost grows with their volume, not yours |
Premium data sync that adds measurable revenue | Package it into a higher tier | Customers pay for the outcome, not the plumbing |
Small independent hotels | Never charge per interface | The fee math kills the deal before the demo |
Integration pricing is one input into the price stage of the hotel tech GTM system. The structure you choose should match your core model, whether per room, per property or flat.
What named vendors publish about integration fees
Most hotel tech vendors keep integration costs off their pricing page. A few publish them in docs, partner terms or buyer guides. Here is what the public record says.
Vendor | Who pays | Published model | Source |
|---|---|---|---|
Stayntouch (PMS) | Hotel | No per interface fees, free API certification, unlimited connections; hotels still pay each third party its own fee | |
Oracle OPERA Cloud via OHIP | Integration partner | Pay as you go subscription; a 10,000 transaction plan with extra calls billed at approximately USD 20 per 10,000; sandbox calls are billed too | |
Mews (PMS) | Nobody | Connector API is free of charge for integration partners and Mews customers to access, build against and use | |
Hotelogix (PMS) | Hotel | Subscription cost varies with hotel size and the type of third party integrations required | Hotelogix pricing FAQ |
Shopify App Store | App developer | One time USD 19 registration, 0% revenue share on the first USD 1,000,000 of lifetime app revenue, 15% above that | Shopify App Store revenue share docs |
Salesforce AgentExchange | App developer | 15% revenue share, no setup fees or monthly service charges |
The spread is wide. Mews and Stayntouch use free integrations as a selling point. Oracle meters every call, even in testing. Hotelogix ties the hotel's price to the integrations it needs. The two horizontal marketplaces show the third option: no fee to connect, a share of revenue once you sell. If you are weighing a listing, our guide to getting listed in a PMS marketplace covers the gates and costs on the partner side.
The four shapes integration fees take
Stayntouch's PMS integration guide lists four shapes of hotel PMS integration pricing: a one time connection fee, a recurring monthly interface fee, per transaction charges and, occasionally, a revenue share. It adds that both sides of a connection may charge separately for the same link. Stayntouch is a PMS vendor selling against per interface fees, so read its numbers as a competitor's framing, but it puts legacy enterprise integrations at as much as $10,000 each and says a hotel connecting five to eight systems can spend $150 to $400 per month on integration costs alone.
That last point matters for your pricing. The hotel does not see your integration fee in isolation. It sees it stacked on the PMS interface fee, the channel manager fee and its own IT time. Your fee is the one it can still negotiate away.
Pros of charging for integrations
Pro | What it does for you | The catch |
|---|---|---|
Recovers real cost | Pays for build, certification, monitoring and upstream API usage | Only if the fee is sized to cost, not to what the market will bear |
Filters unserious requests | A build fee stops one hotel from consuming a sprint on an interface nobody else uses | Needs a clear line between standard and custom |
Protects margin on metered platforms | Covers per call or per event bills like Oracle's OHIP usage pricing | Hotels cannot see your upstream bill, so explain it plainly |
Funds support | Interface failures land on your support desk first | Hotels expect working connections as part of the product anyway |
Signals value on premium syncs | Two way, real time data can justify a higher tier | Works as a tier, not as a line item |
Cons of charging for integrations
Con | Why it hurts in hospitality | Evidence |
|---|---|---|
It taxes the reason they buy | Hoteliers shortlist on whether you connect to their stack | See why integrations sell hotel software more than features |
Competitors use free as a weapon | PMS vendors market no per interface fees and free certification | Stayntouch and Mews both publish this |
It stacks on other fees | The hotel already pays the PMS side and each third party | Stayntouch notes both sides may charge for the same link |
It complicates procurement | Extra line items trigger more approvals and discount requests | A clean pricing page pre-qualifies better |
It rarely moves your revenue | Interface fees are small next to subscription revenue | Partner economics favour the platform, as the next section shows |
Why small integration fees rarely pay off
Impala's analysis of why PMS integration is hard, written by its founder Ben Stephenson, runs the numbers from the PMS side. A 100 room hotel paying a PMS around €15 per room per month is worth €1,500 a month to that PMS. A partner charging €250 a month and giving away 35% generates €87.50. That means about 18 hotels on one PMS to match the revenue of a single hotel customer. The piece is illustrative, but the point holds: your integration fee is rarely big enough to matter to you, yet it is visible enough to matter to the buyer.
Charge if, don't charge if
Charge for integrations if | Don't charge for integrations if |
|---|---|
The interface is custom, legacy or built for one customer | It is a standard connection to a PMS most of your customers run |
The upstream platform bills you per call, event or connection | The upstream API is free to build against and use, as Mews states for its Connector API |
Your buyers are groups with IT teams who expect project fees | Your buyers are independent hotels comparing monthly totals |
The sync creates revenue you can measure, such as upsell or direct booking data | The integration only removes manual work the hotel assumes software should remove |
You can show the cost behind the fee in one sentence | You cannot explain the fee without sounding defensive |
If you do charge, price it this way
Include every standard PMS and channel manager connection in the base price, and say so on the pricing page.
Charge custom interfaces as a one time build fee, quoted like implementation pricing, with scope written down.
Pass through metered upstream costs only above an included allowance, and show the allowance in the contract.
Put premium, revenue linked syncs in a higher tier rather than in a separate integration line.
Review your fees against what peers publish in our hotel software pricing index every quarter.
The vendors winning hotel deals treat standard integrations as part of the product and charge only where the work or the upstream bill is genuinely theirs.
Not sure whether your integration fees are winning deals or quietly losing them? Book a free GTM leak audit and we will show you where pricing friction is costing you pipeline.
Frequently Asked Questions
Should hotel software charge for integrations?
What is integration pricing?
How much does Oracle charge partners for OPERA Cloud integrations?
Is the Mews API free for integration partners?
How should I price a custom integration for a hotel group?
FREE RESOURCES
Free GTM resources for hotel tech vendors
The Hotel Deal Kit, the Hotel Software Pricing Index, the 12-point leak audit and the complete GTM guide, all in one place.
See the resources
Get the latest strategies, trends, and expert advice to help your hotel tech business stay competitive and grow.
Where is your revenue actually leaking?
Twelve questions, about twenty minutes, on your own funnel. The same audit I run on day one of an engagement. No call required.
Get the free leak audit
