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

When an Amazon FR seller loses access to their own sales data, the damage is not the notification – it is the inventory decisions, pricing strategies, and VAT reports that depend on that data every single day. EU marketplace rules give sellers concrete rights to the information that platforms generate about their activity, and those rights are enforceable. The question is whether the seller knows the steps to use them before the commercial harm compounds.

TL;DREU sellers on Amazon FR have legally grounded data access rights under the Platform-to-Business (P2B) Regulation and the Digital Services Act (DSA). When a platform restricts, denies, or delays access to seller data, a structured internal complaint followed, if necessary, by mediation or regulatory escalation is the realistic path to restoring that access. The window to act effectively is shorter than most sellers expect, and the first step is documenting exactly what is missing before sending anything to Amazon.

This guide walks through the step sequence in the order that matters – what data EU sellers are actually entitled to, how to recognize when access has been unlawfully restricted, how to build and submit a complaint, and where the process most often breaks down. Each stage carries a decision point; the guide flags those explicitly.

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

Data access rights in the EU marketplace context are not a single entitlement – they are a cluster of obligations imposed on large platforms by several overlapping instruments, each with its own scope and enforcement path.

The Platform-to-Business (P2B) Regulation is the foundation. It requires Amazon and other platforms to give business sellers access to the personal and non-personal data that the seller's activity on the platform generates or that the seller has provided. That includes order data, buyer interaction records (to the extent the platform holds them), performance metrics that the platform uses to rank or restrict the seller's listings, and the inputs into any algorithmic system that affects the seller's visibility. The P2B Regulation applies to Amazon's EU-based marketplace operations, meaning Amazon FR is squarely within scope.

The Digital Services Act (DSA) adds a second layer. Amazon operates as a Very Large Online Platform (VLOP) under the DSA. VLOP obligations include transparency about how recommender systems work, how content or seller accounts are moderated, and what data the platform holds and uses in those decisions. Where a seller's data has been used to justify a restriction, suspension, or de-ranking, the DSA statement of reasons requirement means the platform must explain the decision in terms specific enough for the seller to understand and challenge it.

The Digital Markets Act (DMA) is a third instrument. Amazon has been designated as a gatekeeper under the DMA. Gatekeeper obligations include not using data generated by business users to compete against those users, and giving business users access to their own data in real or near-real time. For an Amazon FR seller, the DMA data portability and non-discrimination obligations sit on top of P2B and DSA rights – they do not replace them.

What does this mean in practice? If Amazon FR has restricted your Seller Central dashboard, removed access to historical order data, withheld the data inputs behind an Account Health Rating change, or declined to explain the algorithmic basis for a listing demotion, each of those situations is potentially a violation of one or more of the instruments above. In matters we handle, sellers often arrive having accepted a platform's generic response as the end of the road. It rarely is.

For the broader regulatory backdrop behind these instruments, see our EU marketplace regulation: the complete guide for sellers, which maps how P2B, DSA, and DMA interact across the main dispute types.

Step 1: Audit what data you are missing and document the gap

The first concrete step is a structured audit of what you can and cannot access, conducted before you contact Amazon. This sounds obvious; in practice, sellers almost always skip it, which weakens every subsequent step.

Open a clean working document. For each category of data you rely on – order history, return reasons, buyer messages, performance metrics, advertising attribution data, FBA inventory history – record three things: the specific data set, the date you last had reliable access, and the platform message or system behavior that indicates the restriction. Screenshots with timestamps are the minimum. If you can export what you still have access to, export it now.

This matters because EU rights are specific, not general. A complaint that says "I cannot access my data" will receive a generic response. A complaint that says "Since [date], the Seller Central Business Reports for Amazon.fr have been restricted to 30-day exports, whereas the P2B Regulation and your own terms require access to the full trading history for the duration of the commercial relationship" gives the platform a precise obligation to respond to and gives a mediator or regulator a concrete fact pattern to evaluate.

Decision point: At this stage, determine whether the restriction is a technical glitch, a policy-driven change, or a consequence of an account action (suspension, verification hold, ASIN removal). The three scenarios require different approaches. A technical restriction often resolves through Seller Support. A policy-driven change or post-suspension restriction requires the formal route described in the steps below.

One further check: confirm which Amazon marketplace entity holds the data. For Amazon FR, the contracting entity is Amazon Services Europe S.à r.l., and the data controller for P2B and GDPR purposes will be specified in your Business Solutions Agreement and privacy notice. This determines which complaint body has territorial jurisdiction.

Step 2: Send a formal data access request through Amazon's internal complaint system

Every platform operating under the P2B Regulation must provide an internal complaint-handling system for business sellers. Amazon FR has one; it is the entry point for any formal data rights claim, and using it creates the paper trail that every subsequent escalation depends on.

Your request should be in writing. If Amazon's system allows free-text complaints, use that channel. If not, email is acceptable – direct the message to the business seller support channel and state explicitly that it is a formal complaint under the P2B Regulation, Article 11. That statutory reference matters: it triggers the platform's obligation to handle the complaint in a timely and non-discriminatory manner and to communicate the outcome and reasoning.

