How one seller resolved DMA gatekeeper obligations and sellers

A UK-based marketplace seller receives an automated notice from Amazon. Listings are suppressed, the account dashboard shows degraded visibility, and no explanation is offered beyond a generic policy reference. The seller does not know whether this is a suspension, a ranking adjustment, or something triggered by the Digital Markets Act. The distinction matters – a great deal.

TL;DRThe Digital Markets Act (DMA) imposes specific obligations on Amazon as a designated gatekeeper, and those obligations create enforceable rights for sellers on Amazon UK. When a seller's listings are suppressed, account access is restricted, or terms are changed without adequate notice, the DMA's gatekeeper framework may offer procedural tools that standard Seller Central appeals do not. This case study walks through how one anonymized seller identified the DMA angle, built a structured challenge, and reached a resolution.

This account covers the situation as it presented, what was actually driving it, the strategy used, the realistic outcome, and the lesson for other Amazon UK sellers in similar circumstances. It is not a guarantee that the same result follows in every case – every account has a different history, and the applicable DMA obligations depend on how Amazon interprets its own gatekeeper compliance posture at the time. What it illustrates is the decision map: where the DMA fits, where it does not, and what to do at each junction.

What was the seller's situation on Amazon UK?

A consumer electronics accessories brand – a mid-market seller trading on Amazon UK for several years with a well-established product catalogue – noticed a sustained, unexplained decline in organic search placement over several weeks in winter 2026. The seller had not received any Account Health notification, had not violated any obvious policy, and had not changed its product listings in a material way. Sales dropped sharply. Advertising spend rose, but impressions declined in proportion.

The seller initially assumed this was an algorithm change. That assumption is common and usually correct. In this case, it was not the full picture. When the seller pulled its performance data more carefully, it found a pattern: the suppression coincided with an increase in placement for Amazon's own-brand electronics accessories in the same search result pages. This is a pattern that sits at the intersection of platform self-preferencing and the DMA's gatekeeper obligations.

Under the DMA, Amazon – as a designated gatekeeper for its online intermediation service – is required to treat goods and services provided by third-party sellers on the same terms as its own products or services when it comes to ranking. The operative prohibition is against self-preferencing: a gatekeeper may not rank its own products or services more favorably in a general ranking than competing products or services offered by third parties, unless the differential treatment is objectively justified. That is a paraphrase of the rule; the actual text of the DMA is the controlling source. The seller's data pattern suggested the differential was not incidental.

This is what the Digital Markets Act actually means in practice for an Amazon UK seller: it is not an abstract regulatory instrument. It is a rule that can be invoked when a platform's behavior – ranking, access, data, or terms – disadvantages a seller in ways that track the prohibited categories. Knowing that requires reading the account data against the regulatory categories, which most sellers do not have the background to do on their own.

What was really happening beneath the account data?

Identifying the surface pattern is only the first step. The harder question is whether the pattern reflects a gatekeeper-compliance failure, a legitimate algorithm update, an unannounced policy change, or a technical anomaly. Each of those possibilities calls for a different response. Conflating them is the most common error sellers make when they encounter unexplained visibility declines on Amazon UK under the current EU-influenced operating environment.

In matters we handle, the first task is to distinguish the DMA scenario from three look-alike scenarios that do not support a DMA challenge. The first look-alike is a standard performance-based ranking change: Amazon's algorithm legitimately rewards products with higher conversion rates, stronger review profiles, and better fulfillment metrics. A seller whose metrics have declined will see ranking fall without any DMA implication. The second look-alike is a policy-based suppression triggered by a compliance flag – an inauthentic complaint, a safety report, or a restricted product classification. That is handled through the standard appeal process, not a DMA procedure. The third is a technical error in Amazon's catalogue or search infrastructure, which Amazon's Seller Central support is the appropriate channel to address.

For this seller, none of those three explanations fully accounted for the data. The seller's metrics had not declined materially. No performance or policy notice had been issued. No catalogue error had been flagged. What remained was the self-preferencing hypothesis – and with it, the DMA's internal complaint-handling procedure became the relevant procedural path.

The Platform-to-Business (P2B) Regulation, which predates the DMA and remains operative for Amazon UK's treatment of its third-party sellers, adds a parallel layer. Under the P2B rules, Amazon is required to set out the main parameters determining ranking and their relative importance in its terms and conditions. Where a seller believes its ranking has been affected by undisclosed parameters, the P2B framework provides a basis to challenge the adequacy of Amazon's explanation. In this case, the seller had a compound position: a DMA self-preferencing concern and a P2B transparency concern running in parallel.

What strategy did the seller use, and where were the decision points?

The seller came to Tutamen after two internal escalations through Seller Central had produced no substantive response – a pattern we regularly see when the underlying issue has a regulatory dimension that standard seller support is not equipped to address. The first task was mapping the applicable obligations: which DMA articles were engaged, whether the DSA's statement-of-reasons mechanism applied, and how the P2B transparency requirement framed the ranking disclosure question.

