Margin Squeeze Analysis in Vertically Integrated Digital Platforms

1. Introduction

A margin squeeze occurs when a vertically integrated undertaking controls an important upstream input or infrastructure and also competes downstream with firms that depend upon that input, while setting the upstream and downstream conditions in a way that makes effective downstream competition difficult or unprofitable.

In digital markets, the traditional model becomes more complex. A platform may simultaneously control:

• an app store or marketplace;
• an operating system;
• an advertising exchange or ad-tech infrastructure;
• a cloud-computing layer;
• an API or interoperability interface;
• a payment system;
• a data-access infrastructure;
• search, ranking or recommendation infrastructure; and
• a downstream consumer-facing service.

The concern is therefore not merely whether the platform charges a high upstream price. The crucial question is whether the relationship between the upstream access conditions and the downstream price/cost structure leaves an equally efficient rival unable to compete effectively.

2. Meaning of Margin Squeeze

A simplified margin-squeeze test can be expressed as:

Downstream revenue − relevant downstream costs − upstream access price ≤ 0

If a vertically integrated dominant undertaking charges independent downstream competitors an upstream price that, when combined with the undertaking's own downstream pricing, leaves insufficient margin for an equally efficient competitor, competition may be foreclosed.

For example:

Platform's upstream API/access charge: ₹100
Downstream price charged by platform: ₹120
Efficient downstream cost: ₹30

An independent competitor faces:

₹100 + ₹30 = ₹130 cost

while the platform sells downstream at ₹120.

The rival therefore cannot profitably match the platform's downstream price.

The digital complication is that the upstream input may not have a conventional monetary price. It may instead involve:

• data access;
• API calls;
• cloud capacity;
• interoperability;
• ranking visibility;
• technical certification;
• payment access;
• authentication;
• app distribution;
• advertising inventory;
• identity services; or
• access to a user base.

Thus, a digital margin squeeze may exist even where the platform's formal upstream price is zero.

3. Why Vertical Integration Matters

Vertical integration itself is not unlawful.

A platform may legitimately operate at several levels of a supply chain because integration can produce:

• lower transaction costs;
• better interoperability;
• improved security;
• economies of scale;
• innovation;
• reduced duplication;
• improved consumer experience.

The competition concern arises where integration allows the platform to control an upstream bottleneck while competing downstream against the firms dependent on that bottleneck.

The platform effectively becomes:

supplier + infrastructure operator + downstream competitor + rule-maker

This combination is particularly significant in digital markets because the upstream infrastructure may be indispensable for reaching users.

4. Elements of a Digital Margin Squeeze

A. Dominance at the upstream level

The undertaking ordinarily needs substantial market power over the upstream input.

Relevant factors include:

• market share;
• network effects;
• switching costs;
• technical dependency;
• data advantages;
• interoperability barriers;
• ecosystem effects;
• economies of scale;
• control over essential interfaces; and
• barriers to multi-homing.

A platform need not necessarily possess a conventional 90% market share. In digital ecosystems, control over a strategically important gateway can be more significant than simple market share.

B. Downstream competitive presence

The platform must also operate downstream or otherwise compete with businesses using the upstream input.

Examples include:

App-store infrastructure → platform's own apps

Search infrastructure → platform's own specialised-search services

Advertising exchange → platform's own advertising services

Cloud infrastructure → platform's competing software/service

Marketplace infrastructure → platform's own retail products

This creates the central conflict:

The platform determines the conditions under which its downstream competitors can compete against it.

5. The Price-Cost Test

Traditional margin-squeeze analysis frequently asks whether the platform's own downstream business could profitably operate under the same upstream price and downstream conditions.

The classic formulation is sometimes described as an equally efficient competitor test.

Suppose:

• upstream price = €50;
• platform's downstream price = €70;
• platform's downstream cost = €25.

The platform's downstream margin is:

€70 − €50 − €25 = −€5

If the platform itself could not profitably operate under the relevant price structure, this may support a margin-squeeze finding.

However, EU competition law does not reduce every case to a mechanically calculated accounting margin. The legal assessment depends upon the particular conduct, market structure and effects.

6. Digital Markets Complicate the Test

A. Zero-price upstream services

Digital platforms may provide APIs, authentication, ranking access or basic infrastructure for free.

The absence of a monetary upstream price does not automatically eliminate competition concerns.

The relevant "price" may consist of:

• mandatory commissions;
• data surrender;
• technical restrictions;
• access fees;
• payment charges;
• advertising obligations;
• cloud consumption requirements;
• certification costs.

