How to handle data access rights for EU sellers: a step-by-step guide

As enforcement automation has tightened across European marketplaces, sellers on Amazon FR are finding that the data flowing through their accounts – sales records, performance metrics, customer-return signals, and the inputs that feed algorithmic ranking – is both a commercial asset and a legal right. A suspension under EU rules can look final. The appeal path is rarely spelled out. And sellers who do not understand what they are entitled to ask for often miss the leverage that the law puts directly in their hands.

TL;DREU sellers on Amazon FR have legally enforceable data access rights under the Platform-to-Business (P2B) Regulation, the Digital Services Act (DSA), and – for data access between systems – relevant aspects of the Digital Markets Act (DMA). These instruments give sellers the right to request data held about their account, to receive a reasoned statement for any restriction, and to challenge restrictions through internal complaint and, where applicable, mediation or court proceedings. The path requires knowing which instrument applies, what to request, and in what order.

This guide walks through the precise sequence: from identifying what data you are entitled to, through drafting the right request, to escalating if Amazon FR declines or delays. Each step includes the common mistakes that derail the process and the decision points where professional input changes the outcome.

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

EU data access rights for marketplace sellers are not a single rule – they are a cluster of overlapping entitlements drawn from three instruments, each applying at a different layer of the relationship between a seller and the platform.

The Platform-to-Business (P2B) Regulation (EU) 2019/1150 is the most seller-specific. It requires Amazon, as an online intermediary with business users in the EU, to provide sellers with access to the data they have generated or which affects their performance ranking. This includes data that is not shared with consumers and data that the platform processes to generate ranking outputs. The P2B obligation covers transparency about how ranking is determined and, critically, what data inputs feed into it. If Amazon FR restricts a seller's access to this data without explanation, the restriction itself may be challengeable.

The Digital Services Act (DSA) operates at a different level. Amazon FR, as part of Amazon's European operations, falls under the DSA as a Very Large Online Platform (VLOP). The DSA's statement-of-reasons obligation means that every content moderation decision – including listing removals and account restrictions – must be accompanied by a document that tells the seller the factual basis, the legal basis, and any redress option. A statement of reasons is not optional; it is a procedural right that exists independently of whether Amazon's underlying decision was correct.

The Digital Markets Act (DMA) adds a third layer for sellers who depend on Amazon as a gatekeeper. Where Amazon acts as a gatekeeper under DMA designation, it carries obligations around data portability and non-discriminatory access to data that business users generate on the platform. In practice, the DMA layer is most relevant when a seller is being squeezed by asymmetric data access – for example, where Amazon's own retail arm can use data that the independent seller generated but cannot itself retrieve.

A seller on Amazon FR who receives a listing restriction, an account flag, or an unexplained ranking drop may have active rights under all three instruments simultaneously. The mistake we regularly see is treating this as a single appeal under one set of rules, when the procedural path is actually a sequence across three legal regimes.

Step 1 – Identify the specific restriction and which instrument governs it

Before sending any request, classify the restriction precisely, because the right instrument determines the deadline, the correct recipient, and the escalation route.

Start by pulling the notification from Seller Central or the email record and asking three questions. First: is this a restriction on what data you can see about your own account, or a restriction on your ability to operate – a listing removal, a selling privilege suspension, or a hold on disbursements? Data-visibility restrictions and operational restrictions often travel together, but they require separate responses. Second: does the notification include a statement of reasons under the DSA, or does it lack one? If it lacks one, the absence itself is a procedural deficiency. Third: does the restriction affect ranking-related data in a way that could trigger P2B obligations?

Write down the exact date and time of the restriction, the ASIN or account feature affected, and the text of any reason given. This record becomes the foundation of every step that follows. If Amazon FR has not provided a statement of reasons, note that gap explicitly – you will be asking for it formally in Step 2.

One common mistake at this stage is to start engaging with Seller Central's generic appeal interface before classifying the restriction. The standard appeal flow does not distinguish between a P2B data request, a DSA statement-of-reasons request, and an ordinary performance appeal. Sending through the wrong channel often results in a generic response that neither addresses the data entitlement nor creates a formal record of the refusal.

