DSA rights for suspended sellers: what it means for marketplace sellers

A suspension on Amazon Italy can feel like a closed door. The listings go dark, the disbursements stop, and the notice that arrives in Seller Central is terse enough to leave a seller genuinely uncertain whether any route back exists. That uncertainty is the problem this analysis addresses.

TL;DRUnder the Digital Services Act (DSA), Amazon – as a designated Very Large Online Platform (VLOP) – must give sellers a statement of reasons for any suspension or delisting, operate an accessible internal complaint-handling system, and permit access to out-of-court dispute settlement. Those obligations create real procedural leverage that EU sellers can use; the appeal path is not optional for the platform to offer.

This analysis works through what those DSA rights actually mean in practice on Amazon IT: what triggers them, what the complaint and escalation path looks like step by step, and where the decision points are for a seller choosing between internal complaints, out-of-court dispute settlement, and regulatory engagement. The Platform-to-Business (P2B) Regulation sits alongside the DSA and adds its own procedural requirements; both are addressed here where they interact.

Why the DSA changes the position of a suspended seller on Amazon IT

The DSA transforms the suspended EU seller's position because it shifts the legal burden onto the platform to justify its action, rather than placing the entire burden on the seller to prove innocence.

Before the DSA applied to Amazon as a VLOP, a suspended seller's main recourse was the platform's own internal appeals process – a mechanism entirely within the platform's design and discretion. A seller could draft a Plan of Action, resubmit, and wait. The platform was not legally required to explain its reasoning in any standardized format, nor to route the dispute to an external body. In matters we handle on Amazon IT, that asymmetry produced outcomes that were hard to predict and harder to contest systematically.

The DSA changes that calculus in three specific ways. First, a statement of reasons is mandatory. The platform must identify the specific ground for the restriction, the legal or contractual basis it relies on, and whether automated decision-making was involved. Second, the internal complaint-handling system must be accessible and effective – not a nominal channel. Third, sellers have a route to certified out-of-court dispute settlement bodies that operate independently of the platform. These are not informal goodwill gestures; they are obligations enforceable by national Digital Services Coordinators and, at EU level, by the European Commission.

For a seller on Amazon IT, the relevant Digital Services Coordinator is the Italian authority. The existence of that national regulator creates a background pressure that did not exist under the pre-DSA environment. Platforms facing scrutiny from a national regulator have a compliance incentive to take the internal complaint path more seriously. That is the opening a well-constructed complaint can use.

It is also worth being precise about scope. The DSA rights described here apply to restrictions on the seller's service – suspensions, delistings, account terminations. They are distinct from individual product-level enforcement actions that may be governed primarily by the General Product Safety Regulation (GPSR) or Extended Producer Responsibility (EPR) rules, though a product-safety-based account suspension can trigger DSA complaint rights alongside those product-specific processes. For the full regulatory picture, our complete guide to EU marketplace regulation for sellers maps how these regimes interact.

What does a DSA statement of reasons actually tell you?

A DSA statement of reasons is the starting document for any challenge, and what it contains – or conspicuously omits – determines the strategy from the first step.

The DSA requires the statement to include: the specific restriction imposed; the grounds on which the platform relied; identification of the contractual or legal basis; and, where the decision was made wholly or partly by automated means, a statement to that effect. On Amazon, the statement of reasons typically maps to the suspension notice in Seller Central, but the quality and detail of that notice varies considerably. In practice, we regularly see notices that cite a policy category – "related account" or "inauthentic items" or "review manipulation" – without explaining the specific conduct alleged or the evidence the platform relied on. A statement of reasons that does not meet the DSA's specificity standard is itself challengeable.

Why does the level of specificity matter? Because the internal complaint and any out-of-court settlement submission need to engage with the stated reasoning. A complaint that addresses a vaguely described ground is harder to anchor. A complaint that identifies that the statement of reasons was legally deficient – and therefore that the restriction was procedurally flawed – operates on a different and often more powerful footing. The platform is then in the position of either improving the statement (which requires it to articulate its case more precisely) or defending a suspension that it inadequately documented.

