Ask a hotelier what an OTA booking costs and you'll get the commission rate. That's the visible layer. The full cost is higher, and knowing the real number is what turns "OTAs are expensive" from a grumble into a strategy.
Quick answer (for the impatient)
Commission is the headline, not the total. Payment processing, rate parity effects and visibility spend all sit underneath it.
The real comparison is contribution per booking, not rate per booking.
The conclusion is not "leave the OTAs." It's knowing which bookings you're happy to pay for and which you should be winning yourself.
The cost stack
Layer by layer, for a typical independent property:
Commission — the visible percentage, and genuinely the largest single component.
Payment costs — depending on the model, gateway or processing costs may sit on your side of the transaction.
Visibility spend — sponsored placement and boosted-visibility programmes are usually presented as optional and function as a competitive floor once your neighbours are on them.
Rate parity effects — if your public rates are effectively anchored to what platforms display, that constrains your own pricing everywhere, which is a real cost that never appears on any invoice.
Cancellation and no-show exposure — free-cancellation inventory converts worse than committed bookings, and the platform's cancellation terms govern, not yours.
The relationship — the guest is the platform's. Their next stay starts on the platform again unless you did something about it during this one.
Why the answer still isn't "leave"
Two reasons that survive any amount of frustration. First, OTAs supply genuine incremental demand — travellers who were never going to find your property, and would have booked someone else. A commission on a booking you'd otherwise not have had is a cost of sale, not a loss.
Second, there's the billboard effect: significant numbers of guests discover a property on a platform and then book direct. Delisting removes the discovery as well as the commission.
So the useful framing isn't platform versus direct. It's: which portion of your OTA volume is genuinely incremental, and which portion is guests who already knew about you and used a platform because it was easier than your own booking flow? The second group is expensive volume you're paying for unnecessarily, and it's the group worth attacking.
Working out your real number
Do this for one quarter and the strategy usually becomes obvious:
Total room revenue by channel, gross.
Subtract every cost attributable to that channel — commission, processing, visibility spend.
Divide by room nights, giving contribution per room night by channel.
Compare that against your direct channel, including what your website and payment costs actually are.
Most independent hoteliers doing this for the first time find the gap is wider than they assumed — and, more usefully, that it differs sharply between platforms. That's the number that should drive where you push.
What to do with the answer
Make direct booking genuinely easier. Most direct-booking losses are usability, not price. If your own booking flow is worse than a platform's, guests will keep using the platform.
Give a reason that isn't a discount — early check-in, a room upgrade where available, breakfast included. Perks protect rate parity in a way discounting doesn't.
Capture the guest during the stay. A platform-sourced guest who leaves with a direct booking route is a one-time commission, not a permanent one.
Keep the platforms. Just stop paying for demand you already had.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind What an OTA Booking Actually Costs You (It Isn't the Commission Rate) does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: Commission is the headline, not the total. Payment processing, rate parity effects and visibility spend all sit underneath it. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: The real comparison is contribution per booking , not rate per booking. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: The conclusion is not "leave the OTAs." It's knowing which bookings you're happy to pay for and which you should be winning yourself. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
Can I offer a lower rate on my own site?
That depends on your agreements with each platform. Read them, and consider perks instead of price where parity applies.
Is a metasearch listing better than an OTA?
Different economics — usually cost-per-click rather than commission, meaning you pay regardless of conversion. Better for some properties, worse for others.
How do I know which platform is most profitable?
Contribution per room night, by channel. Anything else is a guess.
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
The commission rate is the sticker price on a longer bill. Work out contribution per channel for one quarter, and the argument about OTAs stops being emotional and becomes a decision about which demand you're happy to buy.
See how commission-free direct booking works, how channel manager keeps inventory honest, or pricing.
Know what each booking really earns. Start free →
Comments