How to handle Bundeskartellamt proceedings and sellers

For an Amazon ES seller, the moment a suspension notice arrives citing EU regulatory concerns is rarely the moment the trouble began. By then, a proceeding or complaint process has usually been building in the background – and the window to shape the outcome is already narrowing. This guide sets out the exact step sequence for handling the intersection of Bundeskartellamt proceedings and marketplace-seller obligations, explains where the process typically goes wrong, and identifies the decision points that matter most.

TL;DRBundeskartellamt proceedings relevant to Amazon sellers arise from Germany's Federal Cartel Office exercising authority over Amazon as a gatekeeper platform, with its findings directly informing how Amazon structures its terms across EU surfaces, including Amazon ES. Sellers are not parties to those proceedings, but they are directly affected when Amazon adjusts its policies, listing rules, or suspension procedures in response to regulatory pressure. The practical question is not how to intervene in the authority's process – it is how to use the rights those proceedings have generated, and the P2B Regulation, the Digital Services Act (DSA), and the Digital Markets Act (DMA), to defend your account and trading position on Amazon ES.

This guide moves through six steps: understanding what Bundeskartellamt findings mean for your account; reading the suspension or restriction notice correctly; building the internal-complaint and statement-of-reasons response; deciding whether to escalate under P2B or the DSA; managing the Amazon ES account timeline; and knowing when to involve counsel. At each step, the most common failure points are flagged.

Step 1: What does "Bundeskartellamt proceedings" actually mean for an Amazon ES seller?

The Bundeskartellamt's proceedings against Amazon are not abstract regulatory events – they produce concrete changes to the rules Amazon applies across its European surfaces, and Amazon ES is one of those surfaces. Germany's Federal Cartel Office has authority under Section 19a of the German Competition Act (GWB) to designate undertakings of paramount cross-market significance and to impose behavioral obligations on them. Amazon has operated under that designation. The direct consequence for sellers is that Amazon has modified certain terms – around parity obligations, Buy Box mechanics, and seller data use – as a result of undertakings made to or imposed by the authority.

Why does this matter to you as an Amazon ES seller? Because any suspension, restriction, or delisting that your account now faces occurs against a regulatory backdrop where Amazon's own room to act unilaterally has been formally constrained. That constraint does not guarantee you a favorable outcome. What it does is give you a legal vocabulary and a set of procedural levers that did not exist before those proceedings concluded. In matters we handle, sellers often arrive not knowing that these levers exist – they treat the suspension as if it were a standard Account Health issue, and they miss the arguments that the regulatory record supports.

The first step is therefore conceptual: separate the Bundeskartellamt proceedings as a background fact from the immediate problem on your account. The proceedings set the regulatory environment. Your job is to use the rights that environment creates – under the P2B Regulation, the DSA's statement-of-reasons requirement, and the DMA's gatekeeper obligations – in the specific appeal or complaint you are filing now.

A practical illustration: a consumer-electronics distributor selling on Amazon ES (winter 2025) received a listing restriction citing a pricing-parity concern. The seller assumed this was a standard repricing flag. In fact, the restriction touched directly on a category of parity obligation that the Bundeskartellamt proceedings had addressed. Reconstructing that connection – and invoking the seller's DSA and P2B rights in the response – changed the framing of the appeal from a routine Account Health submission to a rights-based complaint. The listing restriction was reviewed on a different track. This is the kind of context that a generic Plan of Action template will not surface.

For a fuller account of how EU regulatory instruments interact with platform enforcement, see EU Marketplace Regulation: The Complete Guide for Sellers, which maps the full legislative environment across the DSA, DMA, and P2B Regulation.

Step 2: How do you read the suspension or restriction notice correctly?

The notice Amazon sends when it restricts or suspends an account on Amazon ES is the single most important document in the process, and it is routinely misread. Amazon's automated enforcement system generates notices that use standardized policy language. The seller's instinct is to focus on the label – "policy violation," "inauthentic," "used sold as new" – and draft a response to that label. That instinct is almost always wrong.

