Responding to data access rights for EU sellers the right way

When an Amazon FR seller cannot access the data their business depends on – transaction records, performance metrics, buyer interaction data, or the reasoning behind a ranking or visibility change – the problem is not just frustrating. It cuts directly into the seller's ability to price, plan, and defend their account. And because the right to that data is embedded in EU law, failing to assert it properly means leaving a real legal lever unused.

TL;DRData access rights for EU sellers are grounded in the Platform-to-Business (P2B) Regulation, the Digital Services Act (DSA), and, for sellers on platforms designated as gatekeepers, the Digital Markets Act (DMA). On Amazon FR specifically, sellers have enforceable rights to certain categories of data the platform holds about their activity, and Amazon – as a Very Large Online Platform under the DSA – carries corresponding obligations. The procedural path to enforcing those rights runs through formal requests, internal complaint mechanisms, and, where necessary, regulatory or judicial escalation.

This guide walks through the exact sequence: what data rights exist, how to request them correctly, where the process tends to stall, and what decisions a seller faces at each stage. It is written for sellers operating on Amazon FR who are either being denied data they need or who have received a suspension or restriction and want to understand what information Amazon is required to give them about that decision.

What data access rights for EU sellers actually means on Amazon FR

Data access rights for EU sellers cover several distinct legal entitlements, and the applicable source determines what you can demand and on what timeline.

Under the P2B Regulation, business users on marketplace platforms have a right to know what data the platform collects about them, what data it processes in connection with their listing and sales activity, and what data is shared with third parties or retained after the contract ends. Amazon is required to set out its data practices clearly in its terms, but those terms do not limit what a seller can ask for formally – the Regulation provides a floor, not a ceiling.

Under the DSA, Amazon operates as a Very Large Online Platform (VLOP), which carries heightened obligations. When Amazon takes a content-moderation or visibility decision that affects a seller – restricting a listing, suspending an account, or demoting search placement – the DSA requires Amazon to issue a statement of reasons. That statement must explain the specific grounds for the decision, the facts and circumstances relied upon, and the means of redress available. In matters we handle, this statement is often too vague to be actionable on its first issue. Pressing for the more detailed version is frequently the most important early move a seller can make.

Where Amazon also meets the DMA definition of a gatekeeper – and for the purposes of this guide, that question depends on the specific designation status, which we check first – the DMA adds obligations around data portability and the prohibition on self-preferencing that can amplify a seller's position in a dispute about data access.

On Amazon FR specifically, the P2B Regulation applies directly as EU law. That means a seller on the French marketplace can assert P2B data-access rights without needing to show harm. The right exists because the seller is a business user of a platform that falls within the Regulation's scope. That is a meaningful foundation to build on – and it is one that sellers who handle these matters alone often fail to use.

Step one: Map what you are actually asking for before you file anything

The most common mistake at the start of a data-access process is sending a vague request that Amazon can satisfy with a vague response.

Before filing any formal request, the seller needs to categorize the data at issue. There are three broad categories that come up most often in our practice:

• Operational data – sales history, return rates, A-to-z Guarantee claim records, FBA inventory data, and customer feedback data linked to the seller's ASINs. Most of this is accessible in Seller Central, but there are gaps, especially around historical data following a deactivation.
• Decision data – the specific data points Amazon says it used to take an enforcement or ranking decision. This is the category most likely to be withheld and most legally significant if it has been.
• Post-termination data – data the seller is entitled to access or export after a contract or account relationship ends. The P2B Regulation and, depending on the data type, the GDPR impose separate obligations here.

Once the seller knows which category they need, the request can be drafted with enough specificity that Amazon cannot respond with a generic data-export link and call it resolved.

A practical audit of the account before making any formal filing is essential. Check what is already accessible in Seller Central, document it, and identify the precise gaps. This baseline serves two purposes: it shows the scope of what is genuinely missing, and it prevents the request from being dismissed because some of the data was technically available all along.

Step two: The formal request and Amazon's internal complaint path

Amazon's internal complaint-handling system – required under the DSA for VLOPs – is the first formal channel. The DSA obliges Amazon to operate this system in good faith and to provide a reasoned response. A well-structured initial request through this channel creates the documentary record that supports every later step.

The request should:

1. Identify the seller's account precisely and the period to which the data request relates.
2. Name the specific categories of data being requested, with reference to the legal basis (P2B Regulation, DSA Article on statement of reasons, or both).
3. Request, where relevant, the statement of reasons for any enforcement decision in a form that identifies the specific evidence or signals relied upon.
4. Set a reasonable response deadline – the DSA does not fix a single timeline for all data requests, but a period of several weeks is the working norm for internal complaint processes.
5. Preserve the correspondence by keeping a copy immediately; do not rely on Amazon's Seller Central messaging to retain records permanently.

