How to handle P2B Regulation notice of suspension: a step-by-step guide

TL;DRA P2B Regulation notice of suspension on Amazon ES is a formal communication that the platform is restricting or terminating your access to its marketplace services – and under EU law, that notice must meet specific content requirements that give you enforceable procedural rights. The Platform-to-Business (P2B) Regulation obliges Amazon, as a platform providing services to EU-based business users, to issue a statement of reasons before most suspensions take effect and to operate an internal complaint-handling system you can use to challenge the decision. The realistic options are an internal complaint, an escalation under the platform's own redress mechanism, or a structured legal challenge – and the path you choose in the first few days shapes what remains available later.

On paper, the suspension appeal looks clear: read the notice, respond, wait. In practice, the sellers we work with regularly discover that the notice is ambiguous, the internal complaint system loops back to the same outcome, and the clock on any meaningful challenge runs faster than expected. This guide walks through the step sequence that actually matters, the points where it most often goes wrong, and the decisions you face at each stage.

What a P2B Regulation notice of suspension actually is on Amazon ES

A P2B notice of suspension is a legally required document, not simply a Seller Central alert. Under the Platform-to-Business Regulation – which applies across the EU, including Amazon ES – platforms must provide business users with a statement of reasons setting out the specific facts or circumstances that led to a suspension or termination decision, the legal or contractual grounds invoked, and, where relevant, the evidence that triggered the action.

That obligation matters for practical reasons. A notice that fails to meet those content requirements is itself a basis for complaint. In matters we handle, it is surprisingly common for a seller's first reading of the notice to miss the gap between what the platform is required to say and what it actually said. The notice may cite a policy category in general terms without naming the specific conduct, or it may reference an automated detection flag without identifying the underlying facts.

Amazon ES is part of the EU single marketplace regulatory regime. Amazon qualifies as a Very Large Online Platform (VLOP) under the Digital Services Act, and its P2B obligations sit alongside DSA transparency duties and, depending on the conduct at issue, potential Digital Markets Act (DMA) gatekeeper obligations. That layering is relevant when a suspension also involves access to algorithmic ranking, the Buy Box, or Amazon Advertising – all areas where the DMA creates independent obligations. For a wider view of how these instruments interact, the guide to DMA gatekeeper obligations and sellers covers the DMA layer in detail.

The suspension itself may be partial – listings restricted, advertising paused, disbursements withheld – or full, meaning account-level deactivation. The P2B Regulation's procedural rights apply to both, though the urgency and the procedural sequence differ. A full deactivation with no prior notice is permitted by the Regulation only in narrow circumstances, and where it occurs, Amazon is required to provide reasons without undue delay afterward.

Step 1: Read the notice against the regulation's minimum requirements

The first practical step is to treat the notice as a document to be assessed for legal compliance, not just a platform communication to respond to commercially. The P2B Regulation sets out what the statement of reasons must contain, and checking the notice against those requirements takes priority over drafting a response.

Read for: the specific facts alleged, the precise policy or contractual ground invoked, and whether any evidence base is identified. If the notice describes only a general category – "violation of Amazon's selling policies" – without identifying the conduct, the product, or the ASINs at issue, that is a deficient notice under the Regulation. That deficiency does not automatically reinstate an account, but it is a procedural ground for a formal complaint that carries more weight than a general appeal.

Save everything. Download the notice from Seller Central, note the timestamp, and preserve any related Performance Notifications, Account Health emails, and Case Log entries from the period immediately before the suspension. Amazon ES operates in Spanish; if your working language is different, a translation of the notice is needed before the compliance check. The date of the notice and the date of the suspension itself are both material – the Regulation requires prior notice except in the circumstances we address below.

At this stage, resist the instinct to respond immediately with an explanation or an apology. A response sent before you have assessed what the notice actually requires – and what rights it triggers – can limit the procedural options that remain open. We regularly see sellers send a rushed reply that frames the matter as a straightforward policy fix when the real issue is a notice that did not comply with the Regulation's requirements. That framing shift is difficult to undo.

Step 2: Identify the suspension type and the procedural path that follows

Not all P2B suspensions follow the same procedural track, and identifying the correct one early is where sellers who work through this alone most often lose ground. The relevant question is not just why the account was suspended, but what the Regulation requires at this stage given the notice you received.

There are broadly three situations. First: a suspension with prior notice and a statement of reasons, where the seller had advance warning and the Regulation's standard path applies. Second: an immediate suspension where Amazon claims an exception – typically that allowing prior notice would compromise a legitimate security interest or legal obligation. Third: a termination of the relationship, which triggers both the Regulation's statement-of-reasons requirement and a minimum notice period under the Regulation's notice rules.

