Data access rights for EU sellers: a seller's checklist

When an Amazon FR seller asks for their account data – performance metrics, ranking signals, the reasoning behind a listing restriction – the platform's response is rarely a clean download. The EU rules that underpin these requests exist, they carry real procedural weight, and most sellers on Amazon France have never used them. That gap is a lost opportunity: the same data that platforms treat as proprietary is precisely the evidence that can unlock a suspended listing, challenge a termination, or support an arbitration claim.

TL;DREU sellers on Amazon FR hold concrete data access rights under the Platform-to-Business (P2B) Regulation, the Digital Services Act (DSA), and the Digital Markets Act (DMA). These rights cover the ranking parameters that affect listing visibility, the grounds for any restriction or suspension, and the data used to support those decisions. Exercising them follows a specific sequence – internal complaint first, then escalation – and a seller who skips or misframes a step weakens every avenue that comes after.

This checklist works through that sequence phase by phase. Each phase identifies what to check, what to preserve, and where the decision points sit.

Phase 1: Understand what data rights you actually hold

The first question is not "how do I get the data?" – it is "what does EU law say I am entitled to see?" The answer spans three separate instruments, and the overlap between them is what gives sellers real leverage on Amazon FR.

The Platform-to-Business (P2B) Regulation was the first instrument to impose transparency obligations directly on marketplace operators toward business users. It requires platforms to disclose the main ranking parameters and the reasons for any individual restriction or termination. A seller on Amazon FR is a business user under P2B. That is not a legal argument to be made – it is a classification the regulation sets automatically for any business selling on a platform that is subject to EU law.

The Digital Services Act (DSA) applies to Amazon as a Very Large Online Platform (VLOP). The DSA's statement-of-reasons obligation means that every time a platform restricts, demotes, suspends, or terminates a seller's account or listing, it must provide a statement explaining the decision – the facts, the grounds, and the policy or rule applied. The seller has a right to that statement. We regularly see sellers who received a generic notice from Amazon FR that cites a policy category but gives no reasoning specific to their account; that notice may not satisfy the DSA requirement.

The Digital Markets Act (DMA) applies to Amazon as a designated gatekeeper. The DMA creates additional data-access obligations, particularly around the data Amazon holds about a seller's customers and transactions that the seller cannot access directly through Seller Central. This is a distinct category from the transparency rights under P2B and the DSA, and it sits in a different enforcement channel.

Checklist – Phase 1:

1. Confirm that your Amazon FR seller account is registered as a business entity (not an individual consumer account). P2B coverage requires business-user status.
2. Identify every notice, policy alert, or account action you have received in the last twelve months. Note whether each one included a specific statement of reasons or only a generic policy reference.
3. List the data categories you need: ranking parameters, restriction grounds, performance-metrics history, transaction and customer data held by Amazon but not visible in Seller Central.
4. Separate those three categories into the instrument that governs each – P2B, DSA statement of reasons, or DMA data access – because the request mechanism and escalation path differ for each.
5. Check the date of each adverse notice. Some procedural rights have time windows that begin from the date of notification, not from the date you choose to act.

Phase 2: Audit your existing Seller Central records before making any request

Before sending any formal data request, preserve and document everything already available to you – because once you have filed a complaint or request, what you had at the outset shapes what the platform can claim it already disclosed.

In matters we handle for Amazon FR sellers, a significant share of the evidence we use was already present in the account dashboard, performance notifications, and email correspondence – it had simply not been captured in a usable form before the seller contacted us. Platforms have a structural advantage here: they retain records in their own systems; the seller's access to Seller Central can be restricted at any point.

Checklist – Phase 2:

1. Download all Account Health notifications and any policy-violation messages, including any that were later removed or marked as resolved.
2. Export your transaction history, disbursement records, and any held-balance or reserve notices.
3. Take timestamped screenshots of your current listings, their status, any suppressed or blocked indicators, and the ranking or visibility metrics visible in Seller Central.
4. Save all email correspondence with Amazon Seller Support, including ticket reference numbers and dates. These may later establish the timeline of your requests and the platform's responses.
5. If you have received a restriction or suspension notice, copy and preserve the exact text of that notice, including any codes, policy references, or case identifiers it contains.
6. Record whether you have received a DSA-compliant statement of reasons (specific facts and grounds) or only a generic policy citation. That distinction matters procedurally.

