Inside DSA rights for suspended sellers: the seller's real options

TL;DRThe Digital Services Act gives suspended marketplace sellers concrete procedural rights that did not exist under older EU rules – including the right to a statement of reasons, access to an internal complaint system, and, for Amazon sellers on Amazon IT and other EU surfaces, a pathway that sits entirely outside Amazon's standard appeal flow. These rights do not reinstate an account automatically, but they change the leverage position. What follows is a practitioner's account of how those rights work, what they require operationally, and where they fit against other tools available to an EU-suspended seller.

A suspension on Amazon IT looks, on the surface, like every other Amazon deactivation: the listings go dark, the disbursements stop, and Seller Central returns a notice that may say very little. The difference in the EU is that the law now requires more from the platform than a notice – and a seller who knows the procedural sequence can use that gap to create options that simply do not exist in the US market.

This analysis covers three things: what DSA rights for suspended sellers actually give you on Amazon IT; the realistic procedural path from suspension to resolution; and the decision points that determine which route is worth pursuing. If you are already familiar with the EU marketplace regulation landscape, you can move directly to the section on the internal complaint mechanism. If this is your first suspension on an EU surface, the full sequence matters.

What the DSA actually gives a suspended seller – and what it does not

The Digital Services Act is a mandatory transparency and accountability regime that applies to all intermediary services operating in the EU, with stronger obligations on Very Large Online Platforms (VLOPs) – a designation Amazon holds. For sellers, the operative provisions are not in the sections about harmful content; they are in the obligations around statements of reasons and internal complaint-handling that apply every time a platform restricts, suspends, or terminates a commercial user's account or listings.

Under the DSA, a VLOP must provide a statement of reasons when it restricts a seller. That statement must identify the ground for the restriction, specify whether a policy, legal rule, or algorithmic system was the trigger, and – critically – tell the seller what, if any, redress is available. This is qualitatively different from the generic performance-notification emails that have been the standard for suspended sellers on most platforms. The law creates a baseline floor of procedural transparency.

What the DSA does not do is override Amazon's substantive right to make commercial decisions about its marketplace. If Amazon deactivates an account for genuine fraud, counterfeiting, or a verified safety violation, the DSA does not require reinstatement. The rights it confers are procedural: the right to know the real reason, the right to challenge through a specific channel, and the right to access a form of redress that is not simply the same Seller Central appeal flow the seller has already exhausted.

In matters we handle on Amazon IT and other EU surfaces, the single most consistent finding is that sellers do not know these procedural rights exist. The practical consequence of that gap is that many sellers spend weeks cycling through Seller Central appeals – which Amazon is not legally required to treat as a DSA complaint – while the window for using the statutory internal complaint mechanism remains open but unused.

The DSA also interacts with the Platform-to-Business (P2B) Regulation, which preceded it and still governs specific transparency obligations around ranking, differentiated treatment, and the grounds on which a trading party can be suspended or terminated. For sellers on Amazon IT, both instruments are in play. They do not duplicate each other entirely: the P2B Regulation carries its own requirement for a minimum 30-day advance notice before termination of a business relationship (with exceptions for certain policy violations), and the DSA adds the statement of reasons and complaint-handling layer on top. Understanding which rule applies to which part of the seller's situation is a threshold question – and it matters, because the remedies and timelines differ. For a fuller treatment of how P2B interacts with the suspension process, our analysis on P2B regulation and the notice of suspension covers the mechanics in detail.

How does the DSA internal complaint mechanism actually work on Amazon IT?

The internal complaint-handling system required by the DSA is a separate channel from the standard Seller Central Performance Notifications workflow, and it carries its own procedural standards. Amazon, as a VLOP, must maintain this system, handle complaints free of charge, and process them in a timely manner – the DSA specifies a requirement for timely handling, though the precise calendar standard for any given case type depends on the platform's published complaint-handling policies at the time, which is a volatile detail worth verifying at the moment of filing.

In practice, the internal complaint mechanism is not a visible button in Seller Central. Sellers on Amazon IT who want to use it must identify the correct submission channel – which Amazon is required by the DSA to make accessible – and frame the complaint in terms the system recognizes as a DSA-based challenge, not a standard performance appeal. The framing distinction matters. An appeal that reads as a routine Plan of Action submission goes into Amazon's standard review queue. A complaint framed as a DSA-based challenge to the adequacy of the statement of reasons or the procedural fairness of the restriction process goes to a different review track, with different obligations on Amazon's side.

