Before you act on Spanish marketplace suspension: a checklist

TL;DRA Spanish marketplace suspension on Amazon ES is a formal restriction or deactivation of a seller's account, listings, or both, triggered by Amazon under its own policies or under EU regulatory requirements that now apply to the platform. Under the Platform-to-Business (P2B) Regulation and the Digital Services Act (DSA), sellers have concrete procedural rights – including the right to a statement of reasons and access to an internal complaint-handling system – that many sellers do not know to invoke before they start drafting a reply.

The notices arrive without warning. One morning the listings are gone, or the account is restricted, or a disbursement is frozen. The commercial damage starts immediately: inventory in Spanish fulfillment centers is immobilized, advertising spend stops converting, and the next restocking order has no certain destination. At that moment, most sellers do one of two things – they either panic-reply to the notice or they wait, hoping the problem resolves itself. Both responses cost time the seller does not have.

This checklist is structured in phases. Work through them in order. The goal is not to file the fastest response; it is to file the right one, using the procedural levers that EU law and Amazon's own rules actually give you.

Phase 1 – Read and classify before you do anything else

The single most important step in any Spanish marketplace suspension is correctly classifying the notice before touching a keyboard to reply, because the classification determines which procedural path you take.

Amazon ES operates under a layered regulatory environment. A suspension notice may originate from any of the following distinct bases, and the response to each is different:

A policy deactivation – triggered by a performance metric, a listing violation, or an account-level flag under the Amazon Business Solutions Agreement (BSA). These follow Amazon's standard appeal path through Seller Central.
A DSA-linked restriction – where Amazon, as a Very Large Online Platform (VLOP) under the Digital Services Act, has restricted content or an account on the basis of illegal content, systemic risk mitigation, or a notice from a trusted flagging body. Under the DSA, a statement of reasons is legally required.
A P2B-based restriction – where the Platform-to-Business Regulation applies and requires Amazon to give reasons for any restriction or termination of a business user's access, with at minimum 30 days' notice for termination (less where illegal content or security is involved).
A product-safety or regulatory-compliance delisting – under the General Product Safety Regulation (GPSR) or Extended Producer Responsibility (EPR) rules, where a listing has been removed for a specific product or category compliance failure.

Run through this checklist for Phase 1:

Locate the exact notice in Seller Central and in every registered email address. Do not rely on a notification summary; find the full text.
Identify which Amazon entity sent the notice – Amazon Services Europe SARL or another entity – because this affects which complaint mechanism applies.
Note the stated reason. Is it a policy violation? An illegal-content decision? A product-safety flag? A verification (KYC) failure? Write it down verbatim.
Check whether a statement of reasons was provided. Under the DSA, one is required for restrictions on content or accounts. If it is missing, that absence is itself an actionable point.
Check the notice for any stated deadline. Some notices carry a response window; others do not state one but the clock runs anyway.
Do not click "submit appeal" yet. The first submission matters most; a weak first filing often forecloses options on the second.

In matters we handle, incorrect classification at Phase 1 is the single most common reason a well-prepared seller files a strong Plan of Action to the wrong team – and receives a generic rejection that does not engage with the real issue at all.

Phase 2 – Secure your account data and document the pre-suspension state

Documentation gathered in the first hours after a suspension is far easier to obtain than documentation gathered two weeks later, when Amazon may have purged certain account health records or when a seller's memory of the sequence of events has blurred.

Work through this list before you draft a single word of a response:

Download your Account Health report from Seller Central in full. Note every metric and flag visible on the day of suspension and on each of the preceding 30 days.
Screenshot every listing that is restricted or removed, including the ASIN, the listing status, and any visible violation notice. Some notices disappear from the Seller Central interface after the initial display.
Pull your disbursement history. Note the last date of disbursement and the current balance visible in your payment account. If funds appear to be held, document the amount and the stated basis, if any.
Preserve every communication from Amazon – email, in-Seller-Central message, case log entry – in chronological order. Do not forward them piecemeal; export or print each in full.
If the suspension mentions a specific ASIN or product category, pull the full documentation for that product: invoices, supplier declarations, CE markings, responsible person designations under GPSR, EPR registration certificates.
If the suspension cites an inauthentic or counterfeit complaint, identify whether there is a corresponding rights-owner complaint visible in the IP complaint section of Seller Central.
Note the date and local time of every Amazon communication. The timestamp may matter for calculating P2B notice periods.