What the notice actually contains – when read closely – is a combination of elements: the stated policy basis; the specific listings or ASINs involved; sometimes a timestamp; and a reference (often implicit) to the mechanism Amazon used to trigger the action. Under the DSA, Amazon as a Very Large Online Platform (VLOP) is required to provide sellers with a statement of reasons for restrictions and delistings. That statement of reasons may be embedded in the notice or available through a separate channel in Seller Central. If it is not present, that omission is itself a procedural lever.

When we review notices in matters involving EU surfaces, the most common misreading is treating a policy-level description as a factual finding. Amazon's notice may say "counterfeit concern" – but what triggered that notice may have been a third-party IP complaint, an automated quality signal, or a buyer-return pattern. Those are three different root causes, and they require three different responses. Conflating them produces a response that addresses none of them effectively.

Checklist for reading the notice:

• Identify the specific policy provision cited – and locate its published text in the Amazon Services Business Solutions Agreement (BSA) or the Amazon Services Europe Business Solutions Agreement as applicable.
• Identify whether the trigger was a seller-performance metric, a rights-owner complaint, an automated algorithm flag, or a buyer report.
• Check whether the notice constitutes a statement of reasons under DSA Article 17 obligations or whether you need to request one separately.
• Note the response deadline stated in the notice – and note whether that deadline is a hard cutoff or a guideline for internal-complaint purposes.
• Check the Account Health dashboard in Seller Central for any parallel flags or open actions that may compound the restriction.

Where this commonly goes wrong: sellers focus on the headline violation and write a detailed rebuttal of that label. Amazon's review system is not evaluating your rebuttal of their characterization – it is looking for evidence that the root cause has been identified and addressed. A response that argues "we do not sell counterfeits" without identifying what actually triggered the notice will be rejected, often automatically.

Step 3: How do you build the internal-complaint and statement-of-reasons response?

The P2B Regulation requires Amazon to maintain an internal complaint-handling system for business users on its EU platforms, including Amazon ES. The DSA adds the statement-of-reasons requirement for content restrictions. Together, these instruments give a suspended Amazon ES seller two distinct procedural rights: the right to a written explanation of the restriction, and the right to have a complaint reviewed through a process that Amazon must maintain and report on. Using both – in the right sequence – is the core of an effective EU-grounded response.

Step 3a: Request or confirm the statement of reasons. If the suspension notice does not contain a clear statement of reasons identifying the specific content or behavior at issue and the legal or policy basis for the restriction, submit a written request through Seller Central's appeal channel referencing the DSA's statement-of-reasons obligation. Do this before drafting any substantive response. Why? Because the statement of reasons may reveal information – a specific ASIN, a complaint reference, an algorithm trigger – that changes your entire response strategy. Filing a full appeal before receiving this information is working blind.

Step 3b: Draft the internal complaint using the P2B framework. Your internal complaint to Amazon's complaint-handling system should be structured around three components: (1) a clear identification of the restriction and its claimed policy basis; (2) a factual account of the root cause as you understand it, with supporting evidence – invoices, authorization letters, quality-control records, correspondence; (3) an explicit reference to your rights as a business user under the P2B Regulation and, where applicable, under the DSA. The complaint does not need to be long. It needs to be precise, evidence-backed, and rights-anchored.

Step 3c: Preserve the evidentiary record. Every communication, every Seller Central notification, every ASIN-level flag – screenshot and timestamp them immediately. Amazon's Seller Central interfaces are dynamic; information visible today may not be accessible in the same form later. This documentation is not just for Amazon's complaint process. If the matter escalates to a regulatory body or to formal dispute resolution, the record of what Amazon communicated – and when – is material.

Where this goes wrong: sellers submit a Plan of Action (POA) written for the US Seller Central model – root cause, corrective action, preventive measures – without anchoring it in the EU regulatory rights framework. The POA format is not wrong, but in an EU context it should be supplemented with explicit P2B and DSA references. In our practice, the failure to use this layer is the single most common reason that otherwise well-evidenced responses are rejected at the internal-complaint stage.

Step 4: Should you escalate under the P2B Regulation or the DSA?