The DSA complaint must identify: the specific restriction being challenged; the ground for contending that the restriction violates the platform's obligations (inadequate statement of reasons, failure to follow the procedure for voluntary measures, algorithmic decision without human review where required, etc.); and the outcome sought. Vague complaints that simply say "I was suspended unfairly" do not satisfy the threshold, and in our experience they do not produce substantive responses. The complaint has to be precise about which DSA obligation the platform has failed to meet.

One autumn 2026 matter involved a fashion accessories FBA seller on Amazon IT whose account was deactivated following an automated product-safety flag. The standard appeal cycle had returned no meaningful explanation. We built a DSA-based internal complaint around the failure of the statement of reasons to identify the specific legal basis for the restriction and the absence of an explanation of the algorithmic trigger. Amazon's complaint-handling response identified the specific GPSR-related policy that had been applied and opened a remediation path that had not been available through the standard appeal flow. The account was restored after the seller addressed the underlying product-safety documentation. No outcome guarantee is implied; this is an illustration of the procedural sequence.

What role does the P2B Regulation play once a suspension has happened?

The Platform-to-Business Regulation is not superseded by the DSA – it remains in force and provides distinct grounds for challenge that complement the DSA's procedural rights. For Amazon IT sellers facing a suspension or a delisting decision, the P2B Regulation is relevant in three specific ways.

First, the P2B Regulation requires Amazon to include in its terms of service a clear, plain-language description of the grounds on which it may restrict or terminate a seller's account. If the suspension is not clearly covered by the stated grounds, that is a P2B argument. Second, the Regulation requires the platform to explain, in the notice of suspension or termination, which ground applies. Where the notice is vague or generic, that is both a DSA statement-of-reasons issue and a P2B transparency issue – two grounds running in parallel. Third, the P2B Regulation established the right to complain to a trade organization or association that has standing under the Regulation, adding a collective redress dimension that individual DSA complaints do not have.

For most individual sellers, the most actionable P2B lever is the transparency argument around the grounds for suspension – especially where Amazon's notice cites a policy category rather than the specific conduct alleged. In matters we handle, we regularly see suspensions that reference a broad policy umbrella without identifying what the seller actually did. That gap is useful: it forces a more specific response from the platform and can shift the frame from "did the seller violate the policy?" to "did the platform explain which violation it is alleging?"

The interaction between DSA and P2B obligations also touches the DMA. Amazon is a designated gatekeeper under the Digital Markets Act, which creates additional obligations around non-discriminatory access for business users. The DMA's relevance to individual suspension disputes is more limited than the DSA or P2B, but in cases involving systematic treatment of a category of sellers – for example, sellers whose products compete with Amazon's own private-label range – DMA non-discrimination arguments can reinforce a DSA/P2B challenge. For a structured overview of the EU regulatory landscape as a whole, the complete guide to EU marketplace regulation for sellers is the right starting point.

What are the realistic procedural steps for an EU-suspended seller on Amazon IT?

Mapping the correct procedural sequence is the most practical contribution a practitioner can make to a seller facing a DSA-era suspension. The sequence is not intuitive, and the wrong step at the wrong stage can foreclose options.

Step one: Analyze the notice. The statement of reasons is the document. If it is absent, incomplete, or identifies a legal basis that does not match Amazon's published policies, that is the first lever. The analysis looks at whether the notice meets DSA standards, whether P2B grounds for the restriction were stated, and whether the notice identified the appeal and complaint channels the platform is required to disclose.

Step two: Separate the Seller Central appeal from the DSA complaint. These are legally distinct channels. Filing a Plan of Action in Seller Central does not constitute a DSA internal complaint, and it does not start the clock on Amazon's complaint-handling obligations. Sellers who conflate the two often find that Seller Central appeals exhaust without ever triggering the statutory complaint process. In some cases, the Seller Central appeal is the right first move – particularly where the suspension involves a clear correctable root cause. In others, especially where the notice is inadequate or the deactivation appears systemic or algorithmic, leading with the DSA complaint preserves more options.

Step three: Build and file the DSA internal complaint. This requires identifying the correct submission channel on Amazon IT's platform, framing the complaint with precision, and documenting the statutory obligation Amazon has allegedly failed to meet. The complaint is not an appeal; it is a challenge to the procedural adequacy of how the restriction was imposed. The distinction matters for how Amazon routes and reviews the submission.

Step four: Assess escalation options. If the internal complaint does not produce a satisfactory response, the DSA provides for access to out-of-court dispute settlement through certified bodies. For Amazon IT, the relevant national Digital Services Coordinator and certified out-of-court settlement bodies are the escalation points. Regulatory complaints to the Digital Services Coordinator in the member state of the platform's EU establishment are a further option, particularly for cases involving apparent systematic non-compliance. The Digital Markets Act provides for European Commission jurisdiction over gatekeeper violations, relevant in pattern-of-conduct cases.

