Data access rights for EU sellers: what to do, step by step on Amazon FR

On paper, the data Amazon holds about your performance on Amazon FR belongs, at least in part, to you. The Platform-to-Business Regulation, the Digital Services Act, and the Digital Markets Act each create obligations that give EU sellers meaningful rights to that data. In practice, most sellers never exercise those rights – and a significant share discover too late that missing or withheld data was the reason an appeal failed, a suspension stuck, or an account health dispute went nowhere. This guide walks you through the exact sequence, the realistic obstacles at each step, and the decision points that matter.

TL;DREU sellers on Amazon FR have the right to request the data Amazon holds about their account, performance, and ranking under the Platform-to-Business (P2B) Regulation and, for larger operations, the Digital Markets Act (DMA). The process involves a formal written request, a defined response window, and a structured escalation path if Amazon does not comply or the data is incomplete. Exercising these rights often provides the evidentiary foundation for a suspension appeal, an internal complaint, or a formal regulatory complaint.

This guide covers: what data access rights actually cover on Amazon FR; the step-by-step request and escalation path; where the process goes wrong; the decision points sellers face; and when legal support changes the outcome. Each step is designed to be actionable before you speak to anyone.

What do data access rights for EU sellers actually cover on Amazon FR?

Data access rights for EU sellers on Amazon FR are grounded in three overlapping instruments, and understanding which one covers which type of data is the first practical decision you face.

The Platform-to-Business Regulation (P2B Regulation, Regulation (EU) 2019/1150) applies to all business sellers operating on Amazon FR. It requires Amazon to provide sellers with access to the personal data and other data generated through their use of the platform that they provided to Amazon or that was generated through the activities of the business user. The right is not unlimited – it covers data generated by or attributable to your business activities on the platform. What it does not cover, clearly, is Amazon's proprietary algorithmic logic or data belonging to third parties. But in practice, the categories that matter in a dispute are usually within scope: order history, return and refund records, Buy Box eligibility data, account health scores, and the specific policy-enforcement data that underpins a deactivation or listing suppression.

The Digital Services Act (DSA) adds a separate layer. Amazon is designated as a Very Large Online Platform (VLOP) under the DSA. For sellers, the most immediately relevant DSA rights relate to statements of reasons – Amazon must provide a clear, specific statement of reasons when it restricts your account, removes a listing, or suspends a service. If the statement of reasons you received is vague or generic, that is a DSA compliance issue, and the DSA's internal complaint-handling mechanism exists precisely to address it.

The Digital Markets Act (DMA) applies if you qualify as a business user of Amazon as a gatekeeper. The DMA creates stronger data portability obligations, requiring the gatekeeper to provide real-time access to data generated by your business activities on the platform. The practical relevance of the DMA for most individual sellers is narrower than the P2B Regulation, but for larger operations – particularly brand owners and distributors with significant Amazon FR revenue – it is a genuine additional lever.

A data access rights exercise on Amazon FR is therefore not a single request to a single regulation. It is a layered inquiry: which instrument covers the data I need, and which procedural path does that instrument require? In matters we handle, the P2B Regulation is the most commonly used starting point, with the DSA's statement-of-reasons mechanism used in parallel when the underlying issue is a suspension or listing removal.

Step 1: Map the data you need before you file anything

Sending a data request without first knowing exactly what you need is the single most common mistake sellers make, and it produces vague responses that are technically compliant but operationally useless.

Before drafting any formal request, build a data map. Start with the specific dispute or business problem driving the request. If the issue is a listing suppression, the relevant data includes: the date and time of the suppression, the policy rule cited, any automated system outputs that triggered the decision, and the account health record for the relevant ASIN. If the issue is a Buy Box loss, the relevant data includes: the eligibility criteria applied to your account, the data inputs Amazon used to evaluate those criteria, and any data held about competing offers on the same ASIN.

This mapping step has a practical legal function. A well-specified request is harder for Amazon to deflect with a partial or categorical response. A vague request – "please send all data about my account" – invites a response that identifies categories broadly and provides nothing specific. The P2B Regulation does not require Amazon to provide data in a particular format, but it does require the access to be effective. If the data you receive does not allow you to understand what happened to your account, the response is arguably non-compliant regardless of its length.

