Responding to data access rights for EU sellers the right way on Amazon FR

A suspension under EU marketplace rules can feel like a door slamming shut. The notice arrives in Seller Central, the listing or account goes dark, and the next step – the one that actually matters – is not obvious. EU sellers on Amazon FR sit inside a layered regulatory regime that most platform dispute guides never properly address.

TL;DRData access rights for EU sellers on Amazon FR are legal entitlements, grounded primarily in the Platform-to-Business (P2B) Regulation and reinforced by the Digital Services Act (DSA), that require Amazon to disclose what data it holds about a seller's performance and account, and to explain how that data drives ranking, restriction, or suspension decisions. Asserting those rights correctly – in the right sequence, through the right channel – is the difference between a reinstatement path and a stalled complaint that goes nowhere. This guide sets out the step-by-step process and identifies where sellers most commonly lose ground.

We cover: what data access rights actually mean on Amazon FR, the procedural path from first notice to formal complaint, the decision points where strategy diverges, where the process typically breaks down, and when outside legal support changes the outcome.

What do data access rights actually mean for EU sellers on Amazon FR?

Data access rights, in the context of EU marketplace regulation, are the enforceable legal rights that allow a business seller to see, understand, and challenge the data that a platform uses to affect that seller's commercial position. On Amazon FR, those rights are not hypothetical – they are grounded in binding EU law that Amazon, as a platform operating in the EU and classified as a Very Large Online Platform (VLOP) under the DSA, must respect.

The P2B Regulation requires that Amazon provide business sellers with access to the personal and other data generated through their use of the platform. This includes transaction data, performance data, and the data Amazon collects from consumer interactions on a seller's listings. The Regulation further requires that any restriction on data access be explained in the platform's terms, and that differentiated treatment – where Amazon uses that data for its own commercial purposes while restricting the seller's access – be disclosed transparently.

The DSA adds a separate layer. As a VLOP, Amazon must maintain and apply consistent, accessible procedures for handling seller complaints about platform decisions that affect them. A failure to provide data that a seller is entitled to, or a refusal to explain a data-driven ranking or suspension decision, can constitute a platform failure under the DSA's internal complaint-handling obligations.

In practice, we regularly see sellers on Amazon FR receive a suspension or ranking restriction with no explanation beyond a generic policy notice. The notice may reference a performance threshold, an algorithm-driven signal, or a vague community safety concern – but it does not show the underlying data. That is the gap that EU data access rights are designed to close. Knowing what data Amazon holds and how it was applied is not just a transparency measure. It is the foundation of any effective appeal or complaint.

A statement of reasons is the formal document Amazon must provide under the DSA when it restricts, suspends, or terminates a seller's account or removes a listing. It must explain the facts and circumstances relied on, the grounds under the platform's terms, and the means of redress available. If the statement of reasons you received is incomplete or generic, that is itself a basis for complaint – and a starting point for asserting your data access rights formally.

For a broader map of the EU rules that apply to Amazon sellers across marketplaces, our EU marketplace regulation complete guide for sellers sets out the full regulatory picture.

Step 1: Read the notice carefully and identify what data it references – and what it omits

The first and most consequential step is a disciplined reading of the deactivation or restriction notice, not to find a quick fix, but to map exactly what Amazon has and has not disclosed. Every word in the notice is deliberate; every omission is legally significant.

Start by identifying the stated basis. Is the restriction framed as a policy violation, a performance failure, a safety concern, or an unexplained algorithmic decision? Each basis carries different implications for what data you are entitled to request and how to frame the request.

Next, identify what data the notice relies on. If Amazon says a product was flagged as non-compliant, you are entitled to know which data point triggered that flag. If a ranking suppression is described as the result of "customer signals," you are entitled to know what those signals are and how they were weighted. A notice that cites data without showing it is, on its face, incomplete under both the P2B Regulation and the DSA's statement-of-reasons requirement.

Document the gaps. Before you file anything, create a written record of what the notice says and what it does not say. This record becomes the backbone of your data access request and, if the platform fails to respond adequately, your formal complaint. Sellers who skip this step often find themselves responding to a general problem rather than the specific data Amazon actually used.

As enforcement automation has tightened across EU marketplaces, the proportion of notices that are algorithmically generated – and therefore thinner on factual specifics – has increased. That is not a reason to panic. It is a reason to be precise about what you are asking for.

Step 2: Submit a formal data access request through the correct channel

Submitting a data access request correctly is a distinct procedural act from appealing a suspension. Many sellers conflate the two and lose the legal protection that a properly framed data request provides. The request should be clear, specific, and grounded in the applicable regulatory instrument.

Address the request to Amazon's business seller support channel and, separately, to the data protection contact where GDPR personal data is also in scope. State the legal basis: the P2B Regulation, the DSA, and, where personal data is involved, the General Data Protection Regulation (GDPR). Specificity matters. A request for "all my data" is easily deflected. A request for "the performance data, including all underlying metrics, used to assess compliance with [the specific policy cited] between [date range] and [date of notice]" is much harder to dismiss without explanation.