For sellers who received a suspension before the DSA's obligations applied to Amazon as a VLOP, the picture is more complex. The DSA applies to restrictions imposed while those obligations are in force; earlier decisions may not carry the same statement-of-reasons entitlement, though P2B Regulation requirements on notice and grounds were already in place before the DSA for many business users. The interaction of the two instruments is addressed further below.

One question sellers ask often: what if the platform cites an automated system but provides no further detail? The DSA's transparency requirement for automated decision-making is precisely intended to address this. A bare reference to automated detection without any further identification of what the system flagged, and why the platform considers the flag sufficient grounds for suspension, does not meet the standard. That gap is a complaint ground in its own right.

How the DSA internal complaint path works in practice

The internal complaint-handling system is the mandatory first step, and on Amazon IT, the path runs through Seller Central's established appeal and escalation channels – but the DSA requires those channels to be effective, not merely nominal.

A DSA-grounded internal complaint is structurally different from a standard Plan of Action. A Plan of Action addresses root cause, corrective action, and preventive measures – it is framed as the seller's explanation of what went wrong and what they will do differently. A DSA-grounded internal complaint is framed as a challenge to the platform's decision: it identifies the legal and procedural obligations the platform carries, asserts specifically where the statement of reasons is deficient or where the decision is disproportionate or unfounded, and requests a substantive review by a human decision-maker if the original decision was automated. Those are different documents with different purposes, and conflating them is one of the most common mistakes sellers make when they handle EU suspension appeals without specialist input.

The practical sequence typically runs as follows. The seller reviews the statement of reasons and identifies every specific ground the platform stated. The complaint then addresses each ground in turn: if the ground is factually contested, the complaint sets out the evidence; if the ground is procedurally deficient, the complaint identifies the deficiency. Where the DSA's automated-decision-making transparency requirement has not been met, the complaint explicitly requests the additional information required. The complaint closes with a specific ask: reinstatement of the account, or at minimum a fully reasoned response that meets the DSA standard, within a stated period.

The realistic timeline for an internal complaint response varies. The DSA does not prescribe a fixed response deadline for internal complaints in the way some other instruments do, but it does require the system to be "timely." In matters we handle, internal complaint cycles on large platforms tend to run over several weeks, sometimes longer. That is relevant to a seller managing inventory, suppliers, and cash flow – the commercial cost of downtime does not wait for the complaint cycle to complete. Flagging urgency, with specific commercial evidence, is part of how a well-structured complaint is built.

If the internal complaint does not produce a satisfactory outcome, the DSA's out-of-court dispute settlement route opens. That path is addressed in the next section.

Out-of-court dispute settlement: when it becomes the right tool

Out-of-court dispute settlement under the DSA is a distinct mechanism, and for Amazon IT sellers it represents a substantive escalation path that did not exist before the DSA applied.

The DSA requires Very Large Online Platforms to make out-of-court dispute settlement available through certified bodies – bodies certified by the relevant national Digital Services Coordinator as meeting independence, expertise, and procedural fairness standards. The platform is required to engage in good faith with the process; it cannot simply ignore a referral. Importantly, the outcome of out-of-court settlement is not binding on the seller in the same way arbitration under the Amazon Business Solutions Agreement (BSA) may be – the seller retains the ability to pursue other routes afterward, whereas the platform's obligation to engage in good faith is a live one throughout the process.

When does this route become the right tool? In our practice, out-of-court settlement is most useful where the internal complaint has been refused or has produced a response that fails to engage with the specific grounds raised, where the seller has a documented, well-evidenced case that needs a neutral reviewer, or where the scale of commercial impact justifies the time and cost of the process. It is not the right first move when the internal complaint path has not been exhausted – platforms can and do raise that procedural point, and a premature referral can weaken the seller's position.

