Booking.com fined for algorithmic demotion of hotels over price parity

The Spanish competition authority fined Booking.com for using its ranking algorithm to penalize hotels that offered lower prices on other platforms. This practice was found to be an abuse of its dominant market position.

Booking.com · Incident Jan 1, 2019 · Indexed Jun 9, 2026 · 2 sources

Records by entity: Booking com

The short version

Booking.com was fined €413 million for using its search algorithm to demote hotels that offered lower prices on competing platforms.

The company algorithmically demoted hotels in search rankings to enforce price parity.
What
The Spanish competition authority fined Booking.com for using its ranking algorithm to penalize hotels that offered lower prices on other platforms.
Incident date
Jan 1, 2019
Who
Booking.com
Failure mode
Policy Violation
AI surface
Recommender
Severity
High

What happened

The Spanish competition authority (CNMC) fined Booking.com €413.24 million for abusing its dominant market position. The regulator found that Booking.com used its ranking algorithm to penalize hotels that offered lower prices on other platforms. This practice was intended to enforce price parity across the travel industry.

What broke inside the model

The ranking system was programmed to automatically demote hotels in search results if they offered lower rates on competing sites. This algorithmic mechanism effectively punished hotels for offering more competitive pricing elsewhere.

Public visibilityHigh
Regulatory exposureNone
Customer impactMany customers
Financial impactEstimated
Time to disclosureHours
  1. PrimaryBooking.comcnmc.es
  2. PressSpanish regulators fine Booking.com €413Mphocuswire.com
Permalinkhttps://failureindex.ai/failures/booking-com-fined-algorithmic-demotion-hotels
CitationAI Failure Index. "Booking.com fined for algorithmic demotion of hotels over price parity" (FI-0340). Realm Labs. https://failureindex.ai/failures/booking-com-fined-algorithmic-demotion-hotels (indexed Jun 9, 2026).
Share cardA branded image of this record for posts and slides.

Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0340. Full dataset at /data.

Note from Realm Labs, the Index steward

How Realm fits

Controls for this failure mode
  • Prism
  • OmniGuard

This entry sits in the index's predictive wing: a system that scores, ranks, perceives, or steers rather than generates. Realm's runtime layer is built for the generative and agentic systems now moving into these same decision seats, where it watches a model's internal state and holds an unsupported claim or an unchecked action before it commits. The control gap on this record, an automated decision that reached people with no runtime check in front of it, is the same gap. The index keeps predictive failures on the record because the pattern carries straight into the systems shipping today.