Data access rights for EU sellers: what it means for marketplace sellers

A seller on Amazon France builds years of transaction history, pricing data, and customer interaction records – and then discovers that accessing or challenging the platform's use of that data is not straightforward. The listings may still be live, the account still active, yet a critical decision that affects the seller's competitive position is being driven by data the seller cannot see, verify, or contest. That gap – between the data the platform holds and the data the seller can access – is exactly what EU marketplace rules are now designed to close.

TL;DREU data access rights give marketplace sellers a legal basis to request information that platforms use in ranking, moderation, and suspension decisions. Under the Platform-to-Business Regulation, the Digital Services Act, and the Digital Markets Act, sellers on Amazon FR and other covered platforms can compel disclosure of the data underpinning decisions that affect their accounts – and can challenge a refusal through internal complaint systems, mediation, or court proceedings. The path is procedural and requires careful framing, but the leverage is real.

This analysis covers what those rights actually consist of, how they interact on Amazon FR, what the realistic procedural sequence looks like, and where the decision points are for a seller deciding whether and how to act.

What EU data access rights actually cover for marketplace sellers

EU data access rights for marketplace sellers are a composite of obligations spread across three instruments, each addressing a different slice of the data relationship between a platform and a business user.

The Platform-to-Business Regulation (P2B Regulation) was the first instrument specifically designed for marketplace sellers. It requires platforms to give business users access to personal and non-personal data that those users have provided or that has been generated through their activity on the platform. That is a broader category than it initially sounds. It includes transaction data, performance metrics, buyer interaction data, and data generated by the seller's use of platform tools. Critically, it also requires platforms to disclose the data they use in ranking decisions – not the underlying algorithm, but the main parameters of how goods are ranked and what weight each parameter carries.

In matters we handle on behalf of Amazon FR sellers, the P2B ranking-transparency obligation is one of the most practically useful levers. A seller whose organic position has dropped significantly is entitled to know what the platform says drives ranking for its category – and whether the stated parameters match what the seller can observe in its own data.

The Digital Services Act (DSA) adds a separate layer. Amazon operates as a Very Large Online Platform (VLOP) under the DSA, which means it faces heightened obligations around the data it provides to affected parties. When a moderation or enforcement decision affects a seller's listings – a takedown, a restriction, a suspension – the platform is required to issue a statement of reasons that identifies the information the decision was based on. That statement of reasons is itself a form of data access: the seller now has a documented record of what the platform claims it relied on, which can then be compared against the seller's own records.

The Digital Markets Act (DMA) operates at a different level. It applies to Amazon's gatekeeper designation in the EU, and it includes obligations around data portability and data access that are more structural than individual. For most individual sellers, the DMA's daily relevance is indirect – it shapes Amazon's data-sharing architecture – but in complex disputes involving systematic data asymmetry, the DMA obligations are relevant background that informs how the platform's data practices should be assessed.

Together, these instruments mean that a seller on Amazon FR has, for the first time, a layered legal basis to ask: what data are you holding about me, what data are you using to make decisions that affect me, and on what basis are you declining to share it?

How does data access interact with account health and suspension on Amazon FR?

Account Health on Amazon FR is driven by metrics – order defect rate, late dispatch rate, policy compliance flags – that are generated and held by the platform, and that sellers can see in part through Seller Central but never fully audit. When a suspension or restriction follows from those metrics, the seller has a right under the DSA statement-of-reasons requirement to know what specific data triggered the action.

In practice, that statement of reasons is sometimes too generic to be useful. It may say that certain performance thresholds were breached without specifying which transactions, which buyer claims, or which calculation window drove the result. That is where a formal data access request under the P2B Regulation becomes a separate and targeted tool: the seller is not simply appealing the suspension through the Plan of Action path, but is formally requesting the underlying data so the Plan of Action can address the actual root cause.

This matters because the Plan of Action structure – root cause, corrective action, preventive measures – only works if the root cause is correctly identified. We regularly see cases where a seller's first Plan of Action is rejected not because the argument is weak, but because it addresses the wrong data point. The suspension was triggered by a metric the seller could not see clearly, the appeal addressed a metric the seller could see, and Amazon's review team found the disconnect. A data access request, framed correctly before or alongside the appeal, can resolve that problem.