In a typical matter involving an Amazon FR suspension, we reconstruct the account timeline first – identifying the specific events, dates, and account health signals that preceded the deactivation. That reconstruction tells us exactly which data records we need to request, which regulatory instrument covers each category, and what a compliant response looks like. That groundwork makes every subsequent step faster and more targeted.

Step 2: Draft and submit the formal data access request

The formal request is a written document, and its content determines how much leverage you have in the steps that follow.

For a P2B Regulation data request, address the request to Amazon Services Europe S.à r.l. as the contracting entity for Amazon FR sellers. The request should identify the relevant platform, your Seller Central account identifier, the specific data categories requested (mapped in Step 1), and the regulatory basis – the P2B Regulation and, where applicable, the DSA. Include a clear statement that you are requesting the data for legitimate business purposes, which is the standard the Regulation uses.

For a DSA statement-of-reasons request, use Amazon's designated internal complaint-handling system. Amazon as a VLOP is required to maintain an internal complaint-handling mechanism that is accessible, fast, and free of charge. The complaint should specify the restriction you are challenging, the ASIN or account element affected, and the legal basis – the DSA's content moderation transparency obligations. The DSA sets a requirement that Amazon handle these complaints without undue delay.

Document everything. Keep a timestamped record of when each request was submitted, through which channel, and the exact wording used. If Amazon's system does not generate an acknowledgment automatically, follow up within a short period and preserve that follow-up. This record is essential if you need to escalate to a regulator.

One practical note for Amazon FR: some channels in Seller Central are routed to English-language support teams regardless of the seller's language preference. If you submit in French, document the language choice. If you are redirected to an English-language process, document that too. Language of process can become relevant in a formal complaint under French or EU consumer and business protection rules.

Step 3: Review the response and identify gaps

Amazon's response to a data access request is almost never everything you asked for, and reviewing it rigorously is where the practical value of the exercise appears.

A compliant response under the P2B Regulation provides effective access to the data generated through your use of the platform. Assess the response against four questions. First: was every category you requested addressed? Second: is the data provided in a form that allows you to understand what happened to your account? Third: are there unexplained gaps – records that should exist but are absent? Fourth: does the response contain any data that was not in the request, suggesting Amazon's systems hold broader records than disclosed?

A common pattern in matters we handle is a response that provides high-level account summaries but withholds granular enforcement data – the specific signals, automated outputs, or policy-mapping records that caused the adverse decision. That gap is itself legally significant. If the data you received does not allow you to understand the basis for a platform decision that harmed your business, the P2B Regulation and the DSA together provide the argument that the response is insufficient.

Identify every gap and document it in writing. The gap analysis is the input to Step 4.

Step 4: Use the internal complaint mechanism and escalate if necessary

The DSA's internal complaint-handling system is the first formal escalation point if Amazon's data response is incomplete or if the statement of reasons you received was inadequate.

A complaint through the internal mechanism should be specific. Reference the original request, identify the data that was not provided or the statement of reasons that was insufficient, and state the legal basis for the complaint. The complaint is not a negotiation – it is a formal record that Amazon is required to respond to, and its content determines what a regulator will see if the matter escalates further.

If the internal mechanism does not resolve the issue, the next step depends on the regulatory instrument. For P2B Regulation complaints, EU member states are required to designate enforcement bodies. In France, the relevant enforcement authority for business-to-platform disputes has jurisdiction over P2B compliance on Amazon FR. A formal complaint to that authority creates a regulatory record and, in some cases, triggers a direct inquiry to Amazon. For DSA violations, the European Commission has direct enforcement jurisdiction over VLOPs, and the Digital Services Coordinator in France is a separate escalation point.

This is also the step where the choice between handling the matter alone and engaging legal support becomes most consequential. A regulatory complaint filed without a clear articulation of the legal basis tends to be deprioritized. A well-framed complaint that identifies the specific DSA or P2B Regulation obligation, the evidence of non-compliance, and the harm to your business is far more likely to produce a substantive response. For sellers whose account is still suspended, the urgency of that distinction is real.