The audit in this phase does not depend on any platform cooperation. It uses data you already have access to. Do it before anything else, because later steps may prompt platform action that changes your Seller Central view.

For a broader grounding in the instruments that apply, the EU marketplace regulation guide for sellers sets out how P2B, the DSA, and the DMA interact across all major EU marketplaces.

Phase 3: Draft and file the formal data request

A formal data request under EU marketplace rules is not a help-center ticket. It is a written request invoking a specific legal right, directed to the correct entity, framed in terms the platform's legal and compliance team will recognize. The difference between a help-center message and a properly framed P2B or DSA request is the difference between a discretionary customer-service response and a legal obligation to respond.

Amazon FR's internal complaint-handling system – required under the DSA – is the first formal channel. The P2B Regulation also requires platforms to operate an internal complaint-handling mechanism for business users. These are not the same channel as Seller Support. Identifying and using the correct channel is itself a step that requires some care.

What a seller in this position is actually trying to achieve may differ. Some want the specific ranking parameters that explain a drop in visibility. Others want the factual basis for a listing restriction so they can address it directly. Others still want the transaction data Amazon holds about their customers that is not surfaced in Seller Central. The framing of the request should match the specific data category being sought.

Checklist – Phase 3:

1. Identify whether you are requesting (a) ranking-parameter transparency under P2B, (b) a DSA statement of reasons for a specific adverse decision, or (c) DMA gatekeeper data access. Use the right instrument and right channel for each.
2. Write the request in clear, specific terms: identify the decision or action, the date, the data category you are seeking, and the legal basis for the request. Vague requests get vague responses.
3. Direct the request to Amazon's designated internal complaint channel, not to generic Seller Support. Keep a copy of the submission, including the date and method of transmission.
4. Note the response deadline. The P2B Regulation and DSA each impose obligations on the platform to respond; the timeline for compliance is a matter of the applicable regulation and the platform's own stated procedures.
5. If Amazon FR responds but the response does not actually provide the data requested – a common outcome – record that response precisely as it is. A non-responsive reply is itself material for the next phase.
6. Do not submit multiple overlapping requests simultaneously. Parallel filings can allow a platform to argue ambiguity or to respond to the least specific version.

A mid-market fashion seller on Amazon FR (fall 2026) came to us after a listing demotion that had cut visibility on their primary category by more than half. They had already submitted two help-center tickets and received standard responses citing general ranking guidelines. We drafted a P2B-compliant transparency request naming the specific ranking parameters at issue and the relevant listing identifiers. Amazon FR's compliance team responded with a more substantive disclosure than anything previously provided, and the seller was able to identify a policy-compliance issue that had been applied inconsistently across their catalog.

Phase 4: Evaluate the platform's response – and what to do if it falls short

The platform's response to a formal data request tells you several things at once: what it is willing to disclose voluntarily, what it is treating as proprietary, and how carefully it is managing its obligations under the regulation. Not all responses are equal, and a seller's next move depends entirely on what the response actually contains.

In our practice, the most common outcome is a partial response – the platform provides some data but withholds categories it describes as commercially sensitive or covered by third-party rights. That framing is sometimes legitimate; it is sometimes an overclaim. The question is whether the withholding is consistent with the specific obligations under P2B or the DSA.

Checklist – Phase 4:

1. Map the response against your original request item by item. What was provided? What was refused? What was provided in a form that is not actually usable (for example, aggregated data where you requested item-level data)?
2. Check whether any refusal cites a specific exemption under the applicable regulation. Under P2B, a platform may withhold ranking parameters only on specific grounds; a blanket confidentiality claim may not be sufficient.
3. If the response includes a DSA statement of reasons, assess whether it contains the specific facts, the policy or rule applied, and any redress options the platform is required to disclose. Boilerplate does not satisfy the obligation.
4. Decide whether to escalate via the internal complaint mechanism (a second internal stage), seek mediation under the P2B Regulation's mediator-access provision, or move to a regulatory or judicial route.
5. If the data obtained reveals a specific factual error in the platform's decision – for example, a restriction applied on the basis of incorrect performance data – that is a discrete issue you can address directly, separately from the broader data-access question.

The idea that EU sellers have no leverage once a platform suspends or restricts them is a myth worth addressing here. The DSA and P2B regime creates real procedural obligations for platforms. Those obligations are not self-executing – the seller must invoke them in the right form and through the right channel – but when they are properly used, they change the platform's response calculus. A platform that has received a properly framed DSA complaint from a business user cannot treat it the same way it treats a Seller Support ticket.

