Why statement of reasons under the DSA happens and how sellers respond

TL;DRA statement of reasons is the formal notice Amazon must issue under the Digital Services Act when it restricts, suspends, or removes a seller's account, listing, or content on its EU or UK platform. Receiving one is not the end of the process – it is the beginning of a defined procedural path that includes internal complaint rights, the possibility of out-of-court dispute resolution, and, in appropriate cases, regulatory escalation. The DSA establishes that sellers have substantive rights once that notice lands, and the quality of the response filed in the days that follow determines whether those rights are used effectively.

This analysis covers what a statement of reasons actually is on Amazon UK, the procedural sequence that follows, and the decision points sellers face at each stage. The goal is not to provide false reassurance – the path can be long, and the outcome is never certain – but to give operators the factual map they need before they decide how to respond.

What is a statement of reasons under the DSA, and why does Amazon issue one?

A statement of reasons is a mandatory disclosure requirement imposed on Amazon as a Very Large Online Platform (VLOP) under the Digital Services Act. When Amazon restricts or terminates a seller's account, removes a listing, applies a content label, or suspends disbursement access on its EU-facing or UK-facing platform, it must issue a written explanation identifying the specific ground relied on. This is not a courtesy – it is a legal obligation embedded in the DSA framework that creates a corresponding right for the recipient to understand and challenge the decision.

In practice, a statement of reasons will name the policy, rule, or legal basis Amazon says the seller violated. It will describe, at least in outline, the conduct or content Amazon identified as the trigger. And it will confirm whether the restriction is temporary or indefinite. On Amazon UK, where the DSA framework continues to apply post-Brexit through retained and equivalent provisions, Amazon's compliance systems generate these notices as part of its VLOP obligations. The notice may arrive in Seller Central, by email, or through account notifications – the format matters less than what it says.

Why does Amazon issue these notices? Because the DSA compels it to. Before the Act, platform decisions were opaque. A deactivation notice might reference a policy heading and nothing more. The DSA changed that architecture. Sellers who receive a statement of reasons now have a document they can interrogate, respond to, and build a challenge around. That is the leverage point that most sellers miss: the notice is not proof that Amazon is right – it is an invitation to demonstrate that Amazon is wrong.

In matters we handle, the most common triggers for a statement of reasons on Amazon UK fall into a recognizable cluster: product safety and compliance flags, inauthentic or counterfeit complaint decisions, related-account findings, and content or listing removals tied to intellectual property complaints. Less frequently, sellers receive them following identity or KYC verification failures. Each trigger category has a different procedural logic, and the response strategy differs accordingly.

How does the DSA interact with the Platform-to-Business Regulation on Amazon UK?

The Platform-to-Business Regulation – P2B, as it is commonly called – predates the DSA and remains the foundational layer of seller protection on EU and UK marketplaces. P2B requires platforms like Amazon to give advance notice before restricting a business user's account, to provide a statement of reasons for any restriction, and to offer an internal complaint-handling mechanism. The DSA builds on that base and goes further, mandating specific content for the statement of reasons and adding out-of-court dispute settlement as an available route.

For Amazon UK sellers, the interaction between P2B and the DSA creates a layered set of obligations that Amazon must satisfy and a layered set of rights that sellers can invoke. P2B requires Amazon to give at least 30 days' notice before terminating a business account, except where it relies on an imperative reasons exception – typically safety, legal compliance, or fraud. The DSA then requires that any restriction, whether with or without advance notice, is accompanied by a clear statement of reasons. Together, these instruments mean that an Amazon UK seller facing suspension or delisting is not dealing with a purely contractual dispute: they are operating within a regulated framework with enforceable procedural rights.

We regularly see sellers who are unaware of the P2B layer entirely. They receive a statement of reasons under the DSA, focus solely on the Amazon-internal appeal process, and never invoke the complaint-handling or escalation rights that sit alongside it. That is a missed opportunity. The P2B and DSA mechanisms are additive – using one does not foreclose the other – and the choice of which to pursue first, or in parallel, is one of the key strategic decisions at the outset.

For further background on the regulatory structure governing EU and UK marketplace sellers, the analysis at EU marketplace regulation – the complete guide for sellers covers the full framework in depth, including the DMA gatekeeper obligations that sit alongside P2B and the DSA.

What does the statement of reasons actually contain, and what should sellers look for?

Reading a statement of reasons is a specialist task. The document's surface language is often compressed and policy-referential, and the ground that actually matters for a response may not be the most prominently stated one. Sellers who treat the statement as a form letter and respond with a generic appeal consistently underperform against those who read it with the specificity it demands.