Each situation produces a different next step. For a prior-notice suspension, the internal complaint is the first formal channel. For an immediate suspension without a compliant statement of reasons, the complaint should address the procedural deficiency as well as the underlying merits. For a termination, the minimum notice period provided by the Regulation may itself be in issue if Amazon shortened it.

For context on how the full regulatory picture connects – the P2B Regulation, the DSA, and the DMA together – the complete guide to EU marketplace regulation for sellers maps the relationship between the instruments and how they bear on Amazon ES accounts.

Step 3: File the internal complaint correctly – and completely

The P2B Regulation requires platforms to operate an internal complaint-handling system that is free of charge, easy to access, and designed to handle complaints from business users about the platform's compliance with its own obligations. Amazon's system for EU sellers is its internal appeal and escalation process within Seller Central, supplemented by its published dispute-resolution procedures.

Filing the complaint correctly means more than submitting a rebuttal in the Case Log. A complaint under the P2B framework should explicitly invoke the Regulation, identify the specific obligation alleged to have been breached, set out the factual and legal grounds, and request a specific outcome – reinstatement, reversal of a listing restriction, or release of withheld funds.

Structure matters. The complaint should address the statement-of-reasons obligation directly: if the notice was deficient, say so and explain why. If the notice was adequate but the underlying decision was wrong, address the facts and the platform's stated grounds point by point. Platforms are required by the Regulation to handle complaints within a reasonable timeframe and to communicate the outcome and its reasons to the seller.

Common errors at this stage include: framing the complaint as a general appeal rather than invoking P2B rights; failing to request a specific remedy; and omitting the factual record that supports the complaint. A complaint that does not reference the Regulation is processed on the platform's own internal terms, which provides less procedural protection than a complaint that invokes the P2B framework explicitly.

Step 4: Assess the internal complaint outcome – and your decision points

What happens after the internal complaint is the most commercially significant decision point in the process. The platform must handle the complaint and communicate its outcome. If the outcome is favorable – reinstatement, restriction reversed, funds released – the matter concludes at this stage. If the outcome is unfavorable, or if the platform fails to respond within a reasonable period, the seller faces a genuine decision about whether and how to escalate.

The realistic escalation options are: a formal external dispute-resolution process using one of the certified mediators named in the P2B Regulation; a complaint to the competent national authority in the relevant EU member state (for Amazon ES, the Spanish authority for P2B enforcement); or a legal challenge that combines P2B grounds with any applicable DSA or DMA obligations. Each route has different cost, speed, and leverage profiles.

In our practice, the decision between mediation and authority complaint turns heavily on the nature of the suspension. A suspension that appears to involve Amazon's algorithmic enforcement or access to ranking tools may engage DMA gatekeeper obligations in addition to P2B duties – and that can shift the leverage and the appropriate venue. For sellers weighing the dispute-resolution routes, the case study on how one seller resolved a P2B dispute illustrates how that decision played out in a comparable matter.

What should you do if you filed the internal complaint alone and it was rejected? A rejection is not the end of the procedural path. It is the point at which the external channels open. The grounds for rejection, the adequacy of the platform's reasons for rejecting the complaint, and the timeline of the whole process become the building blocks of any external filing.

Step 5: Build and preserve the documentary record throughout

Every stage of the process described above depends on a documentary record. This is not bureaucratic caution – it is the practical basis for any external escalation. A mediation, an authority complaint, or a legal challenge all require evidence of what was said, when, and by whom.

What to preserve: the original suspension notice with its timestamp; every Performance Notification and Account Health message sent or received in the relevant period; the Case Log entries; any communications from Amazon's Seller Support or Compliance teams; the internal complaint filing and Amazon's response; and the account health history showing the timeline of any prior actions Amazon took that may be relevant to the suspension.

Platforms may update or remove internal communications over time. Download and store copies outside Seller Central as each document is generated. In matters we handle involving Amazon ES, it is common for sellers to lose access to specific Case Log entries or notifications when their account status changes, which is why real-time preservation matters.

The record also supports a timeline reconstruction – which is often essential to show whether Amazon's notice was timely, whether the exceptions to prior notice apply, and whether the internal complaint was handled within a reasonable period. These are the procedural grounds on which external challenges often turn, and they require precise dates, not approximate recollections.

Where this process most often goes wrong

A suspension under EU marketplace rules can look final. Many sellers believe, incorrectly, that once Amazon suspends an account on Amazon ES, EU regulatory rights are theoretical rather than practical. That is the myth we see most often, and it understates the leverage the P2B Regulation actually provides.

