How to handle statement of reasons under the DSA: a step-by-step guide

A suspension notice lands in your Amazon UK seller account. The listings are down, disbursements have stopped, and a formal document labeled "statement of reasons" sits in Seller Central with a deadline attached. The path forward is not obvious – and the first move matters more than most sellers realize.

TL;DRA statement of reasons under the Digital Services Act (DSA) is the formal notice a platform such as Amazon must give when it restricts or removes a seller's content, listing, or account. On Amazon UK, it sets out the ground for the action and triggers specific rights to challenge it – through an internal complaint mechanism, out-of-court dispute settlement, or, ultimately, a competent authority. Acting on it correctly, and in sequence, is the difference between preserving those rights and quietly losing them.

This guide walks through each step in order: what the statement actually says and what it obliges the platform to do, how to read it against the DSA's requirements and the Platform-to-Business (P2B) Regulation, where sellers go wrong in the first response, and what decisions face you at each fork in the process. The focus is Amazon UK, but the procedural logic applies across EU-listed Very Large Online Platforms.

What is a statement of reasons under the DSA and why does it matter on Amazon UK?

A statement of reasons is the DSA's mandatory disclosure requirement: when Amazon restricts, suspends, or removes a seller's content or account, it must tell the seller in writing which provision was violated, what specific content or behavior triggered the action, and what rights the seller has to challenge it. That obligation sits in Article 17 of the Digital Services Act, which designates Amazon as a Very Large Online Platform (VLOP) subject to the regulation's most demanding transparency rules. In practical terms, this means the notice you receive is not just a courtesy – it is a legal instrument that also starts a procedural clock.

Why does this matter commercially? Because a suspension on Amazon UK can lock inventory in FBA warehouses, halt disbursements, and strand a business mid-season. We regularly see sellers who assume the process is identical to a standard US deactivation appeal. It is not. The DSA layer adds explicit procedural rights – the right to a reasoned explanation, the right to use an internal complaint mechanism, and the right to out-of-court dispute settlement – that do not exist in the US system. Failing to use them in order means forfeiting leverage that the regulation specifically built for your benefit.

The P2B Regulation (Platform-to-Business Regulation, EU 2019/1150) ran parallel to the DSA on transparency and fair treatment grounds and remains relevant as a source of additional rights, particularly around ranking, differentiated treatment, and the terms under which access to the platform is restricted. As enforcement automation has tightened and Amazon's VLOP obligations have deepened, the interplay between the DSA statement of reasons and the P2B Regulation's complaint path has become a real strategic question in matters we handle.

One definitional point worth holding onto: a statement of reasons is not an infringement notice, not a warning, and not an invitation to submit a Plan of Action in the traditional sense. It is a reasoned administrative act by the platform. Treating it as anything else – especially as a routine US-style appeal trigger – is the single most common mistake we see from sellers working without a specialist.

Step 1 – Read the notice and identify exactly what Amazon is asserting

The first concrete step is to read the statement of reasons carefully, against a checklist of what the DSA actually requires it to contain. Amazon's VLOP status means the notice must specify: the factual basis for the restriction, the contractual or legal provision relied on, whether automated tools were involved in the decision, and the available redress options. If any of those elements are missing or ambiguous, that absence is itself a procedural point in your favor.

Start with the factual basis. The statement should identify the specific listing, ASIN, or account conduct that triggered the action. Vague language – "policy violation" without more – may not meet the DSA standard. Note it. Next, check the provision cited: is it the Business Solutions Agreement (BSA), an Amazon specific policy, EU product-safety law, or a combination? The answer determines which response path has traction.

Check whether the notice says the decision was automated. The DSA requires Amazon to disclose when an automated system made or contributed to the restriction. If the notice confirms automation, the right to human review is engaged under DSA Article 20 and Amazon's own internal complaint process is the procedurally correct first channel – not an email to Seller Performance.

Finally, read the redress section of the notice. Does it list the internal complaint mechanism? Does it name an out-of-court dispute settlement body certified under Article 21? Does it give a time limit? Write these down in a working log before responding to anything. The clock on some rights begins on receipt.

Where does the first response go wrong?

The most reliable way to weaken your position is to send a generic Plan of Action (POA) in response to a DSA statement of reasons. Amazon's US-facing appeal process and the DSA's complaint mechanism are structurally different. A POA submitted outside the internal complaint framework does not formally engage the DSA process, does not create a reviewable record, and does not preserve the seller's right to escalate to an out-of-court settlement body if the internal review fails.

