Competition Law and Public Marketplace Interoperability Frameworks

1. Introduction

Public marketplace interoperability refers to legal and technical arrangements that allow different participants in a marketplace—buyers, sellers, platforms, payment providers, logistics providers, data intermediaries, and public authorities—to communicate, exchange data, transact, authenticate users, and switch between services through common standards or interfaces.

Examples include:

• government-backed digital commerce platforms;
• public procurement marketplaces;
• open banking and public payment infrastructures;
• digital identity and authentication systems;
• interoperable logistics platforms;
• public agricultural and commodity marketplaces;
• health or insurance exchanges;
• open API-based government platforms;
• digital public infrastructure used by competing private providers.

Interoperability can be pro-competitive, because it reduces switching costs and permits competitors to access customers and infrastructure. At the same time, an interoperability framework can itself create competition concerns if a dominant platform uses standards, APIs, technical rules, data access, certification, or governance mechanisms to exclude rivals or favour affiliated participants.

The central competition-law question is therefore:

Does the interoperability framework preserve open and non-discriminatory competition, or does control over the framework become a mechanism for exclusion, foreclosure, or concentration of market power?

2. Meaning of Interoperability

Interoperability generally involves the ability of independent systems to work together.

It may occur at several levels:

A. Technical interoperability

Different software or platforms can technically communicate.

Examples:

• common APIs;
• common data formats;
• authentication protocols;
• payment interfaces;
• messaging standards.

B. Data interoperability

Users or businesses can transfer or access data in a usable format.

Examples:

• transaction histories;
• product catalogues;
• customer information;
• inventory data;
• logistics information.

C. Functional interoperability

Different services can perform complementary functions together.

For example:

Marketplace → payment provider → logistics provider → seller.

D. Commercial interoperability

Participants can transact across different platforms without being forced into one ecosystem.

E. Governance interoperability

Independent businesses participate in common rules concerning:

• technical standards;
• certification;
• access;
• dispute resolution;
• security;
• data governance.

This last category is particularly important because control of governance can become a source of market power.

3. Competition-Law Framework

Public marketplace interoperability can engage several areas of competition law.

A. Abuse of Dominance

Where one undertaking controls an indispensable marketplace or interoperability layer, refusal or restriction of access may constitute an abuse where the applicable legal conditions are satisfied.

Typical concerns include:

• refusal to provide API access;
• discriminatory access conditions;
• exclusion of rival marketplaces;
• technical degradation;
• discriminatory certification;
• interoperability restrictions;
• excessive access fees;
• tying interoperability to unrelated services.

B. Essential-Facility-Type Concerns

An interoperability framework may resemble an essential facility where:

1. access is controlled by a dominant undertaking;
2. the infrastructure is difficult or impossible to reproduce;
3. access is indispensable for competing effectively;
4. refusal is capable of eliminating effective competition;
5. there is no objectively justified reason for refusal.

However, not every important digital infrastructure is automatically an essential facility. Competition authorities generally examine indispensability and the effect of denial carefully.

C. Discriminatory Access

A public marketplace may establish apparently neutral interoperability rules that actually disadvantage particular competitors.

Examples:

• faster API access for affiliated companies;
• lower transaction fees for an incumbent's own merchants;
• preferential search ranking;
• discriminatory authentication requirements;
• delayed technical certification for rivals;
• restrictive data formats.

The concern is especially serious where the marketplace operator is simultaneously:

infrastructure provider + marketplace operator + competitor.

4. Interoperability and Network Effects

Public marketplaces frequently exhibit network effects.

The value of the marketplace may increase as more:

• buyers participate;
• sellers participate;
• payment providers connect;
• logistics companies integrate;
• data becomes available.

This can produce a self-reinforcing cycle:

More users → more sellers → more transactions → more data → better service → more users

Interoperability can interrupt this cycle of concentration by allowing competitors to participate without recreating the entire network.

Conversely, restrictions on interoperability can strengthen network effects and create durable entry barriers.

5. Switching Costs and Lock-In

A major competition concern is technological or commercial lock-in.

Suppose a seller has accumulated:

• customer reviews;
• transaction histories;
• inventory data;
• reputation scores;
• customer relationships;
• payment records.

If the marketplace does not permit meaningful portability or interoperability, the seller may find switching platforms economically difficult.

The competition problem is not merely inconvenience.

High switching costs can:

• reduce customer mobility;
• weaken competitive pressure;
• increase incumbent market power;
• discourage entry;
• permit higher fees;
• reduce innovation.

6. Interoperability as a Pro-Competitive Remedy

Competition authorities may sometimes require interoperability as a remedy.

Possible remedies include:

1. API access

Dominant platforms may be required to provide access to specified interfaces.