For a complete overview of the regulatory instruments and complaint paths available to EU sellers, our guide on EU marketplace regulation for sellers sets out the full picture. If your matter involves a listing takedown on product safety grounds specifically, the step-by-step process is covered separately in our guide on EU listing takedowns on safety grounds.

If the data access question is arising in a broader dispute that may move toward mediation, our analysis of mediation under EU marketplace rules on Amazon IT covers procedural parallels that apply across surfaces.

A mid-sized fashion brand operating on Amazon FR (winter 2025) came to us after a listing suppression that Amazon's notice attributed to a generic policy category. The account health record showed no prior violations, and the suppression had been in place long enough to affect seasonal inventory commitments. We mapped the relevant data categories under the P2B Regulation and DSA, submitted a targeted request, identified gaps in the response, and filed an internal complaint under the DSA. The data subsequently provided contained the specific automated-system output that had triggered the suppression. That record, which the seller had not previously been able to access, became the basis for a well-evidenced appeal that addressed the actual root cause. The listing was restored.

Step 5: Use the data as evidence in the substantive appeal or dispute

A data access exercise that stops at receipt of the data has not yet created the practical value it is capable of producing. The data is the input to the substantive dispute – not the end of the process.

Once you have the data Amazon holds, map it against the basis for the adverse decision. If a suspension notice cited a policy rule, does the data show that the events described in the notice actually occurred? If not, that discrepancy is the core of your appeal. If a Buy Box loss was attributed to pricing metrics, does the pricing data in the response match what your own records show? Discrepancies between Amazon's held data and the actual account history are more common than sellers expect, and they are frequently the reason a first-attempt appeal fails – the seller is trying to answer a factually incorrect premise.

A Plan of Action (POA) built on Amazon's own data is structurally stronger than one built on the seller's assumptions. Root cause analysis is the central component of any POA, and you cannot write an accurate root cause if you do not know what data Amazon used to make its decision. The data access step converts a guessing exercise into an evidence-based filing.

The same logic applies to arbitration or regulatory proceedings. A Notice of Dispute, a pre-arbitration demand, or a formal regulatory complaint is significantly stronger when it attaches, or refers to, data that Amazon itself produced and that contradicts the basis for the adverse action. In matters we handle involving EU marketplace suspension disputes, the data access step routinely surfaces records that change the direction of the substantive case.

Where this process goes wrong

Most sellers who attempt a data access exercise without support make one or more of the same errors. Recognizing them in advance avoids the cost of correcting them later.

The most common error is submitting a request through the wrong channel. Amazon's Seller Central interface has multiple support pathways, and the one a seller intuitively uses – often the general "Contact Us" form or an Account Health case – is not the legally designated channel for P2B or DSA requests. A request filed through the wrong channel may be responded to informally, outside the regulatory framework, in a way that creates no binding record. When we review a matter that has already been attempted, we regularly see that the seller made a genuine request that Amazon treated as a routine support inquiry because it was not framed and filed as a regulatory submission.

The second common error is conflating the data access request with the appeal itself. They are separate processes with different legal bases, different timelines, and different escalation paths. Mixing them produces responses that partially address the appeal and partially address the data request, satisfying neither. Keep them procedurally distinct.

The third error is failing to document the process in real time. By the time a seller is considering a regulatory complaint, weeks or months may have passed. Reconstructing the timeline of requests, responses, and gaps from memory is unreliable. A contemporaneous record of each step, including screenshots, submission timestamps, and exact wording of both the request and the response, is the difference between a complaint that can be evaluated on its merits and one that cannot be corroborated.

The myth that EU sellers have no leverage once a platform has suspended them or withheld data is pervasive and wrong. The P2B Regulation, DSA, and DMA create real obligations that carry real regulatory enforcement consequences. The difficulty is not that the leverage does not exist – it is that exercising it requires knowing the exact procedural sequence and having the documentary record to support it. That is where most self-represented sellers lose ground they should not lose.

