Competition Concerns in Booking Engine Integrations

1. Introduction

A booking engine integration is the technical connection between a booking platform and other systems such as hotel property-management systems (PMS), central reservation systems (CRS), online travel agencies (OTAs), airline reservation systems, payment gateways, channel managers, metasearch platforms, or third-party distribution platforms.

Integration can improve competition by reducing transaction costs, expanding distribution, enabling price comparison, and allowing smaller suppliers to reach customers. At the same time, a powerful booking-engine operator can use the integration layer to restrict competitors, impose parity obligations, discriminate against rival channels, control access to data, or make switching technically difficult.

The principal competition-law concerns therefore arise around market power, exclusionary conduct, discriminatory access, MFN/rate-parity clauses, tying, interoperability, data advantages, exclusivity, and coordination among competitors.

2. Relevant Competition-Law Framework

In an Australian competition-law analysis, the principal provisions of the Competition and Consumer Act 2010 (Cth) potentially relevant include:

• s 45 – contracts, arrangements or understandings that substantially lessen competition;
• s 46 – misuse of market power;
• s 47 – exclusive dealing, subject to the current statutory framework;
• s 50 – acquisitions likely to substantially lessen competition;
• s 90 and related provisions – authorisation and competition-law exemptions in appropriate circumstances.

For digital booking systems, the analysis normally begins with:

1. defining the relevant product/service market;
2. identifying the participants and levels of the booking ecosystem;
3. assessing market power;
4. identifying the impugned integration practice;
5. examining its actual or likely competitive effects;
6. considering efficiencies and legitimate technical justifications.

3. Relevant Markets

A single "booking market" should not automatically be assumed.

Potentially separate markets may include:

A. Booking-engine software

Software supplied to hotels, airlines, restaurants, travel operators or other accommodation providers to receive direct bookings.

B. OTA distribution

Platforms through which consumers book accommodation or travel services.

C. Channel-management services

Technology allowing suppliers to distribute availability and prices simultaneously across multiple booking channels.

D. Reservation infrastructure

CRS/PMS/API infrastructure connecting suppliers with distributors.

E. Online travel intermediation

The consumer-facing market for matching customers with hotels, airlines or other travel providers.

F. Metasearch and comparison services

Platforms that compare prices from multiple booking channels.

The same integration may therefore have different competitive effects at different levels.

4. Major Competition Concerns

A. Foreclosure of Rival Booking Platforms

A dominant booking-engine provider may require hotels or other suppliers to use its own booking interface exclusively.

For example:

Hotel → Booking Engine A → OTA/consumer

If Booking Engine A prevents integration with Booking Engine B, the incumbent can potentially prevent rival platforms from obtaining sufficient scale.

The concern becomes stronger where the integration is an essential distribution interface and alternative technical routes are commercially or technically impractical.

B. API Access Discrimination

Modern booking systems frequently depend upon APIs.

A platform may provide:

• fast APIs to its own affiliated service;
• delayed APIs to competitors;
• greater inventory access to affiliated platforms;
• fewer functions to competing booking services;
• higher technical fees for rivals.

This can amount to competitive discrimination where the provider has substantial market power and the discrimination harms the competitive process.

A particularly important distinction is between:

legitimate technical differentiation
and
commercial discrimination designed to disadvantage rivals.

For example, limiting API calls because of genuine cybersecurity or server-capacity concerns may have a legitimate justification. Arbitrarily giving an affiliated booking platform preferential access is more problematic.

5. Rate-Parity and MFN Clauses

One of the most important issues in booking-engine markets is the most-favoured-nation (MFN) or rate-parity clause.

A booking platform may require a hotel to promise:

"The hotel must not offer a lower room price through another booking channel."

There are several possible forms.

Wide MFN

The hotel cannot offer a lower price through:

• another OTA;
• its own website;
• another distributor;
• offline channels.

Narrow MFN

The hotel cannot offer a lower price on its own website than the OTA price, but may offer lower prices through other OTAs.

MFN provisions can have both procompetitive and anticompetitive effects.

Possible benefits

They may:

• prevent opportunistic free-riding;
• protect investment by booking platforms;
• facilitate consumer confidence;
• reduce search costs.

Possible harms

They may:

• prevent price competition between booking platforms;
• increase commissions;
• discourage entry;
• reduce direct-booking competition;
• stabilize prices at artificially high levels.

6. Self-Preferencing

A booking-engine operator may operate both:

1. the infrastructure used by suppliers; and
2. its own consumer-facing booking platform.

It may then rank its affiliated service above competing booking channels.

Examples include:

• preferential search ranking;
• superior availability;
• better API response times;
• preferential access to inventory;
• default placement;
• lower integration charges;
• preferential cancellation functionality.

This creates a potential vertical foreclosure/self-preferencing concern.

The legal analysis should examine whether the conduct actually restricts competitive opportunities rather than assuming that every preferential ranking is unlawful.

7. Tying and Bundling

A booking-engine provider may condition access to one service on purchasing another.

For example:

"To use our booking engine, the hotel must also use our payment gateway."

Or:

"Access to our API is available only if the hotel purchases our channel-management service."

The competition concern becomes stronger where:

• the supplier has substantial market power in the tying product;
• the tied product is separately demanded;
• customers are pressured to purchase both;
• rivals are excluded from the tied market.

8. Exclusive Integration Agreements

Long-term contracts may require a hotel chain or travel supplier to integrate exclusively with one booking platform.

Potential provisions include:

• exclusive API integration;
• minimum-volume commitments;
• preferred-provider clauses;
• prohibition on rival integrations;
• termination penalties;
• automatic renewal provisions.

Such provisions may foreclose competitors from obtaining sufficient scale.

However, exclusivity is not automatically unlawful. The duration, coverage, market power, and actual foreclosure effects are important.

9. Data-Related Competition Concerns

Booking integrations generate extensive data, including:

• room availability;
• prices;
• cancellation rates;
• booking volumes;
• consumer search behaviour;
• conversion rates;
• occupancy information;
• competitor prices.

A dominant platform could potentially use data obtained from independent hotels or booking partners to strengthen its own downstream service.

Concerns may arise where the platform:

1. collects commercially sensitive data;
2. uses it to compete against the data provider;
3. restricts the provider from accessing its own data;
4. prevents interoperability with rival systems.

Data access can therefore become an important competition issue even where the original contract appears technologically neutral.

10. Algorithmic Pricing and Coordination

Booking engines can automatically adjust prices based on:

• demand;
• competitor prices;
• occupancy;
• historical bookings;
• inventory;
• algorithmic forecasts.

If competing booking platforms or suppliers use interconnected algorithms, there may be a risk that the technology facilitates parallel pricing or coordination.

Competition authorities may examine:

• common pricing algorithms;
• shared commercially sensitive information;
• automated responses to competitors;
• contractual restrictions preventing independent pricing;
• communications between competitors concerning algorithmic parameters.

The existence of an algorithm alone does not establish an unlawful cartel. The relevant question is whether the conduct involves prohibited coordination or otherwise produces an unlawful anticompetitive effect.

11. Six Important Case Laws

1. ACCC v Flight Centre Travel Group Ltd (2016)

High Court of Australia

This is one of the most directly relevant Australian authorities for booking/intermediation markets.

Flight Centre operated as a travel intermediary and sought to prevent airlines from offering lower fares directly to customers than fares available through Flight Centre.

The High Court considered whether Flight Centre and the airlines were competitors for the relevant purpose and whether Flight Centre's conduct constituted a prohibited attempt to maintain price parity.

Relevance to booking engines

The case demonstrates that competition law can examine the economic relationship between an intermediary and suppliers, rather than simply accepting contractual descriptions of the parties' roles.

It is particularly relevant to:

• OTA/supplier relationships;
• price-parity provisions;
• online travel distribution;
• intermediary competition;
• attempts to prevent suppliers from offering better prices through alternative channels.

2. Bundeskartellamt – Booking.com (2021)

German Federal Cartel Office

The German competition authority examined Booking.com's use of narrow price-parity clauses.

The authority concluded that Booking.com's substantial position in the market for hotel booking platforms justified restrictions on its ability to prevent hotels from offering lower prices on their own websites.

Relevance

The decision is important because it illustrates how MFN clauses can be examined in a platform market.

It highlights concerns that parity obligations can:

• reduce price competition;
• restrict direct hotel sales;
• protect an established intermediary from competitive pressure.

It also demonstrates that competition authorities may distinguish between different forms of MFN clauses rather than treating all parity clauses identically.

3. HRS – Hotel Reservation Service (2015)

Bundeskartellamt / German competition proceedings

The German competition authority previously addressed HRS's best-price or price-parity clauses imposed on hotels.