A compliant statement of reasons under the DSA must identify: the legal or policy basis for the decision; the facts and circumstances relied on; and, where automated means were used to detect a violation, that fact and what the detection mechanism flagged. This last requirement is significant. If Amazon's notice acknowledges that an automated system triggered the restriction, the seller has an immediate line of challenge – automated systems produce false positives, and the DSA's transparency requirements create a record that can be interrogated in the internal complaint process or before an out-of-court dispute settler.

When we review a statement of reasons, we are looking at several specific things. First, is the stated ground legally coherent? Does the cited policy actually prohibit the conduct described? Second, is the factual assertion accurate? Is the underlying product, listing, or account history consistent with the allegation? Third, is there a mismatch between the severity of the restriction and the gravity of the stated violation – a question that becomes important both in the internal complaint and in any regulatory or dispute-settlement escalation. Fourth, is the notice formally deficient? A statement of reasons that omits mandatory elements is itself an arguable basis for challenging the restriction.

Sellers often focus on the conclusion of the notice – the restriction itself – and overlook the reasoning. The reasoning is what you respond to. A response that addresses only the outcome and not the stated basis is, in Amazon's system, no response at all.

What is the realistic procedural path after receiving the notice?

The path begins with the internal complaint mechanism. Under the DSA, Amazon is required to operate an internal complaint-handling system that considers challenges to restrictions, and to decide those complaints without undue delay. On Amazon UK, this system runs in parallel with the standard Seller Central appeal process, but it is not the same thing. A DSA complaint can raise the deficiency of the notice itself, the procedural errors in how the restriction was imposed, and the substantive inaccuracy of the stated grounds – grounds that the standard account-health appeal process does not always accommodate.

The realistic sequence, in most cases, is: internal complaint filed on the substantive and procedural grounds identified in the statement of reasons – response from Amazon's complaint team – either resolution or rejection. If the internal complaint is rejected, the seller has reached the boundary of Amazon's self-governance. At that point, two tracks open: out-of-court dispute settlement under the DSA, and – where the restriction engages P2B rights – engagement with the relevant competent authority in the seller's member state or, for UK sellers, the relevant regulatory body. These are not mutually exclusive.

The internal complaint-handling under the DSA – your questions answered page covers the mechanics of that process in detail, including what a well-structured complaint looks like and what Amazon's response obligations are at each stage.

Out-of-court dispute settlement is a DSA innovation that gets less attention than it deserves. Sellers who have exhausted the internal complaint process can refer their dispute to a certified out-of-court dispute settlement body. Amazon, as a VLOP, is required to engage with those bodies in good faith. The outcome is not binding on the seller – if unsatisfied, they retain all legal options – but it is a meaningful pressure point, particularly for sellers who cannot absorb the time and cost of regulatory litigation. The out-of-court route is available to sellers who have completed the internal complaint process first – the internal step is a prerequisite, not an optional preliminary.

If neither internal complaint nor out-of-court settlement resolves the matter, the regulatory track is the next consideration. Digital Services Coordinators in EU member states have oversight functions under the DSA, and the European Commission has direct enforcement authority over VLOPs for systemic violations. Individual sellers do not typically file direct complaints with the Commission, but they can feed information to the relevant Digital Services Coordinator, whose investigations can influence platform behavior at scale. For UK sellers, the equivalent regulatory picture is evolving, and the practical options depend on the specific type of restriction and the legal basis Amazon cited.

A mid-market electronics seller on Amazon UK (summer 2026) came to us after receiving a statement of reasons citing a product safety compliance failure. Amazon had flagged a documentation gap identified by an automated review. We reviewed the notice, identified that the safety documentation Amazon required had in fact been submitted to Amazon's systems prior to the flag, and built the internal complaint around that factual discrepancy – including evidence of the submission timestamps. The internal complaint was upheld and the listing restriction lifted. The key was engaging with the specific automated-detection claim in the notice, not appealing on generic compliance grounds.

What are the seller's decision points, and how should trade-offs be weighed?

The first decision is timing. The internal complaint mechanism does not carry a hard statutory deadline for the seller to file, but Amazon's practice is to treat restrictions as confirmed if unchallenged, and delay weakens the factual record. A seller who waits several weeks to file an internal complaint will find that the documentation of their original position – what the listing said, what the account history showed, what the supply chain looked like – is harder to reconstruct. The window is not infinite.

The second decision is scope. Should the internal complaint address only the procedural deficiency of the notice, only the substantive ground, or both? A complaint that raises procedural deficiency alone can be resolved quickly but leaves the substantive question open. A complaint that addresses both requires more preparation but is less likely to be re-opened after a procedural fix. In our practice, we typically recommend addressing both where the factual record supports it.

