Competition Law and Ecosystem Coordinator Dominance

1. Introduction

Ecosystem coordinator dominance refers to a situation in which one undertaking occupies a central coordinating position within a business or technological ecosystem and possesses sufficient market power to influence the conduct, access, conditions, or competitive opportunities of other ecosystem participants.

The coordinator may be:

a digital platform;

cloud provider;

operating-system provider;

payment network;

marketplace;

AI infrastructure provider;

industrial automation platform;

logistics network;

app store;

data intermediary;

standards-setting organisation;

vertically integrated technology company.

The important point is that the coordinator does not necessarily have to manufacture every product in the ecosystem. It may exercise power simply because it controls a critical coordination layer.

Basic formula

Ecosystem Coordinator + Market Power + Control of Critical Layer + Exclusionary Conduct = Potential Dominance Concern

2. What Is an Ecosystem Coordinator?

An ecosystem coordinator is an undertaking that occupies a central position connecting different participants.

For example:

Consumers
↓
Platform Coordinator
↓ ↓ ↓
Developers — Suppliers — Advertisers
↓
Cloud / Payments / Data / Distribution

The coordinator may establish:

technical rules;

access conditions;

ranking systems;

APIs;

interoperability standards;

payment rules;

data-access rules;

commercial terms;

certification requirements.

This creates a special competition problem because the coordinator may simultaneously be:

infrastructure provider;

rule-maker;

market intermediary;

competitor of ecosystem participants.

That combination can produce substantial conflicts of interest.

3. Coordinator Dominance vs Ordinary Dominance

Traditional dominance generally concerns a firm's ability to behave independently of competitors, customers and consumers.

Ecosystem coordinator dominance adds another dimension:

The firm may control the rules through which competitors themselves reach customers.

For example:

A normal manufacturer competes with other manufacturers.

A platform coordinator may:

provide the marketplace + set marketplace rules + collect data + rank products + sell its own competing products.

This creates a potentially stronger strategic position.

4. Sources of Coordinator Power

An ecosystem coordinator may obtain power from several sources.

A. Network Effects

More users attract more suppliers.

More suppliers attract more users.

This creates:

Users → Suppliers → More Users → More Suppliers

A successful ecosystem may therefore become self-reinforcing.

B. Data

The coordinator may collect:

transaction data;

consumer behaviour;

search data;

supplier information;

pricing information;

performance data;

location information.

The data advantage can improve the coordinator's own services.

C. Switching Costs

Users may be reluctant to leave because they have:

stored data;

subscriptions;

accumulated reputation;

loyalty benefits;

proprietary equipment;

integrated applications.

D. Interoperability Control

The coordinator may control:

APIs;

technical protocols;

authentication;

operating systems;

payment interfaces;

data formats.

Control over interoperability can become a significant source of market power.

E. Ecosystem Scope

A coordinator operating across several markets can leverage its position.

For example:

Operating system → App store → Payment → Advertising → Cloud

The power of one layer may reinforce another.

5. When Does Coordinator Position Become Dominance?

Being an ecosystem coordinator is not automatically equivalent to being dominant.

Competition analysis must establish market power.

Relevant factors include:

market share;

barriers to entry;

network effects;

switching costs;

data advantages;

access to customers;

control of infrastructure;

technological advantages;

financial strength;

vertical integration;

ability of competitors to expand.

The analysis should also identify the relevant market.

6. Relevant Market Problem

Ecosystems make market definition more complicated.

A coordinator may operate across:

Market 1

Platform services

Market 2

Advertising

Market 3

Payment services

Market 4

Cloud services

Market 5

Data services

The authority may need to determine whether these are:

separate markets;

complementary markets;

multi-sided markets;

interconnected markets.

The correct market definition can significantly affect the dominance assessment.

7. Multi-Sided Markets

Many ecosystems connect multiple groups.

For example:

Platform ↔ Consumers
Platform ↔ Developers
Platform ↔ Advertisers

The value of the platform to one group may depend on participation by another.

Therefore, market power cannot always be understood simply by looking at price.

Relevant parameters may include:

quality;

innovation;

privacy;

data;

access;

ranking;

interoperability.

8. Coordinator as Both Referee and Player

This is one of the most important concepts.

An ecosystem coordinator can simultaneously be:

Referee

It establishes rules for participants.

Player