2. Data portability

Users or businesses may be permitted to transfer their data.

3. Non-discrimination

Access must be offered on objectively equivalent terms.

4. Technical compatibility

A dominant platform may be required to maintain compatibility with competing services.

5. Independent governance

The interoperability framework may be placed under neutral governance.

6. Transparent technical standards

Changes to APIs or technical specifications should be documented and made available on predictable terms.

7. Six Major Case Laws

Case 1: Microsoft Corp. v. Commission — European Union

Facts

Microsoft's conduct concerning interoperability between its operating system and work-group server products became a major European competition-law dispute.

The European Commission concluded that Microsoft had abused its dominant position by restricting interoperability information necessary for competing work-group server products.

Legal Principle

The case established an important framework for examining interoperability refusals by dominant firms.

The Commission and EU courts considered whether the refusal prevented competitors from competing effectively and whether interoperability information was necessary for meaningful competition.

Relevance to Public Marketplaces

A dominant marketplace controlling an interoperability layer could similarly create competition problems where:

• competitors cannot technically connect;
• access information is withheld;
• interoperability is selectively provided;
• rival services are placed at a technical disadvantage.

Principle

Control over technical interoperability can become an instrument of exclusion when exercised by a dominant undertaking under the applicable legal conditions.

8. Case 2: IMS Health GmbH & Co. OHG v. NDC Health GmbH — European Union

Facts

IMS Health controlled a pharmaceutical sales-data structure based on a particular system for organizing regional information.

Competitors argued that access to the system was necessary to compete effectively.

Legal Principle

The European Court of Justice developed important criteria for applying the exceptional circumstances doctrine to refusal of access to an intellectual-property-related infrastructure.

The case emphasized that refusal to license or provide access is not automatically abusive merely because the refusing firm is dominant.

Relevance

For interoperability frameworks, this is significant because competition law must balance:

• preserving incentives to innovate;
• protecting legitimate proprietary systems;
• preventing exclusionary use of indispensable infrastructure.

Principle

Interoperability obligations require more than simply demonstrating that access would be commercially useful to competitors.

9. Case 3: Bronner v. Mediaprint — European Union

Facts

Mediaprint operated an extensive newspaper home-delivery network in Austria.

Bronner sought access to that distribution infrastructure.

Legal Principle

The ECJ established a demanding test for treating an infrastructure as indispensable.

Among the relevant considerations was whether there was a realistic possibility of creating an alternative infrastructure.

Relevance

A public marketplace operator cannot automatically be required to provide interoperability simply because its infrastructure is widely used.

Authorities may ask:

• Can an alternative marketplace be created?
• Can competing infrastructure realistically be developed?
• Is access genuinely indispensable?
• Would denial eliminate effective competition?

Principle

Importance and convenience are not necessarily equivalent to indispensability.

10. Case 4: Slovak Telekom v. Commission — European Union

Facts

Slovak Telekom was a dominant telecommunications operator. The Commission found problems concerning access to its infrastructure and the conditions imposed on competitors.

The matter reached the EU courts.

Legal Principle

The case is significant for the relationship between:

• dominant infrastructure;
• access obligations;
• exclusionary effects;
• competition in downstream markets.

Relevance to Public Marketplaces

A dominant digital marketplace can similarly operate an infrastructure layer while competing downstream.

For example:

Public marketplace infrastructure → seller access → transactions → downstream retail competition.

If infrastructure access is manipulated to disadvantage downstream rivals, competition law may intervene.

Principle

Control over an upstream infrastructure can confer significant competitive advantages in downstream markets when access conditions restrict effective competition.

11. Case 5: Google Shopping — European Union

Facts

The European Commission found that Google had abused its dominant position in general search by systematically giving prominent placement to its comparison-shopping service while applying less favourable treatment to competing comparison-shopping services.

Legal Principle

The case is important for self-preferencing and platform neutrality.

The competition concern was not simply that Google operated a service competing with other services. The concern concerned the manner in which its control over a dominant infrastructure affected competitive visibility.

Relevance to Interoperability

A public marketplace may face similar issues where its operator:

• controls the infrastructure;
• operates its own marketplace service;
• controls access to users;
• determines rankings or visibility.

Interoperability without neutral treatment may therefore be insufficient.

For example:

Formal API access + discriminatory ranking = potentially ineffective interoperability.

Principle

Interoperability must be assessed together with the competitive conditions under which connected rivals actually operate.

12. Case 6: Google Android — European Union

Facts

The European Commission examined Google's conduct concerning Android, including arrangements involving mobile-device manufacturers and application distribution.

The Commission found several practices that contributed to strengthening Google's position in mobile search.

Relevance to Interoperability

