Inside P2B Regulation notice of suspension on Amazon ES

When Amazon ES suspends a seller's account and cites a policy or compliance ground, the suspension email can look like the end of the matter. Listings go dark. Revenue stops. The clock starts running on inventory already in a Spanish or EU fulfillment center. For many mid-market sellers, the commercial damage sets in within days – not weeks. What the email rarely explains is that a specific piece of EU law, Regulation (EU) 2019/1150 on Platform-to-Business (P2B) relations, grants sellers a procedural set of rights that Amazon is legally required to honor, including a statement of reasons before any restriction or suspension takes effect in all but the most exceptional circumstances.

TL;DRA P2B Regulation notice of suspension on Amazon ES is a formal written statement that Amazon must provide before restricting or terminating a seller's access to the platform, setting out the specific grounds for the action and the seller's right to contest it through an internal complaint-handling process. EU sellers are not helpless once Amazon acts: the P2B Regulation, the Digital Services Act (DSA), and related EU instruments create a procedural path – a statement of reasons, an internal complaint, and escalation to out-of-court dispute resolution – that a well-prepared seller can use to challenge the decision on the merits.

This analysis covers what a P2B suspension notice actually says and what it omits, how the procedural path works in practice on Amazon ES, and the decision points a seller faces at each stage. The goal is to give you a clear picture before you file anything, because the first formal response sets the tone for everything that follows.

What the P2B Regulation actually requires Amazon to do before suspending you

The P2B Regulation requires Amazon – as a platform intermediation service operating in the EU – to give business sellers a statement of reasons whenever it restricts, suspends, or terminates their access to the platform, and in most cases that statement must come before the action, not after.

Article 4 of the P2B Regulation sets the substantive floor. Amazon must state the specific facts or circumstances that led to the decision, explain the applicable grounds from its terms and conditions, and tell the seller what, if any, redress mechanism is available. On Amazon ES, that obligation translates to the suspension notice you receive through Seller Central – but in practice the notice often satisfies the letter of the obligation while giving the seller very little to work with. The stated ground may be a generic policy category ("product authenticity", "customer experience", "related account") without the underlying data that actually triggered the algorithm or the human review.

That gap matters procedurally. In matters we handle involving Amazon ES suspensions, we frequently see notices that cite one category while the real flag sits in a different part of the account history. A seller who responds to the stated ground alone will miss the actual root cause, and the internal complaint or Plan of Action (POA) they file will fail not on the merits but on the framing.

The P2B Regulation also requires Amazon to maintain a minimum 30-day prior notice period before terminating a seller's access to the platform under Article 8 – a rule that applies to termination of the overall business relationship, as distinct from individual listing suspensions or account-level deactivations tied to an alleged breach. Understanding whether your situation is a listing restriction, an account-level suspension, or a notice of termination matters because the procedural rights, and the timelines attached to them, differ across those three categories.

What the Regulation does not do is tell you how to win the internal complaint. That is the territory where the commercial choices become important, and where the distinction between a statement of reasons that is procedurally correct and one that is substantively accurate becomes the key variable.

How does the internal complaint-handling process work on Amazon ES?

Amazon's internal complaint-handling system for P2B purposes is the structured channel through which a seller challenges a suspension or restriction before escalating to any external mechanism, and on Amazon ES it operates through the same Seller Central interfaces used for standard appeals.

The P2B Regulation requires Amazon to provide a free, accessible, and effective internal complaint-handling system. In practice on Amazon ES, that system is a combination of the standard appeal flow in Seller Central, the Account Health dashboard, and, where applicable, the Selling Partner Support escalation path. The Regulation requires Amazon to consider complaints in good faith, reach a decision promptly, and communicate the outcome with reasons. It does not require Amazon to reverse every decision – only to give it genuine consideration.

This creates a specific strategic question: what does "effective" complaint look like at the internal stage? In our practice, a complaint that maps precisely onto the grounds stated in the notice, addresses the underlying data Amazon is relying on (which you have to reconstruct from the account timeline, the notice language, and the policy documents Amazon references), and proposes a concrete corrective action tends to perform better than a general denial. The internal stage is also, importantly, the stage at which you build the record for any subsequent escalation to out-of-court dispute resolution or, in the EU context, a regulatory complaint.

One practical reality on Amazon ES specifically: the platform operates under both the P2B Regulation and the DSA, since Amazon holds Very Large Online Platform (VLOP) status under the DSA. That dual-layer structure means the internal complaint mechanism must also comply with the DSA's requirements for transparent, non-discriminatory handling of complaints by business users. For sellers, the operational implication is that the statement of reasons Amazon provides must be traceable to a stated policy ground in its terms and conditions, and if it is not, that gap is itself a basis for complaint.