It competes against those same participants.

Gatekeeper

It controls access to consumers.

Data collector

It receives information about participants.

This creates a potential conflict of interest.

For example:

Marketplace controls seller ranking while also selling its own products.

The coordinator could potentially use information obtained as a platform operator to improve its competing business.

9. Self-Preferencing

Self-preferencing occurs when a platform gives preferential treatment to its own products or services.

Examples:

higher ranking;

preferential search placement;

better API access;

superior technical integration;

lower fees;

greater visibility.

The central question is whether the coordinator is using its gatekeeper position to disadvantage competitors.

10. Discriminatory Access

A coordinator may provide ecosystem access under different conditions.

For example:

Company A: low access fee + complete API access

Company B: high access fee + restricted API access

If the coordinator has substantial market power, discriminatory access may become a competition issue.

However, differences may be legitimate where they reflect:

genuine costs;

security;

quality;

technical requirements;

objectively different circumstances.

11. Refusal to Deal

A dominant coordinator may refuse access to its ecosystem.

Examples:

refusing API access;

refusing marketplace listing;

refusing payment access;

refusing technical certification;

refusing interoperability.

Competition law generally does not impose an unlimited duty to deal.

The strongest refusal-to-deal cases normally involve questions such as:

indispensability;

elimination of effective competition;

inability to duplicate;

objective justification.

12. Essential-Facilities Dimension

The coordinator may control infrastructure that rivals cannot realistically reproduce.

Examples:

dominant payment infrastructure;

critical cloud interface;

app distribution system;

industrial operating system;

unique technical standard.

The essential-facilities doctrine may become relevant.

But:

Importance is not automatically indispensability.

A business asset can be commercially important without satisfying the strict legal requirements for mandatory access.

13. Tying and Bundling

A coordinator may require ecosystem participants to purchase another product.

Example:

Cloud platform + cybersecurity service

or

Operating system + payment service.

If the coordinator is dominant in one market, tying can potentially leverage that dominance into another market.

Relevant questions include:

Are the products separate?

Does the coordinator possess dominance in the tying market?

Is participation effectively conditional?

Is there foreclosure?

Are there efficiencies?

14. Exclusivity

A coordinator may require ecosystem participants to:

use only its payment service;

use only its cloud service;

sell exclusively through its marketplace;

avoid rival platforms.

Exclusivity can create legitimate efficiencies.

But substantial exclusivity by a dominant coordinator may foreclose rivals.

Important factors:

duration;

coverage;

market power;

switching costs;

rival access;

entry barriers.

15. Data Exploitation

The coordinator may possess privileged access to ecosystem data.

Suppose a marketplace knows:

which products are selling;

seller margins;

consumer demand;

inventory levels.

It then launches competing products based on this information.

The competition concern may involve data leveraging or exclusionary use of platform-generated information.

16. Algorithmic Coordination

A coordinator may operate algorithms that determine:

prices;

rankings;

recommendations;

allocation;

inventory;

commissions.

If the system is used by multiple competitors, it may facilitate coordination.

The competition analysis asks whether the coordinator:

merely provides neutral infrastructure;

knowingly facilitates coordination;

exchanges sensitive information;

imposes common pricing rules;

actively coordinates participants.

17. Hub-and-Spoke Competition

The coordinator can become the hub.

Competitors become spokes.

Structure

Competitor A
↘
Coordinator
↗
Competitor B

If the coordinator transmits sensitive information between competitors or facilitates a common commercial strategy, hub-and-spoke concerns can arise.

18. Vertical Foreclosure

The coordinator may operate at several levels.

Example:

Hardware → Software → Cloud → Marketplace → Payments.

It could potentially disadvantage rivals at one level using power at another level.

Input foreclosure

Rivals cannot access important inputs.

Customer foreclosure

Rivals cannot access customers.

Platform foreclosure

Rivals cannot access the ecosystem.

19. Innovation Foreclosure

Coordinator dominance can affect future competition.

A coordinator may:

acquire emerging competitors;

restrict APIs;

discourage alternative technologies;

prevent developers from using rival platforms;

make interoperability difficult.

Therefore, competition authorities may examine dynamic competition.

The relevant question becomes:

Could the conduct prevent the next generation of competing technology?

20. Economic Dependence

Ecosystem participants may become economically dependent upon the coordinator.

For example:

A developer obtains:

90% of its customers from one platform;

almost all payments through the platform;

all advertising through the platform;

all technical distribution through the platform.

Even without formal exclusivity, the participant may have few realistic alternatives.

Under the UAE competition framework, abuse of economic dependence is therefore especially relevant to ecosystem coordinator relationships.

21. UAE Legal Framework

The principal UAE competition statute is Federal Decree-Law No. 36 of 2023 on the Regulation of Competition.

The ecosystem coordinator analysis may involve:

Restrictive agreements

Agreements between ecosystem participants that restrict competition may attract scrutiny.

Abuse of dominance

A dominant coordinator may face scrutiny for conduct such as:

discriminatory treatment;

unjustified refusal to deal;

tying;

restrictions on technological development;

predatory conduct;

other exclusionary practices.

Economic dependence

Article 7 is especially relevant where ecosystem participants lack realistic alternatives.

Economic concentrations

Acquisitions involving:

AI companies;

cloud providers;

data businesses;

robotics firms;

software companies;

may require competition assessment where applicable thresholds and conditions are met.

22. Case Law

There are relatively few judgments expressly using the phrase “ecosystem coordinator dominance.” The following authorities provide direct or analogical principles.

1. Microsoft Corp. v Commission

Case T-201/04

Microsoft's position in the Windows ecosystem and its conduct concerning interoperability and tying were central to the case.

Principle

Control over a technological platform can have competitive consequences in complementary markets.

Ecosystem coordinator relevance

A coordinator controlling a critical software layer may be able to influence:

interoperability;

application development;

rival technologies;

downstream competition.

23. Bronner v Mediaprint

Case C-7/97

The case concerned access to a newspaper distribution system.

Principle

A refusal to provide access is not automatically abusive.

Strict conditions apply where a competitor claims access to infrastructure.

Ecosystem relevance

A dominant coordinator cannot automatically be compelled to provide every competitor access to its infrastructure.

The critical questions include:

indispensability;

inability to duplicate;

elimination of effective competition;

justification.

24. IMS Health v NDC Health

Case C-418/01

IMS Health concerned access to a pharmaceutical data structure.

Importance

The case is important for:

data;

interoperability;

intellectual property;

market access.

Ecosystem relevance

It provides an important analogy where a coordinator controls a proprietary data architecture that competitors need in order to compete.

25. Google Shopping

Case T-612/17; CJEU appeal C-48/22 P

Google's treatment of its own comparison-shopping service within its search ecosystem was examined under EU competition law.

Ecosystem relevance

This is particularly important for self-preferencing.

A coordinator controlling an important gateway may potentially influence downstream competition by favouring its own service.

26. Google Android

Case T-604/18; CJEU appeal C-738/22 P

The case involved contractual restrictions within Google's Android ecosystem.

Ecosystem relevance

It demonstrates how a dominant platform can use contractual arrangements across connected markets.

Important concepts include:

platform power;

tying;

contractual incentives;

ecosystem foreclosure;

network effects.

27. MEO – Serviços de Comunicações e Multimédia

Case C-525/16

The case concerned discriminatory pricing by a dominant undertaking.

Principle

Different treatment is not automatically an abuse.

The assessment requires attention to the actual or potential competitive disadvantage.

Ecosystem relevance

This is important when an ecosystem coordinator provides different:

API access;

commissions;

licensing terms;

technical support;

platform visibility.

28. Eturas

Case C-74/14

The case involved an online booking platform and potential coordination among businesses using the common system.

Ecosystem relevance

It demonstrates the competition-law significance of digital platforms that facilitate coordination among independent businesses.

A coordinator can therefore create competition risk not only through its own conduct but through the architecture it imposes on ecosystem participants.

29. United States v Microsoft

D.C. Circuit, 2001

The U.S. Microsoft litigation remains an important platform-dominance authority.

Relevance

It demonstrates how control of an important technological platform can be used in ways affecting competition in complementary products.

For ecosystem coordinator analysis, it is particularly useful for:

platform power;

technological barriers;

exclusion;

interoperability;

complementary products.

30. MCI Communications Corp. v AT&T

708 F.2d 1081 (7th Cir. 1983)

The case concerned telecommunications infrastructure and access.

Ecosystem relevance

It provides an important analogy for situations in which a coordinator controls infrastructure necessary for competitors to operate.

