Why data access rights for EU sellers happens and how sellers respond

When an Amazon FR seller discovers that the data underpinning their business – performance metrics, consumer interaction data, ranking signals – is withheld or presented in a form they cannot act on, the commercial damage starts immediately. Inventory decisions stall. Advertising optimization freezes. The seller cannot see what the platform sees. That information asymmetry is exactly what the EU's layered marketplace-regulation regime was designed to correct, and understanding how those rules operate is the difference between a passive complaint and a structured legal response.

TL;DRData access rights for EU sellers on Amazon FR arise from a combination of the Platform-to-Business (P2B) Regulation, the Digital Services Act (DSA), and the Digital Markets Act (DMA). Together they oblige Amazon – as a Very Large Online Platform and, under the DMA, a gatekeeper – to provide sellers with meaningful access to the data generated by their activity on the platform. When that access is denied, restricted, or opaque, sellers have a defined procedural path to assert their rights: internal complaint, DSA-backed escalation, P2B mediation, and, where warranted, regulatory referral or civil enforcement.

This analysis covers what data access rights actually mean on Amazon FR, why the rights exist and why they are routinely underused, and the realistic sequence of steps a seller can take when the platform's conduct falls short of its obligations.

What do "data access rights" actually mean for a seller on Amazon FR?

Data access rights for EU sellers are not a single entitlement; they are a cluster of obligations spread across three interlocking instruments, each targeting a different dimension of the platform relationship. The P2B Regulation (Regulation (EU) 2019/1150) is the foundation: it requires online intermediation services to give business users transparency about the parameters that determine ranking, and access to the personal and non-personal data that those users or their customers generate on the platform. Amazon is squarely covered. The DSA strengthens enforcement by requiring Very Large Online Platforms (VLOPs) – a designation Amazon holds – to maintain an internal complaint-handling system for sellers and to report on how access issues are resolved. The DMA adds a sharper edge: as a gatekeeper, Amazon faces specific obligations to share with business users the data relevant to their use of the platform, in real time and in a usable format, where that data was generated by those users' own activity.

In practical terms, what this means for an Amazon FR seller is that certain categories of data should not be a black box. Ranking parameters – the factors Amazon uses to determine where a listing appears in search results – must be disclosed in a way the seller can understand and act on. Data about how consumers interact with the seller's listings, to the extent it is generated by the seller's own commercial activity, falls within the scope of the DMA's access obligations. And when Amazon takes a decision that restricts the seller's access to data – or modifies how it is presented, or removes it without explanation – the P2B Regulation requires that decision to be explained in a statement of reasons.

What the rules do not do is require Amazon to hand over all platform data or to disclose proprietary algorithms in full. The obligations are calibrated: they attach to data generated by the seller's own activity, not to the platform's general business intelligence. That distinction matters enormously when a seller is deciding which data point to push on. In matters we handle on Amazon FR, the most common dispute is not a blanket refusal but a selective opacity – the seller receives data, but in an aggregated or delayed form that strips out the granularity they need to make operational decisions. That is where the legal argument lives.

Why does the problem arise? The structural mechanics of platform data asymmetry

The data gap between Amazon and its third-party sellers on Amazon FR is not accidental – it is structural, and it has commercial logic from the platform's perspective. Amazon operates simultaneously as a marketplace facilitator and as a competing retailer through its own first-party business. The same data that would help a third-party seller optimize their listings also informs Amazon's decisions about which products to stock, source, or promote directly. That dual role is precisely what the DMA's gatekeeper obligations target, and it explains why the access problem tends to cluster around the most commercially sensitive categories: search ranking signals, buy-box eligibility criteria, and advertising attribution data.

For a seller on Amazon FR, the practical effect is familiar. They can see their own sales data and a filtered version of their performance metrics in Seller Central. What they typically cannot see is why their ranking changed, how their performance compares to the internal benchmarks Amazon uses to make buy-box determinations, or how Amazon's own first-party listings are treated in the same algorithmic environment. With EU marketplace rules now in force and the DMA's gatekeeper obligations actively applying to Amazon, those gaps are no longer purely a commercial grievance – they are potentially a regulatory compliance failure on the platform's part.

