Digital Supply Chain Protocol Dominance Issues

Introduction

Digital supply chain protocol dominance refers to a situation in which a firm or a small group of firms obtains substantial control over the technical protocols, standards, interfaces, authentication systems, data formats, APIs, cloud infrastructure, operating systems, logistics platforms, or interoperability rules through which businesses coordinate supply-chain activities.

Modern supply chains increasingly depend on digital protocols for ordering, inventory management, procurement, payments, shipment tracking, warehouse management, customs compliance, forecasting, authentication and data exchange. A protocol may therefore become a critical gateway between suppliers, manufacturers, distributors, logistics providers and customers.

From a competition-law perspective, the central problem arises when control over a protocol allows its owner to:

• exclude competing suppliers or service providers;
• discriminate between downstream businesses;
• impose excessive access or licensing conditions;
• restrict interoperability;
• exploit proprietary data;
• raise switching costs;
• engage in self-preferencing;
• foreclose rival platforms;
• impose tying or bundling;
• use technical standards to entrench market power; or
• convert a supposedly neutral infrastructure into a competitive bottleneck.

The issue is particularly important in digital markets because a protocol can exhibit network effects, economies of scale, data advantages, high switching costs and technical lock-in simultaneously.

1. Meaning of Digital Supply Chain Protocol Dominance

A digital supply-chain protocol is a technical or contractual framework through which participants communicate or transact.

Examples include:

• electronic data interchange (EDI);
• API standards;
• cloud-based procurement protocols;
• digital freight platforms;
• warehouse-management interfaces;
• electronic invoicing systems;
• supply-chain blockchain protocols;
• authentication and identity standards;
• payment and settlement interfaces;
• IoT communication standards;
• logistics tracking protocols;
• digital customs interfaces;
• marketplace APIs; and
• proprietary software ecosystems.

Dominance does not necessarily mean ownership of the protocol alone. It may arise because the firm controls the gateway necessary for meaningful participation.

For example:

Manufacturer → procurement protocol → suppliers → logistics network → retailers

If one undertaking controls the central protocol and competitors cannot realistically reach customers without using it, the protocol may become an essential digital infrastructure.

2. Why Protocols Can Create Market Power

A. Network Effects

The value of a supply-chain protocol increases as more firms use it.

A logistics protocol with 100 participating suppliers may be useful; one connecting 100,000 suppliers, warehouses and carriers may become indispensable.

This produces a feedback loop:

More users → more data → better service → more users → stronger network → greater market power

Once critical mass is achieved, competing protocols may struggle to attract participants.

B. Switching Costs

Supply chains are deeply integrated systems.

Changing protocols may require:

• software redevelopment;
• employee retraining;
• data migration;
• cybersecurity testing;
• contractual renegotiation;
• equipment replacement;
• interoperability testing; and
• operational downtime.

Consequently, even when an alternative protocol exists, customers may be economically unable to switch.

This creates digital inertia.

3. Protocol Lock-In

Protocol dominance becomes particularly problematic where a dominant firm deliberately or structurally creates technical dependence.

Lock-in may arise through:

1. proprietary APIs;
2. incompatible data formats;
3. restricted access credentials;
4. contractual exclusivity;
5. non-portable historical data;
6. proprietary authentication;
7. technical certification requirements;
8. expensive integration tools; and
9. restrictions on third-party interoperability.

A dominant undertaking may then say:

"The supplier is free to leave."

But if leaving requires replacing the entire digital infrastructure of the supply chain, the freedom may be largely theoretical.

4. Essential-Facility Dimension

A digital supply-chain protocol may resemble an essential facility where:

1. the infrastructure is controlled by a dominant undertaking;
2. competitors require access to compete effectively;
3. duplication is technically or economically impracticable;
4. access can be provided without eliminating the legitimate function of the infrastructure; and
5. refusal substantially restricts competition.

However, competition law generally does not impose a universal duty to deal merely because an asset is valuable.

The strongest cases arise where refusal of access causes effective elimination of competition or where the infrastructure has become indispensable.

5. Refusal of Interoperability

One of the most important issues is refusal to make a dominant protocol interoperable with competing systems.

Suppose a dominant logistics platform controls:

• shipment identifiers;
• warehouse APIs;
• tracking data;
• authentication;
• delivery-status protocols.

If it refuses interoperability with rival logistics software, customers may effectively be prevented from using competing services.

The competitive harm is therefore not simply:

"Competitor cannot access software."

It may be:

"Customers cannot realistically change their entire supply-chain infrastructure."

6. Self-Preferencing

Protocol operators may simultaneously operate downstream services.

This creates a conflict of interest.

For example:

Protocol owner → provides logistics interface

while also operating:

Protocol owner → logistics service

The platform may technically remain open while designing:

• API priorities;
• ranking;
• authentication;
• data access;
• integration permissions; or
• technical certification

in a manner favouring its own downstream operation.

This can produce vertical foreclosure.

7. Discriminatory Access

A dominant protocol operator may give different access conditions to different participants.

Potential discriminatory practices include:

• higher API fees for competitors;
• slower data access;
• restricted functionality;
• inferior technical documentation;
• discriminatory authentication requirements;
• delayed certification;
• preferential access to transaction data; and
• differential interoperability.

The competition-law question is whether such differences reflect legitimate technical or commercial reasons or instead constitute exclusionary discrimination.

8. Data as a Source of Protocol Dominance

Digital supply-chain protocols generate enormous quantities of data:

• supplier performance;
• inventory levels;
• customer demand;
• transportation routes;
• prices;
• production schedules;
• warehouse capacity;
• delivery performance; and
• purchasing behaviour.

A dominant protocol operator may therefore obtain information unavailable to its rivals.

This creates a potentially reinforcing cycle:

Protocol dominance → data accumulation → improved prediction → better service → increased adoption → further protocol dominance

The competition problem becomes particularly serious when the operator uses confidential participant data to compete against those same participants.

9. Tying and Bundling

A dominant protocol can also be used to force adoption of complementary services.

For example:

Mandatory procurement protocol + mandatory cloud service

or:

Logistics API + payment service

or:

Warehouse-management protocol + proprietary analytics

If customers cannot obtain access to the protocol without purchasing another service, competition authorities may examine the conduct as tying or bundling.

10. Exclusive Protocol Arrangements

A dominant firm may require suppliers to use only its protocol.

Such arrangements may create:

• exclusionary effects;
• reduced multi-homing;
• increased switching costs;
• foreclosure of competing protocols;
• reduced interoperability; and
• increased dependency.

The analysis should consider duration, coverage, market power, foreclosure percentage and availability of alternatives.

11. Interoperability as a Competition Remedy

Competition authorities may respond through remedies such as:

Structural remedies

• divestiture;
• separation of infrastructure and downstream operations.

Behavioural remedies

• mandatory interoperability;
• non-discriminatory access;
• API access;
• data portability;
• transparent technical standards;
• prohibition of self-preferencing;
• firewalls protecting confidential information.

Technical remedies

• open APIs;
• common data formats;
• interoperable authentication;
• real-time data portability.

The most effective remedy may therefore involve technical architecture, rather than simply imposing a monetary penalty.

12. Important Case Laws

1. United Brands v Commission — C-27/76

The European Court of Justice established important principles concerning abuse of a dominant position and discriminatory commercial conduct.

Relevance

The case demonstrates that dominance does not give an undertaking unlimited freedom to impose discriminatory conditions on commercial partners.

For digital supply chains, the principle can become relevant where a dominant protocol operator gives materially different access conditions to similarly situated suppliers or distributors.

Significance

The case provides an early foundation for analysing discriminatory treatment by dominant infrastructure operators.

13. Commercial Solvents v Commission — Joined Cases 6/73 and 7/73

Commercial Solvents concerned refusal to supply an essential input to a downstream competitor.

The Court treated the conduct as potentially abusive because the dominant undertaking could use control over an upstream input to eliminate competition downstream.

Digital supply-chain relevance

The modern equivalent could involve:

Upstream digital infrastructure → downstream supply-chain service

For example, where a dominant firm controls a critical protocol and simultaneously competes in a downstream market, refusal to provide access may create foreclosure concerns.

Principle

A dominant undertaking controlling an indispensable input cannot necessarily exploit that position to eliminate downstream competition.

14. Magill — Joined Cases C-241/91 P and C-242/91 P

Magill is one of the leading European cases concerning refusal to license intellectual property.

The Court recognised circumstances in which refusal to provide access to protected information could constitute abuse.

Digital protocol relevance

Protocol ownership may involve:

• copyrights;
• database rights;
• trade secrets;
• patents;
• proprietary interfaces.

The mere existence of intellectual-property rights does not automatically immunise exclusionary conduct.

Importance

Magill is especially relevant where control over proprietary information becomes a bottleneck preventing the emergence of a new product or competing service.