Step 2 – Send a formal data access or statement-of-reasons request

A formal written request, sent through a traceable channel, starts the clock on Amazon's obligation to respond and creates the evidentiary record you need for any escalation.

For a DSA statement-of-reasons request, address the request to Amazon FR's designated point of contact for DSA compliance. The DSA requires platforms to publish this contact information. Your request should identify the specific decision (date, ASIN, account feature), state that you are exercising your right to a statement of reasons under the DSA, and ask for: the factual basis of the decision, the legal or policy basis, and the available redress options. Keep the request factual and short. A long complaint at this stage often gets routed to a general customer support queue rather than the compliance function.

For a P2B data access request, the request should identify the specific data category (ranking inputs, performance metrics, return-signal data) and cite the P2B Regulation by name. Ask for confirmation of the data Amazon holds about your account that influences your ranking, and ask for any restriction on your access to that data to be explained. The P2B Regulation obliges Amazon to provide this explanation in its general terms – if the terms do not address the specific data category, that itself is a P2B compliance gap.

Send both requests in writing, keep copies with timestamps, and note the date sent. If you use the Seller Central messaging interface, screenshot the sent confirmation. If you use email through Amazon's designated compliance address, retain the sent-mail record. The formal request date is the anchor for any later mediation or court filing.

Step 3 – Evaluate Amazon FR's response (or non-response)

What Amazon FR says – or fails to say – in response determines which escalation route is open.

A substantive response that provides a genuine statement of reasons and identifies a redress path allows you to move to Step 4 on the merits: assess whether the stated reason is factually accurate, whether the legal basis cited actually applies, and whether the redress offered is the correct one. In matters we handle at this stage, the most common problem is a statement of reasons that names a policy category without explaining what conduct triggered it – which satisfies Amazon's form but not its substance.

A non-response or a generic acknowledgment that does not engage with the DSA or P2B request is itself actionable. The DSA requires platforms to act with due diligence; an unexplained delay creates a basis for escalation to Amazon's internal complaint-handling system and, if that fails, to an out-of-court dispute settlement body or the competent Digital Services Coordinator in France (the ARCOM, as the relevant national authority).

A refusal – an explicit statement that Amazon will not provide the requested data or statement of reasons – is the clearest escalation trigger. Document the refusal precisely: quote it, date it, and record which channel it came through.

What should not happen at this stage is a second informal appeal through the standard Seller Central interface. We regularly see sellers, frustrated by a non-response, send a follow-up complaint through Seller Central that effectively restarts the informal queue and obscures the formal request record. Keep the formal and informal tracks separate.

Step 4 – Use Amazon FR's internal complaint-handling system

Both the P2B Regulation and the DSA require Amazon to provide sellers with access to an internal complaint-handling system. Using this system formally is not optional for sellers who want to preserve their escalation rights – skipping it may limit later options.

The internal complaint should be structured differently from the initial request. Where the initial request asked for information, the complaint asks for a decision. State what you requested, state what Amazon provided (or failed to provide), and state what you are asking the complaint system to do: reverse the restriction, provide the missing data, or issue a compliant statement of reasons. Attach copies of the original request and any response received.

A well-constructed internal complaint also sets up the mediation record. Out-of-court dispute settlement bodies operating under the P2B Regulation are required to consider whether the platform's internal process was followed before accepting a referral. A seller who can show a documented, unanswered complaint is in a stronger position than one who moved directly to external escalation.

Timing matters here. The P2B Regulation does not set a specific number of days for the internal complaint to be resolved, but it requires the process to be conducted in good faith and within a reasonable period. If Amazon's internal system produces no substantive response within what a reasonable observer would regard as an adequate window, you have the material for a P2B mediation referral.

For more detail on how the P2B and DSA systems interact in practice, the EU marketplace regulation complete guide for sellers covers the full procedural architecture across both instruments.

Step 5 – Consider mediation and external escalation

Mediation under the P2B Regulation is an underused tool. Amazon is obliged to engage with certified mediators in good faith, and a seller who has an auditable complaint trail has real leverage at this stage.