Escalation beyond Amazon's internal complaint system is a real option under EU law – and it is the option that most sellers do not know they have. The P2B Regulation allows business users to bring complaints about non-compliant platform behavior to competent national authorities. The DSA creates supervisory mechanisms for Very Large Online Platforms, with the European Commission as lead supervisor for designated VLOPs. The DMA creates separate obligations for gatekeepers, with potential for Commission intervention in specific behavioral domains. None of these routes is fast, and none guarantees a specific outcome for an individual seller. But they create leverage.

The decision to escalate is not binary. The more useful question is: does the threat of escalation – formally signaled in your internal complaint – change Amazon's incentive to review your case more carefully? In matters we handle involving EU surfaces, the answer is often yes. A complaint that explicitly flags a potential DSA compliance issue, or a potential P2B systemic-non-compliance concern, is treated differently from a standard Seller Central appeal. It moves from the automated review queue toward human review.

Escalation also has costs. Filing a complaint with a national authority or the Commission takes time, requires documentation in the appropriate language and format, and does not pause your account restriction in the interim. The decision matrix here is practical:

• If the suspension is clearly a standard performance-metric issue with no EU regulatory dimension – a POA through Seller Central is the right primary route.
• If the notice touches on parity obligations, data access, ranking, or Buy Box visibility in ways that connect to Bundeskartellamt or DMA findings – a DSA/P2B-framed complaint is appropriate, and the threat of regulatory escalation should be explicit in your filing.
• If Amazon has failed to provide a statement of reasons or has failed to respond to an internal complaint within the timeframe its own policies require – a formal P2B complaint to the relevant national authority is a proportionate response.
• If the DMA's gatekeeper obligations are implicated – access to data, interoperability, self-preferencing – Commission-level escalation may be appropriate, typically as part of a coordinated strategy rather than a first step.

For a detailed comparison of how escalation paths differ between EU and US enforcement contexts, EU versus US enforcement differences: what it means for marketplace sellers sets out the structural contrasts that affect your strategy.

Step 5: How do you manage the Amazon ES account timeline while the process runs?

Regulatory and complaint processes take time. A Seller Central appeal cycle can span days to several weeks. A P2B formal complaint to a national authority runs longer. Commission-level DMA proceedings are measured in months to years. Meanwhile, your Amazon ES account is suspended or restricted, your FBA inventory may be accumulating fees, and your cash flow is affected. Managing the account timeline in parallel with the legal process is not an afterthought – it is an operational necessity.

Practical timeline management steps:

• File the strongest possible internal complaint first, as quickly as the evidence permits. Every day the account is restricted is a commercial loss. Speed matters – but not at the expense of the substance of the complaint. A weak first filing that is rejected narrows the options for a second filing.
• If FBA inventory is affected, monitor removal-order and reimbursement windows actively. Amazon's reserve and reimbursement policies have time-sensitive components, and a suspended account can incur storage fees on inventory you cannot sell.
• If the restriction is on specific ASINs rather than the whole account, identify whether you can continue trading on unaffected listings while the complaint runs. A partial restriction is not an account suspension – but conflating the two wastes the window on unaffected inventory.
• Keep your Amazon ES account compliant on all other dimensions during the process. An unrelated performance metric violation arising while a regulatory complaint is pending can give Amazon grounds to escalate the restriction to a full suspension. In matters we handle, we regularly see sellers allow secondary compliance issues to develop during a primary appeal, inadvertently undermining their position.
• Document the commercial impact. If the matter eventually involves a formal claim or regulatory complaint, evidence of the business harm – lost revenue periods, canceled orders, supply-chain disruption – strengthens the record. It also demonstrates that the restriction has concrete consequences proportionate to the rights-based arguments you are making.

Where this goes wrong: the seller treats the account timeline and the legal process as sequential rather than parallel. They wait for the appeal to resolve before addressing inventory, or they delay filing the complaint while trying to manage stock. The two tracks must run simultaneously. We work with sellers to map both tracks from the first day of engagement so that neither is allowed to undermine the other.

Step 6: When should you involve a lawyer – and what should they actually do?

