P2B Regulation notice of suspension: what to do, step by step

TL;DRA P2B Regulation notice of suspension from Amazon ES is not a final decision – it is a formal procedural step that triggers specific seller rights under EU law. Regulation (EU) 2019/1150 on promoting fairness and transparency for business users (the Platform-to-Business Regulation, known as P2B) requires the platform to give you advance notice before restricting or terminating your account, explain the grounds, and provide access to a complaint-handling process. Acting on those rights in the right sequence, and before the wrong deadline passes, is what determines whether the suspension can be reversed.

This guide walks through that sequence step by step – what the notice means, what P2B Regulation requires Amazon ES to do, where sellers consistently go wrong, and the decision points that matter most. If you are looking at a notice right now, the first thing to understand is that EU marketplace suspension rules give you more leverage than most sellers realize.

What does a P2B Regulation notice of suspension actually mean on Amazon ES?

A P2B notice of suspension is Amazon ES's written notification that it intends to restrict or terminate your business user account, issued under the procedural obligations the platform accepted when the P2B Regulation came into force across EU member states. Under P2B, a marketplace that qualifies as a platform operator must give business users advance notice – ordinarily at least 30 days before the restriction takes effect – and that notice must state the specific grounds for the action in plain language.

That notice requirement is not a courtesy. It is a legal obligation. Amazon ES's compliance with the P2B Regulation means it must include a statement of the reasons for the restriction, and it must point you toward its internal complaint-handling system. If the notice you received does not contain those elements, that gap is itself a procedural defect worth recording.

In practice, we regularly see notices that satisfy the form requirement but bury the operative ground in generic policy language – "violation of Amazon's policies" – without specifying which policy, which listing, or which conduct triggered the flag. That ambiguity is not just frustrating; it is a substantive problem, because the P2B Regulation requires the grounds to be stated with enough specificity that you can meaningfully respond. Identifying whether your notice meets that standard is the first analytical step.

A P2B suspension notice is distinct from a short-notice or immediate restriction. For cases involving illegal content, fraud, or a genuine safety risk, Amazon ES may act immediately and provide the statement of reasons afterward. If that is what happened to your account, the procedural path is different and the timeline is compressed. Most commercial suspensions – policy violations, quality metrics, product-safety flags – follow the advance-notice route, and that is the route this guide addresses.

Step 1: Read the notice carefully and document everything

The first step is to read the suspension notice in full and treat it as a legal document, not a support ticket. Save the original email, the Seller Central notification, and any related communications in a single folder immediately – before responding to anything.

Check for four specific things in the notice:

• The stated ground or grounds for the restriction (policy violation, safety issue, identity/KYC failure, IP complaint, metrics).
• The effective date of the restriction – this tells you how much of the advance-notice window, if any, remains.
• A reference to Amazon's internal complaint-handling mechanism and how to access it.
• Whether the notice references any external mediation or arbitration body.

In matters we handle, sellers often overlook the effective-date language entirely and lose days they could have used. If the notice says the restriction takes effect in ten days, you have ten days to engage the internal complaint process before the account is actually restricted. Engaging after the restriction date is harder, not impossible, but you have given up the pre-restriction window.

Also note what the notice does not say. A notice that cites only a policy category – "product safety" or "selling practices" – without identifying the specific ASIN, order, complaint, or measurement period is procedurally thin. Under P2B, the grounds must be sufficient for you to understand what conduct is in question. If they are not, your internal complaint can and should make that deficiency explicit.

Step 2: Map the root cause before drafting anything

Before you write a single word of response, reconstruct the account history that led to this notice. What you draft in the internal complaint process sets the evidentiary record for everything that follows – including any escalation to an external mediation body or, in a more serious case, regulatory referral.

