SAP Antitrust Decision: What It Means for Third-Party Support

Go straight to an AI summary of this blog post instead

In July 2026, the European Commission closed its SAP antitrust investigation by making a set of commitments legally binding. Among other commitments, SAP will abolish the reinstatement fees it charged customers who left maintenance and later wanted to come back, cap back-maintenance fees at the lower of six months’ fees or half the fees for the period away, and clarify the conditions under which on-premises ERP customers can split their estate into separate installations served by different support providers, by SAP at different levels, or by no one at all..

For anyone who has spent years watching enterprise software customers weigh the cost of staying against the cost of leaving, this SAP antitrust decision is worth reading closely. Even if it changes nothing in anyone’s contract outside SAP’s customer base, it matters anyway, because of what the Commission chose to treat as a competition problem.

What the European Commission’s Decision Actually Is

Precision matters here. The Commission accepted SAP’s commitments under Article 9 of Regulation 1/2003. That procedure closes a case without deciding whether the company broke the law. There is no infringement finding. SAP admitted no wrongdoing. The commitments bind SAP alone, and only in the aftermarket for maintenance and support of its on-premises ERP software.

So this is not a precedent that customers of other vendors can invoke as a right. If another software company charges reinstatement fees today, it can keep charging them tomorrow. Nothing in this decision obliges any other vendor to change a single line of its price list. A customer who wants the same relief enforced against a different vendor would need to file a complaint and wait for a separate investigation, or take the vendor to court and prove the case from scratch.

A decision doesn’t need binding effect on other vendors to be useful at the negotiating table, though. The Commission has now put on record which fee structures raised serious enough competition concerns that it required binding commitments to remove them, and it did so with the largest software company in Europe.

A procurement team renegotiating support terms can put the decision in front of a vendor and ask why a fee SAP has now committed to abolishing should survive in their contract. The vendor is free to say no. But reinstatement fees are already negotiable in practice at some vendors, and a documented regulatory position strengthens the customer’s hand in a conversation that was always about leverage rather than law.

Why It Matters Beyond the Negotiating Table

The Commission examined the market for keeping installed software running, the maintenance and support aftermarket, and concluded that contract terms that restrict a customer’s choice of support provider can harm competition. It identified specific mechanisms: terms that kept customers paying maintenance on licenses they no longer used, fees that made returning punitive, initial support terms that restarted with every additional license purchase, and all-or-nothing rules that forced customers to take the same SAP support across their whole estate.

Teresa Ribera, the Commission’s Executive Vice-President overseeing competition policy, said the decision gives SAP customers “more freedom to choose maintenance and support services without unfair restrictions that raised their costs and stifled competition.” She also placed the decision in a wider context: she called the commitments a benchmark for the industry more broadly, said they should serve as a warning against similar practices in the cloud markets where customers are increasingly moving, and warned that dominant firms should not abuse their power to lock in users at the expense of choice and innovation.

Read that as a statement of principle. A regulator examined third-party support, the business of maintaining software that the original vendor would rather you paid them to maintain or upgrade away from, and treated it as something competition law should protect, not as a gray market. Third-party support providers for SAP environments pressed this argument for years. The Commission agreed with enough of it to extract binding commitments.

The Pattern Is Bigger Than SAP

Reinstatement fees are not a SAP invention. Among some of the major enterprise Linux vendors, published support policies include reinstatement charges for lapsed support, retroactive payment for periods a system kept running unsubscribed, or both. The same category of exit barrier the Commission just made SAP dismantle remains in force elsewhere.

What these fees do is straightforward, and it’s the Commission’s own reasoning: when leaving support is priced punitively on the way back in, customers stop considering alternatives at all. The independent option can be better and cheaper, and the re-entry math still kills it before evaluation starts. Fees that in some cases matched what customers would have paid by staying made the freedom to leave theoretical. The vendor sets the terms under which you’re allowed to keep running what you already own.

For Linux infrastructure, the moment this matters most is a familiar one. When a distribution or runtime reaches end of life, standard vendor coverage ends, and a decision is due: upgrade now, buy the vendor’s extended support where offered, or keep the system running with an independent third-party support provider. EOL itself is a normal lifecycle event. The question the SAP case puts on the table is whether that decision gets made on the merits, or under fee structures designed to make every path but one irrational.

What to Take From This if You Run Linux Infrastructure

Not new legal rights. Your contracts are the same as they were in June.

But two things did change. First, the posture question: the SAP case confirms that support choice is a market, that regulators are willing to examine it, and that third-party maintenance is a legitimate, pro-competitive option rather than a workaround. If your organization has treated vendor support as the only defensible choice, the ground for that assumption is thinner than it was. Second, the negotiation file: the next time a renewal conversation turns to vendor lock-in terms like reinstatement charges or back-maintenance fees, there is now an EU decision to point to that names those exact structures as competition concerns.

At TuxCare, we’ve built our Endless Lifecycle Support business on a principle closely related to the one the Commission just defended: that the choice of who maintains your software, and for how long, should belong to the people running it rather than to the vendor’s release calendar. When an enterprise Linux distribution, language runtime, or open source library reaches end of life, ELS continues to deliver security patches for as long as it remains in your stack, without dictating your upgrade deadline.

So even if the EU didn’t hand anyone that choice last week, it did confirm the choice deserves to exist.

Summary