The bridge to the next stage is worth stating plainly. If the internal complaint is rejected, the seller has two principal external paths: mediation through an accredited out-of-court dispute resolution body under Article 12 of the P2B Regulation, or, in specific circumstances, collective legal action under Article 14. For most individual sellers, the mediation path is the realistic one. For sellers whose suspension is tied to broader competition or gatekeeper conduct by Amazon, the Digital Markets Act (DMA) and the Bundeskartellamt proceedings framework provide an additional layer – a point covered in more depth in our analysis of what sellers should know about DMA gatekeeper obligations.

What should the statement of reasons actually contain – and what happens when it falls short?

A legally adequate statement of reasons under the P2B Regulation must identify the specific facts or behaviors Amazon is relying on, connect those facts to a defined term or condition in the Business Solutions Agreement or equivalent platform contract, and explain the available redress path – but in reality, many statements of reasons on Amazon ES fall short of that standard in at least one dimension.

The most common shortfall is specificity. Amazon may state that a seller violated its "authenticity policy" without identifying which ASIN, which complaint, which date, or which supply chain document was reviewed and found deficient. A seller receiving that notice has to work out, from external signals and internal account data, what the actual trigger was. In matters we have worked through, that reconstruction often reveals that the stated ground is secondary to a different, undisclosed trigger – a related-account flag, a fraud-detection alert, or a prior warning on a different marketplace that Amazon linked to the ES account.

When the statement of reasons is legally insufficient, that insufficiency is itself a ground for the internal complaint. The seller's first response should document the deficiency – not just defend against the stated ground. That approach serves two purposes. It creates a contemporaneous record that the seller tried to engage properly. And it puts Amazon on notice that the seller understands the regulatory floor, which often changes the tone of the subsequent handling.

The DSA adds a further layer here. Amazon's obligations as a VLOP include transparency about content-moderation decisions that affect business users. A suspension driven by automated detection (algorithmic flagging of account metrics, for example) has to be disclosed as such under the DSA, and the seller can request human review of an automated decision. That right is procedurally distinct from the P2B internal complaint but can be invoked in parallel, and in matters where the suspension looks automated, invoking both paths simultaneously tends to produce a faster substantive response than the internal complaint alone.

A home-goods FBA seller on Amazon ES (winter 2025) faced a suspension notice that cited an "authenticity concern" with no further detail. We reconstructed the account timeline and identified that the actual flag had been triggered by a spike in A-to-z Guarantee claims on a single ASIN following a logistics disruption. We built the internal complaint around the logistics root cause, attached corrective action documentation, and invoked the DSA automated-decision review right in parallel. The complaint reached a favorable resolution without escalation to the out-of-court dispute resolution stage.

The seller's decision points: internal complaint, out-of-court mediation, or regulatory escalation?

Once the statement of reasons is in hand, the seller faces a genuine fork in the road: engage the internal complaint process with the expectation that it will resolve the matter, treat the internal stage as a necessary formality before moving to out-of-court mediation, or consider whether the facts support a regulatory complaint to a competent authority.

The internal complaint is always the first step – the P2B Regulation's mediation mechanism is only accessible after the internal stage has been exhausted without resolution. But "exhausting" the internal process does not mean waiting indefinitely. In practice, Amazon's internal complaint handling on a suspension has a variable resolution timeline. A seller whose account drives significant GMV on Amazon ES may see faster substantive engagement than a smaller seller, purely because the economic signal reaches a different tier of account management. That disparity is commercially real even if it is legally irrelevant to the P2B obligation.

If the internal complaint does not produce a satisfactory resolution, the seller can refer the dispute to a P2B accredited mediator. Article 12 of the P2B Regulation requires Amazon to name at least two mediators in its terms and conditions for EU sellers. The mediation process is structured, time-bound, and can address both the suspension itself and any consequential commercial loss. Critically, the costs of mediation are largely borne by Amazon under the P2B rules – the seller's share is capped at a reasonable level.

The regulatory escalation option is less commonly used for individual suspensions, but it is a real option in specific fact patterns. If the suspension appears to be part of a broader discriminatory practice – for example, systematic action against third-party sellers who compete with Amazon's own retail operation – the case for a complaint to a national competition authority under the DMA gatekeeper framework becomes stronger. The Bundeskartellamt has active proceedings relevant to Amazon's treatment of marketplace sellers. For EU sellers on Amazon ES, the relevant national authority for P2B enforcement complaints is the Spanish Secretaría de Estado de Digitalización e Inteligencia Artificial, which has enforcement powers under the P2B Regulation.