B. Non-price margin squeeze

A platform may technically provide access while imposing conditions that make effective downstream competition commercially impossible.

Examples include:

• API-rate restrictions;
• delayed access;
• inferior technical functionality;
• discriminatory latency;
• mandatory use of affiliated payment systems;
• interoperability restrictions;
• excessive security requirements imposed selectively;
• preferential access for the platform's own service.

The analysis therefore increasingly concerns a commercially effective margin, rather than merely an accounting margin.

7. Data as an Upstream Input

Data can function as the upstream resource in a digital ecosystem.

Consider a platform that controls:

• consumer behavioural data;
• transaction data;
• location data;
• search data; and
• advertising-performance data.

It then competes downstream in advertising.

If independent advertising intermediaries receive materially inferior access to the relevant data while the platform uses the same data internally, the competitive problem may resemble a margin-squeeze or discriminatory-input problem.

The analysis should examine:

1. what data is controlled;
2. whether competitors depend upon it;
3. whether equivalent data is realistically available;
4. whether access is technically feasible;
5. whether the platform uses superior internal access;
6. whether downstream competition is weakened; and
7. whether legitimate privacy/security justifications exist.

8. APIs and Interoperability

APIs are particularly important in digital margin-squeeze cases.

A platform may control an API necessary for downstream services.

Suppose:

Platform API → third-party application → consumer

while the platform simultaneously operates its own competing application.

If the platform:

• increases API charges;
• limits API functionality;
• restricts call volume;
• imposes discriminatory technical requirements; or
• provides its own service with superior access,

the resulting margin may become insufficient for independent competitors.

The competition question becomes:

Is the downstream rival genuinely able to compete using the commercially available upstream access conditions?

9. App Stores and Payment Infrastructure

A vertically integrated mobile ecosystem provides a particularly strong illustration.

A platform may control:

1. operating system;
2. app distribution;
3. payment infrastructure;
4. identity/authentication;
5. developer rules; and
6. competing applications.

If developers must pay a commission and cannot freely use alternative payment systems, the platform may affect the downstream economics of competing applications.

However, the legal analysis may involve several doctrines simultaneously:

• margin squeeze;
• tying;
• refusal to deal;
• exclusive dealing;
• self-preferencing;
• discriminatory access;
• anti-steering;
• excessive pricing.

The precise classification matters because the legal tests are not identical.

10. Cloud Computing and Margin Squeeze

Cloud ecosystems create another important example.

Imagine a cloud provider controlling:

• compute infrastructure;
• storage;
• networking;
• identity services;
• databases;

while also selling competing downstream software.

Independent software providers may incur:

• compute charges;
• storage charges;
• API charges;
• data-egress charges;
• interoperability costs.

If the cloud provider's own downstream product receives preferential infrastructure economics unavailable to rivals, an effective margin squeeze may arise.

The analysis should therefore examine total infrastructure-adjusted cost, not merely the headline cloud price.

11. Important EU Legal Principle: Margin Squeeze as an Independent Abuse

A major development came from the EU courts' treatment of margin squeeze as a potentially distinct form of abuse.

A margin squeeze can arise through the relationship between:

• the upstream price; and
• the downstream price,

rather than requiring proof that the upstream input itself was indispensable under the strictest refusal-to-supply test.

This is particularly important for digital platforms because otherwise a dominant platform could potentially avoid scrutiny simply by arguing that competitors were not legally entitled to access the input in the first place.

12. Key Case Laws

1. Deutsche Telekom AG v Commission — Case C-280/08 P

This is one of the foundational EU margin-squeeze decisions.

Deutsche Telekom controlled access to the telecommunications network while competing downstream in retail telecommunications.

The Court confirmed that a margin squeeze can constitute an independent abuse of dominance.

Importance

The Court emphasised the relationship between:

• wholesale access charges; and
• retail prices.

The central question was whether the spread between them was sufficient to allow an equally efficient competitor to compete.

Digital-platform relevance

The principle translates readily to digital ecosystems where a platform controls upstream infrastructure and competes downstream.

Examples include:

• API access;
• app distribution;
• cloud infrastructure;
• payment systems;
• advertising infrastructure.

2. TeliaSonera Sverige AB — Case C-52/09

The Court of Justice further clarified margin-squeeze doctrine in TeliaSonera.

The case concerned broadband access and the relationship between wholesale and retail pricing.

The Court rejected the idea that margin squeeze necessarily depends upon a conventional refusal-to-supply situation.

Major principle