To understand how mediation fits into this escalation path, the guide to mediation under EU marketplace rules explains the P2B mediator-access provision and when it is the right tool.

Phase 5: Escalation routes and when to use each

When internal complaint channels have been used and the response is still inadequate, the EU regime offers several escalation routes. Choosing among them is a strategic decision – it turns on what you are trying to achieve, how quickly you need it, and what evidence the data-request process has already produced.

The decision path in outline: if the platform has failed to provide a P2B-compliant transparency disclosure, and the information relates directly to a listing restriction or suspension, the most time-efficient first step is usually a written escalation through the DSA's internal complaint mechanism with an explicit statement that the prior response did not comply. A significant share of properly escalated complaints at this stage produce a more substantive reply than the first response, simply because the complaint is now visible to a different internal team.

If internal escalation produces nothing useful, the P2B Regulation provides a right to access mediators from a list of bodies the European Commission has approved. This is not arbitration, and it is not litigation – it is a structured facilitated process that can produce a practical resolution faster than regulatory enforcement. The seller does not need the platform's agreement to trigger it; the right to access mediation is the seller's unilaterally.

For data-access failures that appear systemic – affecting multiple sellers, or involving clear non-compliance with DSA VLOP obligations – a complaint to the national Digital Services Coordinator (in France, the relevant designated authority) or, for DMA issues, to the European Commission's DG COMP directorate, may be appropriate. These routes do not produce individual remedies quickly, but they establish a regulatory record.

Checklist – Phase 5:

1. If the internal complaint has produced no compliant response, send a formal written escalation identifying the specific obligation not met and the specific data not provided. Preserve this communication.
2. Assess the mediation route: is the dispute about a specific platform decision (listing, suspension, termination) or about a category of data access? Mediation is better suited to specific decisions; regulatory complaints are better suited to systemic issues.
3. If a suspension or restriction is continuing to harm your business while the data-access process runs, consider whether the data obtained to date is sufficient to support a separate suspension challenge under the DSA's internal complaint system. These are parallel tracks; using one does not foreclose the other.
4. For DMA data-access claims, document the specific data category Amazon holds and the specific harm to your business from not having it. The DMA channel is different from the DSA/P2B channel, and the filing needs to reflect that.
5. If you are considering litigation in a French court or a formal regulatory filing, take legal advice before filing. The framing of earlier correspondence can affect what arguments remain open at that stage.

If your data-access issue overlaps with a product-safety listing removal, the checklist for EU listing takedowns on safety grounds covers the parallel steps for that specific category of restriction.

Phase 6: Decision points and trade-offs

A seller working through a data-access dispute faces several genuine decision points where the right choice is not obvious. This phase identifies them clearly.

Speed versus record: The fastest resolution is often an informal one – a responsive Amazon compliance team, a corrected disclosure, a cleared restriction. But an informal resolution that does not produce a written record of what was disclosed and on what basis leaves the seller with no protection against the same issue recurring. In matters we handle, we recommend that any resolution, even an informal one, be confirmed in writing before treating the matter as closed.

Individual remedy versus regulatory leverage: Using a regulatory channel (DSA complaint to the Digital Services Coordinator) does not guarantee an individual remedy for the seller. Regulatory enforcement runs on a different timeline and serves a broader public interest. A seller whose primary goal is to restore a suspended listing or obtain specific data to support an appeal should generally pursue the internal and mediation routes first, and hold the regulatory route for situations where those have genuinely failed.

Data request versus suspension appeal: These are related but distinct proceedings. A data request helps you understand the grounds for a restriction; it does not substitute for a properly framed suspension appeal. In some cases, the data obtained through a DSA statement of reasons is exactly what gives the suspension appeal its factual basis. Running them in parallel, with care for how each affects the other, is often the right approach.

Cost versus risk of inaction: For a mid-market seller on Amazon FR, a continued listing restriction or suspension is a direct revenue loss. A data-access dispute that runs for several months without resolution is not a neutral cost – it compounds. The earlier the formal request is filed, the earlier the response clock starts.

Checklist – Phase 6 decision points:

1. Do you need the data primarily to support a suspension appeal, or is the data-access failure itself the harm you are addressing? The strategy differs.
2. Have you exhausted the internal complaint channel with a properly framed request, or has only informal Seller Support contact been used? If the latter, the formal channel should be used before escalation.
3. Is the restriction affecting your business now? If yes, assess whether the data needed to challenge the restriction is available without a full formal process – sometimes the Phase 2 audit alone reveals what is needed.
4. Have you documented every step in writing? If a regulatory complaint or litigation becomes necessary, the trail of formal requests and responses is the foundation of the case.
5. If you are considering using a mediator, have you identified whether your dispute is about a specific decision (eligible for mediation under P2B) or about a systemic data-access refusal (more appropriate for regulatory channels)?

Where this goes wrong: the most common seller errors

In our practice, the failures we see in seller-driven data-access attempts follow a small number of patterns. Knowing them in advance is more useful than encountering them after the fact.

Filing through Seller Support instead of the internal complaint mechanism. These are structurally different channels. Seller Support responses are not DSA-compliant statements of reasons and do not reset any regulatory clock. A seller who has only used Seller Support has not yet triggered the platform's formal complaint obligations.

Requesting too broadly. A request for "all data Amazon holds about my account" is not a P2B or DSA request – it is an unframed inquiry. The regulation entitles you to specific categories of data in specific contexts. Broad requests are easier to refuse and harder to enforce.

Not preserving correspondence. It is common for sellers to conduct all communication with Amazon through Seller Central's messaging tools, which can be restricted or closed when an account is deactivated. Keep copies of every communication outside the platform.

Treating an inadequate response as a final answer. A platform's first response to a formal data request is rarely its fullest response. The internal escalation step exists precisely because the first-level response is often inadequate. Moving directly to external escalation without using internal escalation first may weaken the regulatory complaint.

Conflating GDPR data-subject access rights with P2B and DSA rights. A GDPR subject access request (SAR) is a different instrument for a different purpose. It covers personal data in the sense of the GDPR. The P2B and DSA rights cover business-operational data – ranking parameters, restriction grounds, performance data. Both may be relevant, but they run through different channels and different timelines. Using one does not substitute for the other.

The steps above describe the standard path. Your situation turns on the specific notices you have received, the data categories at issue, and the stage your account is currently at – which is what we review first.

To discuss your Amazon FR data-access dispute, email info@tutamenlaw.com. We review the account position and the correspondence before advising on the right route forward, with a fixed fee quoted up front.

Related areas

• EU Marketplace Regulation – full practice coverage for EU and UK marketplace sellers facing suspensions, DSA complaints, and P2B disputes
• EU marketplace regulation: the complete guide for sellers – how P2B, the DSA, and the DMA interact and what each means operationally

Frequently asked questions

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

The timeline depends on which route you are using. An internal complaint to Amazon FR's designated complaint mechanism should produce a response within the period the platform's own terms specify; a non-response or inadequate response within that window becomes the basis for escalation. P2B mediation is typically faster than litigation but still takes several weeks to several months depending on the complexity and the mediator's availability. Regulatory complaints to the Digital Services Coordinator or the European Commission run on longer timelines and should not be relied on if a fast individual remedy is the goal. Filing promptly and framing each request correctly is the most reliable way to compress the timeline.

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

The main practical risk is filing through the wrong channel and receiving a response that does not advance the matter, while the time cost of the restriction continues to accumulate. A Seller Support ticket does not satisfy the DSA internal complaint process. An overly broad request is easier for the platform to deflect. If correspondence is not preserved outside the platform, evidence of what was requested and what was refused may be lost if the account is deactivated. The procedural sequence matters: internal complaint before external escalation, mediation before litigation. A misstep at any of those junctions can limit what is available later.

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

Not for the initial audit and record-preservation steps. A seller can and should run Phase 2 – documenting what they already hold – without waiting for legal input. From Phase 3 onward, the framing of a formal data request under P2B or the DSA, and any subsequent escalation to mediation or a regulatory channel, benefits from legal input because the framing of those communications affects what options remain open. For sellers where a data-access dispute overlaps with a suspension or a listing restriction that is actively harming revenue, attorney involvement earlier in the process tends to produce a cleaner record and a faster path to resolution.

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 practice on EU marketplace regulation covers data-access rights, DSA and P2B complaints, mediation, and regulatory escalation – and we build the statement-of-reasons and internal-complaint case from the correspondence the seller already holds. To discuss your situation, email info@tutamenlaw.com.

By Priya Raman – IP & Brand Registry analyst, Tutamen. Published February 12, 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.