The practical decision matrix looks like this. If the suspension notice contains a specific, traceable factual ground and the seller can address that ground with evidence – the route is a well-framed internal complaint, within the response window Amazon's notice specifies. If the notice is vague or the stated ground is clearly inconsistent with the account record – the route is a dual-track internal complaint plus a DSA automated-review request, on a timeline of several weeks for the internal resolution. If both internal paths fail without adequate reasons – the route is out-of-court mediation under Article 12 of the P2B Regulation, which adds time but puts the cost burden on Amazon. If the pattern is systemic or discriminatory – regulatory escalation is an additional lever, pursued in parallel with or after mediation.

For a deeper read on the dispute-resolution options that sit alongside these P2B paths, the analysis of P2B dispute resolution for sellers and the realistic options sets out the procedural architecture in full.

The steps above describe the standard path. Your specific situation turns on the exact language of the notice, the account history on Amazon ES, the timeline of any prior warnings or related-account flags, and whether the suspension is tied to an automated decision – which is what we review first.

To discuss your Amazon ES suspension with our team, email info@tutamenlaw.com.

What sellers consistently get wrong when responding to an Amazon ES P2B suspension

The most common mistake is treating the P2B suspension as an ordinary Amazon appeal and filing a standard Plan of Action without engaging the regulatory dimension. That approach is not wrong in itself – a well-evidenced POA addressing the root cause remains the core of any internal response. But it leaves the seller's P2B procedural rights on the table and signals to Amazon's compliance team that the seller is operating as an ordinary appeal rather than a business user asserting rights under EU law.

A second common error is responding too quickly without reconstructing the account timeline. The temptation to file within 24 to 48 hours is understandable – revenue is down and inventory is accumulating costs. But a rushed response that addresses the wrong ground is more damaging than a slightly delayed response that addresses the right one. Once Amazon's internal review team has considered and rejected a response, the next filing faces a higher bar. In matters we handle, we consistently find that the account timeline reconstruction, done before the first response is filed, changes the framing of the entire complaint.

A third mistake is failing to preserve the record. The P2B internal complaint, the DSA human-review request, and the subsequent correspondence are the evidentiary foundation for any mediation or regulatory escalation. Sellers who treat the internal stage as informal and do not keep dated copies of all submissions and responses find themselves at a material disadvantage if the matter needs to go further. Document everything, with timestamps.

The myth that EU sellers have no leverage once a platform suspends them is exactly that – a myth. The P2B Regulation, the DSA, and the DMA together create a structured procedural environment in which a well-prepared seller has meaningful options at every stage. The leverage is procedural and regulatory, not commercial – Amazon does not restore accounts because a seller is a good customer; it responds when the regulatory and evidentiary case is made correctly.

A software-tools seller on Amazon DE (spring 2026) came to us after a first internal complaint had already been rejected, with a one-line response citing "continued policy non-compliance" without elaboration. We identified that the original notice had not met the P2B specificity requirement, documented the insufficiency, and filed a revised internal complaint under the DSA human-review channel, attaching a root-cause analysis of the account metrics that had triggered the automated flag. The matter was resolved at the internal stage on the second submission, without the need for out-of-court mediation.

How the DSA and DMA interact with P2B rights on Amazon ES

The P2B Regulation is the foundation for seller rights on EU marketplaces, but it does not operate in isolation – the DSA and DMA add layers that are increasingly relevant to the practical handling of Amazon ES suspensions.

The DSA's obligations on Amazon as a VLOP include the requirement to provide statements of reasons for content-moderation decisions affecting business users, maintain a complaint-handling mechanism that is distinct from the general customer-complaint flow, and subject automated-decision systems to human review on request. For sellers, the key DSA lever is the human-review right: if the suspension was algorithmically triggered, invoking that right puts Amazon's automated system's output in front of a human reviewer who must apply the substantive standard from the platform's terms, not just the algorithmic output.

The DMA's gatekeeper obligations are relevant in a narrower set of cases – principally where the suspension can be characterized as Amazon using its gatekeeper position on the EU marketplace to disadvantage third-party sellers who compete with its own retail operation. Amazon's designation as a gatekeeper under the DMA means that specific obligations around fair and non-discriminatory treatment of business users are enforceable by the European Commission and national authorities. For an individual suspension, the DMA angle is usually a secondary lever; but it becomes primary in patterns of repeated, unexplained suspension of sellers in categories where Amazon has a competing private-label offering.

The Platform-to-Business Regulation also interacts with the Spanish regulatory environment in specific ways. Spain has designated a national enforcement body for P2B purposes, and the complaint mechanism available to Amazon ES sellers differs in some procedural respects from the mechanism available to sellers on Amazon DE or Amazon FR. That jurisdictional nuance matters for sellers who operate across multiple EU marketplaces – the account may be deactivated globally while the P2B complaint is filed nationally, and coordinating the timing of complaints across multiple jurisdictions requires care.