A margin squeeze can constitute an independent abuse where the spread between upstream and downstream prices is insufficient to allow effective downstream competition.

Digital significance

This is particularly important for digital platforms because it prevents the analysis from becoming artificially dependent on whether the platform formally "refused" access.

A platform can theoretically grant access while setting conditions that make downstream competition economically unsustainable.

3. Telefónica SA v Commission — Case C-295/12 P

Telefónica concerned broadband services and the Commission's finding of margin squeeze.

The Court upheld the essential structure of the Commission's approach.

Importance

The case illustrates that competition authorities can examine:

• wholesale access conditions;
• retail prices;
• costs;
• competitor economics; and
• exclusionary effects.

Digital-platform relevance

A vertically integrated digital platform could similarly be assessed by comparing the economics of its upstream infrastructure with its downstream service.

For example:

Platform infrastructure charge + efficient downstream cost versus platform's downstream price.

4. Slovak Telekom a.s. and Deutsche Telekom AG — Joined Cases C-165/19 P and C-166/19 P

This is especially significant for modern margin-squeeze analysis.

The Court considered exclusionary conduct involving access to telecommunications infrastructure.

The case reinforced the importance of examining the actual conditions of access and the competitive consequences of the dominant firm's conduct.

Digital relevance

The case is useful for understanding situations where access to infrastructure is formally available but the structure of access conditions may nevertheless weaken downstream competition.

This is highly relevant to:

• digital infrastructure;
• APIs;
• cloud services;
• platform interfaces;
• interoperability.

5. Commission v Alrosa — Case C-441/07 P

Although Alrosa was principally concerned with exclusivity and commitments rather than a classic margin-squeeze claim, it is highly relevant to the economic assessment of exclusionary effects and proportionality in dominance cases.

The case demonstrates the importance of assessing whether restrictions substantially affect competitive opportunities.

Digital-platform relevance

A platform's commercial conditions should not be examined solely as isolated contractual provisions.

Authorities may need to consider their:

• cumulative effect;
• duration;
• market coverage;
• foreclosure potential; and
• impact on alternative suppliers.

6. Google Shopping — Google and Alphabet v Commission — Case C-48/22 P

The Google Shopping litigation is not a conventional margin-squeeze case, but it is extremely important for vertically integrated digital platforms.

Google operated a general search engine while also offering its own comparison-shopping service.

The Court confirmed the relevance of Google's conduct in giving preferential positioning to its own downstream service.

Why it matters for margin squeeze

The case demonstrates that digital-platform foreclosure may operate through access conditions and discriminatory treatment rather than only explicit prices.

A platform may effectively improve its own downstream margin by:

• giving its service privileged infrastructure access;
• reducing rivals' visibility;
• imposing technical disadvantages;
• restricting interoperability.

Thus, modern digital margin-squeeze analysis increasingly overlaps with self-preferencing and discriminatory access.

7. Bronner — Case C-7/97

Bronner concerned access to a newspaper distribution system.

The Court established the demanding conditions traditionally associated with a refusal-to-supply/essential-facility theory.

The case is important because it helps distinguish refusal to supply from margin squeeze.

Digital significance

A digital platform may argue:

"Competitors have no right to use our infrastructure."

Bronner illustrates the stringent conditions associated with a pure refusal-to-supply theory.

But TeliaSonera and subsequent margin-squeeze jurisprudence demonstrate why a margin-squeeze analysis can sometimes be legally distinct from an outright refusal to supply.

8. Oscar Bronner-type Essential-Facility Logic and Digital Gateways

Although Bronner itself is not a margin-squeeze case, its conceptual importance should not be underestimated.

Digital infrastructure can resemble a bottleneck:

• app distribution;
• operating-system functionality;
• search access;
• cloud infrastructure;
• digital identity;
• payment rails.

The legal question becomes whether the conduct is properly characterised as:

refusal to deal → discriminatory access → margin squeeze → tying → self-preferencing

rather than automatically treating every disadvantage imposed by a platform as a margin squeeze.

13. Relationship Between Margin Squeeze and Self-Preferencing

The two doctrines overlap but are not identical.

Margin squeeze

Focuses primarily on:

Can an equally efficient downstream competitor survive economically under the platform's upstream and downstream pricing conditions?

Self-preferencing

Focuses primarily on:

Does the platform favour its own downstream service over competing services using the platform?

Combined digital scenario

A platform may:

1. charge competitors for infrastructure;
2. provide its own service with lower internal costs;
3. give its own service better ranking;
4. restrict competitors' API functionality; and
5. impose payment restrictions.