Work backward from the stated ground. If the notice cites a product-safety issue, pull the relevant ASIN history: when was it listed, what documentation was submitted at the time, are there any customer complaints or A-to-z claims on that product, and when did Amazon ES first flag it? If the notice cites a seller-metrics violation, identify the performance period, the affected orders, and whether there were external factors – a carrier delay, a supplier failure – that drove the numbers.

The P2B Regulation's internal complaint-handling obligation is meaningful here. Amazon ES is required to process your complaint "in good faith" and to deal with complaints "quickly and effectively." Those are legal standards, not aspirations. A well-evidenced complaint that maps the root cause to a specific, fixable problem is easier to process in good faith than a general disagreement with the platform's decision. The former is a correction; the latter is a dispute about Amazon's judgment.

In matters we handle, the cases that move most efficiently through Amazon's internal process are the ones where the seller's account team reconstructed the full causal chain before filing anything. What caused the underlying issue? What changed in the interim? What concrete step prevents recurrence? Those three questions form the spine of every effective P2B complaint.

For a structured overview of how EU rules fit together across this process, the guide to EU marketplace regulation for sellers covers the full regulatory environment, including how P2B intersects with the Digital Services Act and the Digital Markets Act.

Step 3: File the internal complaint – the form and substance that work

Amazon ES's internal complaint-handling system, required under P2B Article 11, is the first formal step in the resolution process. Filing it correctly matters more than filing it quickly, although you should not let time pass unnecessarily.

The complaint should address, in this order:

1. Acknowledge the notice formally. State that you are responding under the P2B Regulation's internal complaint process, cite the notice date and the ground stated. This establishes the P2B procedural frame from the outset – it is not a support ticket, it is a regulated complaint.
2. Challenge any procedural deficiency. If the notice did not specify the grounds with the precision required by P2B, say so. A platform's failure to state grounds adequately is not just a technicality; it goes to whether the restriction is itself procedurally valid.
3. Address the substantive ground. Provide your root-cause analysis and the evidence that supports it. Where the ground involves a product, attach documentation – safety certificates, test reports, supplier declarations. Where it involves account metrics, attach the performance data with your explanation of the causal factors.
4. State the corrective action already taken or committed to. P2B requires the complaint-handling mechanism to be result-oriented. The platform is looking for a path to resolution. Give it one.
5. Request the specific remedy. Ask for reinstatement of listings, reversal of the restriction, or at minimum a reasoned response to each ground you have raised. An internal complaint that does not specify what outcome you are seeking leaves the platform without a clear decision to make.

What does not work: a general denial of wrongdoing with no supporting evidence; a complaint that focuses on the commercial impact on your business rather than on the legal and factual ground for the restriction; and any suggestion that the suspension is motivated by competitor manipulation unless you have specific, documented evidence you can attach. Allegations without evidence read as noise in an internal process.

The detailed response checklist for P2B disputes – covering exactly what to include and in what order – is at P2B dispute resolution for sellers: the response checklist.

Step 4: Understand the decision and the escalation options

After you file the internal complaint, Amazon ES is required to respond to it through a process that is transparent, easily accessible, free of charge to you, and capable of resolving the complaint efficiently. That obligation is on the platform. What you receive in response is either a resolution or a reasoned refusal.

If the complaint is resolved in your favor – the restriction is lifted, the listing is reinstated – document the resolution in writing and monitor the account for recurrence. The same underlying issue recurring within a short period often triggers a harder restriction the second time.

If the response is a reasoned refusal, or if you receive no substantive response within a reasonable time, you have two main escalation routes under P2B:

• External mediation. P2B Article 12 requires platform operators to identify at least two certified external mediators in their terms and conditions. You have the right to attempt mediation before the platform bears the costs on an equal basis. Mediation is non-binding, but it creates a formal record and puts the platform in the position of having to justify its decision to a neutral third party.
• Regulatory referral. EU member states are required to designate a public body responsible for enforcing the P2B Regulation. In Spain, the relevant authority for Amazon ES is the body designated under the national P2B enforcement framework. A regulatory complaint is slower than mediation but places the enforcement question before a body with investigatory powers.