Specify the format you need. The P2B Regulation requires that data be provided in a commonly used, machine-readable format where technically possible. If you need the data to run an independent analysis – for example, to check whether a performance threshold was actually breached – say so in the request.

Set a response deadline that reflects the regulatory obligation. The DSA's internal complaint-handling provisions require timely processing. Reasonable and durable framing is to expect a substantive response within a few weeks, though the exact period depends on the channel and the specificity of the request. Keep a timestamped record of the request and every response.

In matters we handle, a well-framed data access request often surfaces information the original notice omitted – and that information then anchors a much stronger appeal or statement-of-reasons challenge.

Step 3: Evaluate the response and decide whether to escalate

Amazon's response to a data access request determines the next fork in the road. There are three realistic outcomes: full disclosure, partial disclosure with explanation, or a refusal. Each leads to a different procedural path, and the decision at this point is one of the most consequential trade-offs a seller faces.

Full disclosure is the best outcome. If Amazon provides the underlying data, you can assess whether the platform's decision was consistent with its own stated methodology, whether the data supports the action taken, and whether there is a factual basis to challenge the restriction. In many matters, the data reveals an error – a mis-attributed performance metric, a signal generated by an isolated event rather than a pattern, or a threshold calculation that does not withstand scrutiny.

Partial disclosure is more common and more ambiguous. Amazon may provide some data while declining to produce proprietary ranking methodology details, on the basis that those constitute confidential commercial information. The P2B Regulation permits this limitation, but it requires that the limitation itself be justified and proportionate. If the partial disclosure is inadequate to understand the basis for the platform's decision, that is a documented failure of the statement-of-reasons obligation – and a ground for escalation to the DSA's internal complaint system.

Refusal or silence is the clearest ground for formal escalation. A platform that does not respond substantively to a properly framed data access request from a business seller, within a reasonable period, has a compliance exposure under both the P2B Regulation and the DSA. Document the refusal – including any automated acknowledgment that does not address the substance – and proceed to the complaint path.

This is also the point where the question of mediation under EU rules becomes relevant. Our analysis of mediation under EU marketplace rules and your account explains when that route is useful and when it is not.

Step 4: File through the DSA internal complaint-handling system

The DSA requires that VLOPs, including Amazon, maintain an effective internal complaint-handling system for business users. Filing through that system is not just a procedural formality. It creates a compliance record that Amazon must address within its own obligations, and it gives you a documented escalation path to national Digital Services Coordinators if the internal process fails.

A complaint through the DSA internal system should state the specific decision being challenged, the data access request that was made and the response received, the regulatory obligation that the platform has not met, and the remedy sought. Generic complaints about being suspended are treated as policy appeals and routed to standard seller support. A complaint that names the DSA, references the statement-of-reasons obligation, and identifies a specific compliance gap is treated differently.

One seller we worked with – a cosmetics brand on Amazon FR (summer 2026) – received a listing restriction citing safety concerns but no data supporting the classification. We drafted a formal DSA internal complaint, citing the inadequacy of the statement of reasons and the unanswered data access request. Amazon's compliance team, rather than standard support, addressed the complaint and provided the underlying safety assessment data. The listing restriction was then challenged on the merits using that data, and the restriction was lifted.

Keep every communication, timestamped and in written form. If the internal complaint system fails to produce a substantive outcome, the Digital Services Coordinator for the EU member state where the seller is established is the next escalation tier. In France, the competent authority is the Autorité de régulation de la communication audiovisuelle et numérique (ARCOM). Filing a complaint with a national Digital Services Coordinator is not a common step for most matters, but the fact that it exists changes the dynamics of the internal complaint.

Where a listing has been taken down on product safety grounds, there is an additional overlay to consider. Our guide on EU listing takedown on safety grounds sets out how safety-based removals interact with the data access and statement-of-reasons framework.

Step 5: Build the appeal or challenge on the data you have obtained

With the underlying data in hand – or with a documented record of the platform's failure to produce it – the appeal or challenge has a factual foundation that a standard Plan of Action does not. This is where the work done in the earlier steps pays off commercially.

If the data supports the platform's decision, the appeal needs to address the root cause directly and specifically, with evidence of correction and prevention. Vague commitments to "improve processes" fail at this stage. The appeal should map the specific data point to the specific corrective action, and the preventive measure should be demonstrably tied to the mechanism that generated the data signal.

If the data does not support the platform's decision – or if the platform refused to produce it – the challenge is different in character. It is not an admission of fault and a remediation plan. It is a factual and legal challenge to the basis of the decision, supported by the regulatory obligations Amazon failed to meet. In matters we handle, this distinction between a remediation appeal and a rights-based challenge is often the difference between a quick auto-rejection and a substantive review.

A second micro-case illustrates the other end of the spectrum. An apparel marketplace seller on Amazon DE (spring 2025) – whose account was under review for related-account linkage, with a data access request that had been partially answered – came to us after two standard appeals had been rejected. We reframed the submission as a DSA statement-of-reasons challenge, citing the incomplete data disclosure, and requested a formal internal review under the DSA complaint mechanism. The account was restored after the internal review team identified that the related-account flag had been generated by a shared IP address with no transactional link. Without the data access request, that fact would not have been available.