Amazon's response at this stage often falls into one of three patterns. First, the data is provided in full and the matter closes. Second, a partial response is given – some data is provided, some is withheld with a brief explanation. Third, the response is formulaic, repeating the original action without engaging with the specific request. The second and third patterns are where legal escalation becomes relevant.

In matters we have handled, a partial or formulaic response is not the end of the road. It is, rather, the point at which the seller's legal position is clearest: Amazon has acknowledged the request, failed to satisfy it, and the paper trail exists.

Where this goes wrong: the four failure points

What happens when a seller handles a data access request alone? The answer, in a significant share of the matters that come to us after a first attempt has failed, is one of four predictable patterns.

Failure point one: The request is too broad. A request for "all data Amazon holds about my account" is easy for the platform to resist. It is either technically impossible to satisfy in full, or Amazon can offer a bulk export that technically responds to the letter of the request while excluding the decision-specific data that actually matters. Specificity is not a technicality – it is the engine of the right.

Failure point two: The seller uses informal channels. Seller Central support messages, account health escalations, and case logs are not substitutes for the formal internal complaint process required under the DSA. A response from Seller Central support does not satisfy Amazon's obligation under the Regulation. Using informal channels and accepting their responses as final is a lost opportunity in almost every case.

Failure point three: The seller accepts a vague statement of reasons. If Amazon issues a statement of reasons that says only that a decision was taken because the account did not meet Amazon's policies, and the seller accepts that without challenge, the seller loses the ability to build a targeted appeal or regulatory complaint. The DSA requires Amazon to identify the specific grounds and facts. A generic reference to policy breach does not meet that standard.

Failure point four: The timeline for escalation is missed. Internal complaint responses are not indefinitely available as the basis for regulatory referral. Acting on a failed or inadequate internal process while the matter is still live is far more effective than trying to reconstruct the factual record months later. This is the lost-opportunity dimension of data access rights that sellers most consistently underestimate.

A home-goods seller on Amazon FR (winter 2026) came to us after a listing restriction had remained in place for several months. The seller had submitted support cases through Seller Central and received standardized responses citing policy compliance. We reviewed what had been filed, identified that no formal DSA-compliant internal complaint had been made, and sent a properly structured request citing the statement-of-reasons obligation. Amazon's response within that process provided the specific signal data that had triggered the restriction – data the seller had never been given before. That information changed the appeal entirely.

For a structured overview of how EU marketplace rules interact across suspension types, see our complete guide to EU marketplace regulation for sellers, which covers the broader legal architecture of which data rights form one part.

Step three: Escalation options when the internal process fails

When Amazon's internal complaint process produces an inadequate response, the seller has three realistic escalation paths. Choosing the right one turns on the specific data at issue, the commercial urgency, and the seller's appetite for a longer process.

Path A: Regulatory referral. The DSA is enforced at the EU level by the European Commission for VLOPs. Sellers can submit complaints to the Digital Services Coordinator (DSC) in their member state – in France, the relevant authority is ARCOM. A DSC referral does not deliver data directly to the seller, but it creates regulatory visibility and, in some cases, prompts platform compliance faster than a private escalation alone. The timeline for regulatory action is not short, and a seller who needs data urgently to defend a live suspension should treat this as a parallel track, not a primary remedy.

Path B: P2B enforcement action. The P2B Regulation is enforced in France through national civil courts and, in some cases, through collective action by business association bodies. A seller can bring a private claim against Amazon for non-compliance with the Regulation's data-transparency obligations. The procedural path through the French courts takes time, but the availability of a private right of action is itself a negotiating point in a pre-litigation context.

Path C: Mediation. The P2B Regulation requires Amazon to offer access to at least two mediators for out-of-court dispute resolution. Before litigating or filing with a regulator, a seller can propose mediation. Amazon is obliged to engage in good faith. Our guide on mediation under EU marketplace rules sets out what to check before taking that step – it is not always the most efficient route, and the choice matters.

The decision between these paths is rarely obvious on the surface. If the data being withheld relates to a live enforcement action – a suspension, a listing restriction, or an account-level restriction on disbursements – the urgency of the commercial situation should drive the sequencing. A regulatory referral that takes months to mature is the wrong primary tool when an account is down and inventory costs are running. The right sequencing: exhaust the internal complaint process formally, then use the threat and reality of external escalation to create pressure within the platform's own compliance function.

If the underlying dispute also involves a listing removal on safety grounds, our analysis of responding to an EU listing takedown on safety grounds addresses the overlap between product-safety enforcement and data rights in the same process.

The seller's decision points and trade-offs

Every data access dispute involves a set of decisions where the wrong call compounds the problem. The myth that EU sellers have no leverage once a platform restricts them is exactly that – a myth. The P2B Regulation, the DSA, and, where applicable, the DMA give sellers enforceable tools. But those tools only work if they are used at the right moment in the right sequence.

