Booking.com Account Closures: EU Rights for Hotel Owners
EU rules generally require Booking.com to give hotel partners 30 days’ notice, state reasons and show that closure is proportionate. Repeated breaches can shorten the process.

Booking.com generally must give a hotel partner at least 30 days’ notice before closing its account, under Article 4(1) of the EU P2B Regulation.
The platform must also state clear grounds, explain the termination and show that the response is proportionate. Repeated breaches can justify immediate closure, provided Booking.com proves that multiple violations occurred.
Closure removes the property from online booking, which can reduce reservations and disrupt day-to-day operations. These safeguards apply to hotels and other accommodation partners that use the platform to reach prospective guests.
Booking.com is also an important sales channel for many hotels and cannot easily be replaced. Closure can therefore cause substantial revenue loss, although the article gives no commission rate, booking volume or property-level loss estimate.
Operators can challenge a closure, but the source provides no win rate, enforcement timetable or concrete financial model. Four conditions frame a termination:
- Breach of the rules: Booking.com must set clear terms and demonstrate that the hotel breached them.
- Notice: Booking.com generally must provide at least 30 days before termination, subject to exceptions.
- Reasons: Booking.com must justify every closure with specific facts.
- Proportionality: A minor breach does not automatically justify immediate closure.
What grounds can Booking.com use?
Article 3(1)(c) of the P2B Regulation requires Booking.com to list every account-termination ground in its terms and conditions. The terms must use clear, comprehensible language and let partners reasonably foresee the consequences. The source treats vague or insufficiently specific terms as void and inapplicable.
The agreement is governed by Booking.com’s General Delivery Terms, or GDT. The GDT also incorporate information published on the partner extranet. Any further instructions or requirements there remain binding.
Because Booking.com can amend the extranet and scatter binding instructions across the platform, a hotel must monitor more than the original contract to determine which requirements actually apply.
Articles 7.2 and 7.3 list the closure grounds. They range from “breaching the agreement” to review manipulation, commission avoidance and non-payment of invoices.
Booking.com carries the full burden of proof. Plausibility or strong suspicion does not establish a breach.
When can Booking.com skip the 30-day notice?
Article 4(1) generally requires at least 30 days’ notice. During that period, Booking.com must give the partner an opportunity to challenge the decision or clarify ambiguities in the stated reasons.
The repeated-breach exception permits immediate termination, but only when Booking.com demonstrates that several actual breaches occurred.
The article alleges that Booking.com regularly misuses that exception. It also says many terminations arrive without giving the owner a chance to present its case.
That claim lacks supporting termination data in the source, so it signals a risk rather than a measured rate of enforcement.
A closure can still become final before a partner completes its challenge. The article notes that legal action generally takes longer than 30 days, leaving little value in notice after access has already ended.
Hotels should therefore treat even the 30-day protection as vulnerable to a sudden exception, not as an unconditional safeguard.
How much detail must the explanation contain?
Article 4(1) also requires a statement of reasons. The statement must identify the specific facts and circumstances behind termination and include relevant third-party reports, including guest complaints or negative reviews.
It must contain enough detail for the hotel to test the decision and decide whether a challenge is worthwhile.
The article says Booking.com may provide limited reasons and merely cite the provision it says the hotel violated. It suggests this may protect internal control processes rather than explain the decision.
No quick remedy compels a fuller explanation while the account remains open. Each waiting day can increase the hotel’s revenue loss.
The recommended first step is internal. A hotel should investigate a possible dissatisfied guest, negative review, payment issue or other breach before deciding how to respond.
When is closure proportionate?
Dutch law requires contracting parties to act reasonably and fairly toward one another. Closure must therefore fit the seriousness of the breach and the harm involved.
Booking.com’s sales role and a hotel’s dependence on the platform make permanent closure harder to justify than a lesser measure.
Termination is a last resort. Before closing the account, Booking.com must demonstrably consider temporary suspension, partial withdrawal of services, a warning, additional arrangements or a lower ranking.
A warning leaves the hotel bookable; closure removes it from the platform and blocks future booking access through that channel.
Other relevant facts include whether the breach harmed the platform or guest, whether the guest received compensation, and whether the breach was intentional.
Partnership duration, average revenue and dependence on Booking.com may also affect the analysis.
The source supplies no formula, threshold or mandatory order for those alternatives. It also identifies no enforcement agency or partner-claim filing deadline.
What can a hotel do after notice?
A hotel may successfully challenge a closure, but only after it understands the applicable grounds, evidence and legal options. The source promises a later article with practical post-closure steps, not a complete procedure here.
Operators should compare the alleged conduct with the GDT, current extranet instructions and the stated reasons.
Any challenge must account for the delay between closure and a remedy. The hotel continues losing booking access during that period.
The forward test is concrete: can Booking.com identify a clear rule, specific facts, proven repeated breaches where invoked, and lesser measures it actually considered?
More from Marcus Bennett
Show full bio
Market editor covering technology and product news in Restaurant and hotel operations at The Pass Brief.
712 articles


