Responding to DSA rights for suspended sellers the right way

When Amazon IT suspends a seller account, the commercial damage begins immediately. Listings go dark, inventory sits in Italian fulfillment centers, and disbursements stop. What most sellers on Amazon's Italian marketplace do not realize is that the Digital Services Act and the Platform-to-Business Regulation give them enforceable procedural rights that the platform must respect – rights that, used correctly, change the calculus of an appeal.

TL;DREU marketplace suspension rules require Amazon IT to provide a statement of reasons before or at the point of restriction, to operate an internal complaint-handling system, and to apply measures proportionate to the identified breach. A suspended seller on Amazon IT has a defined path: review the statement of reasons, file an internal complaint, pursue mediation if the complaint fails, and – where appropriate – use national regulatory or judicial routes. Missing or misusing any step reduces what is still open.

This guide walks through each stage in sequence, identifies the decision points where sellers most often lose ground, and explains where legal involvement changes the outcome. The steps apply specifically to Amazon IT accounts, but the underlying DSA and P2B framework is EU-wide.

What DSA rights for suspended sellers actually mean on Amazon IT

The Digital Services Act imposes concrete obligations on Amazon as a Very Large Online Platform, and those obligations translate into specific rights the suspended seller can invoke. The most important for a suspended Amazon IT seller are the right to a statement of reasons, the right to use the platform's internal complaint-handling system, and the right to out-of-court dispute settlement through a certified mediator.

A statement of reasons is not simply a notification email. Under the DSA, it must set out the facts or circumstances that led to the restriction, the legal or contractual basis relied on, and – where the decision was taken with the involvement of automated means – that fact. On Amazon IT, the suspension notice a seller receives in Seller Central is the platform's attempt to discharge this obligation. In practice, these notices vary significantly in quality. Some specify the policy ground with enough precision to write a targeted response. Others are templated to the point of uselessness. The first task in any Amazon IT DSA suspension response is reading the notice against the DSA's requirements and identifying what it says, what it omits, and whether the stated basis is proportionate.

Proportionality matters. The DSA does not prohibit platforms from restricting access, but it does require that the measures taken correspond to the seriousness of the breach. A seller suspended entirely for an isolated listing violation has a different proportionality argument than one whose account was deactivated after a pattern of policy breaches. This distinction shapes whether the internal complaint focuses on procedural deficiency, substantive error, or disproportionate remedy.

The Platform-to-Business Regulation layers on additional protections, including minimum notice periods for terminations and restrictions on grounds considered. For sellers whose accounts have been running on Amazon IT for some time, the P2B framework is often the more immediately useful instrument – particularly where the suspension notice falls short of the notice period the regulation requires. For a detailed breakdown of how P2B interacts with Amazon suspension procedures, our P2B Regulation notice-of-suspension analysis sets out the parallel procedural points.

In matters we handle involving Amazon IT, the statement of reasons is often the central document. A notice that fails to identify the specific conduct, references only a policy section number, or attributes the decision solely to automated detection without further explanation gives the seller a substantive procedural complaint – one that must be made through the right channel at the right time.

How does the internal complaint process actually work?

Amazon's internal complaint-handling system is the mandatory first step after receiving a suspension notice, and the DSA requires the platform to process complaints in a timely, non-discriminatory, and diligent manner. Filing it correctly is not the same as sending a Plan of Action through Seller Central's standard appeal interface.

The formal DSA complaint is a distinct communication. It identifies the contested restriction by reference to the statement of reasons, articulates the specific legal or factual error in the platform's decision, and – where proportionality is at issue – explains why the restriction exceeds what the stated breach would justify. Attaching evidence is standard practice. So is requesting a human review of any automated decision, which the DSA explicitly protects.

What goes wrong at this stage? Several things, in our experience. The most common failure is conflating the internal complaint with a standard Amazon appeal. A seller who responds through the regular Seller Central appeal path, submitting a Plan of Action focused on corrective action, may never formally invoke the DSA complaint-handling route at all. That matters for two reasons: the DSA timeline for processing a complaint starts from the complaint, not from the first appeal; and a decision on a formal DSA complaint is a separate document that can itself be challenged through mediation.