The authority considered the effect of these provisions on competition between hotel booking platforms and direct hotel distribution.

Relevance to booking-engine integration

The case is significant for analysing contractual provisions requiring hotels to maintain equivalent or better prices across distribution channels.

It supports examination of:

• OTA parity;
• restrictions on direct booking;
• platform bargaining power;
• foreclosure of rival booking channels.

4. Expedia – Hotel Booking Parity Investigations

European competition-law proceedings involving Expedia and hotel-booking parity

European competition authorities investigated contractual arrangements involving online travel agencies and hotel price-parity obligations.

The proceedings illustrate the competition-law sensitivity of agreements restricting hotels from offering different prices through competing distribution channels.

Relevance

The Expedia proceedings are useful for analysing:

• OTA agreements;
• MFN clauses;
• online distribution;
• platform-to-supplier restrictions;
• competition between booking intermediaries.

They also demonstrate why the precise wording of a parity clause matters.

5. United States v. Sabre Holdings Corp. / Travelport-related airline distribution proceedings

United States

US competition authorities have examined competition in airline reservation and distribution systems, particularly relationships between airlines and computerized reservation systems.

These proceedings addressed concerns surrounding powerful reservation intermediaries and their contractual relationships with airlines.

Relevance to booking-engine integrations

The underlying competition issue is highly relevant to modern API ecosystems:

Supplier → reservation infrastructure → competing distributors → consumer

Where the intermediary controls an important technological gateway, contractual restrictions may affect the ability of competing distributors to access inventory.

The case law illustrates the importance of analysing distribution infrastructure as a potential competitive bottleneck.

6. Ohio v. American Express Co. / United States v. American Express Co. (2018)

US Supreme Court

The Supreme Court examined contractual restrictions imposed by American Express on merchants concerning steering customers toward alternative payment networks.

Although this was a payment-platform case rather than a hotel-booking case, it is particularly useful for analysing platform restrictions and two-sided markets.

Relevance to booking engines

Booking platforms similarly connect two groups:

• suppliers; and
• consumers.

Restrictions preventing suppliers from directing customers to competing channels can affect competition on both sides of the platform.

The case is therefore useful when analysing:

• platform contracts;
• anti-steering restrictions;
• two-sided markets;
• indirect network effects;
• platform competition.

12. Additional Relevant Authorities

Other competition-law authorities that can assist in analysing booking-engine integration include:

7. Google Shopping – European Commission

The European Commission examined preferential treatment of Google's own comparison-shopping service in search results.

Relevance: self-preferencing and preferential ranking by vertically integrated platforms.

8. Microsoft v Commission

The European Union Microsoft proceedings examined interoperability and the withholding of information necessary for competing products to operate effectively.

Relevance: API interoperability and technical access.

9. IMS Health v NDC Health

The EU courts considered refusal of access to an important interoperability-related asset.

Relevance: access to technologically important infrastructure and potential foreclosure.

10. Bronner v Mediaprint

The EU Court of Justice examined refusal of access to a distribution system.

Relevance: when denial of access to infrastructure may raise competition-law issues.

13. Competition Issues by Integration Practice

14. Refusal to Integrate With Competitors

A particularly difficult issue is whether a dominant booking-engine provider must integrate with a rival.

Competition law generally does not require every company to assist competitors.

A refusal becomes more significant where the infrastructure is exceptionally important and:

• the provider has substantial market power;
• the input cannot reasonably be replicated;
• access is necessary for effective competition;
• refusal eliminates or substantially weakens competition;
• there is no legitimate commercial or technical justification.

Accordingly, a mere refusal to integrate is not automatically anticompetitive.

15. Switching Costs and Lock-In

Booking engines can generate significant switching costs.

A hotel may have to change:

• website integration;
• PMS connection;
• payment systems;
• CRM;
• channel manager;
• reporting infrastructure;
• customer databases;
• mobile applications.

A provider could potentially exploit these costs by imposing:

• lengthy contracts;
• automatic renewals;
• excessive termination charges;
• proprietary technical formats;
• non-portable customer data;
• incompatible APIs.

Competition authorities may therefore consider technical lock-in as an important entry barrier.

16. Network Effects

Booking platforms frequently benefit from strong network effects.

More hotels → more inventory → more consumers → more bookings → more hotels.

This can create a feedback loop:

More suppliers
↓
Better consumer choice
↓
More consumers
↓
Greater platform attractiveness
↓
More suppliers