A suspension under EU rules can look final, and the appeal path is far less clearly signposted than the standard Seller Central reinstatement process. That opacity is itself a commercial risk: sellers who do not know the EU regulatory levers available to them simply do not use them. The myth that EU sellers have no leverage once a platform suspends them is exactly wrong. The DSA, the P2B Regulation, and the regulatory record created by Bundeskartellamt proceedings give EU sellers a more developed rights framework than exists in the US context.

When is legal involvement clearly justified? If the suspension notice is ambiguous about its root cause; if you have already filed one internal complaint and been rejected; if the restriction touches on pricing, ranking, data access, or Buy Box mechanics in ways that connect to regulatory proceedings; or if you are considering formal escalation to a national authority or the Commission – in all of these situations, attorney involvement adds structure to a process where the procedural missteps are costly. The cost of a rejected first appeal is not just the time to refile. It is the narrowing of the evidentiary record and the reinforcement of Amazon's initial characterization of the problem.

What a specialist should actually do in these matters: review the deactivation or restriction notice and identify the true trigger; map the account history against the claimed policy basis; draft a rights-anchored internal complaint using the EU regulatory vocabulary the situation warrants; advise on whether escalation is proportionate and strategically timed; and, if necessary, build the statement-of-reasons and DSA/P2B case that goes beyond Seller Central. We also assess whether the Bundeskartellamt proceedings record supports any specific argument about Amazon's obligations toward your category or listing type.

A second illustration from our practice: a fashion-accessories seller on Amazon ES (spring 2026) had already submitted two standard Seller Central appeals after a Section 3-equivalent deactivation. Both were rejected. When we reviewed the account, the original trigger was a pricing-parity signal that directly intersected with the category of obligations Amazon had agreed to modify under regulatory pressure. The prior appeals had addressed the wrong root cause entirely. We reconstructed the complaint on the correct basis, invoked the P2B internal-complaint procedure formally, and the account was reviewed on its actual merits. The seller had not run out of options – they had been using the wrong process.

The steps above describe the standard path through a Bundeskartellamt-connected Amazon ES matter. Where your situation turns is on the specific language of the notice, the trigger type, the account history, and whether a prior appeal has already been filed – all of which we review first. If you are at an early stage and want to understand which procedural track fits your situation, email info@tutamenlaw.com for a short preliminary review before committing to a response strategy.

For practical guidance on appealing an EU delisting step by step, including the specific documentation standards Amazon ES applies, see How to handle appealing an EU delisting: a step-by-step guide on Amazon DE, which covers the core procedural sequence in detail.

Where the process commonly breaks down: the five failure points

Sellers handling EU marketplace proceedings alone encounter the same failure patterns repeatedly. Knowing them in advance is a structural advantage.

Failure point 1: Treating the EU process as a US Seller Central appeal. The Plan of Action format is familiar, and the temptation to adapt a US-format POA for an EU restriction is understandable. But the EU regulatory levers – DSA statement-of-reasons, P2B complaint, DMA gatekeeper arguments – do not appear in a standard POA template. Using one without the EU layer leaves the strongest available arguments unused.

Failure point 2: Filing fast and thin. Speed matters, but a thin first filing that is rejected does more damage than a slightly slower, evidence-backed filing that addresses the actual root cause. Amazon's internal complaint system is not infinitely patient with repeated resubmissions. In our experience, a well-constructed first filing is materially more likely to produce a substantive review than two or three inadequate resubmissions.

Failure point 3: Not requesting the statement of reasons before filing. As noted in Step 3, the statement of reasons may contain information that changes your entire strategy. Filing before requesting it – or before reading it carefully – is the single most correctable error in EU marketplace proceedings.

Failure point 4: Ignoring the commercial timeline. The legal process takes time. Sellers who do not actively manage their inventory, their reserve position, and their secondary compliance obligations during that period often arrive at a successful appeal only to find that the commercial damage has compounded. Both tracks – legal and operational – must run in parallel.

Failure point 5: Assuming that a second rejection means the account is gone. It does not. EU regulatory law creates escalation paths that exist entirely outside Amazon's own internal review system. A formal P2B complaint to a national authority, or a DSA supervisory complaint, can create pressure that reopens a matter after Amazon's internal process has concluded unfavorably. The myth that sellers have no leverage is false – but accessing that leverage requires knowing it exists.