A second common error is mischaracterizing the root cause. The internal complaint is not an admission of wrongdoing with a promise to do better. It is a legal challenge to a platform decision. Framing it as the former – which many Seller Central templates implicitly encourage – concedes grounds the seller does not have to concede. This is particularly true on Amazon IT, where the automated enforcement systems have at times flagged accounts for IP or authenticity issues based on cross-marketplace signals that are not straightforwardly applicable to the Italian storefront.

Timing is the third factor. The DSA does not set a fixed window for filing an internal complaint in the same way that some national procedural rules specify limitation periods, but delay weakens the position on proportionality. The longer a seller waits without formally challenging the restriction, the harder it becomes to argue that the suspension has already exceeded a proportionate duration.

What is the realistic procedural path after the internal complaint?

If the internal complaint does not resolve the suspension, the DSA provides for out-of-court dispute settlement through a certified dispute settlement body. This route is available to sellers – particularly business users under the P2B framework – and is distinct from arbitration under the Business Solutions Agreement. The path depends on the BSA version that applies to the account, which we check first before advising on which route is best positioned to move the matter.

Out-of-court settlement through a certified DSA body is not automatic. The seller must identify a body that the relevant EU member state has certified for the category of dispute, initiate the process, and present the matter in a way the body can evaluate. Amazon is required to engage in good faith, but the outcome is not binding in the same way a court judgment is. That said, the process has real leverage: it creates a formal record of the dispute, establishes a timeline of platform non-responsiveness if Amazon fails to engage, and generates documentation that supports follow-on judicial or regulatory action.

Mediation and regulated dispute resolution procedures are not the only downstream options. National consumer and market supervisory authorities in Italy – and the DSA's coordinating Digital Services Coordinator mechanism – can receive complaints about platforms that fail to comply with their DSA obligations. A well-documented internal complaint failure, escalated to the appropriate authority, creates regulatory exposure for the platform that informal complaints do not. Sellers should not underestimate this channel, especially where the suspension decision has procedural deficiencies that the platform has refused to correct.

For sellers whose accounts are also active on other EU surfaces, the dispute can intersect with the Digital Markets Act's gatekeeper obligations, particularly where Amazon's decision applies across storefronts in ways that affect market access. This cross-surface dimension is more relevant for larger brands than for single-marketplace sellers, but it is worth mapping at the outset. Our complete guide to EU marketplace regulation for sellers covers the interaction between the DSA, DMA, and P2B framework in detail.

Does the suspended seller on Amazon IT always need to exhaust all these steps? No. In many matters, a well-framed internal complaint that correctly identifies the procedural deficiency in the statement of reasons produces a response – and sometimes a reinstatement or partial restoration – within weeks. The broader procedural ladder is the fall-back, not the default route. The decision of when to escalate, and to which body, is one of the critical judgment calls.

Where does this go wrong – and why sellers lose ground they didn't have to lose

A suspension under EU rules can feel final, and the appeal path is genuinely unclear to most sellers. That combination – urgency plus opacity – produces predictable errors. Understanding them is part of mounting an effective response.

The first place sellers lose ground is in the initial response to the suspension notice. Responding quickly is the right instinct; responding through the wrong channel with the wrong framing undoes the advantage the DSA creates. A template Plan of Action that accepts the stated basis for suspension, commits to training and monitoring, and asks for a second chance has very little procedural weight under the DSA framework. It is not engaging with the statement of reasons. It is not requesting human review of an automated decision. It is not a formal complaint. And once that response is on record, the seller has implicitly accepted the accuracy of the platform's stated basis – which narrows the argument in any formal complaint that follows.

The second failure point is incomplete evidence. The DSA complaint process is evidence-led. Assertions that the suspension is wrong are less useful than documented proof: business records showing the product's supply chain, correspondence establishing authorization from brand owners, order histories demonstrating the pattern that contradicts the platform's automated finding. Building this file takes time that sellers often do not spend before responding, because the first response goes out in the immediate aftermath of suspension, before the evidence is assembled.

Third, and frequently underestimated: the proportionality argument is abandoned too early. Many sellers who accept that there was some policy issue – a listing error, a delayed response to a customer complaint – assume the suspension is therefore correct. But proportionality is separate from liability. Even if the underlying infringement was real, a full account suspension may be disproportionate where a listing removal or a temporary restriction would have addressed it. This argument is available in the internal complaint, and it is the argument most frequently left out.