There is a second driver that matters operationally: enforcement automation. As Amazon has scaled its compliance and enforcement infrastructure, decisions about data provision are increasingly made at the system level rather than through individual account management relationships. A seller whose access to a particular data set is quietly changed by a policy update may not even receive a notice. The absence of a formal deactivation notice makes the path forward less obvious, which is why many sellers on Amazon FR sit with the problem for longer than they should.

We regularly see a pattern where a seller has noticed the data gap for several months before they take any formal step. That delay matters because the P2B Regulation's internal complaint mechanism and the DSA's internal complaint-handling system both work better when the seller can document a clear and dated account of what changed, when, and what operational decisions were affected. Starting the paper trail early is not a procedural nicety – it is the foundation of any later legal argument. For a broader grounding in how these instruments interact, the complete guide to EU marketplace regulation for sellers maps the full regulatory picture.

What is the realistic procedural path on Amazon FR?

The first formal step is the internal complaint mechanism that both the P2B Regulation and the DSA require Amazon to operate. A seller asserting a data access right submits a complaint through Amazon's internal system – Seller Central, in practice – identifying the specific data or explanation they are seeking, the legal basis for the request, and the commercial impact of the gap. This step is mandatory before escalation, and it is also where most sellers underperform. A complaint that reads like a support ticket will be treated like one. A complaint that identifies the specific obligation under the P2B Regulation or the DMA, describes the data category in question, and quantifies – even in general terms – the operational harm is a different document with a different processing path.

If the internal complaint does not resolve the matter, the P2B Regulation provides access to a mediation route. Amazon is required to identify at least two mediators in its terms and conditions; those mediators are available to business users who have exhausted the internal complaint process without a satisfactory result. Mediation under P2B is not litigation – it is structured negotiation with a third-party neutral – and it can produce a practical resolution (access to the data, a clearer explanation of ranking parameters, a revised statement of reasons) faster than a regulatory referral. For sellers weighing that path, the analysis of mediation under EU marketplace rules covers the process and what to expect.

Beyond mediation, the DSA opens a further channel: the Digital Services Coordinator (DSC) in France – the regulatory body responsible for enforcing the DSA in the French jurisdiction – can receive complaints from sellers about VLOP compliance. A well-documented referral to the French DSC is not guaranteed to produce an individual remedy, but it serves two functions: it creates an official record, and it contributes to the regulatory pressure that shapes platform behavior at the systemic level. For matters with a cross-border EU dimension, the European Board for Digital Services can also be engaged.

The DMA creates an additional track. The European Commission has exclusive enforcement jurisdiction over gatekeeper obligations. A business user who has a well-documented case that Amazon is failing its DMA data-access obligations can submit a complaint to the Commission. Commission enforcement is slow by design – it operates at a systemic level, not an individual account level – but the existence of an open Commission investigation into Amazon's gatekeeper compliance (a matter of public record in EU regulatory circles) means that a well-evidenced complaint from a French seller is not entering a void. It is contributing to a live enforcement file.

In parallel with any of these administrative routes, a seller may have a civil claim under French or EU law for breach of the regulatory obligations. The P2B Regulation allows representative bodies and certain organizations to bring court proceedings against platforms for breaches of its provisions. Individual sellers can pursue civil remedies in French courts for harm caused by a regulatory violation. The threshold for a civil action is higher – the seller needs to demonstrate actual harm and causation, not just a compliance gap – but it is a real option where the financial stakes justify it.

Where does the seller's strategy actually turn?

The decision that matters most is not whether to complain but how to frame the complaint. A seller who goes to Amazon's internal system with a request for "better data" will get a polished non-response. A seller who arrives with a specific demand – "you are required under Article 9 of the P2B Regulation to provide us access to the data we and our customers generated on this platform in a form that allows operational use, and you are currently providing it in an aggregated weekly format that prevents that use" – is making a legal demand, not a support request. That framing changes how the complaint is handled.