If a first appeal or internal complaint has already come back rejected, a second read of the record often identifies the specific point where the argument failed and what remains open. To discuss whether your situation has an untried angle, contact Tutamen at info@tutamenlaw.com.

Your decision points and trade-offs at a glance

Every Amazon ES seller facing a Bundeskartellamt-connected restriction arrives at the same three decision points, and the trade-offs at each are concrete.

Decision 1: Standard POA vs. rights-anchored EU complaint. A standard POA is faster to file and familiar to Amazon's review teams. A rights-anchored EU complaint takes longer to construct and routes through a different review channel. The trade-off: if the restriction has an EU regulatory dimension – pricing parity, data access, ranking, Buy Box – the rights-anchored route is more likely to produce a substantive review, but it requires legal vocabulary that most sellers do not have.

Decision 2: Internal complaint only vs. escalation signal. Filing an internal complaint without signaling potential escalation is the lower-risk, lower-impact option. Explicitly flagging potential DSA or P2B non-compliance in the complaint is higher-effort but changes the incentive structure for Amazon's review team. The trade-off: escalation signals should be genuine and well-grounded. An unfounded escalation threat damages credibility. A well-evidenced one commands attention.

Decision 3: Self-represent vs. instruct counsel. Self-representation is free and may be sufficient for a straightforward, clearly triggered restriction with obvious corrective steps. Attorney involvement is warranted when the trigger is unclear, when a prior appeal has failed, or when the EU regulatory dimension is significant. The trade-off is fee cost against the cost of a protracted restriction or a lost account. In matters we handle, the analysis typically shows that the cost of a prolonged restriction materially exceeds the cost of specialist engagement.

Related areas

• EU Marketplace Regulation – full practice hub for EU and UK marketplace legal issues affecting sellers
• EU Marketplace Regulation: The Complete Guide for Sellers – DSA, DMA, P2B, and GPSR mapped for business users

Frequently asked questions

How long does resolving Bundeskartellamt proceedings and sellers usually take on Amazon ES?

The timeline depends heavily on which layer of the process you are in. An Amazon ES internal complaint through Seller Central typically runs from several days to several weeks, depending on the complexity of the matter and whether Amazon routes it through automated or human review. Formal escalation under the P2B Regulation to a national authority takes considerably longer – often several months before any authority response. DMA proceedings at Commission level are measured in years. For most sellers, the internal complaint path, well-constructed, remains the fastest viable route. A strong first filing materially reduces the time compared to a sequence of weak filings and resubmissions.

What are the main risks if I handle Bundeskartellamt proceedings and sellers alone?

The main risks are procedural rather than legal in the narrow sense. First, using the wrong appeal format – a US-style Plan of Action without EU regulatory anchoring – means the strongest available arguments are never made. Second, filing before obtaining the statement of reasons means you may be responding to the wrong trigger entirely. Third, failing to manage the account timeline in parallel with the appeal means commercial damage accumulates. Fourth, not knowing that escalation paths exist beyond Amazon's internal system means you may accept a rejection as final when it is not. None of these errors is fatal in isolation, but together they can convert a recoverable situation into a genuinely closed one.

Do I need a lawyer for Bundeskartellamt proceedings and sellers?

Not in every case. A seller with a clear, single-trigger restriction, strong supporting documentation, and familiarity with the EU complaint framework may handle the internal complaint stage effectively without legal support. Legal involvement becomes clearly warranted when the restriction trigger is ambiguous, when a prior appeal has already been rejected, when the matter touches on pricing parity, data access, or Buy Box visibility in ways that connect to regulatory findings, or when formal P2B or DSA escalation is under consideration. In those situations, the EU regulatory vocabulary and procedural architecture are complex enough that the marginal cost of attorney involvement is typically justified by the risk of misusing the available levers.

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. Every matter is handled with direct attorney oversight, and engagements are fully confidential from the first contact. To discuss your situation, email info@tutamenlaw.com.

This page was written by Priya Raman, IP & Brand Registry analyst at Tutamen, whose practice covers intellectual-property enforcement, EU marketplace regulatory proceedings, and brand-protection matters across Amazon's European surfaces.

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.