There is also a third route that is less commonly used but sometimes decisive: the P2B Regulation explicitly preserves sellers' rights to bring civil claims in national courts. The regulation does not require you to exhaust the internal complaint or mediation process before going to court, although in practice courts will want to see that you engaged the available process first.

The decision between mediation and regulatory referral turns on the nature of the underlying ground, the urgency of restoring the account, and whether the platform's refusal appears to reflect a systemic policy rather than a case-by-case judgment. If the latter, a regulatory referral with a well-documented complaint file can be more effective, because it puts the policy itself under scrutiny rather than just your individual case.

For sellers dealing with broader Digital Markets Act gatekeeper obligations – which apply to Amazon as a gatekeeper under the DMA – see the explainer on DMA gatekeeper obligations and your rights as a seller.

Step 5: Assess whether the Digital Services Act adds a parallel lever

The Digital Services Act (DSA) runs alongside P2B and gives sellers of goods and services on Amazon – which is designated as a Very Large Online Platform (VLOP) under the DSA – a separate and reinforcing set of rights. Understanding where P2B ends and DSA begins matters for building a complete case.

Under the DSA, Amazon must provide a statement of reasons for any content moderation decision that restricts a business user's service. That obligation overlaps with P2B's grounds requirement, but the DSA applies more broadly to content-restriction decisions, not just to the contractual suspension covered by P2B. If the suspension involved a listing removal or a restriction on your ability to communicate with customers, the DSA statement-of-reasons obligation may be engaged in addition to P2B.

The DSA also creates an internal complaint-handling obligation that is separately required from P2B's. The two complaint processes can be filed together or sequentially. In matters we handle that involve Amazon ES suspensions with both a contractual element (the account restriction under the BSA) and a content-restriction element (the removal of specific listings), we build the complaint file to address both regimes simultaneously, because the standards of justification are slightly different and the platform's response to one can be used to inform the analysis of the other.

The DSA's out-of-court dispute settlement mechanism, accessed through DSA-certified bodies, is a further option that sits alongside P2B mediation. For most Amazon ES sellers, the practical question is which mechanism to deploy first – and the answer depends on where the platform's procedural failure is clearest.

Where this process goes wrong – and what to do differently

The most common point of failure in P2B suspension cases is the first complaint. Most sellers draft their internal complaint as a customer-service response – apologetic in tone, focused on their own loss, and light on the legal framing that P2B's complaint-handling obligations require. Amazon's teams processing these complaints are trained to look for resolution paths. A complaint that does not offer one, or that spends its first three paragraphs explaining how the suspension has damaged the seller's business, is a complaint that is hard to resolve in the seller's favor even if the underlying merits are strong.

The second failure point is the evidence gap. A complaint that says "we comply with all regulations" without attaching the test reports, safety certificates, or supplier documentation to prove it puts the platform in the position of having to accept a bare assertion. Platforms rarely do. Evidence that was not submitted with the first complaint can be added later, but later is worse: the platform has already formed a view, and reversing it requires more, not less, evidence.

The third failure point is timing. A seller who waits two weeks after receiving a notice to file the internal complaint has used up some or all of the advance-notice window. The complaint is still available, but the account may already be restricted, which changes the urgency and the platform's incentive to act quickly.

A mid-market fashion seller on Amazon ES (winter 2026) came to us after filing two internal complaints that had both been refused on the ground that their product-safety documentation was insufficient for the category. The original notices had cited a general "product safety" ground without identifying the specific ASIN or the test standard the documentation was measured against. We rebuilt the complaint to challenge the procedural adequacy of the original notice, submitted category-specific test reports keyed to the applicable EU safety standard, and pushed for a formal response to each ground. The account restrictions were lifted on the third filing, after we had established in the record that the first two refusals had not addressed the procedural challenge at all.

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 collectively create a procedural architecture that obliges platforms to justify their decisions, process complaints in good faith, and offer access to mediation. That architecture does not guarantee reinstatement, but it creates real pressure points that a well-constructed complaint can use.