31. U.S. v Apple

The U.S. antitrust litigation involving Apple provides a contemporary ecosystem example.

The allegations concern Apple's control over several interconnected elements of its smartphone ecosystem.

Relevance

It demonstrates modern competition theories involving:

interoperability;

platform restrictions;

payments;

applications;

accessories;

ecosystem lock-in.

Important: allegations in litigation should not be treated as judicially established violations unless determined by the court.

32. Case-Law Comparison

33. Coordinator Dominance Test

A useful examination framework is:

C-O-R-E-D

C — Centrality

Does the undertaking occupy a central position?

O — Options

Do ecosystem participants have realistic alternatives?

R — Rules

Does the coordinator control important ecosystem rules?

E — Effects

Does its conduct foreclose or disadvantage competitors?

D — Dominance

Does the undertaking possess substantial market power?

34. Five Questions for Competition Authorities

Question 1

Who controls the ecosystem?

Question 2

What critical resource does the coordinator control?

Examples:

data;

customers;

infrastructure;

API;

operating system;

payment network.

Question 3

Can participants realistically switch?

Question 4

Does the coordinator compete with the participants it regulates?

Question 5

Does the coordinator use its position to exclude or disadvantage rivals?

35. Legitimate Coordinator Functions

Coordinator dominance should not be confused with legitimate ecosystem management.

A coordinator may legitimately impose rules for:

cybersecurity;

consumer protection;

technical compatibility;

product quality;

fraud prevention;

privacy;

safety;

reliability.

The competition question is whether the rules are:

necessary + objective + proportionate + consistently applied.

36. Potential Remedies

Where competition concerns are established, possible remedies include:

1. Non-discrimination

Equal treatment of competing ecosystem participants.

2. Interoperability

Access to APIs or interfaces under appropriate conditions.

3. Data portability

Allowing users to transfer relevant data.

4. Transparency

Clear rules concerning ranking and access.

5. Restrictions on exclusivity

Preventing excessive ecosystem lock-in.

6. Information firewalls

Preventing the coordinator from misusing competitively sensitive participant data.

7. Monitoring

Independent compliance monitoring.

8. Structural remedies

In exceptional circumstances, separation of conflicting ecosystem functions may be considered.

37. Practical Example

Suppose Company X operates a dominant industrial automation ecosystem.

It controls:

robot operating software;

cloud infrastructure;

industrial marketplace;

machine data;

maintenance network.

Company X also sells its own competing robotics applications.

It then:

gives its own applications preferential ranking;

restricts API access to rivals;

requires customers to use its cloud;

obtains competitors' sales data;

makes switching expensive.

The competition analysis would examine:

Market power → ecosystem centrality → discriminatory conduct → data advantage → interoperability restriction → foreclosure → consumer/innovation effects.

38. Exam Answer

Ecosystem coordinator dominance describes a situation in which a central undertaking has substantial market power because it controls an important platform, infrastructure, data resource, technical standard or customer-access mechanism connecting multiple ecosystem participants. The coordinator may simultaneously act as infrastructure provider, rule-maker, gatekeeper and competitor.

Competition concerns can arise through self-preferencing, discriminatory access, refusal to deal, tying, bundling, exclusivity, data leveraging, interoperability restrictions, algorithmic coordination and vertical foreclosure.

Under the UAE competition framework, these issues may fall within the rules concerning restrictive agreements, abuse of dominance, economic dependence and economic concentrations. Comparative authorities such as Microsoft, Bronner, IMS Health, Google Shopping, Google Android, MEO and Eturas provide useful principles.

The decisive issue is not simply whether an undertaking coordinates an ecosystem, but whether its market power and control over the ecosystem are used to restrict effective competition.

39. Quick Revision Table

40. Final Memory Formula

E-C-O-S-Y-S-T-E-M

E – Ecosystem centrality
C – Control of critical infrastructure
O – Options available to participants
S – Switching costs
Y – Yielding/leveraging market power
S – Self-preferencing
T – Tying/exclusivity
E – Exclusionary effects
M – Market and innovation effects

One-line exam mantra

Coordinator Dominance = Central Position + Market Power + Rule/Infrastructure Control + Ability to Exclude − Realistic Alternatives.

Six core authorities: Microsoft → Bronner → IMS Health → Google Shopping → Google Android → MEO.