The third decision is whether to run the internal complaint and the Seller Central appeal simultaneously or sequentially. Amazon's internal complaint mechanism is legally distinct from the account-health appeal process, and the two can theoretically run in parallel. In practice, the interaction between them is not always clean – responses from one process can affect the framing available in the other. A seller who files both without coordination risks inconsistency in their stated factual position, which Amazon's review teams will use against them.

The fourth decision is escalation threshold. Not every statement of reasons merits regulatory escalation. The cost – in time, attention, and sometimes legal fees – of pursuing the out-of-court dispute settlement route or engaging the Digital Services Coordinator is a real consideration. For a restriction on a single low-volume listing, the calculus may favor a focused internal complaint and, if it fails, a commercial decision to relist under a corrected structure. For an account-level suspension affecting a significant portion of a seller's GMV, the calculus is different. The decision matrix is not complicated once the facts are in hand, but it requires honest assessment of what the restriction is actually costing and what the realistic outcome of each track looks like.

The myth that EU sellers have no leverage once a platform suspends them is not only incorrect – it is the belief that Amazon's process is designed to encourage. The DSA and P2B framework deliberately shifted leverage back toward business users. Sellers who understand that the statement of reasons is a legal document, and not a final word, are the ones who use it effectively.

The steps above describe the standard procedural map. Your situation turns on the specific grounds cited in the notice, the account history, the product category, and the documentary record you can assemble – which is what we assess first. If you are looking at a statement of reasons and are uncertain what it is really saying or what to file, contact us at info@tutamenlaw.com for a review.

How do DMA gatekeeper obligations affect the picture for large-volume sellers?

The Digital Markets Act (DMA) operates alongside the DSA but addresses a different set of concerns. Where the DSA governs content moderation and transparency, the DMA addresses the behavior of designated gatekeepers – platforms that meet specific scale and market position thresholds – toward the business users who depend on them. Amazon is designated as a gatekeeper under the DMA in the EU for certain core platform services, and that designation carries obligations that affect how Amazon can treat sellers in ways that interact with the statement-of-reasons framework.

The most relevant DMA obligations for sellers receiving a statement of reasons are the non-discrimination requirement – Amazon cannot apply less favorable conditions to sellers who use competing services – and the requirement that terms and conditions be fair, transparent, and consistent. If a statement of reasons cites a policy ground that is applied inconsistently, or that appears designed to foreclose a seller's access to competing channels, the DMA provides a separate regulatory basis for challenge that operates independently of the DSA's internal complaint route.

For UK sellers, DMA-equivalent obligations are at a different point of development, and the practical regulatory levers available differ from those in the EU. The analysis in why DSA rights for suspended sellers happen and how sellers respond covers that divergence and what it means for sellers operating across both markets.

In matters we handle for larger-volume sellers – those whose relationship with Amazon represents a material share of their revenue – the DMA angle is regularly worth examining alongside the DSA complaint track. A restriction that looks like a compliance decision on its face may, on deeper review, have characteristics consistent with a DMA-relevant concern. These are not common findings, but they are not rare either, and the regulatory consequence for Amazon of a substantiated DMA complaint is considerably more significant than the consequence of a single internal complaint.

What practical steps should sellers take immediately after receiving the notice?

Speed matters, but accuracy matters more. The worst outcome is a fast response that misidentifies the ground Amazon actually relied on and frames the complaint around the wrong factual issue. Amazon's review teams are not obligated to re-read a poorly framed complaint as a well-framed one.

The immediate steps, in order, are these. First, preserve the statement of reasons in its original form – screenshot, download, or forward it before anything in Seller Central changes. Amazon's notification systems sometimes overwrite or archive notices, and the exact language of the original statement is the foundation of every subsequent filing. Second, pull the account history for the period preceding the restriction – listing states, policy notifications, any prior warnings or complaints, and disbursement records. The pattern of what happened before the restriction often explains the ground cited in the notice, and sometimes reveals that the notice is factually inaccurate. Third, identify the specific policy or legal provision Amazon named and read it. Not the headline – the actual text. Sellers consistently discover that the conduct Amazon described does not match what the cited policy actually prohibits.

A home-goods seller on Amazon UK (winter 2025) came to us after a statement of reasons citing a related-account finding – Amazon's allegation that the seller's account was linked to a previously suspended account. The seller had no knowledge of any related account. We pulled the full account history, identified that the flagged connection traced to a shared payment processor configuration that had been used briefly during a platform migration, and built the internal complaint around the technical documentation of the migration. The complaint addressed both the factual inaccuracy of the "related account" characterization and the procedural deficiency of the notice, which had not identified the specific technical indicator Amazon's system used. Amazon's complaint team lifted the restriction. The documentation that made that possible had to be assembled within the first week – delay would have made parts of it harder to obtain.

