Before you act on data access rights for EU sellers: a checklist

A suspension notice from Amazon FR lands without warning. The listings go dark, the disbursements pause, and the path back is genuinely unclear. What many sellers on the French marketplace do not realize is that EU law gives them concrete rights to the data Amazon holds about their account – and that exercising those rights, in the right sequence, can change the dynamic of a dispute before any formal appeal is filed.

TL;DRData access rights for EU sellers on Amazon FR flow from several intersecting instruments: the Platform-to-Business (P2B) Regulation, the Digital Services Act (DSA), and – where Amazon's gatekeeper status applies – the Digital Markets Act (DMA). Together they create enforceable entitlements to transparency, account data, and a structured internal complaint path. Acting on those rights at the wrong moment, or in the wrong order, can foreclose options that would otherwise be available.

This checklist walks through the checks phase by phase. Each phase has a "why it matters" note and the decision points where the choice you make shapes what comes next.

Phase 1: What data access rights for EU sellers actually cover on Amazon FR

Data access rights on Amazon FR are not a single rule – they are a cluster of entitlements under three overlapping instruments, and knowing which one applies to your situation is the first practical decision.

The Platform-to-Business (P2B) Regulation – formally Regulation (EU) 2019/1150, in force since July 2020 – gives sellers rights to transparent terms and conditions, a statement of reasons before any suspension or termination, and access to an internal complaint-handling system. It applies to any professional seller using Amazon FR as a distribution channel, regardless of where the seller is established. When Amazon deactivates a listing or suspends an account, P2B requires that the platform explain the reasons. That explanation is itself a piece of data you are entitled to receive.

The Digital Services Act (DSA) adds a further layer. Amazon operates as a Very Large Online Platform (VLOP) under the DSA. As such, it must provide sellers with a statement of reasons for content moderation decisions – including listing takedowns and account restrictions. The seller has a right to use Amazon's internal redress mechanism, and, where that fails, to pursue certified out-of-court settlement through a DSA-designated body. That right is separate from, and not exhausted by, the standard appeals process in Seller Central.

The Digital Markets Act (DMA) applies where Amazon is designated as a gatekeeper. Among the DMA's obligations are requirements around data portability and access to data generated by the seller's own commercial activity on the platform. The exact scope of what a seller can demand depends on how Amazon has implemented its DMA compliance obligations – which, in matters we handle, we check against the current published compliance statements before advising.

Checks for Phase 1:

• Confirm which EU instrument is most directly engaged: P2B (suspension/termination with a statement of reasons), DSA (content moderation decision with an internal redress path), or DMA (data portability and access to your own commercial data).
• Pull the notice you received from Seller Central and read it for any reference to "reasons", "policy", or "data". A bare suspension with no reasons given is itself a P2B compliance issue.
• Note the date of the notice. Time matters: the DSA's internal complaint mechanism has its own response timelines, and delay can weaken your position on escalation.
• Check whether your seller account is registered as a professional seller (not a consumer) – P2B rights apply only to professional sellers in a business-to-business relationship with the platform.
• Identify the specific surface: Amazon FR, not Amazon DE or Amazon ES. Data-access claims are made to the platform entity operating in the relevant jurisdiction.

Why it matters: Each instrument has a different procedural path, a different addressee inside Amazon's compliance structure, and different escalation options if Amazon does not respond adequately. Conflating them in a single request often produces a generic, unhelpful reply that helps no one. In matters we handle, we identify the correct legal basis before drafting a single word of a formal request.

Phase 2: Before you make any formal data request – what to gather first

Gathering the right internal documentation before you submit any formal request is not optional preparation – it is the step that determines whether your request lands with specificity or gets batted away as too vague to process.

Amazon's compliance teams receive large volumes of data requests. A request that identifies a specific account, a specific decision, a specific date range, and the legal basis for the request is treated differently from one that does not. In matters we handle, we regularly see sellers submit requests that describe the problem in general terms, receive a response pointing them to the Help pages, and conclude that data access rights do not really work. They do work. The framing is what matters.

Checks for Phase 2:

• Download and save a full account health report from Seller Central, including any performance notifications and policy warnings received in the preceding twelve months.
• Export your full transaction history and disbursement records for the period in question. If funds are on hold, note the exact balance shown and the date it was frozen.
• Save every communication from Amazon – automated or otherwise – relating to the relevant listings or the account suspension. Screenshot Seller Central messages and retain the original email notifications.
• Record the ASIN or ASINs affected. Data requests tied to a specific listing are more precise and produce more useful responses than account-wide requests.
• Identify the type of decision at issue. A listing takedown for a product-safety reason engages different rules from an account deactivation under BSA Section 3. A data access request framed around the wrong decision type is likely to come back empty.
• Check whether you have already used Amazon's internal complaint path under P2B – the regulation requires Amazon to operate one, and you should document whether you have accessed it and what response, if any, you received.