The combined conduct may produce a much stronger foreclosure theory than any single restriction viewed independently.

14. Margin Squeeze and Essential Facilities

The doctrines must be kept analytically separate.

This distinction is crucial when analysing vertically integrated platforms.

15. Equally Efficient Competitor Test

The EEC test asks whether a competitor with costs comparable to the dominant undertaking could compete under the dominant firm's pricing structure.

A simplified model is:

Downstream price − upstream price − downstream cost = margin

If:

Margin < 0

there may be a strong indication of a squeeze.

But the assessment can be more sophisticated.

Authorities may consider:

• avoidable costs;
• long-run incremental costs;
• average variable costs;
• average avoidable costs;
• accounting treatment;
• depreciation;
• network costs;
• common costs;
• platform-specific costs.

16. When the EEC Test Becomes Difficult in Digital Markets

Digital markets frequently have:

• zero marginal cost;
• high fixed costs;
• substantial R&D expenditure;
• network effects;
• multi-sided platforms;
• cross-subsidisation;
• advertising-funded services;
• data monetisation.

Consequently, traditional accounting measures may produce misleading results.

For example, a platform may offer a service at zero monetary price while monetising users through advertising.

The relevant downstream "price" cannot simply be treated as zero in a conventional sense.

17. Multi-Sided Platforms

A digital platform may operate several interconnected sides:

Users → Platform ← Advertisers

or:

Developers → App Store → Consumers

or:

Merchants → Marketplace → Consumers

A margin squeeze on one side may generate competitive effects on another.

For example, a platform could:

• charge merchants high commissions;
• subsidise consumers;
• operate its own merchant business;
• use transaction data from independent merchants.

The downstream margin must therefore be assessed within the broader ecosystem.

18. Internal Transfer Pricing

Vertically integrated platforms often do not make explicit upstream payments to themselves.

This creates an important analytical problem.

An independent competitor might pay:

€10 API fee

while the platform's internal downstream division effectively pays:

€0.

The authority may therefore need to construct an appropriate hypothetical internal transfer price or use other cost benchmarks.

The objective is to avoid allowing corporate integration to obscure the economic margin.

19. Data and Algorithmic Advantages

Digital platforms may enjoy advantages that do not appear in financial accounts.

For example:

• better training data;
• real-time user data;
• superior ranking information;
• access to behavioural signals;
• algorithmic optimisation;
• preferential latency;
• internal experimentation.

Consequently, even if the monetary margin appears positive, competitors may face a functional margin squeeze because they cannot obtain equivalent technological inputs.

This suggests a broader concept:

Capability-adjusted margin squeeze

where competitive feasibility is assessed using both financial and technological inputs.

20. Switching Costs and Lock-In

Margin squeeze effects become stronger when customers cannot easily move between ecosystems.

Relevant factors include:

• data portability limitations;
• contractual lock-in;
• technical incompatibility;
• high retraining costs;
• loss of historical data;
• loss of reputation;
• ecosystem-specific APIs;
• consumer network effects.

A relatively small price disadvantage may therefore produce significant foreclosure where switching costs are high.

21. Legitimate Business Justifications

Not every economically narrow margin is abusive.

A platform may have legitimate reasons for its pricing or access conditions, such as:

• cybersecurity;
• privacy;
• fraud prevention;
• network stability;
• technical compatibility;
• investment recovery;
• quality control;
• intellectual-property protection;
• regulatory compliance.

The authority must distinguish genuine efficiencies from post-hoc justifications for exclusionary conduct.

22. Effects-Based Assessment

Modern digital margin-squeeze analysis should consider:

A. Foreclosure

Are competitors actually excluded or materially weakened?

B. Duration

Was the conduct temporary or persistent?

C. Market coverage

What percentage of downstream demand is affected?

D. Replicability

Can competitors realistically reproduce the platform's infrastructure?

E. Multi-homing

Can customers use alternative platforms simultaneously?

F. Network effects

Does exclusion of rivals reinforce the platform's dominance?

G. Innovation

Does the conduct discourage competing innovation?

23. Dynamic Competition

Digital markets require attention to future competition.

A margin squeeze may appear modest today but become strategically significant if it prevents competitors from reaching the scale necessary to:

• accumulate data;
• develop network effects;
• improve algorithms;
• attract developers;
• establish interoperability;
• challenge the incumbent.

Thus:

Short-term price effects may understate long-term foreclosure effects.

24. Remedies

Where a margin squeeze is established, possible remedies include:

1. Price regulation

Require the platform to maintain a commercially viable upstream/downstream spread.

2. Non-discriminatory access

Require equivalent access conditions for internal and external downstream businesses.

3. API access

Mandate reasonable and technically equivalent access.

4. Interoperability

Require technical compatibility.

5. Accounting separation

Require separation of upstream and downstream costs.

6. Internal-transfer transparency

Require the platform to document the economic cost of internal infrastructure use.

7. Non-discrimination monitoring

Create continuing compliance mechanisms.

8. Structural remedies

In exceptional circumstances, separation of infrastructure and downstream operations may be considered.

25. Special Problem of Algorithmic Margin Squeeze

A platform can create a margin squeeze without changing its posted prices.

For example, its algorithm could:

• lower the ranking of competing products;
• increase rivals' required advertising expenditure;
• slow third-party API responses;
• allocate fewer impressions;
• increase competitors' infrastructure costs;
• increase the platform's own conversion rates.

The platform's effective competitive margin is thereby altered.

This produces a useful conceptual distinction:

Price margin squeeze = monetary upstream/downstream spread.

Algorithmic margin squeeze = technological or algorithmic conditions that make the downstream rival's effective cost of competition substantially higher.

26. Margin Squeeze in AI Platforms

The concept is increasingly relevant to AI ecosystems.

Consider a vertically integrated AI undertaking controlling:

GPU/cloud infrastructure → model hosting → API → consumer application

The platform may:

• charge external developers for compute;
• give its own AI products preferential compute allocation;
• provide better inference latency internally;
• limit external model access;
• impose high API charges;
• use proprietary user data to improve its own downstream service.

An independent AI provider may therefore face a materially higher effective cost.

The resulting competitive issue can resemble a compute/API margin squeeze.

27. Key Analytical Framework

For a vertically integrated digital platform, the following sequence is useful:

Step 1 — Identify the upstream input

API, cloud, data, payment system, app distribution, advertising infrastructure, etc.

↓

Step 2 — Establish market power

Market share + network effects + switching costs + infrastructure control.

↓

Step 3 — Identify downstream competition

Is the platform competing with users of the upstream input?

↓

Step 4 — Determine access conditions

Price + technical restrictions + data + interoperability + ranking.

↓

Step 5 — Calculate effective downstream margin

Upstream cost + downstream cost compared with downstream revenue.

↓

Step 6 — Apply the appropriate cost benchmark

EEC or another legally appropriate cost methodology.

↓

Step 7 — Examine foreclosure

Can efficient competitors remain viable?

↓

Step 8 — Assess objective justification

Security, privacy, efficiency, innovation, etc.

↓

Step 9 — Assess consumer and innovation effects

Prices, quality, choice, innovation and ecosystem competition.

↓

Step 10 — Select proportionate remedies

Pricing, access, interoperability, non-discrimination or structural measures.

28. Overall Legal Significance

Margin squeeze is particularly powerful in the digital-platform context because vertical integration allows a dominant undertaking to control both:

the conditions of access to an ecosystem and the competitive outcome within that ecosystem.

The most important legal insight from the EU jurisprudence is that the analysis should not be limited to whether the platform explicitly refuses access.

The critical question is often:

Does the platform's combination of upstream access conditions and downstream competitive behaviour leave an economically viable opportunity for an equally efficient rival?

In digital markets, that inquiry must also account for data, algorithms, interoperability, network effects, switching costs, multi-sided pricing and non-price access conditions.

29. Conclusion

Margin squeeze provides an important framework for analysing vertically integrated digital platforms because such platforms can simultaneously act as infrastructure providers, marketplace operators, gatekeepers and downstream competitors.

The foundational cases—particularly Deutsche Telekom, TeliaSonera, Telefónica and Slovak Telekom—establish the central EU principle that the relationship between upstream and downstream conditions can itself produce abusive foreclosure.

For digital platforms, however, the concept must be adapted to modern forms of economic control. The relevant "margin" may include not only money but also data access, API functionality, computing resources, ranking, latency, interoperability and payment conditions.

Accordingly, a modern digital-platform margin-squeeze analysis should ask three interconnected questions:

1. What essential or strategically important upstream capability does the platform control?
2. What effective cost does an independent downstream competitor bear in accessing that capability?
3. Does the platform's downstream conduct leave an equally efficient rival with a realistic and sustainable competitive margin?

Where the answer demonstrates systematic foreclosure, margin squeeze can become a powerful basis for intervention against vertically integrated digital ecosystems.