Brussels — European competition authorities have accelerated scrutiny of bundling, API restrictions and marketplace rules among major software‑as‑a‑service (SaaS) providers. As of October 2026, the inquiry that began in mid‑2026 has broadened in scope: regulators are now explicitly examining algorithmic promotion in vendor app stores, differential API throttling, and contract terms tied to identity and data services that raise switching costs.

Why this matters now (Who, What, When, Where, Why)

Who: European Commission competition teams, national authorities (including Germany's Bundeskartellamt and France's Autorité de la concurrence) and some member‑state digital regulators.

What: Formal information requests, multi‑jurisdictional coordination and market mapping focused on dominant CRM, collaboration and enterprise productivity suites.

When: The probe accelerated in the second half of 2026 with coordinated evidence requests issued between June and September 2026; follow‑up examinations continue in October 2026.

Where: EU27 jurisdictions, with cross‑border effects for multinational customers and ISVs.

Why: Regulators say persistent technical and contractual lock‑in in CRM and collaboration stacks can foreclose rivals across adjacent markets (analytics, vertical apps, identity services) and limit choice for enterprise customers.

Context: how the inquiry has evolved since July 2026

The original July 2026 inquiry focused on tied sales, API access, and marketplace rules. Since then, authorities have added three concrete focal points:

  • App‑store algorithms: investigators are reviewing whether ranking and featured placement favor first‑party integrations.
  • Identity and single‑sign‑on (SSO) gating: whether control of identity primitives is used to degrade third‑party interoperability.
  • Commercial metadata and telemetry: whether vendors limit the flow of usage data that third‑party ISVs need to operate effectively.

These additions reflect a broader European enforcement trend: regulators are treating platform design and algorithmic choices as potential instruments of foreclosure, not just traditional pricing and contract clauses.

Fresh data and market signals

SaaS Review Hub surveyed 420 enterprise buyers, platform engineers and ISV product leads between 15 August and 30 September 2026. Key findings:

  • 67% of respondents said they had encountered API rate limits or marketplace rules they considered “incompatible with enterprise interoperability” in the previous 12 months.
  • 54% reported that switching a major CRM or collaboration provider would require at least 12 months of engineering work and an average estimated cost of €420,000.
  • 39% of ISVs said platform app stores account for more than 40% of their new customer acquisition, amplifying dependency concerns.

These figures help explain regulators’ focus: even partial restrictions on API access or app‑store discoverability materially affect competition and customer choice.

Examples and real‑world context

Market debates have centered on widely used suites that combine identity, messaging, storage and CRM primitives. Vendors commonly cited in filings by customers and some competitors include large incumbents in CRM and collaboration spaces; regulators have not publicly named enforcement targets in all jurisdictions. What is clear from filings: complaints often hinge less on price and more on lost engineering access, asymmetric access tiers, and opaque promotion criteria for third‑party apps.

Regulatory tools and likely outcomes

Investigations proceed under traditional competition law and by reference to Digital Markets Act (DMA) obligations where gatekeeper status applies. Practical enforcement tools available to authorities include:

  • Information requests and dawn raids (document collection and interviews).
  • Interim non‑discrimination orders requiring parity for third‑party integrations.
  • Binding commitments forcing API changes, standardized documentation, or clearer marketplace governance.

Based on the pace of filings and commitments elsewhere in digital markets, companies can reasonably expect preliminary findings or negotiated commitments within 6–12 months after intensive information exchange; full resolutions—appeals or structural remedies—can take longer.

Immediate implications for vendors

Vendors who are or could be perceived as dominant should assume higher compliance costs and reputational scrutiny. Practical steps we found being implemented in Q3–Q4 2026:

  • Publishing an explicit API‑governance policy that details rate limits, commercial tiers and security requirements.
  • Implementing standardized developer SLAs and a transparent app‑store algorithm and ranking methodology.
  • Offering machine‑readable data export endpoints and “export first” bulk downloads to reduce switching friction.
  • Creating a cross‑functional regulatory playbook (legal, product, platform engineering) to respond to information requests within regulator timelines.

What this means for customers and ISVs

Customers and independent software vendors stand to gain from enforced parity and clearer interoperability rules: lower integration costs, predictable app‑store economics and improved portability. But change brings disruption: some vendors are trimming proprietary connectors and reworking revenue‑share models, which can temporarily reduce marketplace availability.

Procurement and engineering teams should prioritize: contract exit clauses, verified data export checks, and staged migration trials to validate migration timelines and costs before renewing multi‑year commitments.

Updated recommendations — practical checklist for October 2026

  • Conduct a “switchability” audit quantifying data volumes, API dependencies, SSO/identity bindings and third‑party app reliance.
  • Require vendors to demonstrate export capabilities via a signed technical runbook and sample export within 30 days.
  • Negotiate express commitments on API parity and non‑discrimination in marketplace promotion.
  • Adopt open standards where possible (SCIM for identity, OpenAPI for interface docs, CSV/JSON schema for bulk export).
  • For ISVs: diversify distribution channels beyond proprietary app stores and log acquisition attribution to measure platform dependency.

Impact and what to watch next

The inquiry is reshaping expectations for platform openness. Watch for:

  • Regulatory commitments or interim measures announced by DG COMP and national authorities in late 2026.
  • New industry standards or interoperability consortia forming to reduce litigation risk and set baseline technical specs.
  • Vendor product changes—published API roadmaps and marketplace policy updates—over the next 90–180 days.

Reactions

Industry groups and ISV associations have offered mixed responses: many welcome clearer rules that level the playing field, while some vendor trade bodies warn that rushed mandates could undermine security or user experience. Customers generally favor better portability and clearer marketplace transparency; procurement teams we surveyed want legally binding guarantees rather than voluntary promises.

FAQ — Common questions right now

How long will a regulatory probe like this take to resolve?

Expect intensive evidence‑gathering for 6–12 months after a formal inquiry begins, with possible negotiated commitments in that window. Final remedies, appeals or structural options can extend the process for multiple years.

Will regulators force vendors to open all APIs?

Regulators typically aim for proportional remedies: they require access that restores competition and consumer choice while allowing vendors to retain legitimate security‑sensitive controls. Absolute “open all” mandates are rare; expect defined scopes, authentication standards and rate limits.

What immediate steps should procurement teams take?

Run a switchability audit, demand technical export tests, and include express interoperability and non‑discrimination clauses in renewal negotiations. Staged migration trials reduce surprise costs if relationships change.

Should ISVs wait to engage platforms until regulators finish their work?

No. ISVs should diversify distribution and document any discriminatory behavior now—time‑stamped communications and performance logs strengthen regulatory submissions and commercial negotiations.

SaaS Review Hub will continue tracking filings, regulatory notices and vendor responses through October–December 2026 and will publish examples of published commitments and technical templates as they become available.