Step five: Parallel the commercial path. While the legal/regulatory track proceeds, the seller has a commercial interest in recovering inventory, mapping held balances, and deciding whether to rebuild on the same marketplace or shift volume to alternative EU surfaces. The legal steps and the commercial steps run concurrently; neither waits for the other to conclude.

The decision between leading with a Seller Central appeal, leading with a DSA complaint, or running both in parallel is the core strategic choice. In matters we handle, the answer turns on the nature of the deactivation notice, the account history, the type of policy alleged, and how much time has elapsed since the suspension. A clean notice with a specific correctable root cause usually runs through Seller Central first. An inadequate or generic notice often goes to the DSA channel first. A notice that cites a legal obligation under the General Product Safety Regulation (GPSR) or another EU-specific statute needs both tracks coordinated, because the underlying substantive issue and the procedural challenge are intertwined.

A seller who has already filed one Seller Central appeal without success is not necessarily out of options. The DSA complaint channel is independent of Seller Central and remains available. The question is whether the notice was procedurally adequate and, if not, what the most precise challenge looks like – which is what we review first.

If a first Seller Central appeal came back rejected without explanation, the DSA's statement-of-reasons requirement may itself be the argument: a rejection that provides no reasoning may not meet the platform's obligation to explain the basis for maintaining the restriction. This is a distinct ground from the substantive merits of the original suspension, and it opens a second lane that many sellers – and many generalist advisers – miss.

For sellers who want to work through the preliminary checks before engaging external counsel, the pre-action checklist for P2B dispute resolution sets out what to gather and confirm before filing anything.

The seller's decision points: trade-offs and the realistic range of outcomes

The DSA does not guarantee reinstatement. That is the honest framing that any seller needs to hear before committing to this path. What it does is create enforceable procedural standards that a VLOP must meet when restricting a business user – and where those standards are not met, it creates grounds for challenge that did not exist before the DSA came into force. The realistic range of outcomes spans from full account restoration, to partial remediation (some listings reinstated, others not), to a reasoned confirmation that the restriction is valid, to escalation through out-of-court settlement or regulatory complaint.

The decision tree for an Amazon IT seller looks roughly like this: if the notice cites a specific EU-law-based ground (GPSR, product safety, fraudulent activity) and the underlying conduct is contested, the route is a DSA complaint challenging the adequacy of the statement of reasons, combined with substantive evidence addressing the cited ground, on a timeline that depends on the platform's complaint-handling pace and the complexity of the underlying issue. If the notice cites a policy violation but provides no specifics, the route is a DSA challenge to the statement of reasons itself, which may produce a more specific notice – and with specificity comes the ability to respond on the merits. If the notice is technically compliant but the underlying decision appears incorrect, the route is a parallel Seller Central appeal and DSA complaint, with the Seller Central path leading where the root cause is addressable and the DSA path reserved for the procedural track.

The myth we encounter most often is that EU sellers have no leverage once a platform suspends them. That was closer to the truth before the DSA came into force. It is not the situation today. The DSA creates real procedural obligations on VLOPs, and a seller who uses the statutory channels correctly is in a materially better position than one who cycles through Seller Central without knowing the complaint mechanism exists. Leverage is not certainty of outcome – but it is the ability to force a substantively reasoned response, and that is more than the pre-DSA position offered.

The attorney-led, confidential structure of how Tutamen approaches these matters means that the DSA complaint is built and filed as a legal document, not as a seller-authored narrative, which changes how Amazon's compliance function handles the submission. Fixed fees are quoted up front after a short review of the deactivation notice and account history, so there is a clear cost-to-benefit frame before any commitment is made.

A second illustrative matter: a consumer electronics distributor on Amazon IT (spring 2026) had three ASIN listings suspended following an intellectual property complaint filed through Brand Registry. The standard dispute process had stalled. We ran a parallel DSA challenge on the adequacy of the statement of reasons and a P2B-based argument that the grounds for the restriction had not been clearly stated in Amazon's terms as a basis for the type of listing removal applied. The combination produced a more specific explanation from the platform's complaint-handling team and ultimately allowed the distributor to address the underlying IP documentation issue. Two of the three listings were restored. The third remained suspended on a distinct and valid substantive ground. Qualitative outcome, no numbers implied; this illustrates the limits as well as the uses of the DSA path.

Where the DSA path connects to broader EU marketplace regulation