The interaction with the BSA dispute-resolution mechanism matters here. The path available to a seller depends on the version of the BSA that applies to their account, which we check first in every EU matter. Where the BSA's dispute-resolution terms and the DSA's out-of-court settlement route overlap or conflict, the DSA's requirements as a mandatory EU-law instrument take precedence in the EU context – a platform cannot contract out of DSA obligations. For sellers navigating both sets of rules at once, the analysis of DSA rights across other EU marketplaces provides useful comparative context.

A mid-sized electronics accessories seller on Amazon IT (winter 2025) came to us after receiving a suspension citing inauthentic items – a ground the seller firmly disputed. The internal appeal had been rejected with a formulaic response that did not address the specific supply-chain documentation the seller had submitted. We reconstructed the complaint as a DSA-grounded challenge, identified that the statement of reasons had not met the specificity requirement for the automated component of the decision, and filed a structured internal complaint with a parallel notification to the national Digital Services Coordinator pathway. The account was restored following a substantive review, within a timeline of several weeks.

That sequence illustrates the decision architecture: internal complaint first, with a DSA framing rather than a standard POA framing; escalation to out-of-court settlement if the response is insufficient; regulatory notification as a background lever that creates compliance incentive for the platform. The seller's decision at each step turns on how much the internal response engaged with the actual grounds, and what additional evidence or procedural argument is available.

How the Platform-to-Business Regulation sits alongside the DSA

The P2B Regulation provides a complementary layer of procedural protection, and understanding how it interacts with the DSA prevents sellers from overlooking rights that may be easier to invoke in a given situation.

The P2B Regulation requires platforms to give business users notice before restricting or terminating their access to the platform's services, to explain the grounds, and to provide access to an internal complaint-handling system. Those obligations were in force before the DSA applied to Amazon as a VLOP, and they continue to apply alongside the DSA. In practice, the P2B Regulation's notice requirements mean that an immediate suspension without prior warning – as opposed to a restriction following a policy violation notice – may itself be a P2B compliance issue, independent of whether the DSA statement of reasons is adequate.

In our experience handling EU marketplace matters, the P2B Regulation's notice and grounds requirements are underused by sellers who focus exclusively on Amazon's own internal policy framework. A seller who has received a suspension with inadequate or absent prior notice has a P2B complaint ground that can be raised in parallel with a DSA internal complaint. The two instruments address overlapping but distinct procedural obligations; using both where they apply strengthens the overall complaint.

The Digital Markets Act (DMA) is a third instrument that applies to Amazon as a designated gatekeeper. The DMA's focus is on fair and contestable markets at the structural level – it is not a seller-dispute instrument in the same way the DSA is – but where a suspension appears to be connected to Amazon's self-preferencing practices or to gatekeeping behavior in the DMA sense, flagging the DMA dimension adds regulatory context to the complaint. For sellers with distribution or pricing disputes that have precipitated a suspension, the DMA angle can be relevant. Our analysis of the P2B Regulation's notice requirements addresses the procedural ground in more detail.

The seller's decision points and realistic trade-offs

Every suspended EU seller faces a sequence of decisions, and the trade-offs at each step are specific to the facts of the account, the wording of the notice, and the commercial timeline.

The first decision is whether to treat the suspension as a standard Amazon appeal or as an EU-law complaint. That choice shapes the document, the framing, and the escalation path available afterward. A standard Plan of Action that does not invoke DSA or P2B grounds does not foreclose those grounds entirely, but it does mean that a first filing may be consumed without engaging the most powerful levers available. In matters we handle on Amazon IT, the combination of a well-evidenced factual response with a clear DSA procedural challenge consistently produces more substantive platform engagement than a POA alone.