15. Bronner v Mediaprint — C-7/97

Bronner established the strict European test associated with refusal to provide access to infrastructure.

The Court emphasised the importance of indispensability and whether duplication of the facility is realistically possible.

Digital supply-chain relevance

A dominant protocol should not automatically be treated as an essential facility simply because it is popular.

The competition authority should examine:

• whether alternative protocols exist;
• whether interoperability is feasible;
• whether duplication is economically viable;
• whether access is indispensable; and
• whether refusal eliminates effective competition.

Significance

Bronner prevents competition law from becoming a general obligation for dominant companies to share every commercially valuable technology.

16. IMS Health v Commission — Joined Cases C-418/01 P and C-419/01 P

IMS Health involved a highly structured information system and refusal to license.

The case is particularly significant for digital infrastructure because it considered circumstances in which an intellectual-property right could intersect with market foreclosure.

Digital supply-chain application

A proprietary supply-chain data architecture could potentially become a critical interoperability standard.

Examples include:

• pharmaceutical distribution systems;
• logistics coding systems;
• inventory databases;
• supplier-identification protocols.

Where competitors cannot realistically operate without compatibility, access restrictions become more significant.

17. Microsoft v Commission — T-201/04

Microsoft is one of the most important cases for analysing interoperability and digital ecosystem dominance.

The Commission found concerns regarding Microsoft's refusal to provide interoperability information necessary for competing work-group server products.

Supply-chain significance

The case illustrates how technical interoperability can be a competition parameter.

A modern supply-chain equivalent could involve a dominant enterprise platform withholding:

• API specifications;
• communication protocols;
• authentication information;
• interface documentation.

Key lesson

Competition can be harmed not merely through high prices but through technical exclusion.

18. Google Shopping — Case T-612/17

The Google Shopping litigation concerned Google's treatment of its own comparison-shopping service in search results.

The broader significance lies in the relationship between:

platform dominance + control of an important digital gateway + preferential treatment of own downstream service.

Supply-chain relevance

A dominant procurement, logistics or marketplace protocol could theoretically favour its own downstream logistics, warehousing or distribution services.

Examples include preferential:

• ranking;
• routing;
• API access;
• visibility;
• certification;
• transaction processing.

The case is therefore relevant to self-preferencing and vertical foreclosure.

19. Slovak Telekom v Commission — Joined Cases C-165/19 P and C-166/19 P

This case involved access to telecommunications infrastructure and the interaction between dominance and access obligations.

Digital infrastructure relevance

Telecommunications networks illustrate how infrastructure control can affect downstream competition.

The principles are transferable to digital supply-chain systems where the protocol functions as a gateway through which downstream competitors must operate.

Key lesson

Competition analysis must distinguish ordinary commercial refusal from conduct that exploits control over an infrastructure necessary for effective competition.

20. European Commission v Broadcom — AT.40608

The Broadcom matter concerned exclusivity-related practices in the semiconductor sector.

Supply-chain relevance

Semiconductors are foundational inputs for:

• cloud infrastructure;
• industrial IoT;
• logistics;
• vehicles;
• warehouse automation;
• telecommunications.

The case illustrates how contractual restrictions imposed by a powerful upstream technology supplier can potentially foreclose competing suppliers.

Broader lesson

Digital supply-chain dominance may arise upstream, rather than only at the platform level.

21. United States v Microsoft Corp. — D.C. Circuit

The Microsoft litigation is a foundational U.S. competition case concerning technological dominance, exclusionary conduct and the leveraging of control over an important platform.

Digital supply-chain relevance

It demonstrates how control over a technological platform can affect adjacent markets.

The same logic can arise when:

dominant protocol → complementary software → logistics/procurement market

A protocol owner can potentially use technical restrictions to disadvantage competing applications.

22. Aspen Skiing Co. v Aspen Highlands Skiing Corp.

The U.S. Supreme Court considered a refusal-to-deal theory involving cooperation between competitors.

Relevance

The case remains important for understanding exceptional circumstances in which a previously cooperative commercial relationship is terminated in a manner that may harm competition.

For digital supply chains, the principle may become relevant where a dominant platform:

1. previously enabled interoperability;
2. developed a commercially established relationship;
3. abruptly withdraws interoperability; and
4. thereby substantially disadvantages a rival.

23. Eastman Kodak Co. v Image Technical Services

Kodak is particularly important for lock-in and aftermarket power.