The concrete failure points we see are: responding before assessing the notice; framing the response as a general Plan of Action when the issue is a deficient notice under P2B; using the internal complaint channel without invoking the Regulation; accepting a rejection as final without assessing external options; and losing the documentary record because it was not preserved at the time.

Timing errors are the most costly. The P2B Regulation's procedural structure creates windows – for the internal complaint, for external escalation, and for authority complaints – and those windows are not indefinite. Acting on the wrong channel first, or acting on the right channel but framing it incorrectly, can mean that the procedural advantages the Regulation provides are narrowed before any external body considers the matter.

A micro-case illustrates the pattern. An electronics accessories seller on Amazon ES (summer 2025) received a suspension notice that cited a broad policy category without identifying any specific product, ASIN, or transaction. The seller filed a general Plan of Action in response. It was rejected. The seller came to us at that stage; we reconstructed the notice's deficiencies under the P2B Regulation's statement-of-reasons requirements, refiled through the internal complaint channel with a formal P2B invocation, and escalated when the response was again inadequate. The account was reinstated after the escalation. The point is that the first filing – framed as a policy fix rather than a P2B complaint – did not use the available procedural tools.

Decision matrix: which route fits your situation

Not every seller reaches the same decision point. The route forward depends on what the notice said, what the internal complaint produced, and what the commercial stakes are.

If the notice cited specific facts, adequate grounds, and was delivered with prior notice, the internal complaint is the standard first channel and the merits of the suspension are the primary issue. If the notice was deficient – no specific facts, no identified ground, no compliant statement of reasons – the procedural deficiency should lead the complaint, and escalation is available sooner.

If the internal complaint is rejected and the suspension involves access to a core platform function – ranking, the Buy Box, advertising – the DMA gatekeeper dimension may provide additional leverage alongside the P2B path. If the platform has not responded to the complaint within a reasonable period, the external channels open without needing to await a formal rejection.

For terminations, the notice period requirement is a separate issue that sits alongside the statement-of-reasons obligation. Where Amazon shortened the notice period below the Regulation's minimum, that is an independent ground for the complaint.

What you should build into the decision is the commercial cost of each route. Internal complaints are low-cost and should always be the first step. Mediation involves a certified mediator and carries its own timeline and cost. Authority complaints can be slow but build a public record and in some circumstances create systemic pressure. Legal challenge is the highest-cost route and is typically appropriate where the stakes – in terms of account value, inventory, and disbursements at risk – justify the effort and expense. Building a pre-arbitration demand or a Notice of Dispute alongside the P2B complaint is sometimes the appropriate route for sellers whose BSA dispute-resolution path also remains open, depending on the version of the agreement applicable to the account.

Related areas

• EU Marketplace Regulation – suspension, delisting, and P2B rights for Amazon EU and UK sellers
• Amazon Account Reinstatement – Plan of Action and appeal strategy for deactivated accounts

If you have already filed an internal complaint and it came back rejected – or if Amazon has not responded within what appears to be a reasonable period – a second read of the complaint and the notice together can identify whether the procedural grounds were fully used and what, if anything, the external channels can still offer. To have that reviewed, contact Tutamen at 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 procedural stage is reached and how quickly the platform responds. An internal complaint that results in reinstatement can resolve in several weeks. Cases that require external escalation – through a certified mediator or a competent authority complaint – typically take considerably longer. The P2B Regulation requires the internal complaint to be handled within a reasonable period, but that period is not prescribed with a fixed number of days, and in practice the commercial pressure of a suspended account often drives the pace more than the regulatory clock. Acting promptly and filing correctly at each stage avoids delays that are within the seller's control.

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

The primary risk is mischaracterizing the procedural basis of the response. Sellers who file a general Plan of Action without invoking the P2B Regulation's statement-of-reasons requirements miss the most effective procedural lever available. A second risk is losing the documentary record that supports any external escalation. A third is accepting a rejection as final when external channels remain open. The P2B Regulation gives EU business users real procedural rights, but those rights depend on being invoked correctly and at the right stage – they do not apply automatically regardless of how the complaint is framed.

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

Not every P2B complaint requires legal representation. If the notice is clear, the grounds are identifiable, and the internal complaint is straightforward, a well-informed seller can often handle the first stage. Legal input becomes more valuable when the notice is deficient and the procedural deficiency needs to be articulated formally; when the internal complaint has already been rejected and external escalation is in view; or when the suspension involves significant account value, inventory, or withheld funds. In matters we handle, the most common reason sellers seek advice is not the internal complaint itself but what to do after it fails.

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 practice covers the P2B Regulation, the Digital Services Act, the Digital Markets Act, and related 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.

By Priya Raman, IP & Brand Registry analyst, Tutamen. Published February 9, 2027.