If the notice cites a conduct-based ground – inauthentic items, review manipulation, related-account linkage – the internal complaint route is almost always the right first move, with a full evidential dossier addressing the specific allegation and a DSA challenge to any procedural deficiency in the statement of reasons. The realistic timeline is several weeks for a substantive response. If instead the notice is effectively a termination without meaningful grounds – a bare reference to a policy category with no further explanation – the P2B notice deficiency and DSA statement-of-reasons deficiency are both live from day one, and the complaint should address both immediately.

If an internal complaint is rejected with a substantive engagement – the platform explains why it disagrees with the seller's evidence – that response itself becomes the basis for an out-of-court settlement submission, where the seller has a stronger evidential record than before. If the rejection is formulaic or non-responsive, the case for out-of-court settlement is even clearer: the platform has failed the "effective internal complaint-handling" standard.

The myth that EU sellers have no leverage once a platform suspends them is exactly that – a myth. The DSA and P2B Regulation together create a procedural architecture in which the platform must justify its decision, must engage with complaints, and must provide access to external review. What sellers often lack is not leverage but the framing to deploy it. That is what specialist representation provides: the ability to build the statement-of-reasons challenge, the DSA-grounded complaint, and the out-of-court settlement submission as a connected sequence, rather than three separate attempts at the same door.

A clothing brand seller on Amazon IT (spring 2026) came to us after two rejected Plan of Action submissions. Neither submission had identified the DSA framing or the P2B notice deficiency in the original suspension. We reviewed the original notice, identified a grounds specificity failure, and rebuilt the complaint around the DSA and P2B procedural obligations. The account was restored following a further review cycle. The prior rejections had narrowed some options but had not closed the DSA route.

The bridge between completing internal steps and deciding whether to escalate is a short review of what the platform's responses actually said. If they engaged with the evidence: the evidential case may need to be stronger. If they did not engage: the escalation argument is already built. For a review of your account's current position, email info@tutamenlaw.com.

What EU regulatory enforcement adds to the picture

EU regulatory enforcement runs in the background of every DSA complaint, and understanding how it works gives sellers a clearer sense of how the overall system creates compliance pressure on platforms.

The European Commission has direct enforcement authority over VLOPs including Amazon for systemic DSA violations. National Digital Services Coordinators – in Italy, the relevant authority – handle complaints and enforcement at the member-state level for matters that do not rise to the systemic level. A seller's DSA complaint does not automatically trigger a regulatory investigation, and the Commission's and national coordinators' enforcement priorities are set at a systemic level. However, the existence of active enforcement creates a genuine compliance environment: a platform that routinely fails to meet its statement-of-reasons or internal complaint obligations faces regulatory exposure, not merely reputational criticism.

Sellers can notify the relevant national Digital Services Coordinator of a suspected DSA violation as part of their overall strategy. That notification does not itself produce a reinstatement – regulatory proceedings are not a substitute for the internal complaint and out-of-court settlement path. But it creates a documented record of a compliance concern, and in some matters it provides additional incentive for the platform to engage substantively with the outstanding complaint. The decision whether to notify the regulator in parallel with an ongoing complaint is a judgment call that depends on the specific facts; we advise on it as part of the overall EU matter strategy.

The Bundeskartellamt's proceedings against large platforms under its own national rules (Section 19a proceedings, generic reference) operate in parallel in Germany and have influenced how platforms approach market-dominance-linked compliance across the EU. For sellers on Amazon DE, those proceedings add a further regulatory dimension. For Amazon IT sellers, the Italian competition authority's approach to marketplace conduct is the more immediately relevant background. Neither set of proceedings is a direct reinstatement mechanism, but they inform the overall environment in which DSA complaints are evaluated.

Common mistakes that cost sellers their DSA leverage

In our EU marketplace practice, a consistent set of avoidable mistakes limits the options available to sellers who arrive after a first or second filing has already been submitted.