The strategic structure had three components. First, we drafted a formal complaint to Amazon's internal complaint-handling system as required under the DMA. Gatekeepers are required to have an internal mechanism for handling such complaints, and submitting through that channel creates a formal record and imposes a response obligation on the platform. This is not the same as opening a Seller Central support case. It is a distinct procedural path, and using it correctly is the difference between a complaint that generates a substantive response and one that is absorbed by the general support queue.

Second, we constructed a parallel position under the P2B Regulation, requesting that Amazon confirm whether the ranking parameters applicable to this seller's category had been updated and, if so, in what way. This request was framed explicitly by reference to Amazon's P2B disclosure obligations. A platform that fails to respond adequately to a P2B-grounded transparency request is in a different position than one that simply does not answer a seller support ticket.

Third, we assessed the viability of a complaint to the European Commission or a relevant national competent authority. The DMA designates the Commission as the primary enforcement body for gatekeeper obligations, and national authorities may play a coordinating role depending on the matter. For a seller whose primary concern is account revenue, a regulatory complaint is rarely the fastest route to a commercial resolution – but it creates a backdrop that changes the platform's incentive to engage meaningfully with the internal complaint process. In matters of this type, we are transparent with sellers about that trade-off.

The decision point for this seller was whether to proceed with the internal DMA complaint alone, or to signal the regulatory-complaint option as part of the submission. We advised the latter. The seller's position was well-evidenced: a documented period of suppression, contemporaneous search data showing the competing Amazon-brand products' placement improvement, and a clean account history. That combination justifies a firmer approach.

For context on how the DMA's gatekeeper regime has reshaped the obligations Amazon faces on its UK platform, our analysis at Amazon as a Very Large Online Platform – what changed and what to do covers the framework in detail. For sellers who have encountered unexplained ranking changes and want to understand whether they have a P2B transparency argument alongside a DMA position, our resource on what to know about an unfair ranking complaint under EU rules sets out the key elements.

What was the outcome, and what remained uncertain?

Within several weeks of the formal DMA internal complaint submission, Amazon engaged through its seller compliance channel with a substantive response. The response did not concede a DMA violation – platforms rarely do, as a matter of practice – but it provided a specific explanation of the ranking parameters that had changed in the relevant category, acknowledged that the seller's account remained in good standing, and confirmed that no policy flag or enforcement action had been applied to the account.

That response mattered for two reasons. First, it gave the seller actionable information about what had changed – information the seller could use to adapt its listings and advertising approach in a way that the generic "algorithm change" framing never would have provided. Second, it documented, in the platform's own words, that the seller had not done anything wrong. That documentation has downstream value: if the visibility issue recurred, or if the seller later faced a compliance challenge that referenced the same period, the response letter would be part of the record.

Organic visibility improved in the weeks following the complaint resolution, though the seller's metrics had also been adjusted during the engagement period. We are careful not to attribute outcomes to specific filings where causation is genuinely unclear. What is accurate is that the seller had a record, a substantive response, and a clearer understanding of its regulatory position on Amazon UK going forward.

What remained uncertain: the DMA's enforcement architecture is still developing. The European Commission's formal investigations into Amazon's gatekeeper obligations are ongoing in a general sense, and the compliance posture of designated gatekeepers continues to evolve. A seller who uses the DMA's internal complaint mechanism in winter 2026 may find the process differs from what a seller encounters in 2026 or 2027, as the Commission issues further guidance and platforms update their compliance procedures. The durable lesson is not a specific procedure – it is the principle that the DMA creates formal procedural rights that sellers can invoke, and invoking them correctly changes the quality of the platform's response.

What does this mean for other Amazon UK sellers?

The lesson from this matter is not that every unexplained visibility decline on Amazon UK is a DMA violation waiting to be found. Most are not. The lesson is a more disciplined diagnostic question: before treating an unexplained ranking change, listing suppression, or term shift as purely an algorithmic or policy matter, an Amazon UK seller should ask whether the platform's conduct falls within the categories the DMA prohibits for designated gatekeepers.

Those categories are not trivial. They cover self-preferencing in ranking, preventing sellers from offering their goods or services on other platforms on better terms (parity obligations), using seller-generated data to compete with those sellers, and restricting sellers' ability to communicate with customers through channels outside the platform. Each of those prohibited behaviors has a counterpart in the commercial grievances we regularly see from Amazon UK sellers. The DMA does not resolve every grievance – but it does provide a procedural path that did not exist before gatekeeper designation.