We see this pattern repeatedly: a seller receives the DSA notice, drafts a corrective-action document that addresses product safety or policy, sends it through the standard appeal channel, receives a rejection, and then discovers that the formal internal complaint window has closed. At that point, the options narrow significantly.

A second failure mode is treating the statement of reasons as final. It is not. The DSA is explicit: sellers have the right to challenge the decision through the platform's internal complaint-handling system before any question of external escalation arises. That internal step is not optional protocol – it is the procedurally required first stage. Skipping it, or conflating it with the ordinary reinstatement appeal, forfeits the rights that follow.

There is also a documentation failure. The DSA gives sellers the right to a response from Amazon's internal system within a reasonable timeframe. Keeping a timestamped record of every submission, every acknowledgment, and every response is essential – not just for the internal process, but for any later escalation to a certified out-of-court body or a competent authority. For guidance on building that record correctly before you file, the internal complaint handling under the DSA checklist sets out the document sequence in full.

The bridge between reading the notice and filing the formal response is short, and a weak first filing narrows what is possible later. That is the practical reason to review the notice and the response together, in legal context, before anything is submitted.

If a first appeal or filing already came back rejected, a second read can find the specific reason it failed and what, if anything, is still open. To get a read on where your matter stands, email info@tutamenlaw.com.

Step 2 – Use Amazon's internal complaint mechanism under DSA Article 20

Amazon's internal complaint-handling system is the formal procedural channel the DSA requires VLOPs to operate for sellers challenging a restriction. It is distinct from the standard reinstatement appeal and from the general Seller Central contact form. Filing through this channel creates a documented DSA-governed complaint record and obliges Amazon to handle it with qualified personnel.

The submission should address the statement of reasons point by point. For each factual claim Amazon made, provide a direct response with supporting evidence – supply chain documentation, product conformity records, test reports, authorization letters, or historical listing data, depending on the ground cited. For each provision Amazon cited, confirm you understand it and explain, specifically, why the conduct described either did not occur or has been corrected.

If the notice disclosed automated decision-making, say so explicitly in the complaint and request human review. This is not a formality: the DSA creates a distinct obligation for Amazon to ensure that where automation materially contributed to a restriction, a natural person reviews the challenge. Flagging this in the complaint locks that obligation into the record.

One practical point on tone and structure: the DSA complaint is not the place for a general narrative about the seller's business history. It is a formal response to a legal notice. Structure it as: (1) identification of the restriction and the statement of reasons it responds to; (2) specific response to each factual ground; (3) specific response to each legal/policy provision; (4) request for full reinstatement and, where appropriate, expedited review. Keep it short enough to be read in full. A submission that runs to many pages risks the key points being missed.

Timing matters. Amazon's internal complaint process should be engaged promptly after receipt of the statement of reasons. While the DSA does not prescribe a single fixed deadline for sellers to file (check the notice for any specific window Amazon itself has stated), delay undermines both the DSA complaint and any downstream escalation options. In matters we handle, we aim to file within a few working days of the initial review.

Step 3 – Assess the outcome and decide whether to escalate

Amazon's internal complaint-handling system must respond within a reasonable time, as the DSA frames it, and the response must itself be reasoned. If the internal system upholds the restriction without explanation, or gives a response that does not address the specific grounds raised, that response is itself a DSA-level event that can be cited in any escalation.

At this stage, the seller faces a genuine decision fork. The realistic options are: accept the internal outcome and adjust the account accordingly; escalate to a certified out-of-court dispute settlement body under DSA Article 21; engage the competent authority in the relevant member state; or, in appropriate cases, consider whether the Platform-to-Business Regulation or the Digital Markets Act (DMA) – if the conduct in question concerns gatekeeping obligations – adds a parallel route. The DMA gatekeeper framework applies to Amazon in specific contexts, and where it overlaps with a suspension, it opens a distinct regulatory avenue that is worth assessing before filing with a dispute settlement body.

The out-of-court settlement route under Article 21 is not a full litigation substitute. It is a structured mediation with a certified body, operating under DSA procedural rules. The seller can use it without closing off other legal options, but the body's decision is not legally binding on Amazon in the same way a court order would be. Its practical value lies in speed, cost, and the DSA's requirement that Amazon engage in good faith. We assess whether this route is appropriate in each matter based on the specific ground for restriction, the documentation available, and the commercial timeline.