The case illustrates how a dominant ecosystem can use contractual and technical arrangements to reinforce ecosystem power.

Interoperability concerns may arise where:

• access to one service is conditioned on participation in another;
• technical compatibility is restricted;
• competing services cannot obtain equivalent distribution;
• contractual restrictions reinforce network effects.

Principle

Interoperability should be considered together with tying, bundling, contractual restrictions and ecosystem effects.

13. Case 7: Magill — European Union

Facts

Television broadcasters controlled copyright in programme listings. A third party sought to create a comprehensive television guide using that information.

The dispute ultimately reached the European Court of Justice.

Legal Principle

The Court recognized that exceptional circumstances could justify compulsory access to protected information where the refusal satisfied strict conditions.

Relevance

Modern public marketplaces often depend upon:

• product information;
• price information;
• inventory information;
• transaction data;
• standardized catalogues.

A dominant participant's control over such information can raise competition concerns where the information is indispensable for downstream competition.

Principle

Competition law can, in exceptional circumstances, address the exclusionary effects of control over information necessary for downstream competition.

14. Case 8: Aspen Skiing Co. v. Aspen Highlands Skiing Corp. — United States

Facts

Aspen Skiing and Aspen Highlands were competing ski operators.

The dominant operator previously participated in a joint ticketing arrangement but later discontinued cooperation.

Legal Principle

The U.S. Supreme Court considered the termination of a previously profitable cooperative arrangement relevant to an exclusionary-conduct analysis.

Relevance to Interoperability

The case is relevant to the question:

Can a dominant undertaking suddenly terminate interoperability that previously enabled competitors to compete?

Relevant evidence may include:

• historical cooperation;
• economic rationality;
• treatment of competitors;
• impact on consumers;
• whether the termination sacrifices legitimate short-term benefits to exclude competition.

Principle

A change from previously beneficial cooperation to exclusionary conduct may be relevant in determining whether conduct is anticompetitive.

15. Case-Law Comparison

16. Public Marketplace Interoperability Architecture

A competition-friendly public marketplace can be conceptualized as follows:

Public Governance Layer
↓
Common Technical Standards
↓
Open APIs / Interfaces
↓
Identity & Authentication
↓
Data Portability Layer
↓
Multiple Competing Marketplaces
↓
Multiple Sellers and Buyers
↓
Payment + Logistics + Ancillary Services

The objective is to prevent any single participant from controlling every layer.

17. Competition Risks in Public Marketplace Frameworks

A. Gateway Control

The organization controlling access to the marketplace may become a gatekeeper.

B. Self-Preferencing

The marketplace operator may favour its own services.

C. API Discrimination

Competitors may technically receive access but under inferior conditions.

D. Data Concentration

The infrastructure operator may accumulate enormous transaction and consumer datasets.

E. Exclusive Participation

Participants may be prevented from connecting to competing marketplaces.

F. Excessive Certification Requirements

Technical certification can become a disguised entry barrier.

G. Interoperability Fees

Excessive or discriminatory access charges may exclude smaller competitors.

H. Algorithmic Discrimination

The operator may manipulate:

• rankings;
• recommendations;
• search results;
• transaction allocation;
• visibility.

I. Network-Effect Entrenchment

Large incumbent networks can become increasingly difficult to challenge.

18. Data Portability and Interoperability

Data portability is increasingly important.

Suppose a seller's marketplace history consists of:

identity + transaction history + reviews + customer relationships + inventory + reputation.

If that information cannot be transferred or reused, the seller may be effectively locked into the marketplace.

Competition law may therefore examine whether data practices:

• raise switching costs;
• prevent multi-homing;
• exclude competitors;
• create entry barriers;
• reinforce dominance.

However, data portability must be balanced against:

• privacy;
• cybersecurity;
• confidentiality;
• intellectual property;
• trade secrets.

19. Interoperability and Multi-Homing

Multi-homing means that a user or business participates in several platforms simultaneously.

Interoperability can facilitate multi-homing.

For example:

Seller → Marketplace A + Marketplace B + Marketplace C

rather than:

Seller → Marketplace A only

Multi-homing generally makes it harder for one platform to exercise durable market power because users have credible alternatives.

Restrictions preventing multi-homing therefore deserve careful competition analysis.

20. Public Procurement Marketplaces

Public procurement platforms create additional competition concerns.

A government procurement marketplace may determine:

• supplier eligibility;
• tender access;
• ranking;
• product visibility;
• technical certification;
• payment processing;
• procurement data.

If the platform is publicly controlled but permits private firms to participate, competition rules may intersect with:

• procurement law;
• administrative law;
• public-sector neutrality;
• state-aid/subsidy rules where applicable;
• sector regulation.

The platform should ideally maintain:

Transparent access

All qualified participants receive comparable access.

Objective criteria

Certification and participation rules should have legitimate technical justification.

Non-discrimination

Affiliated or incumbent suppliers should not receive hidden advantages.

Auditability

Algorithms affecting market access should be capable of review.

21. Competition-Neutral Interoperability Principles

A well-designed framework should incorporate:

1. Open standards

Standards should not unnecessarily exclude competing technologies.

2. Non-discriminatory access

Comparable participants should receive comparable access.

3. Transparent APIs

Technical requirements should be publicly documented where appropriate.

4. Reasonable access charges

Fees should not become artificial entry barriers.

5. Data portability

Participants should be able to move relevant data subject to legitimate legal restrictions.

6. Interoperable identity

Authentication should not force participants into a single commercial ecosystem.

7. Neutral governance

Rules should not be controlled exclusively by one dominant commercial participant.

8. Procedural safeguards

Participants should have mechanisms for challenging access refusals or technical exclusions.

22. When Interoperability Can Become Anti-Competitive

Interoperability itself is not automatically pro-competitive.

A dominant undertaking could create a supposedly "open" framework that actually produces exclusion.

For example:

Open API → mandatory certification → proprietary certification technology → high compliance costs → exclusion of smaller rivals

Similarly:

Common standard → incumbent controls standard-setting → rival technologies excluded

Thus, competition analysis must examine the actual competitive effect, not merely whether an interoperability standard exists.

23. Interoperability and Standard-Setting

Standards can generate substantial efficiencies.

They can reduce:

• transaction costs;
• duplication;
• incompatibility;
• consumer confusion;
• technical barriers.

But standard-setting can also facilitate:

• exclusion;
• coordination among competitors;
• discriminatory technical specifications;
• foreclosure of alternative technologies.

Competition authorities therefore examine whether standards are:

• transparent;
• objectively justified;
• accessible;
• non-discriminatory;
• developed through appropriate governance mechanisms.

24. Role of Public Authorities

Public authorities designing marketplace interoperability frameworks should distinguish between:

Infrastructure neutrality

The infrastructure should not unnecessarily favour one commercial participant.

Competitive neutrality

State-backed infrastructure should not artificially distort competition between public and private participants.

Regulatory neutrality

Technical rules should apply according to objective criteria rather than commercial affiliation.

Governance neutrality

No dominant participant should obtain disproportionate control over the rules governing competitors.

25. Competition Assessment Test

A practical assessment can follow this sequence:

Step 1 — Define the relevant market

What service or infrastructure is being supplied?

↓

Step 2 — Identify control

Who controls the interoperability framework?

↓

Step 3 — Assess market power

Is the operator dominant or otherwise capable of materially affecting competition?

↓

Step 4 — Identify access conditions

Who can connect?

↓

Step 5 — Examine discrimination

Are competitors treated equally?

↓

Step 6 — Examine indispensability

Can competitors realistically develop alternatives?

↓

Step 7 — Examine foreclosure

Does the conduct exclude or weaken competing firms?

↓

Step 8 — Examine efficiencies

Does the restriction produce legitimate security, privacy, technical or efficiency benefits?

↓

Step 9 — Consider proportionality

Is the restriction broader than necessary?

↓

Step 10 — Design remedy

Possible remedies include:

• API access;
• data portability;
• non-discrimination;
• interoperability;
• transparent certification;
• independent monitoring.

26. Key Legal Tensions

The most important tension is:

Innovation vs. Access

Excessive interoperability obligations may reduce incentives to invest in proprietary technology.

Access vs. Security

Open interfaces may create cybersecurity risks if badly designed.

Portability vs. Privacy

Data portability cannot ignore data-protection obligations.

Standardization vs. Innovation

Rigid standards may prevent technological experimentation.

Neutrality vs. Governance Efficiency

Completely decentralized governance can make technical decision-making slower.

Therefore, competition law should generally seek proportionate interoperability, rather than unlimited mandatory access.

27. Conclusion

Public marketplace interoperability can be a powerful competition-enhancing mechanism because it reduces switching costs, facilitates multi-homing, lowers entry barriers and allows competing providers to connect to common infrastructure.

At the same time, interoperability frameworks can become sources of market power where a dominant infrastructure operator controls:

• APIs;
• data;
• certification;
• technical standards;
• user identity;
• rankings;
• payment systems;
• marketplace governance.

The major case law—Microsoft, IMS Health, Bronner, Slovak Telekom, Google Shopping, Google Android, Magill and Aspen Skiing—illustrates different dimensions of the broader problem: refusal of access, indispensability, infrastructure foreclosure, self-preferencing, ecosystem restrictions, information control and withdrawal from previously cooperative arrangements.