P2B-compliant mediators are certified bodies that meet the independence and transparency criteria set out in the regulation. A referral to a mediator does not require court proceedings and is typically faster. In matters we handle, we prepare the mediation brief by assembling the request, the response or non-response, the internal complaint record, and a clear account of the commercial harm – the listing downtime, the lost ranking position, the data gap that prevented the seller from responding to a performance alert. That factual and commercial picture is what moves a mediator to recommend a remedy.

External escalation to the Digital Services Coordinator (ARCOM in France for Amazon FR) is the regulatory route. A formal complaint to ARCOM about Amazon's failure to comply with DSA statement-of-reasons obligations creates a regulatory record. ARCOM has investigative powers and can compel Amazon to produce information. The regulatory route tends to be slower than mediation, but it is the appropriate escalation for systemic failures – for example, where a category of sellers is being denied data access as a pattern, rather than an isolated incident.

The case of how one seller resolved mediation under EU marketplace rules illustrates what the evidentiary preparation looks like in practice and where the key decision points fall.

If Amazon FR's restriction extends to a listing takedown on safety grounds, the regulatory path diverges further. The guidance on EU listing takedowns on safety grounds covers that specific route and the interaction with the General Product Safety Regulation (GPSR).

Where this goes wrong: the four most common mistakes

Sellers who handle EU data access rights disputes alone consistently make the same four errors. Knowing them in advance is itself a form of protection.

The first mistake is conflating a data access request with a standard performance appeal. Performance appeals in Seller Central follow a different track – they ask Amazon to reverse a finding about seller conduct. A data access request asks Amazon to fulfill a legal obligation about what information it holds and shares. Sending a data access request through the performance appeal queue almost guarantees it will be handled as an operational complaint, not a compliance matter.

The second mistake is failing to document each step in a format that can be used in mediation or before a regulator. A summary of what happened is not a record. A record is: screenshots with timestamps, copies of formal requests with sent confirmations, and Amazon's responses quoted verbatim. The documentation discipline that feels unnecessary on day one becomes the entire basis for escalation on day thirty.

The third mistake is engaging informally with Amazon's account health team while a formal complaint is pending. These two tracks can undermine each other. Amazon's account health representatives operate within a customer-service mandate, not a compliance mandate. Information shared in those conversations can be used to close the formal complaint without addressing the legal substance – and sellers sometimes accept a partial informal resolution that waives the rights they were asserting formally.

The fourth mistake, and the one we see most often in the mofu stage of a dispute, is abandoning the process after a non-response. A non-response from Amazon is not a final answer. It is the trigger for the next step. The belief that EU sellers have no leverage once a platform fails to respond is the myth that most often leads sellers to walk away from rights that the law has already given them.

The seller's decision points and trade-offs

At three moments in the sequence above, a seller must make a judgment call that affects the cost, the timeline, and the likely outcome.

The first decision point is at Step 2: whether to send formal requests under both the DSA and P2B simultaneously, or to sequence them. Simultaneous requests are appropriate when the restriction affects both data visibility and operational access, which is the common pattern in an account-level suspension. Sequential requests – DSA first, P2B second – may be appropriate when the core problem is a specific statement-of-reasons gap and the data access issue is secondary. If the sequencing is wrong, the response Amazon gives to the first request may not address the rights asserted in the second, creating confusion in the record.

The second decision point is at Step 4: whether to use the internal complaint system before attempting informal resolution, or alongside it. Our practice is to keep the formal complaint track open and not to close it in exchange for informal commitments unless those commitments are documented and legally binding. An informal assurance from an account manager that the issue is "being reviewed" does not suspend the clock on a P2B complaint.

The third decision point is at Step 5: mediation or regulatory escalation, or both. The two routes are not mutually exclusive. A mediation referral can proceed while a regulatory complaint is pending. The strategic choice depends on the seller's commercial priority: if the listing needs to come back quickly, mediation is the faster route; if the issue is a pattern that will recur, regulatory escalation creates the deterrent. A combined approach requires careful coordination to ensure the records in each track are consistent.

If a suspension under EU rules has already occurred and the path forward is unclear, a short structured review of the notification, the account history, and the instruments in play is the right starting point. The steps above describe the standard path. Your situation turns on the exact wording of the notice, the account history, and timing – which is what we review first.