Filing a standard Plan of Action without any reference to DSA or P2B grounds is the most common. The POA framing places the seller in a position of explaining and apologizing; the DSA framing places the platform in a position of justifying its decision. Starting with the POA framing alone, especially for a suspension whose grounds are vague or procedurally deficient, concedes the starting position unnecessarily.

Failing to preserve evidence early is a close second. The statement of reasons, the original suspension notice, all correspondence in Seller Central, the account health metrics at the time of suspension – all of these are part of the record for an internal complaint and any out-of-court settlement submission. Sellers who contact us after having cleared their Seller Central notifications or who cannot produce the original notice are in a harder position than those who preserved everything from day one.

Treating the out-of-court settlement route as a last resort to be invoked only when all else has comprehensively failed can mean that the route is used when the seller's evidential record is weakest, rather than at the point of optimal evidential strength. The better approach is to build the record through the internal complaint cycle precisely so that the out-of-court settlement submission, if needed, is based on a complete documented exchange.

Finally, assuming that EU regulatory tools do not apply because the account is on the Italian marketplace rather than a "main" EU marketplace is a factual error. Amazon IT is covered by the DSA's VLOP designation, and all of the procedural rights described in this analysis apply to sellers operating on that surface in the same way they apply on other EU Amazon marketplaces.

Related areas

• EU Marketplace Regulation – full practice area for DSA, P2B, DMA and EU suspension disputes
• Amazon Account Reinstatement – account deactivation, Plan of Action drafting, and appeal for all surfaces

If a first or second submission has already been rejected, and the responses did not engage with the specific DSA or P2B grounds, there is often still a route open. A second review can identify exactly what the platform's responses said – and did not say – and whether escalation is warranted. To discuss your Amazon IT suspension, email info@tutamenlaw.com.

Frequently asked questions

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

There is no single timeline, and the honest answer is that it depends on the complexity of the grounds and how the platform engages at each stage. An internal complaint cycle typically runs over several weeks from submission to substantive response. If the matter escalates to out-of-court dispute settlement, the process takes longer – the certified body's own procedural timeline adds to the overall period. Regulatory notification runs on an independent timeline and is not a reinstatement mechanism in itself. Commercial urgency, evidenced specifically, can influence the pace of internal complaint handling. The most important variable is how well-structured the initial complaint is; a clearly framed, well-evidenced filing tends to receive a more substantive – and therefore more useful – response than a generic one.

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

The primary risk is filing on the wrong legal framing. A seller who submits a standard Plan of Action without invoking DSA or P2B procedural grounds does not benefit from the platform's corresponding obligations to meet those standards. A seller who exhausts the internal complaint round without building a documented record suitable for out-of-court settlement finds that the escalation route is harder to use. Preservation of evidence is another risk area: sellers who do not retain all Seller Central correspondence, the original notice, and account health records from the time of suspension may find that critical documents are no longer accessible. Finally, misreading what the platform's rejection actually says – confusing a formulaic response with a substantive one – can lead to repeatedly filing the same type of appeal instead of escalating at the right point.

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

Not every DSA-related complaint requires specialist legal input, but the cases where a lawyer adds the most value are precisely those where the standard internal appeal has already failed or where the grounds of suspension are contested rather than accepted. The DSA framing – identifying the specific procedural obligation the platform failed to meet, structuring the complaint as a legal challenge rather than an explanation, and advising on whether out-of-court settlement or regulatory notification is the right next step – is the area where legal expertise changes the trajectory of the matter. For sellers with a straightforward reinstatement path on a clearly stated, accepted ground, a structured POA may be sufficient. Where the ground is disputed, vague, or procedurally deficient, the DSA and P2B levers require specialist deployment to be effective. Attorney-led, confidential work with fixed fees quoted up front is the model Tutamen operates on for EU marketplace matters.

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 matters are handled on a fixed-fee basis, with a scoping review before any commitment. To discuss your situation, email info@tutamenlaw.com.

Analysis by Claire Donnelly – arbitration & disputes analyst, 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.