A home-goods seller operating on Amazon ES came to us after a product-safety delisting that also triggered an account-level restriction (spring 2026). The seller had already replied twice to Amazon without preserving the original notices. Reconstructing the pre-suspension account health record from partial screenshots took additional time that the response window did not easily absorb. We rebuilt the timeline from available data, prepared the GPSR responsible-person documentation the notice actually required, and the listings were restored. The lesson: documentation is your raw material; collect it first.

For a broader view of how product-safety rules interact with Amazon ES account status, see our guide on what sellers should know about product-safety delisting in the EU.

Phase 3 – Identify your procedural rights under EU law

EU sellers facing a Spanish marketplace suspension have concrete legal rights that do not depend on Amazon's goodwill – and the most important of those rights is the right to an internal complaint-handling system under the P2B Regulation and the DSA.

Many sellers proceed directly to a Plan of Action without ever using the formal complaint path, which means they skip the mechanism that EU law specifically designed for this situation. That is the myth worth addressing: sellers operating on Amazon ES are not without leverage once the platform acts. The legal structure gives you several distinct pressure points.

Statement of reasons (DSA/P2B): Amazon is required to provide the reasons for restricting or terminating a business user's access. If yours is absent or inadequate, request it explicitly and in writing before responding substantively to the restriction.
Internal complaint-handling: Both the P2B Regulation and the DSA require Amazon to maintain an accessible internal complaint-handling system for business users. Filing through this system creates a documented record that sits outside the standard Seller Central appeal queue.
Notice period for termination (P2B): For a full termination of business user access, the P2B Regulation requires a minimum advance notice period, subject to exceptions for illegal content or security issues. If Amazon has terminated access without the required notice and no exception applies, that procedural failure is a point in your complaint.
Mediation option (P2B): The P2B Regulation requires Amazon to identify mediators it is willing to engage with for unresolved disputes. This is a genuine alternative to an internal appeal or to arbitration under the BSA.
DMA obligations: Where Amazon is acting as a gatekeeper under the Digital Markets Act (DMA), its gatekeeper obligations may affect how it can treat business users. This is a more specialized lever, but worth flagging in your legal review if the restriction affects a core platform service.

Check each right against the facts of your notice:

Was a statement of reasons provided? Is it specific enough to respond to?
Has the internal complaint-handling path been opened in Seller Central?
If the action is a full termination, did you receive the required advance notice? If not, was an exception claimed?
Has Amazon identified mediators in its terms? Is the dispute one where mediation is a realistic tool?
Does the DMA apply to the specific service being restricted?

For a structured overview of how EU rules apply across the entire lifecycle of a marketplace dispute, our full-length guide on EU marketplace regulation for sellers covers each of these instruments in detail.

The steps above describe the standard procedural map. Your situation turns on the exact wording of the notice, the account history, and which EU instrument applies – which is exactly what we review first. To talk through the specifics, email info@tutamenlaw.com.

Phase 4 – Build your response or complaint file

Once you have classified the notice, secured the documentation, and mapped your procedural rights, you are ready to build the response. The structure of what you file depends entirely on which path Phase 1 and Phase 3 identified.

For a standard policy deactivation, the response is a Plan of Action (POA), structured around root cause, corrective action, and preventive measures. Each section must be specific to the facts Amazon cited. Generic plans – "we will improve our processes going forward" – are rejected because they do not demonstrate that the seller understood what triggered the deactivation.

Run through this checklist before you submit any POA or complaint:

Root cause: Does your root cause directly address the specific violation Amazon named, not a related or assumed one? If the notice cited a counterfeit complaint from a specific rights owner, the root cause section should address that complaint, not general inventory procedures.
Corrective action: Have you provided evidence of action already taken, not just actions you intend to take? Amazon's review teams respond better to completed steps ("we have removed all affected ASINs as of [date]") than to promised ones.
Preventive measures: Are the preventive measures proportionate to the stated violation, and do they address the systemic risk Amazon has implied? Overly elaborate prevention plans for a minor one-time listing error can signal that the seller does not understand the actual root cause.
Supporting documents: Are all documents referenced in the POA actually attached? Amazon's review teams frequently reject appeals because a referenced invoice, declaration, or certificate is not in the file.
Tone and length: Is the POA factual and structured, without apology language that implies broader fault than the facts support? Is it concise enough to be read by a reviewer in two to three minutes?