Decision matrix: which route, when

The path forward depends on where the platform's failure is clearest and how urgently the account needs to be restored.

If the notice fails to state grounds with the specificity P2B requires – the route is a procedural challenge in the internal complaint, followed by mediation if the challenge is refused, on a timeline of several weeks to a few months depending on the mediator's caseload. The argument is structural and does not require you to concede the underlying factual ground.

If the notice cites a specific factual ground and you can document that the ground is factually wrong – or that you have corrected the underlying issue – the route is an evidence-heavy internal complaint filed immediately, with mediation held in reserve. If the ground is an IP complaint from a rights owner rather than an Amazon policy decision, a parallel retraction or counter-notice process may be more efficient than the P2B complaint route.

If the platform's refusal of your internal complaint appears to reflect a systemic policy applied to your category or seller type rather than a case-by-case judgment – the route is regulatory referral, because the enforcement authority has the power to examine the policy itself. Mediation cannot change a platform's general policy; a regulator can.

If urgency is critical and the account generates cash flow that cannot wait several months for mediation or regulatory process – the route is a well-evidenced internal complaint filed as quickly as possible, with legal support to ensure it meets the P2B standard, because the internal process is the fastest route when it works. Mediation and regulatory referral are escalation options, not first options.

Related areas

• EU Marketplace Regulation – the full practice covering P2B, DSA, DMA, and EU suspension defense
• Amazon Account Reinstatement – account deactivation and Plan of Action practice for all Amazon surfaces

If a first complaint has already come back refused, a second read can find the specific gap – whether it is a procedural deficiency in the original notice that was never challenged, an evidence gap in your filing, or a response that simply did not engage with the grounds you raised. To have us review the notice and the correspondence to date, email info@tutamenlaw.com.

Frequently asked questions

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

The timeline depends on which route you use and how quickly the internal complaint is resolved. An internal complaint that is well-evidenced and filed promptly can move within a few weeks; platforms are required to handle complaints quickly and effectively under P2B, though what qualifies as "quickly" in practice varies. If the case escalates to mediation, the process typically runs over several months. Regulatory referral is the slowest route and is most appropriate where the platform's conduct is systemic. The pre-restriction window – ordinarily at least 30 days under P2B – is the fastest opportunity to act, and using it well can avoid escalation entirely.

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

The principal risk is filing an internal complaint that fails on form before it can succeed on substance. A complaint that reads as a customer-service response rather than a P2B procedural filing, or that omits the documentary evidence required for the stated ground, gives the platform a defensible reason to refuse it. A refusal of the internal complaint on procedural grounds also complicates escalation to mediation or a regulator, because the evidentiary record is then thin. The second risk is missing the pre-restriction window by not engaging quickly enough – once the account is restricted, the urgency and the platform's incentive both shift.

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

Not every P2B notice requires legal representation. If the ground is narrow, the evidence is clear, and the seller has the resources to build a well-documented internal complaint, that can be handled without a lawyer. Legal support becomes more important when the notice is procedurally deficient and the deficiency needs to be pressed formally; when the ground touches IP, product safety regulation, or cross-border compliance issues that require regulatory analysis; or when a prior complaint has already been refused and the escalation options need to be assessed. In matters we handle, the cases that benefit most from early involvement are the ones where the first internal complaint is still to be filed – because that is where the record is made.

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 marketplace regulation practice covers P2B complaint-handling, DSA statement-of-reasons challenges, and DMA gatekeeper obligations across Amazon's EU surfaces – with all engagement handled by attorneys and fees fixed after a short initial review. To discuss your situation, email info@tutamenlaw.com.

Byline: Priya Raman, IP & Brand Registry analyst, 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.