A mid-market electronics reseller on Amazon IT (winter 2026) reached us after filing two standard Seller Central appeals that were both rejected with identical auto-responses. The account had been deactivated on authenticity grounds. The seller's supplier had all required documentation. We reviewed the original suspension notice, identified that it was based entirely on automated detection without the disclosure the DSA requires, filed a formal internal complaint on that basis alongside the supplier documentation, and requested human review explicitly. The account was restored. The prior appeals, which never invoked the formal DSA complaint path, had counted for nothing procedurally.

The seller's decision points and trade-offs

At each stage of the process, the seller faces a genuine choice that involves real trade-offs, not just mechanical steps. Identifying these in advance is how a seller avoids being reactive and starts being strategic.

The first decision: how to respond to the suspension notice. The options are a standard Seller Central appeal, a formal DSA internal complaint, or a combined approach that addresses both channels. The standard appeal is faster to file but has weaker procedural standing. The formal DSA complaint takes more preparation but creates a record that supports escalation. In most matters involving a substantive suspension – not a trivial listing error – we recommend the combined approach, with the DSA complaint drafted first and the Seller Central submission aligned to it.

The second decision: how much to disclose in the complaint. The DSA complaint requires enough factual detail to establish the basis of challenge. But the seller is not required to provide a complete forensic account of every business practice. What to include, what to hold back, and how to frame the facts without unnecessary concessions is a legal judgment, not an administrative one.

The third decision: when to escalate to out-of-court dispute settlement or regulatory complaint. Escalating too early – before the internal complaint process has genuinely failed – weakens the procedural argument at the next level. Escalating too late allows the suspension to continue for longer than necessary. The window is not defined by a single fixed deadline, but it is bounded by the facts of the specific account and the DSA's requirement of timeliness.

If the internal complaint already came back rejected or ignored, a second read of the complaint and the platform's response can often identify why it failed and whether anything is still recoverable. The decision at that point is whether to pursue out-of-court settlement, a regulatory channel, or – in appropriate cases – a national court application. For a practical mapping of the out-of-court options available under the P2B framework, our analysis of P2B dispute resolution for sellers sets out the real options and their limitations.

The fourth decision: whether to involve legal counsel. This question has a practical answer rather than a formal one. For a suspension that is straightforwardly procedural – a notice that is clearly deficient, a product that is obviously authentic, a policy that the seller demonstrably complied with – the internal complaint is manageable with good documentation. For suspensions involving IP allegations, cross-marketplace enforcement patterns, or account histories that include prior issues, the complaint quickly involves legal analysis that turns on the interaction between the DSA, P2B, and BSA. That intersection is where errors in framing have the most lasting consequences.

There is a persistent myth that EU sellers have no leverage once a platform suspends them. The DSA and P2B framework says otherwise. The platform must give reasons, must operate a complaint process, must engage with dispute settlement, and must act proportionately. These are not aspirational standards. They are enforceable obligations, and in matters we handle, we work to use them directly rather than accepting the suspension as the final word.

The practical reality, though, is that leverage is only realized if it is exercised correctly. A seller who has the right to request human review of an automated decision but never formally requests it cannot complain later that no human reviewed it. The rights exist in the framework; using them requires knowing they exist and knowing how to invoke them.

A branded-goods distributor on Amazon IT (spring 2026) came to us after a suspension that appeared to be driven by a cross-marketplace flag originating from an Amazon DE decision. The seller had no active disputes on the Italian storefront. We mapped the cross-surface signal, filed an internal DSA complaint identifying the statement of reasons as factually defective on its face – it described conduct on a different marketplace as if it were Italian account activity – and requested a separate human review of the Amazon IT account record. The suspension was narrowed to the DE surface, and the IT account was restored to active status.

Step-by-step: the correct response sequence for Amazon IT DSA suspensions

The following sequence is the structure Tutamen uses in Amazon IT DSA suspension matters. It is not a template – each complaint is built on the specific suspension notice and account facts – but the sequence itself is durable across cases.