For a DSA internal complaint or a P2B-based complaint, the file structure is different. It should name the specific EU instrument you are relying on, identify the procedural failure (absent statement of reasons, missing notice period, inadequate complaint mechanism), and request a specific remedy – reinstatement, a compliant statement of reasons, or escalation to a mediator.

The GPSR responsible-person requirement is a common trigger for listing removals that sellers mistake for a policy deactivation. Our page on the GPSR responsible-person requirement and seller options covers the specific documentation steps in that context.

Phase 5 – Evaluate the decision points and trade-offs before you commit

Every Spanish marketplace suspension eventually reaches a fork: appeal through the standard Seller Central path, file a formal complaint under EU law, push for mediation, or accept the restriction and mitigate the damage. The right path depends on the type of restriction and what is still commercially available to you.

Here is how to think about the trade-offs:

If the notice is a policy deactivation with a clear, remediable root cause: The standard POA path is usually fastest. The risk is that a poorly constructed first POA closes off the second. If the first attempt failed, the internal review and complaint mechanism becomes the next realistic tool.
If the notice involves a DSA or P2B procedural failure: The formal complaint path is available independently of the standard appeal. Filing it does not foreclose the appeal; the two can run in parallel. A formal complaint also creates a written record that is useful if the dispute escalates to mediation or litigation.
If funds are frozen in addition to the account restriction: The funds question and the reinstatement question are procedurally separate. Address both, but in parallel – do not wait for account reinstatement before pursuing the funds.
If the restriction involves a GPSR or EPR compliance failure: Reinstatement depends on resolving the underlying compliance gap, not just explaining it. Filing a POA without the compliant documentation in hand is unlikely to succeed.
If the dispute is unresolved after internal channels: The P2B mediation path and, depending on the BSA version governing the account, the arbitration path under the BSA are both available. The BSA dispute-resolution mechanism depends on the version that applies to your specific account – we check this first before recommending any route.

If an initial appeal or formal complaint has already come back rejected, a fresh read of the response can identify the specific reason it failed and what is still open. Email info@tutamenlaw.com with the original notice and the rejection for an initial assessment.

Related areas

EU Marketplace Regulation – suspension, delisting, and compliance disputes across Amazon EU surfaces
EU marketplace regulation: the complete guide for sellers – DSA, DMA, P2B, GPSR in a single structured briefing

Frequently asked questions about Spanish marketplace suspension

How long does resolving Spanish marketplace suspension usually take on Amazon ES?

The timeline depends heavily on the type of restriction and the route taken. A straightforward policy deactivation with a well-evidenced Plan of Action can resolve in a matter of days, but complex cases – those involving regulatory compliance gaps, DSA internal complaints, or a second or third appeal – typically take several weeks. Where a formal P2B complaint or mediation is involved, the process runs longer. We work to compress timelines wherever the procedural options allow, but we do not promise specific resolution dates because the review pace is controlled by Amazon and, in complaint cases, by the complaint-handling process.

What are the main risks if I handle Spanish marketplace suspension alone?

The most common risk is misclassifying the notice and filing a Plan of Action when a formal EU complaint is the correct tool, or vice versa. A poorly structured first filing often receives a generic rejection and makes the second attempt harder. A second risk is missing the P2B or DSA procedural rights entirely – rights that give sellers documented leverage they would not otherwise have. A third risk is failing to preserve documentation in the early hours of a suspension, which makes later submissions harder to substantiate. In matters we handle, the cases that are most difficult to recover are those where two or three poorly constructed filings have already been made before a specialist reviews the account.

Do I need a lawyer for Spanish marketplace suspension?

Not always, but the situations where legal input changes the outcome are predictable. If the notice is a first-time, single-ASIN policy issue with a clear and documented fix, a seller with good Seller Central experience can often handle it. If the restriction is account-level, involves a DSA or P2B procedural right, implicates funds, or follows a rejected appeal, specialist input is worth the cost of the initial review. Tutamen's work is attorney-led and confidential, with fixed fees quoted up front after a short review of the account, so the cost of that first assessment is knowable before you commit.

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. To discuss your situation, email info@tutamenlaw.com.

Two grounded trust signals: every matter is handled by a qualified attorney from first review to final submission; all client communications and account information are treated as confidential from the moment of first contact.

Authored by Claire Donnelly – arbitration and disputes analyst at Tutamen.

Page authored by Claire Donnelly, Arbitration & Disputes 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.