Decision one: whether to request data before or after filing an appeal. In most situations we see on Amazon FR, filing an appeal before obtaining the decision data is a mistake. An appeal built on assumptions about what Amazon relied upon will miss the actual grounds. Getting the statement of reasons first, even if it delays the appeal by a short period, produces a far stronger filing. The exception is where a time-bound deadline for the appeal is running – in that case, the appeal and the data request need to be filed simultaneously, with the appeal expressly reserved pending fuller information.

Decision two: how specific to make the escalation threat. In our practice, sellers who write to Amazon citing the DSA statement-of-reasons obligation by name, with a clear statement that an inadequate response will be referred to the relevant DSC, receive more substantive responses than sellers who simply ask for more information. The platform's compliance function responds to legal specificity. That does not mean every communication should read like a letter before action – but the key legal basis should be named clearly.

Decision three: whether to pursue the data for its own sake or as evidence in a connected dispute. Sometimes a seller needs data because without it they cannot run their account. Other times, the data is the evidence base for an appeal, a regulatory complaint, or an eventual legal claim. These are different cases with different strategic priorities. In the first scenario, speed and cooperation are the primary goals. In the second, creating a clean record of Amazon's responses and non-responses matters more than closing the matter quickly.

The seller facing a suspension under EU rules who believes the process looks final and the appeal path is unclear is often, in reality, standing at a point where the legal tools are most powerful – if they are used correctly and promptly. Delay is the main enemy of a data-access claim, not the absence of rights.

An apparel brand selling on Amazon FR (spring 2026) came to us after a performance-based restriction had led to an effective suspension of their main product category. They had made several informal requests through Seller Central without receiving the underlying data. We issued a formal internal complaint citing the DSA and P2B obligations, followed within two weeks by a letter flagging the ARCOM referral path. Amazon provided the specific complaint-signal data within the internal complaint window. The data disclosed a single ASIN-level issue that had been incorrectly attributed to the full category. The restriction was narrowed on that basis.

Practical checklist before you file

Before sending any formal data access request on Amazon FR, confirm the following:

• You have documented what data is currently accessible in Seller Central, with screenshots and export records dated at the time of access.
• You have identified the specific categories of data being requested and the legal basis for each category.
• You know whether any enforcement decision has been taken and whether a statement of reasons has been issued – if it has, review it for specificity before deciding whether it is adequate.
• You have confirmed the account's current status – active, restricted, or deactivated – because the applicable escalation path differs.
• You have checked whether any appeal deadline is running concurrently and, if so, whether to file both the data request and a placeholder appeal simultaneously.
• Your correspondence is being retained outside Seller Central – email, PDF export, or a documented logging system.
• You understand which legal regime primarily governs your situation: P2B for data-transparency obligations, DSA for statement-of-reasons rights, DMA for portability and interoperability claims if the gatekeeper designation applies.

If the answer to any of these points is unclear, that gap is worth resolving before filing. A premature or misfiled formal complaint narrows the options that remain open.

Related areas

• EU Marketplace Regulation – enforcement of P2B, DSA, and DMA rights for marketplace sellers across EU surfaces
• Amazon Account Reinstatement – working through deactivation and building a root-cause Plan of Action for Amazon sellers

The steps above describe the standard path. Your situation turns on the exact wording of the restriction notice, the account history, and the timeline of any enforcement decision – which is what we review first. To discuss your account, email info@tutamenlaw.com.

Frequently asked questions

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

The internal complaint process under the DSA does not run to a single fixed deadline, but a resolution window of several weeks is the working expectation for a well-structured formal request. If Amazon's internal response is adequate, the matter can close there. Where the internal process produces an inadequate response and escalation to a national Digital Services Coordinator or mediation becomes necessary, the timeline extends considerably. The most significant variable is how early the formal request is made – a delayed start compounds every subsequent step.

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

The primary risk is strategic: most sellers who attempt this alone use informal support channels that do not create the legal record the DSA and P2B Regulation require. A vague request satisfied by a bulk data export, or a Seller Central support response accepted as final, forfeits the seller's ability to escalate effectively. Secondary risks include filing an appeal before obtaining the decision data – producing a weaker filing built on assumptions – and missing the practical window during which regulatory pressure is most effective.

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

Not always – but the cases where legal involvement makes the most difference are precisely the ones where sellers initially believe they do not need it. Where the data at issue relates to a live enforcement action, where Amazon's internal response has already failed, or where the seller is considering regulatory referral or mediation, attorney involvement ensures the legal basis is correctly stated, the record is built properly, and the escalation path chosen is the right one for the specific situation. In matters we handle on Amazon FR, the legal framework gives sellers real tools; the question is whether those tools are used correctly.

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 practice covers the full range of P2B, DSA, and DMA enforcement paths for sellers operating across EU surfaces, including Amazon FR. 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.

By Priya Raman – IP & Brand Registry analyst, Tutamen

Page authored by Priya Raman, IP & Brand Registry Analyst, Tutamen.