The second strategic pivot is the choice between escalation tracks. Mediation is faster and lower cost. A regulatory referral is slower but creates leverage. A civil action is the most resource-intensive but the most powerful for individual remedy. In most matters we handle on Amazon FR, the sequence is: internal complaint with precise legal framing → mediation if not resolved → regulatory referral or civil proceedings depending on the financial stakes and the seller's tolerance for a longer timeline. There is rarely a reason to jump to civil litigation before the administrative routes are exhausted – both because the courts will expect it and because the paper trail from the earlier steps is valuable evidence.

The third variable is urgency. A data access restriction that is causing ongoing commercial harm – a seller who cannot optimize their advertising on Amazon FR because they lack attribution data, losing margin every week – has a different calculus than a seller who wants the data for a retrospective analysis. Where the harm is ongoing, the internal complaint and a parallel DSA complaint to the French DSC are the fastest levers. Where the harm is historical, a more considered approach to mediation or civil recovery may be more appropriate.

There is a common belief among sellers that EU rules give them only a weak argument once a platform has made a decision. That belief is wrong, and it is worth examining directly. The P2B Regulation, the DSA, and the DMA do not give sellers the right to override Amazon's business decisions. But they do impose substantive obligations on how those decisions are made and communicated, and they create enforceable rights when those obligations are breached. The seller who accepts a data gap as a fait accompli, without engaging the legal instruments available, is leaving those rights on the table. That is the lost opportunity this analysis addresses.

The bridge between a data access dispute and a listing takedown or suspension is shorter than many sellers realize. A seller who lacks access to the performance data that explains a listing restriction – who cannot see why their Account Health metrics changed, or why a product was delisted – may be dealing simultaneously with a data access issue and a suspension issue. The tools for each overlap. The response checklist for listing takedowns on safety grounds covers adjacent procedural steps that often run in parallel with a data access dispute.

One further point on the DMA specifically: the gatekeeper obligations around data access are designed to address the conflict of interest inherent in Amazon's dual role. Where a seller can show that the data being withheld is directly relevant to their ability to compete with Amazon's own first-party listings on Amazon FR, that argument is specifically on point for DMA purposes. It is not a hypothetical claim. It is the mechanism the DMA was written to address.

Micro-cases: how the issue presents in practice

A consumer-electronics accessories seller on Amazon FR (winter 2025) came to us after discovering that their buy-box eligibility metrics had changed without any corresponding notice or explanation in Seller Central. Their sales had dropped materially over several weeks. The standard support escalation produced automated responses that cited general performance criteria but gave no specific basis for the change. We identified the relevant obligation under the P2B Regulation – the requirement for a statement of reasons for any restriction of the seller's visibility – drafted a formal internal complaint on that legal basis, and followed it with a request for mediation when the internal complaint produced only a generic acknowledgment. The mediation produced a specific written explanation of the factors that had changed the eligibility assessment, which the seller was then able to act on operationally.

In a separate matter, a fashion-category seller on Amazon FR (summer 2026) contacted us after their advertising attribution data became unavailable in the format they had relied on for campaign optimization. The change followed a platform-wide update to the Seller Central analytics dashboard. The seller's advertising spend was effectively flying blind. We mapped the data obligation under the DMA's access provisions, prepared a detailed internal complaint identifying the specific data category and the legal basis for access, and filed a parallel complaint with the French Digital Services Coordinator documenting the operational impact. The internal complaint resulted in Amazon restoring access to granular attribution data within a defined reporting window. No formal regulatory ruling was required – the documented legal framing, combined with the regulatory referral on file, created sufficient leverage for a practical resolution.

What changes when the stakes are higher?

For most sellers on Amazon FR, the data access dispute is a business problem: they are missing information they need to run their account efficiently. But for some sellers, particularly those in categories where Amazon has significant first-party presence, the stakes are higher. A seller who can demonstrate that the withheld data specifically enabled Amazon to make competitive decisions – to source, price, or promote competing products on the basis of data generated by the seller's own customers – is in the territory of DMA Article 5 and Article 6 gatekeeper obligations. That is a different legal analysis and a different enforcement track.