After those three immediate steps: do not file anything in Seller Central's standard appeal system until you have a clear picture of the internal complaint strategy. Once the standard appeal is filed, it creates a record – and a factual position – that constrains what you can say in the DSA internal complaint. The two processes are legally separate, but the factual consistency between them matters.

What are the realistic limits of the DSA framework for sellers?

The DSA is a significant regulatory advance for sellers. But it is not a guarantee of reinstatement, and it would be misleading to suggest otherwise. The framework creates procedural rights and transparency obligations – it does not dictate substantive outcomes. Amazon can comply with every DSA requirement and still maintain a restriction if the underlying factual and policy basis is sound.

The realistic limit of the DSA framework is that it disciplines process, not result. A statement of reasons that is complete, accurate, and grounded in a legitimate policy position is DSA-compliant. The seller's recourse, if the statement is accurate and the policy is legitimate, is to correct the underlying issue – not to invoke DSA rights as a shield against a valid enforcement decision. The DSA framework is most powerful where Amazon's decision is procedurally deficient, factually inaccurate, or disproportionate relative to the stated violation. In those cases, the procedural levers it creates are genuinely useful.

What the framework does not do is make the internal complaint process fast. The DSA requires Amazon to handle complaints without undue delay, but that standard is not defined with precision, and Amazon's practice on response times varies. Sellers managing a suspension that is materially affecting their business need to be realistic about the timeline – several weeks for an internal complaint decision is common, longer is possible, and the out-of-court dispute settlement route adds further time. Cash-flow planning has to run in parallel with the procedural strategy.

If a first internal complaint has already been rejected and you are evaluating the out-of-court route or regulatory escalation, a second read of the complaint and Amazon's response can identify the specific reason it failed and whether there is a correctable gap. That second read is often the point at which the realistic options become clearer. To discuss your position after a rejected complaint, email info@tutamenlaw.com.

Related areas

EU Marketplace Regulation – account suspension, delisting and regulatory escalation for EU and UK sellers
EU marketplace regulation – the complete guide for sellers – the full DSA, DMA and P2B framework for marketplace operators

Frequently asked questions

How long does resolving statement of reasons under the DSA usually take on Amazon UK?

Resolution through the internal complaint process typically takes several weeks from filing to a substantive response, though the timeline varies with the complexity of the stated grounds and the category of restriction. Amazon is required to handle complaints without undue delay, but that standard does not translate to a fixed number of days. Sellers should plan for the process to run over multiple weeks rather than days, and should not treat absence of an immediate response as a decision. If the internal complaint is rejected and the out-of-court dispute settlement route is used, the overall timeline extends further. Cash-flow and inventory planning should not be built around an optimistic resolution date.

What are the main risks if I handle statement of reasons under the DSA alone?

The primary risk is framing the internal complaint around the wrong ground – responding to the headline restriction rather than the specific factual and legal basis cited in the statement. Amazon's review teams assess complaints against the stated grounds of the notice; a complaint that does not engage with those grounds is typically rejected without detailed analysis. A second risk is inconsistency between the Seller Central standard appeal and the DSA internal complaint, which can create a factual record that undermines both. A third risk is missing the documentary window: the evidence that supports an accurate challenge is often time-sensitive and harder to assemble after the first week.

Do I need a lawyer for statement of reasons under the DSA?

Legal representation is not a formal requirement for filing an internal complaint or pursuing out-of-court dispute settlement. Whether it is practically necessary depends on the complexity of the stated grounds and the commercial significance of the restriction. Sellers dealing with a single listing removal on a straightforward factual ground may be able to handle the internal complaint without specialist input. Sellers facing account-level suspensions, related-account findings, automated-detection flags, or restrictions with a significant P2B or DMA dimension benefit from specialist review before filing. The DSA framework is procedurally precise, and a complaint that does not engage with its specific requirements – particularly the mandatory content of the statement of reasons itself – is less likely to succeed.

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 after a short review. We act for founders, brand owners and in-house teams who need a specialist for a marketplace dispute. Clients value the combination of legal precision and direct commercial understanding of how marketplace businesses operate. To discuss your situation, email info@tutamenlaw.com.

By Priya Raman – IP & Brand Registry analyst, Tutamen. August 12, 2026.

Page authored by Priya Raman, IP & Brand Registry 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.