Procurement teams plan renewals two or three years out, and platform vendors plan their defenses on a similar horizon. Antitrust remedies now move on the same clock, which makes them a planning input rather than a legal curiosity. The question is not whether regulators will act. It is which remedy lands before your next renewal, in which jurisdiction, and what it changes in the contract you are about to sign.
Two enforcement tracks matter. The European Union regulates platform conduct in advance through the Digital Markets Act, which has been in force since March 2024 and has already produced penalty decisions. The United States litigates after the fact, case by case, with remedies that arrive years after the conduct and are then appealed. The first track changes defaults quickly. The second changes them slowly, and sometimes not at all.
What a remedy actually changes
Remedies come in three shapes, and they are not interchangeable. A structural remedy breaks up a company or forces a divestiture. A behavioral remedy prohibits specific conduct and often installs a monitor. Ex ante regulation, the DMA model, writes rules for designated platforms before any violation is proven. Each shape produces a different kind of change in the products you buy.
Behavioral remedies are the most common and the easiest to outlast. A consent decree in the United States is a negotiated settlement with compliance obligations, periodic reporting, and often a court-appointed monitor, and the Microsoft decree that closed the 2001 case ran for about a decade. For a buyer, the lesson is to plan for a five-to-ten-year lag between a case and a usable change in terms.
The DMA already changes defaults in Europe
The Digital Markets Act, Regulation (EU) 2022/1925, applies to platforms the European Commission designates as gatekeepers. The first designations in September 2023 covered Alphabet, Amazon, Apple, ByteDance, Meta, and Microsoft, and Booking was added in 2024. Obligations apply from 7 March 2024. The rules are specific: gatekeepers cannot favor their own services in ranking, must allow business users to steer customers to offers outside the platform, must permit alternative app stores and sideloading, must give business users access to the data they generate, and must obtain consent before combining personal data across services.
The penalty structure is what gives the rules weight: up to 10% of worldwide turnover for a first violation and 20% for repeat non-compliance, plus the possibility of behavioral or structural remedies after a market investigation into systematic infringement. Enforcement has moved from investigation to penalty. The Commission issued its first DMA fines in April 2025, against Apple and Meta. In July 2026 it fined Google twice over search self-preferencing and Play Store rules that limited developers from pointing users to cheaper offers elsewhere. Fines are not the interesting part for a buyer. The interesting part is that the underlying conduct is now prescribed by regulation, which means your vendor's product roadmap in Europe has a compliance deadline attached to it.
Two obligations deserve attention in a procurement file. The first is data portability for end users under Article 6(9) and for business users under Article 6(10), which turns export capability from a nice-to-have into a regulated feature with a compliance date. The second is messaging interoperability under Article 7, which is being phased in through Commission technical work. Neither of these gives you a migration path on its own, but both give you leverage when you ask for data egress terms and API access.
The US track is slower and narrower
The US cases are worth tracking because their remedies, when they arrive, tend to be narrow and durable. In the search case against Google, the court found liability in August 2024, and the remedy decision in September 2025 declined to order a breakup of Chrome or Android. It barred exclusive default-placement contracts and required some data sharing with competitors. Both sides have appealed, so the practical terms are still moving.
In the advertising technology case, the court found liability in April 2025 on two counts covering the publisher ad server and the ad exchange, and the remedy phase followed. In the Apple case filed in 2024, the government's theory centers on smartphone market access, including app distribution and API access for rivals. That case has not reached a remedy. The Federal Trade Commission's case against Meta over the Instagram and WhatsApp acquisitions went to trial in April 2025 and was decided for Meta in November 2025, with the FTC appealing in January 2026.
There is also private litigation that moves faster than government cases. The Epic Games dispute with Apple ended its liability phase years ago, but the enforcement fight over anti-steering produced a 2025 ruling that forced Apple to stop collecting commission on purchases made through external links in the United States. Apple has sought review of the contempt findings, and the Supreme Court has agreed to hear a narrow part of that appeal. Whatever the outcome, a commission assumption that treated in-app purchase as the only monetization path is now out of date.
What actually changes for enterprise buyers
Most antitrust coverage is about consumer products, but the enterprise consequences are concrete. First, default placement and preinstallation rules affect which identity, browser, and productivity tools arrive bundled with the hardware your users buy, and that shapes your support burden. Second, app store and marketplace commission rules affect the unit economics of any internal or customer-facing app you distribute through a platform. Third, interoperability and portability mandates affect switching costs, which is the number that decides whether a multi-vendor strategy is real or rhetorical.
What does not change is physics. A portability mandate does not move petabytes cheaply, and an interoperability requirement does not make two identity systems semantically compatible. Regulation lowers the legal cost of switching. It does not lower the engineering cost, and it does not touch egress pricing unless a specific remedy addresses it.
Watchlist for the next eight quarters
The table tracks the matters most likely to affect enterprise platform contracts, with the trigger that should prompt a procurement review.
| Matter | Forum and status | What it could change for buyers | Trigger to watch |
|---|---|---|---|
| DMA gatekeeper compliance | European Commission, ongoing with fines issued | App distribution costs, browser and search defaults, consent flows | Any change to your vendor's EU terms of service |
| DMA data portability and interoperability | European Commission, phased implementation | Export formats, API access, messaging interop | New export tooling or API deprecation notices |
| US v. Google, search | Remedy decided September 2025, on appeal | Default placement deals, Android licensing, data sharing | Appellate ruling or a change in OEM bundling |
| US v. Google, ad technology | Liability April 2025, remedy phase | Ad server and exchange tying, take rates | Proposed remedy filing or divestiture order |
| US v. Apple | Filed 2024, pending | App distribution, wallet and API access, cloud gaming | Scheduling order or motion to dismiss ruling |
| FTC v. Meta | Decided for Meta November 2025, FTC appealing | Acquisition strategy, messaging interoperability | Appellate outcome in 2026 or 2027 |
| Epic Games v. Apple | Injunction on external purchase links, 2025 | In-app commission assumptions | Appeal ruling and revised store guidelines |
Contract clauses to add now
- A regulatory-change clause that lets you reopen pricing and terms if a designated-platform obligation changes the service you bought, with a named notice period.
- A data portability clause that names the export format, the frequency, and the cost, and treats regulated portability rights as a floor rather than a ceiling.
- An interoperability commitment for identity, messaging, and calendar data, with a technical contact and a test window before renewal.
- An app distribution clause that separates store commission from your own subscription pricing, so a commission change does not reprice your product.
- A most-favored-customer clause scoped to the jurisdiction where the remedy applies, which is where the mandated terms will appear first.
What to do next
- Map every platform in your stack to a jurisdiction and a remedy. If you sell in Europe, the DMA applies to your vendor whether or not you are an EU company.
- Run one real export test per major platform this quarter. Measure the time, the format fidelity, and the egress bill, then put the result in the renewal file.
- Put the seven matters above on the same calendar as your renewals, with an owner for each.
- Ask each strategic vendor for its regulatory roadmap: which product changes are scheduled for compliance, and which markets get them first.
- Price the switching cost you would face if a remedy arrived tomorrow. If the answer is a multi-year migration, the remedy will not help you, and the contract needs to compensate.
Remedies are slow, partial, and uneven across jurisdictions. That is exactly why they belong in the procurement calendar rather than in a legal briefing. The team that knows which term is likely to be mandated, and when, negotiates from a different position than the team that reads about it after the fact.