Why it matters: The quality of your documentation going in determines the quality of Amazon's obligation to respond. A well-documented request creates a clear paper trail. If you later need to escalate to a DSA out-of-court settlement body or to a regulatory authority, that trail is essential. For a broader orientation to the EU regulatory framework that governs these rights, see our complete guide to EU marketplace regulation for sellers.

Phase 3: Drafting the data access request – the decision points

The data access request is not a form letter. Each element of it is a decision, and the wrong decision at this stage can produce a response that is technically compliant but practically useless.

Under the P2B Regulation, the statement of reasons Amazon must provide when it suspends or terminates an account should include the specific facts and circumstances that led to the decision, the applicable legal or contractual ground, and where relevant a reference to the content of the policy engaged. If the notice you originally received did not contain all of that, you are entitled to request it explicitly. Frame the request by referencing Article 4 of the P2B Regulation.

Under the DSA, the statement of reasons for a content moderation decision must be machine-readable and must explain the basis, the facts, and any automated decision-making involved. If Amazon used an automated tool to flag your listing or account, you are entitled to know that. Frame the DSA request by referencing the relevant DSA provision on statements of reasons for content moderation.

The DMA data-access obligation is distinct. It relates to data you generated through your own commercial activity on the platform – order data, click-through rates, conversion data, search placement data. If you believe Amazon is using data generated by your selling activity in a way that disadvantages you, or denying you access to that data, the DMA gatekeeper obligations are the relevant frame.

Checks for Phase 3:

• Decide whether you are making a P2B statement-of-reasons request, a DSA statement-of-reasons request, a DMA data-portability request, or a combination. Each should be stated separately in the request, not bundled into one paragraph.
• State the specific decision you are asking about: the date, the ASIN(s), and the type of action taken.
• Ask explicitly whether any automated decision-making was involved. If it was, ask for the logic applied and any human review that took place.
• State the legal basis for each request. A request that does not identify the instrument it relies on can be processed as a general customer service query rather than a regulatory compliance obligation.
• Set a response deadline that reflects the instrument. P2B requires Amazon to respond within a reasonable time; the DSA sets out specific timelines for complaint responses. Do not give Amazon open-ended time to reply.
• Send the request through the documented channel – typically the internal complaint-handling system required under P2B – and retain proof of submission. A verbal conversation with Seller Support does not count.

Why it matters: A correctly framed request shifts the burden to Amazon. If Amazon does not respond adequately, the inadequacy of its response is itself evidence for any escalation. If Amazon's response contradicts what its initial notice said, that inconsistency is material. We have seen matters where the data access response revealed that the decision was based on an automated flag that was incorrect on its face – and where that disclosure changed the entire trajectory of the dispute.

Phase 4: Reading the response – what Amazon's answer actually tells you

Amazon's response to a formal data access or statement-of-reasons request is not just an administrative reply. It is a document that either confirms the basis for the platform's decision or exposes gaps in it. Reading it correctly is a specialist task.

In matters we handle, we see four types of response. First, a substantive statement of reasons that gives you something to work with – a specific policy ground, a specific fact asserted, a reference to an automated tool. Second, a generic response that restates the original notice without adding anything. Third, a redirect to the standard appeals process, without engaging with the legal basis of the request. Fourth, no response within the applicable timeframe.

Each type points to a different next step. A substantive response that identifies a specific policy ground gives you the basis for a targeted Plan of Action or a counter-notice. A generic or non-responsive reply is itself a P2B or DSA compliance failure that can be escalated. No response within the timeframe puts you in a position to use the DSA's out-of-court settlement mechanism without further internal steps.

Checks for Phase 4:

• Check whether the response identifies a specific legal or contractual basis for the decision, or merely paraphrases the original notice.
• Check whether the response discloses the involvement of automated decision-making. If it does not and you have reason to believe automation was involved, that is a gap you can formally probe.
• Check whether the response is consistent with any prior communication. An inconsistency between what the original notice said and what the statement of reasons says is meaningful.
• Note the date of the response and compare it to the required response timeline. A late response is a separate compliance issue.
• If the response directs you to the standard Seller Central appeal process, assess whether that process can realistically address the specific data-access issue, or whether it is a deflection.
• If the response is substantively useful, assess whether it changes your understanding of the root cause. Sometimes the statement of reasons reveals a different issue from what the original notice implied – and acting on the original assumption would have produced the wrong appeal.