The Supreme Court recognised that substantial switching costs can affect market power even where customers initially purchased equipment in a competitive environment.

Digital supply-chain significance

The analogy is powerful:

Initial software adoption → ecosystem dependency → high switching costs → aftermarket dependence

A business may have chosen a protocol when alternatives existed but subsequently become dependent on:

• proprietary data formats;
• APIs;
• integrations;
• authentication systems;
• historical data;
• specialised hardware.

Thus, competition authorities may need to examine post-adoption market power, not simply the conditions existing at the initial purchase.

24. Key Competition Concerns

25. Theoretical Competition Model

Digital supply-chain protocol dominance can be understood through a five-layer structure:

Layer 1 — Infrastructure

Cloud, networks, chips, authentication and computing resources.

↓

Layer 2 — Protocol

APIs, data standards, communication rules and technical interfaces.

↓

Layer 3 — Data

Inventory, transactions, logistics and supplier information.

↓

Layer 4 — Platform

Procurement, logistics, marketplace and supply-chain management systems.

↓

Layer 5 — Downstream Markets

Manufacturing, retail, transport, warehousing and distribution.

The greatest competition risk arises when one undertaking controls several layers.

For example:

Cloud infrastructure + protocol + data + marketplace + logistics

This produces vertical ecosystem leverage.

26. Protocol Dominance and Contestability

The most important long-term question is not simply:

"Is the protocol dominant?"

It is:

"Can another protocol realistically emerge?"

Contestability decreases where there are:

• strong network effects;
• proprietary standards;
• high switching costs;
• data accumulation;
• interoperability restrictions;
• contractual exclusivity;
• economies of scale; and
• ecosystem-wide integration.

A market may therefore appear technically open while being economically closed.

27. Consumer and Supplier Effects

Although the immediate participants may be businesses, ultimate effects can reach consumers.

Protocol dominance may result in:

• higher logistics costs;
• reduced supplier choice;
• slower innovation;
• higher retail prices;
• reduced product variety;
• weaker service quality;
• supply-chain fragility.

Small suppliers may be particularly vulnerable because they cannot afford parallel systems.

28. Regulatory Challenges

Competition authorities face several difficulties.

First: defining the relevant market

Is the market:

• supply-chain software?
• API access?
• logistics coordination?
• procurement infrastructure?
• data exchange?
• cloud services?

Second: identifying dominance

Traditional market-share analysis may be insufficient because protocols may be provided at zero monetary price.

Authorities may therefore consider:

• user numbers;
• transaction volumes;
• switching costs;
• data advantages;
• interoperability;
• network effects;
• technical dependence.

Third: distinguishing innovation from exclusion

A proprietary protocol may legitimately provide better security or performance.

Competition law must therefore distinguish:

legitimate technical differentiation

from

deliberate interoperability sabotage.

29. Possible Competition-Law Remedies

Authorities may consider:

Access remedies

• reasonable access;
• FRAND-style licensing;
• non-discriminatory access.

Interoperability remedies

• API access;
• technical documentation;
• open interfaces;
• common data standards.

Data remedies

• portability;
• controlled data sharing;
• restrictions on use of competitor data.

Conduct remedies

• prohibition of self-preferencing;
• prohibition of discriminatory access;
• restrictions on exclusivity.

Structural remedies

Where behavioural measures cannot restore competition, separation of infrastructure and downstream commercial operations may be considered.

30. Critical Legal Principle

The central competition-law distinction is:

A firm is generally entitled to design and control its technology, but dominance may limit its ability to use control over indispensable digital infrastructure to exclude competition in neighbouring markets.

The stronger the combination of indispensability + dominance + foreclosure + lack of alternatives, the greater the competition concern.

Conclusion

Digital supply-chain protocol dominance represents a modern form of infrastructural market power. Unlike conventional monopolies, the bottleneck may not be a physical facility or a traditional product. It may instead be an API, authentication layer, data format, technical standard, cloud interface or coordination protocol.

The principal risks are interoperability foreclosure, discriminatory access, self-preferencing, data exploitation, tying, exclusivity and technological lock-in.

The cases of Commercial Solvents, Magill, Bronner, IMS Health, Microsoft, Google Shopping, Slovak Telekom, Broadcom, U.S. Microsoft, Aspen Skiing and Kodak collectively demonstrate the principal legal themes: control over critical inputs, exceptional refusal-to-deal situations, interoperability, technological ecosystems, vertical foreclosure and switching-cost-driven market power.