The DMA gatekeeper obligations add a further layer for sellers whose products compete with Amazon's own-brand lines. Where access to data is being differentially restricted in a way that advantages Amazon's competing product, the DMA's self-preferencing provisions may be relevant. This is a specialist area and the analysis depends on the specific facts, but it is a tool that should be in scope when the data access denial is commercially asymmetric.

Where this process goes wrong

Every step described above has a common failure mode. Understanding them is as important as understanding the correct path, because the EU regulatory framework only protects sellers who use it properly.

The most frequent failure is treating a DSA or P2B data access right as an optional preliminary to a standard appeal. Sellers often go straight to the Plan of Action, without the underlying data, and produce a response that addresses the wrong root cause. When that appeal is rejected, the rejection itself is then taken as confirmation that the suspension was valid – when in fact the appeal was simply incomplete.

The second most common failure is sending an informal message through Seller Central case logs that asks for information, and treating that as a data access request. It is not. A data access request must be formally framed under the applicable regulation to trigger the compliance obligations that Amazon must meet. Informal messages are routed to standard seller support and resolved under standard policies, not under the P2B or DSA obligations.

Third: failing to document. The entire EU regulatory escalation path depends on a documented record. If you cannot show that you made a properly framed request, received an inadequate response, and filed through the DSA internal complaint system, you do not have an escalation case. Documentation is not administrative overhead – it is the evidentiary foundation of every step that follows.

Fourth: waiting too long. The DSA does not specify a hard appeal limitation period for all decision types, but the practical window for an effective challenge narrows over time. Account health history accumulates, inventory decisions compound, and the commercial cost of delay is real. Acting promptly after the notice, not after several failed standard appeals, preserves the widest set of options.

The myth that EU sellers have no leverage once a platform suspends them is exactly that – a myth. The DSA, the P2B Regulation, and the DMA gatekeeper rules create enforceable obligations that Amazon, as a VLOP and gatekeeper, cannot simply override with a policy notice. But that leverage only materializes if the rights are asserted correctly, in sequence, with documentation.

To review whether your notice and the platform's response meet the EU standard, contact Tutamen at info@tutamenlaw.com for an initial read of your situation.

Related areas

• EU Marketplace Regulation – the full regulatory map for Amazon, Walmart, Etsy and eBay sellers operating in the EU
• EU Marketplace Mediation – when mediation under P2B rules is a useful tool and when it is not
• EU Safety-Grounds Listing Takedown – how product safety removals interact with data access and appeal rights

If a first filing through Amazon's internal system came back without a substantive answer, or was routed to standard seller support and closed without addressing the data access issue, that rejection does not end the process. A second read of the complaint record can identify whether the correct regulatory channel was used and what remains open. To discuss a stalled complaint, email info@tutamenlaw.com.

Frequently asked questions about data access rights for EU sellers on Amazon FR

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

The timeline depends on three variables: how quickly Amazon responds to the data access request, whether the internal DSA complaint system resolves the matter or escalates to a Digital Services Coordinator, and whether the underlying suspension or restriction is contested on the merits once the data is obtained. A properly framed data access request, followed by a DSA internal complaint where needed, typically runs across several weeks to a few months. Matters that require escalation to a national Digital Services Coordinator, or that involve a parallel reinstatement appeal, take longer. Acting early and with precise documentation shortens the realistic range considerably.

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

The principal risk is misdirection: asserting a data access right through the wrong channel, in the wrong form, triggers a standard policy response rather than a compliance obligation. That mis-filed request may then be used by Amazon as evidence that the issue was "addressed." A second risk is scope error – asking for general data rather than the specific dataset that underpins the platform's decision, which makes the response easier to deflect. Third, sellers handling the process alone often lack familiarity with the DSA's internal complaint requirements, which means escalation to a Digital Services Coordinator – the strongest external lever – is never properly set up. These are not hypothetical risks; in matters we handle, they are the most common reasons a seller arrives at our desk having already spent time on an ineffective process.

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

Not every data access request requires legal representation, but the cases where legal support changes the outcome are the majority, not the exception. The P2B Regulation, the DSA, and the DMA gatekeeper provisions each have distinct application thresholds and procedural requirements. A lawyer familiar with EU marketplace regulation can identify which instruments apply, frame the request and complaint in terms Amazon's compliance function must address, and recognize when a partial response is legally adequate versus when it is a deflection. The cost of getting the sequence wrong – a rejected appeal that narrows the window for a rights-based challenge – is typically far higher than the cost of an attorney-led filing from the outset. Tutamen's work in this area is attorney-led, confidential, and offered at a fixed fee quoted up front after a short review of the matter.

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. All matters are handled under strict professional confidentiality; consultations are available in English and Russian on request. To discuss your situation, email info@tutamenlaw.com.

Byline: 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.