It is also worth noting that the EU's regulatory apparatus for marketplace compliance is still maturing. The DMA gatekeeper obligations have been in force for a relatively short period, and the Commission's enforcement practice is developing. That means the regulatory pressure on platforms is increasing over time, not decreasing – and sellers who document their data access disputes carefully now are building a record that has value both in their individual matter and in the broader enforcement picture.

If a first complaint or escalation has already come back with a non-substantive response, a second read can find where the framing was too general, whether the correct legal basis was identified, and whether the mediation or regulatory track was properly engaged. In our practice, a significant share of the data access matters we take on have had at least one prior attempt that did not gain traction – not because the underlying legal right was weak, but because the initial complaint did not speak the language the platform's compliance function responds to.

To discuss a data access dispute on Amazon FR or another EU marketplace, email info@tutamenlaw.com for a confidential review of the specific situation.

The seller's decision matrix

The realistic path depends on what the notice or gap actually says. If the data access issue is a missing or inadequate statement of reasons for a ranking or eligibility change, the route is the P2B internal complaint, on a timeline of several weeks for a substantive response. If the data issue involves ongoing denial of access to data generated by the seller's own activity, the route is a parallel internal complaint and DMA-framed demand, with a regulatory referral to the French DSC if not resolved, on a timeline of weeks to several months depending on the platform's response. If the matter involves harm the seller can quantify – lost revenue, advertising waste, margin compression attributable to the data gap – a civil action in French courts is a parallel option, on a longer timeline but with the most direct individual remedy.

If instead the notice cites a general platform policy change with no seller-specific explanation, the argument is under P2B Article 3, requiring transparency about the parameters of the change and any differential treatment. If the issue crosses into the platform's use of the seller's data to compete with that seller directly, the argument is under the DMA's core gatekeeper prohibitions, and the Commission is the right destination.

The decision to act – and how quickly – is ultimately a commercial judgment. A seller who tolerates the data gap because the escalation feels risky is, in practice, subsidizing the information asymmetry that the EU rules were written to correct. The leverage exists. The question is whether the seller uses it.

Related areas

• EU Marketplace Regulation: Complete Guide – the full regulatory picture for EU and UK marketplace sellers
• P2B Mediation for Marketplace Sellers – how to use the required mediation route under EU rules

Frequently asked questions

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

Resolution timelines vary with the route chosen and the platform's responsiveness. An internal complaint under the P2B Regulation or DSA typically draws an initial response within several weeks, though a substantive outcome may take longer if escalated to mediation. A P2B mediation process adds further time – typically several weeks to a few months. A regulatory referral to the French Digital Services Coordinator operates on the regulator's own timeline, which can extend to many months. Civil proceedings in French courts take the longest. In matters where the data gap is causing ongoing commercial harm, the internal complaint and a parallel regulatory complaint are the fastest tools available.

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

The principal risk is framing. An internal complaint that reads as a general dissatisfaction with the platform's data provision will be processed as a support ticket and likely closed with a generic response. The P2B Regulation, DSA, and DMA each impose specific obligations with specific legal language; a complaint that does not identify the relevant provision and the precise data category in issue does not engage the compliance function that processes legal demands. A second risk is sequencing: going straight to a regulatory referral before the internal complaint is exhausted may both delay relief and undermine a later civil claim. A third risk is evidence management – failing to document the commercial impact of the data gap from the outset weakens any later damages argument.

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

Not for every step, but the quality of the internal complaint typically determines whether the matter resolves early or escalates. Sellers who frame their initial complaint with the correct legal basis – identifying the specific P2B, DSA, or DMA obligation in issue and the precise data category – have a materially better rate of substantive response than those who escalate through the standard support channel. Where the matter involves significant ongoing commercial harm, a regulatory referral, or potential civil proceedings, attorney involvement at the drafting stage is worth the cost. A fixed-fee review of the situation and the complaint framing is the most efficient entry point for most sellers.

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 practice covers data access rights, suspension and delisting challenges, P2B mediation, DSA and DMA-based regulatory referrals, and civil enforcement before national courts. To discuss your situation, email info@tutamenlaw.com.

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.