1. Obtain and read the statement of reasons in full. Identify what policy or legal basis is cited, what conduct is described, and whether the decision is attributed to automated means. Note every omission.
2. Gather the supporting evidence before responding. Supply-chain records, authorization letters, order histories, correspondence – everything that contradicts the factual basis of the suspension or establishes proportionality concerns.
3. Draft the formal DSA internal complaint. This document identifies the specific legal deficiency in the statement of reasons, attaches the supporting evidence, requests human review of any automated decision, and – where relevant – makes the proportionality argument explicitly.
4. File through the correct channel. The DSA complaint channel on Amazon IT is separate from the standard Seller Central appeal path. Both can be used, but the DSA complaint must be filed as a formal complaint, not as a Plan of Action.
5. Preserve the record of filing and response. Timestamps, reference numbers, and the content of any platform response are the foundation of any escalation. Keep everything.
6. Evaluate the platform's response. Did it engage with the specific legal grounds? Did it provide a substantive reason for rejecting the complaint? A non-responsive or templated rejection strengthens the escalation argument.
7. Decide on escalation. If the internal complaint fails or receives no substantive response, map the available out-of-court dispute settlement bodies, assess whether a regulatory complaint is appropriate, and – where urgency requires – consider whether a national court application is warranted.
8. Maintain the P2B parallel track. Where the suspension triggers P2B minimum-notice obligations, that non-compliance is a separate ground of complaint, not an alternative to the DSA path.

Each of these steps involves judgment, not just execution. Step 3 – drafting the formal complaint – is the one where legal framing matters most. The way the grounds are characterized in the internal complaint affects the strength of every subsequent step.

For sellers who want to understand the full regulatory context before mapping their specific situation, the complete EU marketplace regulation guide provides the background on how DSA, P2B, and DMA interact across Amazon's EU surfaces.

If you have already filed an appeal or complaint and received a rejection, the first step is identifying why it failed and whether the DSA formal complaint path was actually used. In a significant share of matters we review, the prior filing never formally engaged the DSA framework at all – which means the formal complaint is still available. Email info@tutamenlaw.com with the suspension notice and the prior response; we will review what path is still open.

Related areas

• EU Marketplace Regulation – Full representation for EU and UK sellers facing DSA, P2B, and DMA issues
• Amazon Account Reinstatement – Plan of Action drafting and appeal strategy for deactivated accounts

Frequently asked questions about DSA rights for suspended sellers on Amazon IT

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

There is no single answer, because the timeline depends on the specific suspension ground, the quality of the statement of reasons, and which procedural path is pursued. A well-framed internal DSA complaint that identifies a clear procedural deficiency in the statement of reasons can produce a response within weeks. Where the internal complaint fails and the matter proceeds to out-of-court dispute settlement or a regulatory channel, the timeline extends significantly – typically to several months. One factor sellers often do not account for is that delay in filing the formal complaint, or filing it through the wrong channel, adds to the total timeline without creating any procedural advantage. Speed of correct action matters more than speed of any action.

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

The principal risk is framing the response as a standard Amazon appeal rather than a formal DSA internal complaint. A Plan of Action that accepts the stated basis for suspension and commits to corrective action is not a DSA complaint; it has different procedural weight, and it can implicitly concede grounds the seller does not need to concede. A second risk is failing to invoke specific DSA protections – such as the right to human review of automated decisions – that are only triggered by explicit request. Third, sellers managing the process alone often miss the proportionality argument entirely, focusing on whether the underlying policy ground exists rather than on whether full account suspension was the proportionate response to it. Once a complaint is filed and rejected on its current framing, reopening it on different grounds is harder.

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

Not in every case. A suspension involving a straightforward procedural deficiency – a notice that fails to identify any specific conduct, a product that is demonstrably authentic, a policy the seller clearly complied with – can often be addressed with a well-prepared internal complaint and good documentation. The DSA complaint process is designed to be accessible to business users, not just lawyers. Where legal involvement becomes important is when the suspension involves IP allegations, cross-surface enforcement signals, a prior account history, or a proportionality argument that requires legal framing. In those situations, the complaint involves analyzing how the DSA, P2B framework, and BSA interact on the specific facts – and errors in that analysis are difficult to correct at a later stage. Tutamen offers a fixed-fee initial review of the suspension notice and account facts, quoted up front, so the seller can assess what is involved before committing to representation.

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 is led by attorneys with direct experience of DSA, P2B, and DMA matters across Amazon's European surfaces, including Amazon IT. To discuss your situation, email info@tutamenlaw.com.

Page authored by Dmitri Aronov, Partner, EU Marketplace Regulation, 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.

Written by Dmitri Aronov – Partner, EU Marketplace Regulation. Published September 10, 2026.