For sellers facing an EU listing takedown on safety grounds, the data access question is particularly sharp. The General Product Safety Regulation and DSA obligations mean that when a listing is taken down on safety grounds, the platform must specify the information it relied on. That record becomes the foundation for any challenge – whether through Amazon's internal complaint-handling system or through external escalation.

What is the realistic procedural path for asserting data access rights?

The procedural sequence for asserting EU data access rights is more layered than a standard account appeal, and the order in which steps are taken affects what options remain open later.

The starting point is usually the platform's internal complaint-handling system. Under the DSA, Amazon as a VLOP is required to operate an internal complaint-handling system for business users who have been affected by enforcement decisions. A data access request that has been refused or inadequately addressed can be escalated through that system. The complaint must be specific: it should identify the decision at issue, the data requested, the provision of the applicable regulation that gives rise to the right, and the reason the response received was inadequate.

Generality is the most common reason an internal complaint fails to produce a meaningful result. A request framed as "please provide all data relating to my account" is likely to receive a response that points to Seller Central dashboards and account performance reports already visible to the seller. A request framed as "please provide the transaction-level data and buyer-claim data used to calculate the Order Defect Rate that supported the deactivation notice issued on [date], as required under Article [X] of the P2B Regulation" is more likely to receive a substantive response – or a refusal that can itself be challenged.

If the internal complaint does not resolve the issue, the next step under the P2B Regulation is mediation. The regulation requires platforms to nominate certified mediators, and a seller can refer a data access dispute to mediation without first exhausting internal complaint procedures. In practice, internal complaint and mediation tend to be sequential – the platform's response to the internal complaint sets up the mediation record. We discuss the mechanics of this process in more detail in our analysis of mediation under EU marketplace rules.

Court proceedings – in French courts for Amazon FR, or in other EU member state courts depending on the seller's establishment and the applicable jurisdiction – are available as a backstop. The P2B Regulation has direct effect in EU member states, which means a seller can bring a claim for non-compliance in national courts. The practical threshold for litigation is high: the cost and timeline need to be proportionate to the value of the underlying matter. But the existence of a credible litigation path changes the dynamic in mediation and in internal complaint handling.

A home-goods FBA seller on Amazon FR (winter 2025) approached us after a suspension driven by an Order Defect Rate breach that the seller could not reconcile with its own records. We reviewed the deactivation notice and the Account Health data visible in Seller Central, identified a discrepancy in the buyer-claim calculation window, and framed a P2B data access request alongside the Plan of Action appeal. The platform provided transaction-level data that confirmed the seller's records, the Plan of Action was filed on the corrected root cause, and the account was restored. The data access process ran in parallel with the appeal rather than delaying it.

What are the seller's key decision points and trade-offs?

Deciding whether and how to assert data access rights involves a genuine set of trade-offs, and the right answer varies by the type of account issue, the value at stake, and the stage of the dispute.

The first decision is timing. A data access request filed before an appeal, or in parallel with an appeal, is a different exercise from one filed after an appeal has been rejected. Before or during an appeal, the request is aimed at getting the right information to construct the right Plan of Action. After a rejection, the request is aimed at understanding why the rejection occurred and whether there is still a viable path. Both are legitimate uses of the right, but they require different framing and have different realistic outcomes.

The second decision is scope. A data access request that is too broad will be refused or met with a generic response. A request that is too narrow may miss the data that would actually resolve the dispute. Getting the scope right requires understanding both what the seller already knows from its own records and what the platform is required to disclose under the applicable regulation. That is not always intuitive – the P2B Regulation covers data "generated through" the seller's activity on the platform, which includes derived metrics the seller did not produce directly.

The third decision is the channel. Internal complaint, mediation, and litigation are not mutually exclusive, but they are not entirely parallel either. Pursuing all three simultaneously is rarely efficient. The typical sequence – internal complaint, then mediation if needed, then litigation as a last resort – reflects both the regulatory design and the practical cost curve. Skipping the internal complaint step and going directly to mediation may be justified if the platform has already made clear that its internal process will not engage substantively with the specific data request. A seller facing a time-sensitive suspension may not have the luxury of the full sequential process, which is itself a factor in how the request is framed and prioritized.