A dominant platform may consequently become difficult for entrants to challenge.

Integration restrictions can strengthen this effect if competitors cannot obtain comparable inventory.

17. Raising Rivals' Costs

A booking-engine operator may not need to exclude a competitor completely.

It could instead make competition more expensive by:

• charging rivals higher API fees;
• imposing additional certification requirements;
• limiting technical functionality;
• delaying approvals;
• requiring unnecessary security audits;
• providing incomplete inventory feeds.

This can constitute a raising-rivals'-costs theory of harm where the conduct has the requisite competitive effect and the applicable legal elements are established.

18. Legitimate Business Justifications

Not every restrictive integration practice violates competition law.

A platform may have legitimate reasons for:

• API rate limits;
• cybersecurity controls;
• fraud prevention;
• data protection;
• system stability;
• technical certification;
• quality assurance;
• minimum service standards.

The critical question is whether the restriction is reasonably connected to a legitimate technical or commercial objective or is being used as a mechanism to suppress competition.

19. Competition Compliance Checklist

A booking-engine operator should examine:

Market power

• What share does the platform have?
• Are alternative booking engines available?
• Can suppliers switch easily?

API access

• Are rivals receiving equivalent technical access?
• Are API restrictions objectively justified?
• Are affiliated services receiving preferential treatment?

Contractual restrictions

• Are there MFN clauses?
• Are there exclusivity provisions?
• Are there minimum-volume requirements?

Pricing

• Can suppliers independently determine prices?
• Are commissions restricting competition?
• Are competitors prevented from offering discounts?

Data

• Who owns booking data?
• Can suppliers export their data?
• Is competitor data being used to advantage an affiliated service?

Interoperability

• Can competing booking engines connect?
• Are technical standards open?
• Are proprietary formats being used to create lock-in?

Algorithmic systems

• Does the algorithm use competitors' commercially sensitive information?
• Is pricing independently determined?
• Could the system facilitate coordination?

20. Hypothetical Example

Assume Platform A operates a dominant hotel booking engine.

It requires hotels to:

1. use Platform A's API;
2. maintain the same price on competing OTAs;
3. use Platform A's payment gateway;
4. give Platform A real-time access to booking data;
5. refrain from integrating with competing engines for three years.

Platform A additionally gives its affiliated OTA:

• faster API access;
• preferential ranking;
• greater inventory availability.

The potential competition concerns would include:

MFN: restriction of price competition.

Exclusive dealing: foreclosure of competing booking platforms.

Tying: compulsory use of the payment service.

Self-preferencing: preferential treatment of the affiliated OTA.

Discriminatory access: unequal API functionality.

Data advantage: use of hotel data to strengthen the affiliated OTA.

Switching costs: contractual and technical barriers to migration.

The legality would ultimately depend upon market definition, market power, contractual terms, competitive effects, efficiencies, and the applicable statutory provisions.

21. Key Principles Emerging From the Case Law

The cases collectively demonstrate several important principles:

1. Intermediaries can themselves be participants in competition.
2. Price-parity clauses can restrict competition between distribution channels.
3. Platform contracts must be assessed according to their actual competitive effects.
4. Control over an important technological interface can create significant foreclosure concerns.
5. Two-sided platforms require analysis of effects on both suppliers and consumers.
6. Self-preferencing can become important where a platform controls both infrastructure and a downstream competing service.
7. Interoperability restrictions require careful assessment where the infrastructure is commercially indispensable.
8. Exclusive contracts are not automatically unlawful but become more significant where substantial market power and foreclosure are present.
9. Data obtained through an integration can become a source of competitive advantage.
10. Technical justifications can be relevant defences to apparently discriminatory integration practices.

22. Conclusion

Competition concerns in booking-engine integrations arise primarily because technology can become a competitive gateway. A platform controlling the API, reservation infrastructure, customer interface, ranking system, data flows or payment functionality may possess the ability to influence competition beyond the immediate software market.

The most important issues are API discrimination, interoperability, MFN/rate parity, exclusivity, self-preferencing, tying, data exploitation, algorithmic coordination and switching costs.

The authorities involving Flight Centre, Booking.com, HRS, Expedia, airline reservation systems and American Express provide useful analytical foundations. In an Australian matter, the central inquiry would generally be whether the conduct falls within provisions such as ss 45, 46 or 47 of the Competition and Consumer Act 2010 and whether it has the required effect on competition, rather than merely determining whether the conduct is commercially restrictive.