Why it matters: The response stage is where the data access process either unlocks the dispute or confirms that escalation is needed. Acting on a substantive response requires careful analysis of what is actually asserted versus what is merely implied. For an example of how the EU complaint and mediation path can interact with a platform dispute, see our anonymized account of resolving a dispute through EU marketplace mediation.

An EU home-goods seller on Amazon FR (winter 2026) came to us after submitting a data request that had been redirected three times to the standard Seller Central help pages. We identified that the original request had not cited the P2B Regulation by name and had been processed as a general inquiry. We refiled on the correct legal basis with a stated response deadline, and Amazon's compliance team provided a substantive statement of reasons within the required period. That document revealed that the account flag was triggered by a product-safety review linked to an incorrect ASIN. The seller was then able to target the actual problem rather than filing a generic Plan of Action.

If your first formal request came back unhelpful or was ignored, the issue is usually the framing, not the rights themselves. Email info@tutamenlaw.com to have us review the response you received and advise on whether escalation is warranted.

Phase 5: Escalation paths when Amazon's response is inadequate

When Amazon's response to a data access or statement-of-reasons request fails to meet the standard required by the applicable instrument, EU law provides concrete escalation options – and the path you choose depends on the instrument, the nature of the failure, and your commercial objectives.

Under the P2B Regulation, sellers can raise a formal complaint with a designated national authority in any EU member state. France has designated a national enforcement authority for P2B. A complaint to that authority is not the same as a court claim – it is a regulatory complaint that triggers the authority's investigative powers. The authority can require Amazon to comply, and a pattern of complaints from multiple sellers increases the likelihood of regulatory action.

Under the DSA, sellers can use a certified out-of-court settlement body to resolve disputes about content moderation decisions. Amazon, as a VLOP, must provide access to this mechanism. A DSA out-of-court settlement is typically faster and less costly than litigation, and the existence of a documented complaint trail – showing that the internal complaint path was exhausted first – is a precondition for using it effectively.

Under the DMA, a seller who believes Amazon is violating gatekeeper data-access obligations can submit a complaint to the European Commission directly or, in parallel, to the relevant national competition authority. DMA enforcement is Commission-led, but member state authorities can act in parallel.

Checks for Phase 5:

• Confirm which instrument the escalation is based on. P2B, DSA, and DMA each have different enforcement bodies and different complaint procedures.
• Confirm that you have exhausted the internal complaint path required under P2B and the internal redress mechanism under the DSA before filing an external complaint. Filing externally without exhausting internal steps weakens the complaint and may be rejected procedurally.
• Assess whether your objective is to recover the data (DMA portability), to obtain a compliant statement of reasons (P2B/DSA), or to challenge the underlying suspension decision. Each objective maps to a different escalation tool.
• Consider whether regulatory escalation fits your commercial timeline. A regulatory complaint can take time to produce a result; if the commercial priority is to get the account or listings reinstated quickly, a parallel track – using the data obtained through the access process to file a targeted appeal in Seller Central – may be the more immediate path.
• Document every step taken, every response received, and every deadline. An escalation body will ask for this documentation as a threshold matter.

Why it matters: Sellers frequently assume that EU rights are theoretical – that the regulation exists on paper but that Amazon simply does not comply and nothing happens. That is the myth worth correcting. In matters we handle, we have seen P2B complaints and DSA internal-complaint mechanisms produce meaningful responses from Amazon's compliance function that standard Seller Central appeals did not. The key is using the right instrument, in the right order, with adequate documentation. For sellers wondering whether a listing takedown on safety grounds is truly the end of the road, our article on EU listing takedowns on safety grounds addresses the realistic options in detail.

Phase 6: Decision points and trade-offs – before you commit to a path

The data access rights process is not linear for every seller, and the right path depends on what you are ultimately trying to achieve and what the specific notice and response actually say.

Some sellers work through data access rights as a diagnostic tool – the primary goal is to understand exactly why Amazon took the action it did, so that the subsequent appeal is targeted and evidence-based. Others use the process as a standalone remedy, where the platform's failure to provide a proper statement of reasons is itself the complaint. Still others use it in parallel with an appeal, treating the data request and the Seller Central appeal as complementary tracks rather than alternatives.

The trade-off between speed and thoroughness is real. Filing a regulatory complaint under P2B takes time. If your account is suspended and your cash flow is affected, speed is a commercial priority. The parallel track – using the data access process to sharpen the appeal while simultaneously pressing the commercial reinstatement path – is often the right answer for sellers with active inventory and live disbursement obligations.

There is also a trade-off between doing this alone and getting specialist input. The myth that EU sellers have no leverage once a platform suspends them is directly contradicted by the instruments described in this checklist. But using those instruments correctly requires knowing which one applies, framing the request precisely, and reading the response with a trained eye. Errors at the drafting stage – citing the wrong instrument, failing to state a legal basis, accepting a non-response as an adequate reply – can cost the seller the escalation option that would have resolved the dispute.