Decision points: when to escalate and when to stop

Not every data access dispute should travel the full escalation path, and part of the value of a structured approach is identifying the decision points before you reach them.

If Amazon's response to a data request is substantively complete and the data it provides supports your appeal – even if it shows something you did not expect – the right move is usually to use that data in the appeal rather than to contest the response process further. The objective is the underlying business outcome, not procedural correctness for its own sake.

If the response is incomplete and the missing data is central to the appeal, the internal complaint under the DSA is the appropriate next step. That step is low-cost, requires no legal representation, and creates the formal record needed for any further escalation. Most sellers in this position should file it.

If the internal complaint does not produce a compliant response, the decision to escalate to a national enforcement authority or the European Commission is a genuine strategic choice. Regulatory complaints produce regulatory records and can produce outcomes, but the timeline is not predictable and the seller's account may still be suspended during the process. In that situation, running the regulatory complaint in parallel with the substantive appeal – rather than as an alternative to it – is usually the better approach. The appeal may resolve the account issue on a shorter timeline; the regulatory complaint protects the record and creates accountability for future matters.

If the matter involves a significant volume of withheld funds, a pattern of suppression across multiple ASINs, or a gatekeeper-level data access issue under the DMA, the trade-off calculus changes. Those situations involve commercial stakes high enough to warrant a full legal assessment of the escalation path before any further submissions are made.

The steps above describe the standard path. Your situation turns on the exact wording of the data response you received, the account history behind it, and the regulatory instrument most directly applicable – which is what we review first.

To discuss the data your matter requires and the fastest route to it, email info@tutamenlaw.com for a confidential review. Fees are fixed and quoted up front after a short assessment.

If a first data request or internal complaint already came back with an unsatisfactory response, a second read of both the request and the response frequently identifies the specific framing or channel issue that caused the gap – and what, if anything, is still open under the applicable regulation.

To have us review what you received and advise on next steps, reach out to Tutamen at info@tutamenlaw.com.

Related areas

• EU Marketplace Regulation – full practice overview for EU and UK sellers on Amazon and beyond
• EU marketplace regulation: the complete guide – regulatory instruments, obligations, and seller rights across surfaces

Frequently asked questions

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

The timeline varies significantly depending on how many escalation steps are needed. A straightforward P2B Regulation data request, properly filed, should receive a substantive response within a period of weeks. If the response is incomplete and an internal DSA complaint is filed, the internal mechanism is required to operate without undue delay, but in practice the cycle can extend further. Escalation to a national enforcement authority adds further time. In matters we handle, sellers who file well-specified, correctly channeled requests tend to receive faster and more complete responses than those who submit general inquiries through informal support pathways.

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

The most significant risk is filing through the wrong channel, which produces an informal response that carries no regulatory weight and may exhaust the seller's patience without creating a usable record. A second risk is conflating the data request with the substantive appeal, producing a muddled submission that Amazon addresses only partially. A third risk is missing the decision point at which the internal complaint mechanism becomes relevant – sellers who move directly from an incomplete response to a national complaint, bypassing the internal mechanism, often find the complaint deprioritized because the internal escalation path was not exhausted first. We regularly see matters where the seller's substantive position was strong but the procedural record was too thin to support it.

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

Not for the initial data request – the P2B Regulation and DSA are designed to be accessible to business users without legal representation. Where legal support changes the outcome is at the gap-analysis stage and above: identifying which data is missing, framing the internal complaint with sufficient precision to produce a legally compliant response, and deciding when and how to escalate to a regulator. In matters where the withheld data is the central evidence for a suspension appeal or a significant funds dispute, the cost of getting the framing wrong at the complaint stage typically exceeds the cost of getting it right with assistance at the outset. Our fees for EU data access and regulatory complaint work are fixed and quoted up front after a short 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 P2B, DSA, and DMA matters across Amazon EU surfaces, including Amazon FR, with advice in English. To discuss your situation, email info@tutamenlaw.com.

By Priya Raman – IP & Brand Registry analyst, Tutamen. Published April 2, 2027.

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.