A home-goods seller on Amazon UK (winter 2025) came to us after their account was restricted following a product-safety complaint under the General Product Safety Regulation (GPSR). Amazon's statement of reasons cited automated detection of a compliance gap. We identified that the automated flag had attached to the wrong ASIN variant, drafted a DSA internal complaint with conformity test certificates and the corrected product record, requested human review as required under DSA Article 20, and the restriction was lifted after the internal review concluded. The key was filing precisely within the DSA framework rather than through the standard appeal channel.

For the broader regulatory map – how the DSA fits alongside P2B, DMA, and national enforcement – the EU marketplace regulation complete guide for sellers covers the full architecture and how the instruments interact.

Step 4 – Handle concurrent platform actions without undermining your DSA position

A statement of reasons does not always arrive in isolation. In matters we handle, the DSA notice often runs alongside a separate Amazon policy action – an Account Health metric, an ASIN-level complaint, a Brand Registry dispute, or a customs or EPR (Extended Producer Responsibility) compliance flag. Managing those concurrent actions without undermining the DSA complaint requires care.

The core rule is sequencing. The DSA internal complaint is a formal legal process. Submitting informal appeals, providing contradictory explanations in different channels, or making account changes that touch the restricted products while the DSA complaint is live can complicate the record. It can give Amazon grounds to treat the matter as a new or changed situation rather than a direct response to the original statement of reasons.

This is particularly acute where the suspension involves product-safety grounds. If GPSR compliance is in question, providing updated conformity documentation is appropriate and necessary – but it should be submitted through the DSA complaint record, not sent informally to a separate team, and it should be introduced as part of the factual response to the specific ground cited, not as a standalone upload that appears disconnected from the formal process.

Similarly, if the restriction affects Amazon FBA inventory – creating a risk of removal or disposal orders – the FBA removal process and the DSA complaint run in parallel but do not interact. Initiating removal orders to protect stock does not prejudice the DSA complaint. In matters where the commercial cost of waiting is high, managing the inventory side while the DSA process runs is a routine part of the work.

Step 5 – Know the limits of the process and plan around them

The DSA gives EU sellers real, enforceable rights that did not exist under the pre-regulation regime. But it does not guarantee reinstatement, it does not create a fast-track to a binding decision, and it does not override Amazon's substantive right to restrict access where a genuine compliance failure exists. A seller who has a real product-safety gap, an actual infringement, or a genuine policy breach does not become exempt from enforcement because they invoke the DSA correctly. The regulation governs how the enforcement is done, not whether it applies.

The realistic picture is this: a well-structured DSA internal complaint, filed promptly and responding precisely to the stated grounds, substantially improves the probability of a favorable internal review. Where the restriction was based on an automated error, incorrect data, or a failure to apply Amazon's own stated criteria, the DSA complaint is a powerful tool – it puts Amazon under a documented obligation to review, reason, and respond. Where the restriction reflects a genuine compliance failure, the route is fixing the failure and demonstrating that fix through the complaint record.

What changes this picture? The strength of the documentation, the precision of the response to the specific grounds cited, and the speed of filing. A delayed, generic, or misdirected first filing is the most common reason sellers lose leverage they could have kept. The DSA's complaint architecture was built for situations where a seller is right and a platform acted arbitrarily or with insufficient process. Using it well requires understanding both the regulation and the specific facts of the account.

A tech-accessories brand selling on Amazon UK (spring 2026) came to us after an account-level restriction citing DSA grounds and an alleged inauthentic-goods complaint. The internal appeal had already been rejected through the standard channel. We filed a formal DSA internal complaint identifying that the original statement of reasons had not specified the ASIN-level evidence that triggered the automated flag – a procedural gap under the DSA's Article 17 requirements. Amazon's internal complaint team re-examined the underlying evidence, found that the flag had been applied on the basis of a third-party report that itself contained an error, and reinstated the account. The outcome turned on the procedural argument, not a fresh submission of business documents.

For sellers also facing suspension under the DSA on Amazon Italy or other EU surfaces – where the regulatory framework is identical but Amazon's internal processes sometimes run through different teams – the DSA rights for suspended sellers on Amazon Italy guide covers the surface-specific procedural points in detail.

Decision points and trade-offs: what you are actually choosing at each stage