Checks for Phase 6:

• Decide whether data access is your primary goal (you need information to proceed) or a supporting tool (you are using the data to build the appeal or escalation).
• Assess your commercial timeline honestly. If disbursements are frozen and inventory is building, factor that into how aggressively you move and whether you run parallel tracks.
• Ask whether the specific data you are seeking is actually available. Not all data held by Amazon about your account is subject to the same access rights under the same instrument. A scoping conversation with a specialist – before you commit to a formal request – is a low-cost way to avoid a wasted filing.
• Review whether any prior filings in Seller Central have already used language that affects the data access position. A Plan of Action that concedes a specific root cause can complicate a subsequent argument that the platform's data about that root cause is inaccurate.
• Decide whether you want legal representation for the data access request and any escalation. For a straightforward P2B statement-of-reasons request, a well-informed seller can often proceed alone with the right template. For DMA data-portability claims, DSA out-of-court settlement, or regulatory complaints, specialist representation makes a material difference.

Why it matters: The decision to act without specialist input is not always wrong. But it should be an informed choice made after understanding the risks. In matters we handle, we see sellers who spent weeks on generic Seller Central appeals while the data access path that would have unlocked the dispute sat unused. Attorney-led and confidential, with fixed fees quoted up front, Tutamen's EU Marketplace Regulation practice exists precisely for these decision points.

A software accessories brand selling on Amazon FR (spring 2026) came to us after a three-month suspension in which two rounds of Seller Central appeals had been rejected without meaningful explanation. We identified that Amazon had not provided a compliant statement of reasons under the P2B Regulation at any stage. We submitted a formal P2B request, received a substantive response that identified a specific policy issue unrelated to what the original notices had implied, and worked with the seller to rebuild the appeal on the actual stated ground. The account was restored.

If you are at a decision point and unsure whether to proceed alone, contact us for a fixed-fee scoping review before you file anything further. Email info@tutamenlaw.com with a brief description of the situation and the stage you are at.

Related areas

• EU Marketplace Regulation – full practice hub covering P2B, DSA, DMA and GPSR for Amazon and Etsy sellers
• EU Marketplace Regulation: The Complete Guide for Sellers – comprehensive orientation to the EU rules that govern your account

Frequently asked questions

How long does resolving data access rights for EU sellers usually take on Amazon FR?

The timeline depends on which instrument you use and whether Amazon provides an adequate response at the first stage. A P2B statement-of-reasons request should produce a substantive response within a reasonable period; the DSA sets specific response timelines for internal complaints. If the internal path produces an adequate response quickly, the overall process can be measured in weeks. If escalation to a national authority or a DSA out-of-court settlement body is required, the timeline extends significantly – regulatory complaints and external settlement processes move more slowly than internal ones. In matters we handle, we assess the most likely timeline at the outset so that sellers can plan their commercial response alongside the legal process.

What are the main risks if I handle data access rights for EU sellers alone?

The principal risks are framing errors and procedural gaps. A request that does not cite the correct legal instrument tends to be processed as a general customer service query rather than a regulatory compliance obligation, producing a response that is technically issued but substantively empty. A request that does not exhaust the internal complaint path before escalating externally may be rejected procedurally by the escalation body. And a response that appears unhelpful may actually contain disclosures that change the analysis – but only if you read it with the right legal frame. None of these risks are insuperable, but they are real, and they are the errors we most commonly see in matters that arrive with a prior failed attempt.

Do I need a lawyer for data access rights for EU sellers?

Not always, but the answer depends on the stage and the complexity of the situation. A straightforward P2B statement-of-reasons request, for a single listing takedown with a clear factual record, is a task a well-informed seller can handle with the right template and an understanding of the applicable instrument. DMA data-portability claims, DSA out-of-court settlement filings, and regulatory complaints to national authorities are more procedurally demanding and benefit from specialist representation. The practical question is: what is the cost of getting it wrong? In most disputes involving a suspended account or frozen funds, the commercial stakes are high enough that a fixed-fee scoping review – to identify which instrument applies and how to frame the request – is a proportionate investment before any formal step is taken.

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 attorney-led, covering P2B, DSA, DMA and General Product Safety Regulation matters across Amazon's EU surfaces, with fixed fees scoped after an initial review of the account and the relevant notice. To discuss your situation, email info@tutamenlaw.com.

Disclaimer: This article is general information, not legal advice, and does not create an attorney-client relationship. Marketplace policies and the law change, and every account and case is different. For advice on your situation, contact Tutamen at info@tutamenlaw.com.