When a guest books through an OTA (Booking.com, Expedia, Hotels.com, Agoda, Priceline, Vrbo) and something goes wrong, the hotel is almost always the legally responsible party for guest injury, premises conditions, and service quality, while the OTA's liability is largely limited to the platform's contract with the guest (refunds, fraud, listing accuracy). OTA terms of service typically disclaim all responsibility for the underlying stay; the hotel's GL responds to bodily injury and the hotel's contract with the guest determines refund obligations. Hotels often pay first and work it out with the OTA later.
The "hotel vs Booking.com blame game" Reddit threads capture the real-world frustration: a guest with a problem cannot get a clear answer about who is responsible, the hotel and OTA each point at the other, and the guest is stuck. From an insurance standpoint, the legal answer is clearer than the operational answer. This article walks through the OTA contract structure, who pays for what, and how a hotel structures its insurance and contracts to make the model work. For the parent liability framework, see Hotel Liability Insurance.
Key Takeaways
- The hotel is the legally responsible party for premises liability (slip and fall, bedbugs, pool injury, food illness, room conditions). OTAs disclaim premises liability in their terms of service and rely on agency law to pass through the hotel's responsibility.
- OTA liability is largely contractual: refunds for cancelled bookings, fraud or chargeback resolution, listing accuracy disputes, and platform service issues. OTAs typically do not pay for guest bodily injury or guest property damage.
- The OTA-hotel contract (the OTA partner agreement) governs commission structure, rate parity, content rights, and the OTA's right to refund or chargeback. Most agreements include broad indemnification by the hotel of the OTA.
- Hotels carry the GL, property, and liquor liability that responds to guest claims regardless of booking channel. The hotel's umbrella sits behind those.
- The OTA's general indemnification of the hotel (where it exists) typically covers the platform's failures (listing errors, payment processing failures, fraud) rather than the underlying stay.
- Where a guest sues both the hotel and the OTA, the OTA is typically dismissed early; the hotel remains the defendant because the hotel owns the premises and provides the service.
- Wholesale or channel-manager errors (rate discrepancies, double-bookings, ghost reservations) create a small set of direct hotel-OTA disputes that fall outside the guest claim framework.
- Hotels should maintain the OTA partner agreements in a single file, audit the indemnification language at every renewal of the OTA contract, and verify that hotel insurance does not exclude bookings from third-party platforms.
How Hotel-OTA Contracts Are Structured
The standard OTA partner agreement establishes the hotel as the merchant of record (Booking.com agency model, called the "agency model" or "hotel collect" model) or the OTA as the merchant of record (Expedia merchant model, called the "merchant model" or "OTA collect" model). The merchant designation matters for chargeback and refund mechanics; it does not change premises liability.
Agency Model (Booking.com Original, Some Expedia Hotels)
The OTA acts as agent for the hotel; the hotel is the merchant of record. The guest pays the hotel directly at the property; the OTA invoices the hotel for commission monthly. The hotel handles refunds; the OTA can mediate but cannot unilaterally refund.
Merchant Model (Expedia, Hotels.com, Most Wholesale)
The OTA collects payment from the guest at booking and remits net of commission to the hotel after the stay. Refunds flow through the OTA. The OTA can refund unilaterally per its terms with the guest.
Hybrid and Channel-Manager Models
Many hotels use channel managers (SiteMinder, Cloudbeds, Lighthouse, RateGain) that connect to multiple OTAs. The channel manager pushes rate and inventory; the OTA contracts with the hotel directly; the channel manager is a technology layer.
Indemnification Language
Most OTA partner agreements include broad indemnification by the hotel: the hotel agrees to indemnify the OTA against guest claims arising from the stay, the property, the services, or the hotel's acts or omissions. The OTA typically indemnifies the hotel only for platform failures (data security breach of the OTA's systems, fraudulent OTA conduct), not for underlying stay issues.
The American Hotel & Lodging Association tracks OTA contract negotiation guidance, and several state attorneys general have investigated OTA practices around drip pricing and resort fees, but the contractual liability allocation has remained consistent.
What the Hotel Pays For (Regardless of Booking Channel)
The hotel's GL, property, liquor, and umbrella respond to guest claims arising from the stay. The OTA does not change the coverage analysis.
Bodily Injury
Slip and fall, bedbug bites, pool injury, food poisoning, and other bodily injury claims arising from premises conditions or hotel operations are paid by the hotel's GL up to the per-occurrence limit. The OTA's contract with the guest typically disclaims any responsibility for these events; the hotel's GL is the responding policy. For specifics by category, see Hotel Bedbug Claims and Coverage, Hotel Pool Liability Coverage, and Hotel Guest Injury Liability Coverage.
Guest Property Damage
Damage to or loss of guest property at the hotel is the hotel's responsibility under inn-keeper liability, with state-law limits and policy sub-limits ($1,000 to $5,000 per guest typical). The OTA does not respond.
Room Conditions and Service Quality
Disputes over room conditions, cleanliness, broken amenities, and service quality are between the hotel and the guest. The OTA may mediate per its terms but typically does not pay; the hotel issues the refund or comp.
Alcohol-Related Incidents
Liquor liability for alcohol served at the hotel responds to dram-shop claims regardless of the guest's booking source. The OTA does not contribute.
Auto and Hired-Vehicle Incidents
Where the hotel's shuttle or contracted hired-car service injures a guest, the hotel's auto and GL respond. The OTA does not contribute.
What the OTA Pays For
The OTA's liability is contractual and platform-related.
Refunds for Cancelled or Failed Bookings
Where the hotel cannot honor a confirmed booking (overbooking, unforeseen closure, room category not available), the OTA typically refunds the guest and may charge the hotel back for the booking value, plus the cost of relocating the guest to an equivalent or better property. This is the "walking" cost.
Fraud and Chargebacks
Where a guest disputes a charge through their card issuer, the OTA may process the chargeback, refund the guest, and pass through the loss to the hotel per the partner agreement. The OTA may absorb fraud-related chargebacks where the OTA's payment processing was at fault.
Listing Errors
Where the OTA's listing displayed inaccurate information that the guest reasonably relied on (room features, amenities, location), the OTA may refund the guest and may or may not pass through to the hotel depending on who provided the data.
Platform Service Issues
Where the OTA's website, app, or customer service failed (booking confirmation not delivered, payment processing failed, support unavailable), the OTA typically resolves directly with the guest.
OTA Data Breach
If the OTA's systems are breached and guest data is exposed, the OTA's cyber liability responds. The hotel's cyber may be implicated only if the hotel's data was the breached source.
Real-World Hotel-OTA Liability Scenarios
Common patterns from hospitality programs:
Slip and Fall: Booking.com Booking
A guest booked via Booking.com slips on a wet lobby floor and breaks a wrist. The guest sues the hotel and Booking.com. Booking.com is dismissed early on the basis that it is a booking platform, not the operator of the premises. The hotel's GL responds. Settlement: $185,000 within GL limit.
Bedbug Claim: Expedia Booking
A guest booked via Expedia files a bedbug claim. The guest pursues the hotel directly. Expedia issues a refund per its standard guest policy and charges the hotel back for the booking value. The hotel's GL responds to the bedbug claim itself; settlement $42,000. Hotel ate $300 chargeback plus the GL settlement.
Hotel Walks a Guest
A hotel overbooks; an Expedia guest arrives and cannot be accommodated. Expedia walks the guest to an equivalent property, charges the hotel for the relocation cost ($340 over the original booking value plus $150 transportation). No insurance involvement; the chargeback is operational.
Listing Error
A hotel had its room category described as "ocean view" when the OTA listed "ocean front." A guest disputes; OTA refunds; pass-through to the hotel. No insurance.
Bedbug Listing on TripAdvisor
A hotel had a bedbug complaint resolved internally with a guest. The guest later posts a TripAdvisor review with photos. OTA listing visibility drops; bookings decline. Reputation damage is not insured. The hotel's GL would respond if a lawsuit followed; the reputation hit does not.
OTA Data Breach Affects Hotel Loyalty Members
An OTA data breach exposes guest loyalty data including some hotel loyalty profile data. The OTA's cyber program responds to the OTA's notification and forensics; the hotel may have indirect exposure if the breach implicates hotel-side data. Hotel cyber may be involved.
Third-Party Booking Excluded by Hotel GL?
Almost never. Standard hotel GL forms do not exclude bookings from third-party platforms. A hotel that finds itself with a "third-party booking exclusion" in its GL has an unusual form that should be replaced.
OTA Indemnification Activated
A guest sues both the OTA and the hotel after a pool incident. The OTA tenders to the hotel under the indemnification clause in the partner agreement. The hotel's GL responds to the underlying claim and to the OTA's tender (the OTA is essentially an additional party indemnified). Settlement comes out of the hotel's GL and umbrella.
Common Misconceptions
"Booking.com handles the booking, so they handle the lawsuit"
False. The OTA handles the booking transaction; the hotel handles the stay. Premises liability follows the property and operator, not the platform.
"The OTA's customer service refunded the guest, so the matter is closed"
Not always. The refund resolves the contractual dispute over the booking; it does not resolve any bodily injury or property damage claim that the guest might pursue separately.
"Our insurance excludes OTA bookings"
Almost certainly false; verify the form. Standard hotel GL covers all guest claims regardless of booking source.
"The OTA indemnifies us, so we don't need our own coverage"
False. The OTA's indemnification is narrow (typically platform failures); the hotel's exposure to guest claims is much broader and requires the hotel's own coverage.
"We don't have a direct relationship with the OTA guest, so we owe them less"
False. The hotel's duty of care to anyone on premises is the same regardless of booking source.
How Hotels Should Structure the OTA Relationship
Maintain the Partner Agreements in a Central File
Every OTA agreement, channel manager agreement, and connectivity agreement in a single folder. Indemnification language, term, commission, and dispute resolution captured in a summary log.
Audit Indemnification Language Annually
The hotel typically indemnifies the OTA broadly. Where the indemnification is reciprocal, the OTA's piece typically covers platform failures only. Confirm what each side actually covers; renegotiate where the imbalance is excessive.
Verify Hotel Insurance Has No OTA Exclusion
Standard hotel GL covers all bookings regardless of source. Confirm at every renewal.
Maintain Booking-Source Tracking
For claim defense, knowing which booking channel produced the guest helps reconstruct events: when the booking was made, what was confirmed, what was communicated. PMS booking source code is the simplest mechanism.
Track OTA Chargeback Patterns
OTA chargebacks for service failures (overbooking, walks, no-shows of confirmed reservations) are operational losses that should be tracked and addressed. They are not insurance events but they affect the hotel's economics.
Train Front Desk on OTA Booking Differences
Merchant-model bookings are pre-paid; agency-model bookings are paid at the property. Refund authority differs. Front desk should know which model applies to the OTA in question.
For broader operational liability, see Hotel Liability Insurance and Hotel Insurance Requirements.
How a Hospitality-Specialized Broker Helps with OTA Risk
A hospitality-specialized broker:
- Confirms hotel GL has no third-party-booking exclusion at every renewal.
- Audits OTA partner agreement indemnification language alongside policy language to identify gaps.
- Sources cyber coverage that responds to data sharing with OTAs and channel managers.
- Helps hotels evaluate channel-manager exposure and any specialty technology E&O if the channel manager fails.
- Stands by the operator on any OTA-disputed booking issue that escalates to a lawsuit.
Why Hotel Owners Use Latent Insurance for OTA Exposure
Latent Insurance Services places hotel programs across 20+ specialty hospitality carriers. We audit GL forms for any third-party-booking exclusion (rare but they exist), align cyber coverage with OTA data-sharing obligations, review OTA partner agreement indemnification language with insurance forms together, and stand by operators when an OTA-driven dispute escalates.
Get a hotel insurance quote or schedule a call to walk through your OTA mix and exposure.
Frequently Asked Questions
Who is responsible when a guest gets hurt at a hotel booked through Booking.com?
The hotel is the legally responsible party for premises liability and operations. The hotel's General Liability (GL) responds to bodily injury claims arising from the stay regardless of the booking channel. Booking.com's terms of service typically disclaim premises liability and rely on agency law; the OTA is usually dismissed from any guest injury lawsuit early.
Does Booking.com or Expedia carry liability insurance for hotel guests?
OTAs carry their own corporate liability insurance for platform-related claims (data breach, fraud, platform service failures) but not for premises liability at the hotel. The hotel's GL is the responding policy for guest injury, property damage, and service-related claims at the property.
Who pays the refund when a guest cancels through an OTA?
It depends on the merchant model. In agency-model bookings (Booking.com original model, hotel as merchant of record), the hotel handles refunds. In merchant-model bookings (Expedia, Hotels.com), the OTA collects payment at booking and processes refunds; the OTA may charge the hotel back per the partner agreement.
What happens if a hotel overbooks an OTA reservation?
The hotel must "walk" the guest to an equivalent or better property and pay for the cost difference. OTAs typically charge the hotel back for the original booking value plus the relocation cost (rate differential, transportation, an inconvenience compensation amount per the OTA's policies). The walking obligation is contractual; insurance does not respond.
Does my hotel insurance exclude bookings from Booking.com or Expedia?
Almost never. Standard hotel GL covers all guest claims regardless of booking source. Verify the form at every renewal; an unusual form with a third-party-booking exclusion would be a problem and should be replaced.
Do I need separate insurance because I use OTAs?
No. The hotel's standard GL, property, liquor liability, and cyber coverage responds to OTA-driven exposure the same as direct bookings. The exposure does not change because the booking came through an OTA. Cyber coverage should be reviewed for OTA data-sharing obligations.
Who pays for a chargeback dispute initiated by an OTA guest?
The card-issuing bank initiates the chargeback through the merchant of record. In merchant-model OTA bookings, the OTA absorbs the chargeback initially and may pass the loss back to the hotel per the partner agreement. In agency-model, the hotel is the merchant and handles the chargeback directly.
Does the OTA indemnify the hotel?
OTA partner agreements typically have broad indemnification by the hotel (in favor of the OTA) and narrower indemnification by the OTA (typically limited to platform failures, data breach of the OTA's systems, fraudulent OTA conduct). The OTA's indemnification rarely covers underlying-stay issues.
What if a guest sues both the hotel and the OTA after a slip and fall?
The OTA is typically dismissed from the lawsuit early because it does not own the premises or provide the service. The hotel's GL defends and pays the resulting judgment or settlement. Where the OTA tenders to the hotel under indemnification, the hotel's GL may respond to the tender as well as the underlying claim.
Should I track which guests booked through which OTA?
Yes. PMS booking source codes capture this automatically and become useful evidence in claim defense (when the booking was made, what was confirmed, what was communicated, what rate and what cancellation policy applied). The data also helps the operator manage OTA relationships and chargeback patterns.
Sources
- American Hotel & Lodging Association, Distribution and Online Travel Resources
- U.S. Federal Trade Commission, Online Travel Agency Investigations and Resources
- Hospitality Net, OTA Industry Reports
- Insurance Information Institute, Liability insurance basics
- HotelTechReport, OTA and Distribution Guides
Last updated: May 8, 2026.