The complaint letter should do four things. First, identify the data sets at issue using the specific categories from your Step 1 audit. Second, state the legal basis – the P2B Regulation's access and transparency provisions and, where applicable, the DSA statement of reasons obligation and DMA data-access obligations. Third, state the commercial impact in factual, non-hyperbolic terms: "Without access to historical order data, we cannot reconcile VAT obligations under French tax law for Q3 and Q4." Fourth, state what you want: full restoration of access, or in the alternative, a complete and specific explanation of why access is restricted and under what provision.

Set a response deadline. The P2B Regulation requires platforms to handle internal complaints in a timely manner, and while it does not specify a precise calendar deadline for every scenario, a reasonable benchmark for internal complaints is in the region of several weeks. In our practice, sellers who set an explicit deadline in the complaint letter tend to receive more substantive responses than those who do not.

Keep a copy of everything sent, the timestamp of submission, and any acknowledgment you receive. This is your evidence file for Steps 3 and 4.

Step 3: Evaluate Amazon's response – or absence of one

Amazon will respond in one of four ways: full resolution, partial resolution, a denial with reasons, or silence. Each outcome has a different next step, and confusing them is one of the most common mistakes sellers make at this stage.

Full resolution – access restored, explanation provided – closes the immediate issue. Document the resolution. If access is restored but the explanation is inadequate (for example, if the restriction was caused by an algorithmic system and no explanation of that system's operation was given), the DSA transparency obligation may still be live.

Partial resolution – access restored to some data but not all, or access restored without explanation – leaves the complaint open. Respond in writing, identifying the outstanding items specifically, and give a further short deadline before you escalate.

A denial with reasons is actually useful. It gives you the platform's stated position, which you can now test against the applicable legal standard. If Amazon cites a policy provision as the basis for withholding data, the P2B Regulation requires that provision to be set out in the platform's terms and conditions in plain and intelligible language. If it is not, or if the policy does not justify the restriction under the regulation, you have the basis for an external escalation.

Silence or a generic acknowledgment without substantive engagement is itself relevant. Under P2B, the platform is required to handle complaints. Failure to do so meaningfully is a basis for escalation to a mediator or to the competent national authority.

Decision point: Before escalating, weigh the commercial stakes against the time and effort of external escalation. If the data at issue is non-critical or recoverable by other means, escalation may not be the right tool. If the restricted data is material to your tax reporting, operational decisions, or a pending legal dispute, escalation is worth pursuing. In matters we handle, this weighing conversation takes place before any step 4 filing.

Step 4: Escalate to mediation under EU marketplace rules

The P2B Regulation requires Amazon to identify at least two mediators that the platform is willing to engage for disputes with business sellers. Where internal complaint procedures have not produced a satisfactory outcome, a seller can initiate mediation through one of those named mediators. This is a significant lever that most sellers on Amazon FR do not use.

Mediation under P2B is not binding on the platform in the same way that a court judgment is. However, it has real practical weight. Platforms are required to engage with the process in good faith, and a mediator's findings create a record that regulators and courts find useful. In our experience, the formal initiation of mediation frequently produces a more substantive response from the platform than anything that preceded it.

Our guide on mediation under EU marketplace rules: what to do step by step sets out the full procedural sequence. For present purposes, the key points are: (a) you need the evidence file built in Steps 1 through 3 before you file; (b) the mediator will be evaluating whether the platform complied with P2B obligations, so framing the complaint in P2B terms from the start is essential; and (c) the platform's selection of mediators is published in its terms and conditions, and you are not obligated to use a mediator that the platform itself controls.

Where the data restriction is connected to a listing removal or account action on safety grounds, the procedures interact. See our EU listing takedown on safety grounds: the response checklist for the specific steps when data access and listing removal are linked.

Step 5: Regulatory escalation and the DMA complaint path

Mediation is not the only escalation path. Two regulatory routes run in parallel, and sellers often overlook both.

The first is the competent national authority for P2B enforcement. In France, for Amazon FR matters, the direction responsible for monitoring digital market fairness is the relevant body. A formal complaint to the national authority is distinct from mediation: it asks a public body to assess whether the platform has violated its statutory obligations. The authority has no timeline obligation to any individual seller, but a pattern of complaints generates supervisory attention and, in some cases, formal enforcement proceedings.

The second is the European Commission's DMA enforcement unit. Amazon's designation as a gatekeeper means the Commission has direct enforcement jurisdiction over gatekeeper obligations, including the data-access and portability rules. Complaints from business users feed directly into Commission monitoring of compliance. The Commission has opened proceedings against gatekeeper platforms, and individual seller complaints contribute to the factual record even when the complainant is not a party to the enforcement action.

The DMA path is not a fast-resolution tool. Commission proceedings operate on a regulatory timeline, not a commercial one. But the act of filing a well-documented DMA complaint does two things: it creates an official record of the violation and, in some circumstances, it changes the platform's incentive to resolve the matter internally before regulatory scrutiny intensifies.

Where this goes wrong: sellers who file regulatory complaints without having first exhausted the internal complaint-handling process weaken their case. Regulators will ask whether internal remedies were used. The sequence in this guide – audit, internal complaint, evaluate response, mediate, escalate – reflects the structure that regulators expect to see documented.

Where the process most often breaks down

In matters we handle involving EU data access rights on Amazon FR and other platforms, the failures cluster at three points.

The first is the framing of the initial complaint. Sellers who write to Seller Support in conversational terms, or who describe their problem rather than stating a legal right, receive support-tier responses rather than compliance-tier ones. The P2B and DSA language is not optional decoration; it routes the complaint to the right team within the platform and sets the standard by which the response will be judged externally.

The second is delay. EU marketplace rules contain rights, but those rights operate in a context where commercial harm compounds daily. A seller who waits several weeks before sending the internal complaint, then waits for a further month after an unsatisfactory response before initiating mediation, may have lost the operational window to recover the most time-sensitive data meaningfully. Acting promptly – without acting sloppily – is the discipline this process demands.

The third is conflation of different data rights. GDPR subject access rights, P2B business-data access rights, and DSA transparency rights are different instruments with different scopes, different complaint routes, and different timelines. Sending a GDPR subject access request when you need P2B business data access takes the complaint to the wrong body and wastes the window for the right one. The audit in Step 1 should categorize which instrument governs which data set before anything is sent.

A mid-market accessories seller on Amazon FR (spring 2026) came to us after six weeks of Seller Support exchanges that had produced nothing more than acknowledgments. The seller's VAT reconciliation for the prior year was blocked because Amazon had restricted access to the historical Business Reports as part of a broader account verification hold. We categorized the restriction correctly – a P2B data access issue, not a GDPR request – drafted a formal P2B complaint citing the specific provision and the specific data sets, and set a deadline. Within the internal complaint window, Amazon restored access to the full historical data and provided a written explanation of the restriction. The VAT filing was completed without further delay.

Before you file anything: if you have already attempted to handle a data access restriction through Seller Support without success, a second read of the account situation by a lawyer who works in EU marketplace regulation regularly can identify whether the complaint was framed on the right legal basis – and whether anything is still open.

If the first attempt at resolving a data access issue did not produce a substantive response from the platform, the issue is almost always the framing of that first approach, not the underlying entitlement. To have the situation reviewed, email info@tutamenlaw.com.

Decision points summarized: how to choose your route

Not every data access problem requires every step in this guide. The route depends on what the platform's response has been and what the commercial stakes are.

If the restriction is a technical error and Seller Support confirms it is being corrected – pause at Step 1, document the resolution, and monitor. If the platform has given a substantive denial citing a policy provision, move directly to testing that provision against the P2B standard before deciding whether to mediate. If the platform has given no substantive response after a reasonable period, mediation is the appropriate next step without waiting further. If the restriction is connected to a designation-level obligation – a DMA gatekeeper rule, for example, about not using your data to compete against you – regulatory escalation to the Commission is the right parallel track.

On costs: the internal complaint and regulatory complaint routes carry no platform filing fee. Mediation under P2B costs are borne by the platform for the platform's share and, depending on the mediator's rules, a contribution from the business user. Legal representation in mediation is not mandatory, but it materially affects the quality of the framing. Our work on data access rights matters is handled on a fixed fee basis, quoted after a short initial review of the situation.

Related areas

• EU Marketplace Regulation – representation for EU and UK sellers facing suspension, delisting, and data-access issues
• EU marketplace regulation: the complete guide – how P2B, DSA, and DMA interact for Amazon sellers

Frequently asked questions

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

The timeline depends heavily on which route the matter follows. An internal complaint that is correctly framed and addressed to the right team can produce a substantive response within several weeks. Where mediation is needed, the full process typically runs over a period of months, depending on the mediator's schedule and the complexity of the data sets at issue. Regulatory complaints to national authorities or the European Commission operate on a longer administrative timeline and are not a substitute for mediation where fast resolution is the priority. Acting promptly at Step 1 – and framing the complaint correctly from the start – is the single factor most within the seller's control.

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

The most common risks are mis-framing the complaint (confusing GDPR subject access, P2B business data access, and DSA transparency rights, which route to different bodies and have different scopes), underestimating how quickly the commercial harm compounds while informal channels are exhausted, and accepting a generic platform response as a final answer when the legal obligation has not been satisfied. A further risk is filing a regulatory complaint before the internal complaint process has been properly used, which regulators treat as a procedural gap. Each of these errors is recoverable, but each narrows the practical options for the steps that follow.

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

You are not legally required to use a lawyer at any stage of this process, including mediation. In practice, the P2B and DSA framing of the initial complaint, the selection and engagement of the right mediator, and the drafting of a regulatory complaint that will be taken seriously all benefit materially from specialist input. The cost of legal help at the early stages is typically far lower than the cost of rebuilding an improperly filed complaint track or recovering from a default at a stage where the option has narrowed. Attorney involvement also makes the process formally attorney-led and confidential, which matters if the data at issue is relevant to a parallel dispute or regulatory inquiry.

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, DSA statement of reasons, P2B complaints, and DMA gatekeeper obligations across all covered surfaces. 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. Published February 19, 2027.