The practical implications for sellers fall into three categories. First, documentation. The DMA's internal complaint mechanism works best when a seller has contemporaneous data: ranking screenshots, advertising performance records, search result captures, and a timeline. Sellers who suspect a self-preferencing issue should begin collecting that data as soon as the pattern emerges, not after they decide to pursue a formal complaint. Second, framing. A DMA complaint is not the same as a Seller Central support ticket, and drafting it correctly requires understanding which obligation is engaged and how the seller's specific facts map to the regulatory language. A poorly framed submission is treated as a general inquiry. Third, parallel tracks. The DMA internal complaint, the P2B transparency request, and the regulatory-complaint option are not mutually exclusive. Running them in a considered sequence – with each track designed to generate a record useful to the next – is a more effective approach than choosing one and ignoring the others.

For sellers who want a foundational understanding of the full EU regulatory environment before deciding on a strategy, EU marketplace regulation – the complete guide for sellers covers the DSA, DMA, P2B Regulation, and the practical steps that apply on Amazon UK and other designated platforms.

The fear that a suspension or suppression under EU rules is final – that once a platform acts, the seller has no lever to pull – is understandable but inaccurate. The DMA's gatekeeper obligations exist precisely because the EU legislator recognized that sellers on very large platforms lack the bargaining power to obtain fair treatment through ordinary commercial channels. Those obligations are enforceable. Using them effectively is a matter of knowing the process and building the record.

If you have faced a ranking suppression, term change, or restriction on Amazon UK that you cannot explain through standard account performance metrics, the question worth asking is whether the DMA applies. That assessment is where the analysis begins.

If a first escalation through Seller Central has already come back without a substantive answer, that is not the end of the road. In many of the matters we handle, the DMA and P2B tracks open precisely at the point where standard support channels have been exhausted. A second read of the account situation – with the regulatory overlay applied – can identify what is still available and what the realistic sequencing looks like.

To have your situation reviewed, email info@tutamenlaw.com. We review the account, identify which regulatory obligations apply, and provide a fixed fee quote before any work begins.

Related areas

• EU Marketplace Regulation – the DSA, DMA and P2B rules for Amazon and other EU platforms
• Amazon Account Suspension & Reinstatement – handling deactivation notices, Plans of Action, and appeal strategy

Frequently asked questions

How long does resolving DMA gatekeeper obligations and sellers usually take on Amazon UK?

The timeline depends heavily on which DMA mechanism is used and how quickly Amazon's internal compliance channel engages. A formal internal DMA complaint typically draws a substantive response within several weeks, though the period can extend if the matter is complex or the platform's compliance team requires additional information. If a parallel P2B transparency request is filed, that may run concurrently. Regulatory escalation to the European Commission or a national authority follows a longer, less predictable timeline measured in months. We tell sellers to plan for the internal process first and assess the regulatory track as a secondary option once the platform's initial response is in hand.

What are the main risks if I handle DMA gatekeeper obligations and sellers alone?

The primary risk is procedural mischaracterization: submitting what should be a formal DMA internal complaint through Seller Central's general support queue, where it is treated as a standard policy inquiry and generates no substantive record. A second risk is framing the complaint in terms that do not map to the specific DMA obligation engaged – a self-preferencing claim requires different evidence and legal framing than a P2B transparency request, and mixing them without clarity weakens both. A third risk is missing the parallel options: the P2B route, the DSA statement-of-reasons path, and the regulatory-complaint option each have distinct uses, and an unadvised seller often abandons the matter after a single channel fails without realizing others remain open.

Do I need a lawyer for DMA gatekeeper obligations and sellers?

Not in every case. A seller with a straightforward factual record and a clear grasp of which DMA obligation applies may be able to draft and submit an internal complaint without legal assistance. In practice, the assessment of which obligation applies – and whether the facts actually support a gatekeeper-compliance claim rather than a standard algorithm or policy issue – is the step where legal input makes the most difference. Attorney involvement also changes the platform's perception of the seriousness of the submission. Where the commercial stakes are meaningful and the account history is complex, the cost of legal guidance at the outset is typically lower than the cost of an unsuccessful unadvised submission that has used up the available procedural opportunities.

About Tutamen

Tutamen is an independent law firm for online marketplace sellers. We represent Amazon, Walmart, Etsy and eBay sellers in account deactivations, frozen-funds recovery, intellectual-property disputes, arbitration and Notices of Dispute, and US federal Schedule A defense, plus EU marketplace regulation. Our work is attorney-led and confidential, with fees quoted up front. We act for founders, brand owners and in-house teams who need a specialist for a marketplace dispute. Our EU practice is conducted in English and Russian on request, and for matters involving jurisdictions outside our direct coverage, we work with appropriate local counsel. To discuss your situation, email info@tutamenlaw.com.

Page authored by Dmitri Aronov, Partner, EU Marketplace Regulation, Tutamen.

Disclaimer: This article is general information, not legal advice, and does not create an attorney-client relationship. Marketplace policies and the law change, and every account and case is different. For advice on your situation, contact Tutamen at info@tutamenlaw.com.

Written by Dmitri Aronov, Partner – EU Marketplace Regulation. Published September 19, 2026.