Procedural annulment has a specific meaning in EU administrative law. It doesn’t
reach the merits. It doesn’t say the Commission was wrong to look at Marketplace
through a DMA lens. It says the Commission’s written reasoning, the formal record
supporting the designation decision, didn’t meet the standard the General Court
requires. The consequence is narrow and significant in equal measure: the designation
falls, the Commission’s underlying authority survives, and the re-designation clock
starts immediately.
That’s what happened in Case T-1078/23 (ECLI:EU:T:2026:357) on June 3, 2026.
What the court held, and what it didn’t.
The ruling issued a split decision. Facebook Marketplace lost its gatekeeper status. Facebook Messenger kept every obligation it had before the judgment. Two services,
one parent company, opposite outcomes from a single ruling.
The Marketplace annulment turns on Article 3 of the
Digital
Markets Act, which governs how the Commission designates a “core platform service”
as a gatekeeper. The Commission must establish, with documented reasoning, that the
service qualifies as a specific type of platform, in Marketplace’s case, an online
intermediation service. According to legal analysis of the ruling, the court found
the Commission erred by failing to adequately account for Meta’s pre-designation
operational changes that restricted commercial business use of Marketplace. Whether
those changes were sufficient to remove Marketplace from the DMA’s scope is a
question the court declined to answer. It only concluded the Commission hadn’t
addressed them properly.
The Messenger designation stands on different footing. The Commission’s reasoning for
Messenger, a number-active-user messaging platform with 45 million monthly users in
the EU, the threshold set by Article 3(2)(b), survived the court’s scrutiny. Messenger’s interoperability and data-sharing obligations under the DMA continue
without interruption.
The procedural annulment pattern.
T-1078/23 isn’t isolated. EU courts reviewing Commission technology decisions have
increasingly scrutinized the quality of institutional reasoning rather than simply
the statutory eligibility conclusions. The pattern is visible across DMA, DSA, and
GDPR enforcement challenges over 2024-2026: courts aren’t reliably rejecting the
Commission’s jurisdiction, they’re sending documents back for better justification.
This has a compounding effect. A procedural annulment doesn’t produce legal
uncertainty about whether the DMA applies. It produces certainty about the
documentation standard required to make it apply. Each annulment raises the
Commission’s drafting burden for subsequent designations, and raises the
evidentiary bar for challenges to those designations.
The Commission already knew Marketplace’s designation was under appeal. Legal teams
at designated platforms, and their counsel, have had time to study the General
Court’s approach to tech cases. T-1078/23 adds a specific, usable data point: the
court will examine whether the Commission adequately analyzed a platform’s
operational changes made before or during the designation process. That’s a new
discovery obligation for future designation investigations.
What Meta actually controls now, and what it doesn’t.
Timeline
The following comparison captures the practical state of play:
| | Facebook Marketplace | Facebook Messenger |
|—|—|—|
| Designation status | Annulled (T-1078/23) | Upheld (T-1078/23) |
| DMA obligations | Currently suspended | Fully active |
| Commission next step | May re-designate with corrected documentation | No action required |
| Timeline for re-designation | No regulatory minimum; Commission sets pace | N/A |
| Interoperability required | No (pending re-designation) | Yes, third-party API access |
| Data-sharing required | No (pending re-designation) | Yes |
| Self-preferencing rules | No (pending re-designation) | Yes |
Meta’s DMA compliance program now has an asymmetric structure. Messenger obligations
continue. Marketplace obligations pause. The business consequence isn’t trivial:
Marketplace operators, sellers, buyers, and advertisers using the platform, will
find themselves in a briefly different regulatory environment than Messenger users. The real question is whether the Commission moves quickly enough that the gap closes
before any substantive business changes can be made in response.
The designation timeline that brought us here.
The DMA gatekeeper designation process began in 2022, with the Commission formally
identifying Meta Platforms as a gatekeeper across multiple services in September 2023. Meta challenged the Marketplace designation in Case T-1078/23. The case moved through
the General Court’s standard timeline, with the June 3, 2026 ruling arriving
approximately 32 months after the original designation, consistent with the pace of
EU administrative litigation.
What matters for future planning is that designation challenges don’t produce
fast resolution. A platform that files a T-1078/23-style challenge today should
expect a 2.5-to-3-year litigation window. The DMA obligations that apply during that
window are not paused by the challenge, they continue until a court actually annuls
them. Meta’s experience is instructive: Messenger obligations ran throughout the
appeals period, and will continue running now.
What other designated platforms are watching.
Apple, Google, Amazon, and Microsoft each hold DMA gatekeeper designations covering
specific core platform services. Legal teams at those companies are studying T-1078/23
for two purposes. First, to assess whether any of their existing designations have
analogous documentation gaps, pre-designation operational changes that the Commission
may not have adequately analyzed. Second, to calibrate the re-designation risk: if
they succeed in a procedural annulment, how quickly and how thoroughly can the
Commission repair the record?
The answer to the second question is “faster than the first challenge.” The Commission
now has a specific roadmap for what the General Court requires. A re-designation of
Marketplace, if pursued, will likely be documentarily thorough enough to survive
another annulment challenge on the same grounds. Designated platforms that succeed
procedurally once shouldn’t model the same strategy working twice.
DMA Compliance Review: Post-T-1078/23 Checklist
- Map designation records against pre-designation operational changes, verify Commission addressed them explicitly
- Confirm Messenger-type obligation implementation timelines are unaffected by Marketplace ruling
- Model re-designation speed scenario, assume 12-18 month corrected filing window
- Assess whether your organization approaches Article 3(2)(b) 45M MAU threshold, calibrate designation timing risk
Warning
A procedural win in T-1078/23 doesn't mean the same strategy works twice. The Commission now has the court's documentation standard in writing. The next Marketplace designation will address pre-designation operational changes directly. Platforms modeling a repeat procedural challenge should build their scenario around a substantive ruling, not a second procedural annulment.
What compliance teams should assess.
For teams at DMA-designated organizations, or organizations approaching the
Article
3(2)(b) thresholds, T-1078/23 creates three concrete review items:
First, map your designation records against the pre-designation operational change
issue. If your organization made service modifications before or during the
Commission’s designation investigation, verify that the Commission’s designation
decision explicitly addressed those changes. If it didn’t, you have a documented
annulment ground.
Second, reassess your interoperability and data-sharing implementation timelines. Messenger’s obligations continue, which means the technical implementation deadlines
aren’t affected by the ruling. Don’t let the Marketplace outcome create false
confidence about Messenger-type obligations at your organization.
Third, model re-designation speed. If you’re pursuing or considering a designation
challenge, build a scenario that assumes the Commission files a corrected designation
within 12-18 months of any annulment. The pause in obligations during re-designation
may be shorter than the litigation that produced it.
TJS synthesis.
The EU General Court has done something specific and limited in T-1078/23. It
established that DMA gatekeeper designations are legally vulnerable when the
Commission’s documentation doesn’t fully engage with a platform’s pre-designation
operational changes. That vulnerability is real, and it’s testable. What it isn’t is
a signal that the DMA’s substantive reach is contracting. The Commission will
re-designate Marketplace. The documentation will be thorough. The outcome, whether
Marketplace ultimately qualifies as a gatekeeper, will be decided on the merits,
probably before 2028. What’s already decided is the process standard that will govern
every designation the Commission issues from this point forward. Legal teams that
treat T-1078/23 as a strategic opening should also read it as a closing: the
procedural gap the court identified won’t exist in the next designation decision.