Sellers working through a DSA process face a series of genuine choices, and the right answer depends on the facts of the account, the commercial stakes, and the strength of the available documentation. Understanding the trade-offs before each filing prevents the common error of choosing the fastest option over the most strategically sound one.

At the first stage – internal complaint versus standard reinstatement appeal – the trade-off is primarily between speed and procedural protection. The standard reinstatement route is faster to file, but it does not create a DSA-governed record and does not preserve escalation rights. If the commercial cost of delay is high and the ground for restriction is clearly a platform error, the DSA internal complaint is the right channel even if it takes a few additional days to prepare correctly.

At the escalation stage – out-of-court body versus competent authority – the trade-off is between engagement speed and legal weight. A certified dispute settlement body under Article 21 can move relatively quickly and keeps the process semi-private. A referral to the competent authority (in the UK, the Digital Markets Unit; for EU surfaces, the relevant national authority and the European Commission for VLOP-level matters) carries more formal weight but takes longer and enters a more public process. In matters we handle, escalation to a competent authority is reserved for cases where Amazon has demonstrably failed to comply with its DSA obligations and the internal and Article 21 routes have been exhausted or are genuinely inadequate for the situation.

At the DMA gatekeeper stage – if the conduct involves Amazon's core platform services and there is an argument that the restriction reflects an anticompetitive or self-preferencing practice – the trade-off is between a DSA/P2B-based complaint path and a regulatory intervention path. These are not mutually exclusive, but mixing the arguments in the same filing without clear separation weakens both. DSA sellers' rights arguments and DMA gatekeeper obligations argue under different legal bases and to different regulators.

The underlying point across all of these decisions: the DSA gives EU marketplace sellers leverage they did not previously have. Using it well means choosing the right tool, at the right stage, for the specific situation. It does not mean using every available tool simultaneously.

Related areas

• EU Marketplace Regulation – DSA, DMA, P2B, and GPSR advice for Amazon and EU platform sellers
• Amazon Seller Account Reinstatement – account deactivation appeals and Plan of Action drafting across all surfaces
• IP and Brand Registry – complaint retraction, counter-notice, and Brand Registry dispute resolution

Frequently asked questions

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

Timelines vary considerably depending on whether the matter resolves at the internal complaint stage or requires escalation. In matters we handle, well-prepared internal complaints filed through Amazon's DSA mechanism often receive a substantive response within several weeks. Where the matter escalates to a certified out-of-court dispute settlement body under DSA Article 21, the process takes longer – typically a number of months, depending on the body's caseload and the complexity of the dispute. Escalation to a competent authority is a longer process still. The single biggest factor in timeline is the quality and completeness of the first filing: a precise, evidence-grounded complaint to the correct channel almost always resolves more quickly than an informal appeal that needs to be re-routed.

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

The primary risk is procedural: filing through the wrong channel, filing a response that does not address the specific DSA grounds cited, or missing the window in which certain escalation rights are available. A second risk is evidentiary – a seller working alone may not know which documents Amazon's internal complaint team needs to see for a given type of restriction, and a submission that is factually incomplete is likely to be rejected even where the underlying position is strong. A third risk is strategic: making inconsistent representations across different Amazon channels while a DSA complaint is live can complicate the record in ways that are difficult to undo. The DSA complaint is a legal process, and the risks of handling it without specialist review are similar to those in any formal commercial dispute.

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

Not in every case. Where the restriction is clearly based on a straightforward compliance gap that the seller can document and fix – a missing conformity certificate, an incorrect listing field – a careful seller can often prepare a DSA internal complaint without legal help. Where the statement of reasons is vague, where the restriction was automated, where a first filing has already been rejected, or where the commercial stakes make speed and precision critical, attorney-led review adds real value. The DSA's procedural architecture rewards precise, well-evidenced filings. In matters we handle, the difference between a general narrative submission and a targeted complaint that addresses the specific DSA obligation Amazon failed to meet is consistently significant. The question is less whether you legally require a lawyer and more whether the cost of an error is higher than the cost of specialist review.

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 regulation practice covers DSA internal complaints, P2B-based challenges, DMA gatekeeper arguments, and GPSR and EPR compliance disputes across Amazon UK and EU surfaces – with all fees fixed and quoted after a short initial review. To discuss your situation, email info@tutamenlaw.com.

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.

Written by Priya Raman, IP & Brand Registry analyst, Tutamen. Published October 10, 2026.