For the broader context on how EU marketplace regulation fits together for sellers operating across multiple surfaces and jurisdictions, the complete guide to EU marketplace regulation for sellers covers the full regulatory architecture. For matters that touch on the DMA specifically, the analysis of DMA gatekeeper obligations sets out the practical implications for third-party sellers in more detail.

The commercial reality: what a P2B suspension costs and how to frame the decision to contest it

A suspension on Amazon ES carries costs that extend well beyond the revenue lost on the days the account is inactive. For FBA sellers, inventory in Spanish or EU fulfillment centers continues to accrue storage fees during the suspension. For sellers with active advertising campaigns, the sunk cost of creative and keyword work sits idle. For sellers with distribution agreements in Spain or the wider EU, an unexplained suspension creates reputational exposure with distributors and brand owners who are watching the account performance.

The decision to contest the suspension through the P2B process – rather than simply accept it and work toward reinstatement through the standard Amazon appeal channel – is partly a function of the commercial stakes and partly a function of what the notice actually says. The P2B path adds procedural weight and regulatory accountability to what would otherwise be a one-sided administrative process. It does not guarantee reinstatement. What it does is create a structured, documented record of the seller's engagement, impose specific response obligations on Amazon, and open escalation paths that are not available through the standard appeal process alone.

For a seller with significant EU GMV on Amazon ES – a business where the suspension is causing genuine cash-flow disruption – the P2B process is worth engaging fully, in parallel with the standard reinstatement efforts. For a seller with a minor or experimental presence on Amazon ES, the calculus is different. The P2B process requires time and preparation; if the account represents a small fraction of overall revenue, the standard appeal path may be the more proportionate route.

What sellers should not do is treat the P2B notice as boilerplate. The statement of reasons Amazon provides is the starting point for every subsequent step, and reading it carefully – against the actual account record and against the specific language of the P2B Regulation and Amazon's terms of service for EU sellers – is the most important thing a seller can do in the first 48 hours after receiving it.

If a first appeal or internal complaint has already come back rejected, a second read of the account record and the notice can identify the specific reason it failed and whether the P2B procedural grounds remain open. The regulatory clock on some escalation options is worth understanding before assuming all paths are closed.

To get a read on your P2B suspension notice, email info@tutamenlaw.com.

Related areas

• EU Marketplace Regulation – legal representation for Amazon ES, DE, FR and other EU marketplace suspensions
• P2B Dispute Resolution – procedural options from internal complaint through out-of-court mediation

Frequently asked questions on P2B suspension notices on Amazon ES

How long does resolving a P2B regulation notice of suspension usually take on Amazon ES?

Resolution timelines vary significantly depending on whether the matter is handled at the internal complaint stage or proceeds to out-of-court mediation. An internal complaint that is well-framed and addresses the actual root cause can produce a response within a few weeks. If the internal stage does not resolve the matter and mediation under Article 12 of the P2B Regulation is required, the process adds further time – typically several additional weeks to months, depending on the mediator's schedule and the complexity of the dispute. Suspensions tied to automated decisions that invoke the DSA human-review path sometimes reach a substantive response faster than the standard internal complaint route, because the request triggers a different internal queue.

What are the main risks if I handle a P2B regulation notice of suspension alone?

The principal risk is addressing the stated ground in the notice without identifying the actual trigger, which produces a response that is factually plausible but misses the point Amazon's review is focused on. A second risk is failing to invoke the DSA automated-review right in parallel where it applies, leaving a significant procedural lever unused. A third risk is failing to document the internal complaint and Amazon's response in a way that preserves the evidentiary record for mediation or regulatory escalation. Once Amazon has rejected a first response, the bar for the second is higher, and the cost of a poor first filing is measured in additional weeks of suspension.

Do I need a lawyer for a P2B regulation notice of suspension?

Legal representation is not formally required at the internal complaint stage – sellers can and do file internal complaints without counsel. The practical question is whether the combination of EU regulatory knowledge, account-timeline reconstruction, and procedural strategy required to engage the P2B, DSA, and DMA levers simultaneously is something the seller can put together while also managing the commercial disruption of an active suspension. In matters we handle, the most common finding is that the seller understood the suspension was serious but underestimated the regulatory dimension, which is exactly where the internal complaint fell short.

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 covers P2B Regulation, the Digital Services Act, the Digital Markets Act, and suspension and delisting matters across Amazon's EU surfaces. To discuss your situation, email info@tutamenlaw.com.

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.