The DSA does not operate in isolation. For sellers on Amazon IT specifically, the regulatory environment in 2026 includes the DSA, the P2B Regulation, the DMA (gatekeeper obligations), the General Product Safety Regulation (GPSR) as a substantive compliance trigger, and Extended Producer Responsibility (EPR) obligations that can themselves generate account restrictions if not met. A suspension that appears to be a policy or IP issue may, on closer examination, be driven by a GPSR or EPR non-compliance flag – and the DSA challenge needs to address the actual ground, not the presented label.

The DSA's algorithmic accountability provisions are also relevant for sellers whose suspensions appear to be automated. Where a restriction is imposed by an automated system without human review, the DSA creates specific obligations around transparency and, in certain contexts, the right to human review of the decision. For Amazon IT sellers hit by automated bulk deactivations – which we see regularly in enforcement sweeps across categories like electronics, health products, and toys – the question of whether human review was applied is a live DSA issue, not just a factual background point.

The DMA gatekeeper obligations add a non-discrimination dimension. Amazon is required under the DMA not to treat its own retail arm more favorably than third-party sellers on its platform in comparable situations. Where a suspension affects sellers in a product category where Amazon also sells – and where the suspension appears to track competitive sensitivity rather than genuine policy violation – the DMA non-discrimination argument can run alongside the DSA and P2B channels. These are systemic cases rather than individual-seller matters, but individual sellers can contribute evidence to a coordinated complaint filed through a trade organization with P2B standing.

The practical integration of all these tools is what distinguishes a well-constructed EU suspension challenge from a Seller Central appeal with a DSA label attached. In matters we handle on Amazon IT and other EU surfaces, we build a statement-of-reasons and internal-complaint case, assess which of the DSA, P2B, and DMA levers apply, and use the escalation paths – Digital Services Coordinator, out-of-court settlement, or regulatory complaint – where the internal complaint process does not produce a compliant response. That sequence, run correctly, is what the law makes available to a suspended seller in the EU today.

Related areas

• EU Marketplace Regulation – complete guide – the full EU regulatory landscape for marketplace sellers
• P2B Regulation and suspension notices – procedural rights and options under the P2B Regulation
• P2B dispute resolution pre-action checklist – what to prepare before filing any EU challenge

If you have received a suspension notice on Amazon IT or another EU surface and want a read on whether the DSA and P2B grounds apply, email info@tutamenlaw.com with the notice and a short account of what has already been filed. The first review confirms which channels are still open and what, if anything, a DSA complaint can realistically achieve in your situation.

FAQ: DSA rights for suspended sellers on Amazon IT

How long does resolving DSA rights for suspended sellers usually take on Amazon IT?

The timeline depends heavily on the route taken and the complexity of the underlying suspension. A DSA internal complaint filed through the correct channel typically draws a substantive response within several weeks under the platform's complaint-handling obligations, though the DSA does not specify a fixed calendar deadline applicable to every case type. Where the internal complaint produces a satisfactory resolution, the overall process can conclude within weeks of filing. Where escalation to an out-of-court dispute settlement body or a Digital Services Coordinator complaint is required, the timeline extends materially – typically to several months. Running a parallel Seller Central appeal alongside the DSA complaint can shorten the overall resolution if the appeal succeeds, but it does not change the DSA complaint timeline.

What are the main risks if I handle DSA rights for suspended sellers alone?

The primary risk is conflating the Seller Central appeal with the DSA internal complaint, which means the statutory complaint is never filed and the procedural rights under the DSA are never triggered. A second significant risk is framing the complaint in generic terms – a vague challenge to unfair treatment does not satisfy the DSA's threshold and typically produces a templated response. A third risk is failing to identify which ground – DSA, P2B, DMA, or a substantive regulatory compliance issue – actually drives the suspension, leading to a challenge that addresses the wrong question. Each of these errors can close procedural options or create a record that complicates a later escalation.

Do I need a lawyer for DSA rights for suspended sellers?

You are not required to have a lawyer, but the DSA internal complaint process involves a legal document making specific claims about a platform's failure to meet statutory obligations – which is different in kind from a Seller Central appeal. An incorrectly framed complaint may produce a response that forecloses later escalation. In matters we handle, the distinction between a complaint that forces a substantive response and one that results in a pro-forma acknowledgment often comes down to the precision of the legal framing. Whether that precision requires external counsel depends on your familiarity with the DSA obligations, the complexity of the suspension, and how much is at stake commercially.

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 builds DSA internal complaints, P2B-based suspension challenges, and regulatory escalations as attorney-prepared legal documents – not seller-authored narratives – which changes how platform compliance functions handle the submission. 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 Dmitri Aronov – Partner, EU Marketplace Regulation | Published August 19, 2026

Page authored by Dmitri Aronov, Partner, EU Marketplace Regulation, Tutamen.