To request a review of your Amazon FR data access situation, email info@tutamenlaw.com.

A home-goods seller on Amazon FR (fall 2025) came to us after a ranking collapse that coincided with a change in return-processing data they could no longer access. We mapped the restriction to a P2B data-transparency obligation, sent a formal request to Amazon FR's compliance contact, and followed it with an internal complaint when the initial response failed to address the specific data category. Amazon FR produced the missing data and a revised statement of reasons within a few weeks of the formal complaint, and the seller was able to identify and address the underlying performance signal that had triggered the ranking suppression.

What to do if your first request was already rejected

A rejected first request is not the end of the process – it is the point at which the process becomes adversarial, and where the evidentiary record you built in earlier steps starts doing real work.

Review the rejection notice for three things: whether Amazon cited a specific factual basis, whether it cited a legal or policy basis, and whether it identified any redress option. A rejection that does none of these things is itself a DSA non-compliance. A rejection that identifies a factual basis you can challenge takes you to a different sub-track: you are now disputing Amazon's factual account, which requires evidence rather than procedure.

If the rejection is substantive but incorrect – Amazon says the data does not exist, or that you are not entitled to it – the appropriate response is to prepare a short factual brief for the internal complaint system and, if that fails, for the mediator. The brief should show: the data category you requested, the basis in P2B or DSA for the entitlement, the factual error in Amazon's characterization, and the commercial consequence of the denial.

If the rejection is procedural – Amazon says the request was sent to the wrong channel or was insufficiently specific – resend to the correct channel with greater precision. This is frustrating, but a corrected submission is better than an escalation that Amazon can deflect by pointing to the procedural deficiency.

If a first appeal or filing already came back rejected, a second read can find the specific reason it failed and what, if anything, is still open. For a review of a rejected data access request on Amazon FR, contact Tutamen at info@tutamenlaw.com.

Related areas

• EU Marketplace Regulation – full coverage of DSA, DMA, P2B, and GPSR obligations for marketplace sellers
• Amazon Account Reinstatement – step-by-step representation for deactivated Amazon accounts across EU and US surfaces

Frequently asked questions

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

The timeline depends on which escalation route is used and how quickly Amazon FR responds at each step. An internal complaint that produces a substantive response often resolves the immediate data access gap within several weeks. P2B mediation adds time for the mediator to engage and Amazon to respond in that forum, typically extending the timeline by a further several weeks to a few months. Regulatory escalation to ARCOM is slower and is better suited to systemic issues than to urgent operational problems. In matters we handle, the fastest resolutions come when the formal request and internal complaint are drafted precisely and sent through the correct compliance channels from the outset – poor initial drafting is the single biggest cause of delay.

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

The primary risk is procedural: sending requests through the wrong channel, failing to document each step in a usable format, or accepting an informal resolution that closes the formal complaint track without addressing the underlying legal obligation. A second risk is substantive: misidentifying which instrument applies to the restriction means asserting the wrong entitlement, which Amazon FR can decline on correct grounds. A third risk is strategic: engaging informally with account health teams while a formal complaint is pending can produce statements or concessions that weaken the mediation or regulatory record. None of these errors are irreversible at the early stages, but they become progressively harder to correct as the dispute moves toward external escalation.

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

Legal representation is not formally required at any stage of the P2B or DSA process before court proceedings. In practice, the decision turns on the commercial stakes and the complexity of the restriction. A seller who can clearly identify the data category, the instrument that applies, and the correct Amazon FR compliance contact can draft an effective formal request without counsel. Where legal support adds the most value is in the internal complaint and mediation stages, where the framing of the commercial harm and the legal entitlement together – rather than either alone – is what shifts the outcome. Attorney-led representation at the escalation stage also ensures that the record created is usable in court or before a regulator if needed.

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 representation under the DSA, P2B Regulation, and DMA is a core part of our EU practice, and we work with appropriate local counsel for matters requiring in-jurisdiction filings outside our primary surfaces. To discuss your situation, email info@tutamenlaw.com.

Page authored 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.

Written by Priya Raman, IP & Brand Registry analyst at Tutamen. Published September 21, 2026.