The fourth decision is whether to treat the data access issue as primary or as ancillary to the main account dispute. In many cases, the most efficient path is to pursue the data access request as a tool that supports the main appeal, not as a separate proceeding. The goal is reinstatement or removal of the restriction, and the data access right is the means to that end. In cases involving systematic data issues – where the seller has had multiple unexplained metric fluctuations over time, or where the platform's data appears to be used inconsistently across sellers – a more standalone data access proceeding may be warranted.

A fashion accessories seller on Amazon DE (spring 2026) came to us with a different configuration: the account was active, but the seller had noticed that its organic ranking in a core category had declined sharply over several months, with no corresponding change in its own performance data. We used the P2B ranking-transparency obligation to request the main parameters Amazon uses for ranking in that category and the weights applied. The response, while not granular, identified a parameter the seller had not previously prioritized. The seller's operations team adjusted accordingly, and ranking recovered over the following weeks. No suspension was involved, and no litigation was needed.

The myth that EU sellers have no leverage once a platform acts

A widely held and commercially damaging belief is that once Amazon or another major marketplace has suspended an account or taken down a listing, the seller's only options are to wait, resubmit, and hope. That belief is understandable – the platform's internal processes can feel opaque, the timeline uncertain, and the communications formulaic. But it is not accurate under EU law as it currently stands.

The combination of P2B, DSA, and DMA obligations means that a seller on Amazon FR has more procedural leverage today than at any prior point. The DSA statement-of-reasons requirement means that a platform decision must be documented. The P2B internal complaint right means that an inadequate response can be formally challenged. The mediation mechanism means that an independent third party can be brought in without going to court. And the existence of judicial remedies in national courts means that the platform's cost of non-compliance is not zero.

None of this means that every suspension is wrongly decided or that every data request will produce a result the seller likes. Some suspensions are correctly issued. Some data requests confirm the platform's position rather than undermining it. The leverage is procedural, not substantive – it gives the seller the right tools to find out what is actually happening and to challenge it if the challenge is well-grounded.

We work with sellers at every stage of that process: from the first data access request framed correctly, through the internal complaint and mediation, to court proceedings where the matter justifies it. The process is attorney-led and confidential, with fees quoted up front after a short review of the account situation.

If you have encountered a platform decision on Amazon FR – or another covered marketplace – that appears to rest on data you cannot see or verify, the question is not whether you have rights, but how to use them effectively. Our full treatment of the broader regulatory environment is in EU marketplace regulation: the complete guide for sellers.

Related areas

• EU marketplace regulation – the complete guide – comprehensive overview of DSA, DMA, and P2B obligations for sellers
• Mediation under EU marketplace rules – how to use the P2B mediation mechanism and what to expect
• EU listing takedown on safety grounds – what changed under GPSR and how to respond

Frequently asked questions

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

There is no single timeline, and the duration depends heavily on which procedural path is used. An internal complaint under the DSA must be handled by the platform within a reasonable period, but the regulation does not set a hard deadline for every type of response. Mediation typically runs over several weeks to a few months, depending on the mediator's schedule and the complexity of the data at issue. Where a data access request is running in parallel with a Plan of Action appeal, the practical answer is that the data request needs to be filed promptly – the appeal timeline does not pause for the data access process. In matters we handle, we frame the request and the appeal to run concurrently where possible, avoiding any delay to the reinstatement path.

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

The primary risk is framing the request too broadly or too vaguely, which typically produces a response that points to information already visible in Seller Central without engaging the underlying data at issue. A second risk is conflating the data access right with the appeal itself: they are related but procedurally distinct, and treating them as one document can dilute both. A third risk is escalating prematurely to mediation or litigation before the internal complaint record is clear, which can limit the options available later. Each of these errors is recoverable, but they add time and cost to a process that is already moving against the seller's account position.

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

Legal representation is not a formal requirement at the internal complaint or mediation stage. For a straightforward data access request running alongside a standard Plan of Action appeal, a well-informed seller may be able to handle the initial steps. The case for legal involvement strengthens significantly once a request has been refused, an internal complaint has not produced a useful response, or the underlying account matter is complex enough that the data issue could affect the entire appeal strategy. At that point, the cost of getting the next step wrong is higher than the cost of getting help. We offer a fixed-fee initial review of the account situation to assess whether legal involvement is warranted and what it would involve.

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 DSA, DMA, and P2B Regulation, and we work with appropriate local counsel for matters requiring national-court proceedings in member states outside our direct coverage. To discuss your situation, email info@tutamenlaw.com.

Written 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.