Before you act on unfair ranking complaint under EU rules: a checklist

TL;DRAn unfair ranking complaint under EU rules is a formal challenge by a seller – or a regulatory body acting on a seller's behalf – asserting that a marketplace such as Amazon Italy has altered the seller's search or recommendation position without a lawful, transparent basis. The Platform-to-Business (P2B) Regulation and the Digital Services Act (DSA) together give sellers concrete procedural rights: the right to a statement of reasons, the right to use the platform's internal complaint-handling system, and – in some circumstances – access to out-of-court dispute resolution. Acting on those rights in the right sequence is what determines whether the complaint gains traction.

This checklist works through the process phase by phase. If you are an Amazon IT seller whose ranking has dropped sharply and you suspect a platform-side cause rather than organic performance, the steps below will help you build a factual record, identify which legal instruments apply, and make the key decision about whether to escalate – and how far.

Phase 1: What is an unfair ranking complaint under EU rules, and does your situation qualify?

Not every ranking drop is a regulatory event – and confusing ordinary algorithm changes with a P2B or DSA breach wastes time and undermines the credibility of a genuine complaint.

Under the P2B Regulation, Amazon is required to set out in its terms the main parameters that determine ranking and to explain, in plain language, the relative importance of those parameters. That obligation covers both the general ranking algorithm and the way paid placement interacts with organic search. A seller's complaint has regulatory weight when the platform has failed to explain why a change occurred, has applied conditions not disclosed in its terms, or has treated the seller inconsistently compared with Amazon's own retail offers – which overlaps with the Digital Markets Act (DMA) gatekeeper self-preferencing prohibition. The DSA adds the right to receive a statement of reasons whenever Amazon takes a restrictive measure affecting a business user, including a significant downranking that the platform decides to make.

Before you file anything, work through this qualification check:

• Has your visibility on Amazon IT dropped in a way that is not explained by changes to your own listings, prices, reviews, or inventory?
• Have you received any written notice – a statement of reasons, a policy update notification, or a Seller Central message – that attempts to explain the change?
• Is the change affecting your ASIN specifically, or an entire category, or all sellers on the platform equally? (A platform-wide algorithm update is rarely a viable individual complaint.)
• Is there evidence – even circumstantial – that Amazon's own retail division or a preferred seller is ranking above you for the same search terms on the same or comparable products?
• Did the drop follow a complaint filed against you by a competitor, or coincide with a policy-enforcement action on your account?

In matters we handle, the strongest EU ranking complaints combine at least three of the above factors: an unexplained change, a missing or inadequate statement of reasons, and a traceable self-preferencing or differential-treatment pattern. If only one factor is present, the realistic options are narrower, and we say so at the outset.

Phase 2: Gather your evidence before you contact Amazon

Every document and data point you capture now will either support your complaint or expose gaps in it – and gaps found by Amazon's team are harder to recover from than gaps you find yourself.

What ranking evidence actually means something? Keyword position screenshots alone are rarely enough. The record you need is layered: historical ranking data against specific search terms (exported or screenshotted at regular intervals), the corresponding sales velocity and conversion rate data from Seller Central, the business reports showing traffic source and buy-box win rate, and any Seller Central communications – whether routine or enforcement-related – received in the period surrounding the drop.

Work through this documentation phase:

• Export your business reports for the 90-day period before and after the ranking change. Capture session data, page views, and ordered units by ASIN.
• Take dated screenshots of your Amazon IT search-results position for the five to ten keyword combinations most relevant to your product.
• Screenshot the same keyword results showing the positions of Amazon's own retail listings and of any clearly preferred third-party sellers.
• Download your complete Seller Central message history for the relevant period. Search for any automated notices, policy warnings, or account health alerts.
• Retrieve the current version of Amazon's terms of service and ranking-parameter disclosure as they appear on Amazon IT. Save a dated PDF – this is your baseline for the P2B transparency obligation.
• Note whether Amazon has published any general ranking-algorithm update announcement during the period. If it has, your complaint will need to show why your drop goes beyond that general change.
• If you run sponsored placements, download your advertising performance data for the same window. A paid-placement freeze or quality-score change can masquerade as an organic ranking issue.

Do not contact Amazon's Seller Support or Account Health team yet. A premature, informal complaint can be met with a boilerplate response that then becomes the first document in any subsequent formal process – and a weak opening statement is difficult to walk back. The evidence phase should be complete before any formal contact.

Phase 3: Identify which EU instrument applies and what it requires

The P2B Regulation, the DSA, and the DMA are distinct instruments with different triggers, different addressees, and different procedural consequences – and the right tool depends on the facts you have assembled in Phase 2.

A brief orientation:

• P2B Regulation (Platform-to-Business Regulation, EU 2019/1150): applies to business users of online intermediation services. It requires Amazon to provide transparency on ranking parameters, to include terms for any differential treatment of Amazon's own goods, and to maintain an internal complaint-handling system that business users can access. It does not give individual sellers a direct enforcement route against Amazon – enforcement sits with EU member-state authorities – but a formal complaint through the internal system creates a documented record that regulators and out-of-court mediators can use.
• DSA (Digital Services Act): Amazon is designated as a Very Large Online Platform (VLOP) under the DSA. The DSA's statement-of-reasons obligation is directly actionable by sellers: if Amazon restricts, downgrades, or removes a listing or reduces a seller's visibility and does not provide an adequate statement of reasons, that is a compliance failure the seller can invoke formally.
• DMA (Digital Markets Act): Amazon is designated as a gatekeeper. The DMA prohibits self-preferencing – Amazon ranking its own products more favorably than third-party equivalents using data or position advantages unavailable to those sellers. DMA enforcement is a matter for the European Commission, but evidence of a self-preferencing pattern in your ranking data supports both a P2B internal complaint and any regulatory referral.

For a concrete guide to how these instruments interact in practice, see our complete guide to EU marketplace regulation for sellers.

Your instrument-selection checklist:

• Has Amazon provided a statement of reasons for the ranking change? If not, your first formal step is a DSA-based request for that statement.
• Are Amazon's published ranking-parameter disclosures on Amazon IT adequate under P2B? If the disclosure is vague, generic, or absent, that is the P2B angle.
• Is there evidence that Amazon's own retail offers rank above comparable third-party products in a way that cannot be explained by relevance or performance? That is the DMA self-preferencing angle – document it carefully before citing it.
• What jurisdiction are you primarily operating in? An Italian-registered seller on Amazon IT has specific rights under Italian law implementing P2B and the DSA, and Italian courts have been active on platform-regulation matters. If your business is German-registered and also selling on Amazon DE, the Bundeskartellamt's §19a proceedings against Amazon are relevant context – though enforcement there is separate from an individual seller complaint.

For the self-preferencing angle specifically, our analysis of responding to a self-preferencing complaint under the DMA sets out the practical approach in detail.

Phase 4: Use Amazon's internal complaint-handling system correctly

Amazon's internal complaint-handling obligation under P2B is not optional – the platform is required by law to maintain it and to process complaints within a reasonable time. Using it correctly is both a legal step and a strategic one: a well-constructed internal complaint creates a record, tests Amazon's stated position, and is a prerequisite for most out-of-court escalation paths.

A complaint that simply says "my ranking dropped and I want it restored" will not work. What is actually required is a structured submission that ties the factual record you assembled in Phase 2 to the specific obligation Amazon has failed to meet.

Internal complaint checklist:

• Open the submission through the formal channel designated in Amazon IT's terms – not a Seller Support ticket. If the designated channel is unclear, request clarification in writing and document Amazon's response.
• State at the outset which specific P2B or DSA obligation you are invoking. This signals that you are aware of your rights and are not making an informal commercial request.
• Attach or summarize the evidence from Phase 2: the business report data, the keyword-position screenshots, and any communications you received (or conspicuously did not receive) from Amazon.
• If you are invoking the DSA statement-of-reasons right, state the specific change you believe took place, the approximate date, and the absence or inadequacy of any explanation provided.
• If you are invoking P2B transparency, quote the relevant section of Amazon's ranking-parameter disclosure and identify specifically what it fails to explain about the change you experienced.
• Set a reasonable response deadline in your submission – in matters we handle, a 14-day window is standard – and state that you will treat non-response or an inadequate response as grounds for escalation.
• Retain a complete copy of everything you submit, including any reference numbers Amazon assigns to the complaint.

What happens next depends on Amazon's response. In our experience, the first response is often procedural – an acknowledgment, a redirect to Seller Support, or a generic statement that your account is being reviewed. Do not treat that as a substantive answer, and do not accept it as closing the complaint.

Phase 5: Evaluate Amazon's response and decide whether to escalate

Amazon's response to a formal internal complaint is itself a document you will use if you escalate. This phase is about reading that response with discipline and making a clear decision about next steps.

In matters we handle on behalf of Amazon IT sellers, responses to P2B and DSA-based internal complaints tend to fall into one of three patterns. First, a substantive response that explains the ranking change in terms that, on examination, fail to satisfy the transparency standard – this is the strongest basis for escalation. Second, a generic or irrelevant response that does not address the specific obligation invoked – also escalatable, because it evidences the inadequacy of the internal process. Third, a response that restores ranking or provides a satisfactory explanation – in which case escalation may not be necessary, though the underlying cause remains worth monitoring.

Your escalation-decision checklist:

• Does Amazon's response identify the specific ranking parameter or system change that caused your drop, in terms consistent with the P2B disclosure in its terms? If not, the transparency obligation has not been met.
• Does the response constitute an adequate statement of reasons under the DSA – identifying the facts relied upon, the grounds invoked, and the scope of the restriction? If not, the DSA obligation has not been met.
• Has Amazon's response addressed your self-preferencing concern, if you raised one? A non-response on that point is relevant to any DMA-angle referral.
• Has Amazon offered any remedial action? If so, is it sufficient – and does accepting it require you to release any rights?
• What is the commercial timeline? A ranking complaint that remains unresolved for weeks has a direct cost in lost sales. That cost informs whether out-of-court mediation or a regulatory referral is worth the time and resource it requires.

If escalation is the right step, the realistic options are: out-of-court mediation through one of the mediators certified under the P2B Regulation (available at no or low cost to the seller); a referral to the relevant member-state authority or – for DMA matters – to the European Commission; or, where there is a direct economic harm that meets the threshold, civil proceedings in an Italian or EU court. The path depends on the facts, the strength of your record, and the commercial calculus. We work through that decision with sellers before any escalation is filed.

For context on how a comparable escalation in a German marketplace context was approached and resolved, see our anonymized account of resolving a German marketplace suspension.

Phase 6: Protect your position while the complaint is live

A ranking complaint under EU rules can run for weeks or months. During that time, your Amazon IT account and listings remain active – but they also remain subject to platform enforcement. Protecting your position during the process is as important as the complaint itself.

Sellers sometimes treat an open complaint as a license to reduce operational vigilance. That is a mistake. Amazon can and does take separate enforcement actions during a complaint period, and a policy violation during that period – even a minor one – can be used to reframe the platform's position in the complaint.

Operational-protection checklist while your complaint is live:

• Maintain full compliance with Amazon IT's performance metrics and listing policies. Do not give Amazon a separate enforcement basis.
• Continue documenting your ranking position at regular intervals. A ranking change – up or down – during the complaint period is directly relevant evidence.
• Keep records of all communications with Amazon during the complaint period, however routine they appear.
• Do not accept any automated settlement offer or account-adjustment credit that contains broad release language without reading it carefully. Releases can extinguish your complaint rights.
• If Amazon issues a new policy notice or terms update during the complaint period, review it immediately for any connection to the ranking issue.
• Avoid public commentary about the complaint – on seller forums, social media, or press – until it is resolved. Public statements can complicate the mediation or litigation path.

A home-goods seller on Amazon IT (spring 2026) came to us after a significant organic ranking drop on a core ASIN following what appeared to be an algorithm change that coincided with Amazon launching a competing private-label product in the same category. We gathered the ranking history, identified the absence of any statement of reasons, and filed a structured P2B internal complaint with a DSA overlay, citing the self-preferencing pattern in the keyword data. Amazon's first response was generic. We resubmitted with a targeted challenge to the adequacy of that response under the DSA's statement-of-reasons standard. The second response provided a substantive explanation that – critically – disclosed a ranking parameter adjustment inconsistent with the platform's published P2B disclosure. That disclosure gap became the basis for an out-of-court mediation referral, and the seller's position was addressed without litigation.

Where this goes wrong: the most common mistakes sellers make alone

Filing an unfair ranking complaint under EU rules without a clear procedural map almost always produces one of three outcomes: a boilerplate rejection, a long silence, or an inadvertent waiver of rights. Understanding where the process breaks down is itself a decision-making tool.

The myth that EU sellers have no leverage once a platform changes their ranking is widespread – and it is wrong. The P2B Regulation, the DSA, and the DMA create real obligations with real enforcement consequences. What sellers often lack is not leverage; it is a disciplined method for asserting it.

The mistakes we see most frequently:

• Filing through Seller Support rather than the formal P2B/DSA internal complaint channel. Seller Support responses are not responses to a regulatory complaint; they do not satisfy Amazon's P2B obligations; and they do not create the formal record needed for escalation.
• Failing to invoke the specific legal instrument. A complaint that does not name the P2B Regulation, the DSA, or the DMA – and the specific obligation invoked – reads as a commercial dispute rather than a regulatory one. Amazon's response procedures are different for each.
• Accepting the first response as final. Amazon's internal complaint obligation requires an effective process. A generic or inadequate first response does not close the complaint; it opens the escalation path.
• Missing the self-preferencing evidence. The DMA self-preferencing angle is the strongest lever in ranking complaints where Amazon's own products are involved. Sellers who do not document that angle at the evidence phase cannot use it later.
• Escalating too early. Going to a regulator or court without exhausting the internal complaint process can result in the referral being bounced back – and may signal to Amazon that the complaint is poorly constructed.
• Waiting too long. The commercial cost of a ranking drop accumulates daily. A complaint that could have been filed in week two is filed in week eight, by which time the evidentiary window has narrowed and the business damage is harder to quantify.

If you have already filed an informal complaint and received a generic response, that is not the end of the road. A second read of what Amazon actually said – and what it omitted – can identify specific grounds for a formal refiling. That is where we often start when sellers come to us after an initial attempt.

If a first attempt at an internal complaint has already come back with a non-answer, a careful review of Amazon's response can identify what they failed to address and what a formal refiling should target. Email info@tutamenlaw.com to have your complaint record reviewed.

Related areas

• EU Marketplace Regulation – complete guide for sellers – the full regulatory map across DSA, DMA, and P2B
• DMA Self-Preferencing Complaints – how to build and submit the DMA self-preferencing case

If you are at the evidence-gathering or complaint-drafting stage and want a view on whether your ranking situation meets the P2B or DSA threshold, email info@tutamenlaw.com to arrange a short review.

Frequently asked questions

How long does resolving unfair ranking complaint under eu rules usually take on Amazon IT?

Resolution timelines vary significantly depending on which instrument is invoked and whether escalation beyond the internal complaint is required. An internal P2B complaint that prompts a substantive Amazon response can be addressed in a matter of weeks. If the internal process produces an inadequate response and the case moves to out-of-court mediation under the P2B Regulation, the timeline typically extends to several months. Regulatory referrals to member-state authorities or the European Commission for DMA matters operate on longer horizons – often a year or more. The commercial cost of that timeline is a key factor in deciding which path to pursue. In matters we handle, we assess the seller's revenue exposure against the realistic duration of each route before recommending an escalation path.

What are the main risks if I handle unfair ranking complaint under eu rules alone?

The primary risks are procedural rather than substantive. Filing through the wrong channel (Seller Support instead of the formal P2B mechanism), omitting the specific legal instrument from the complaint, accepting a generic first response as final, and missing the evidence window for a self-preferencing argument are the four errors we see most often. Each can be individually recoverable, but in combination they can foreclose escalation or significantly weaken the factual record for mediation or litigation. A seller who has already made one or more of these errors is not necessarily without options – but the path narrows with each procedural misstep.

Do I need a lawyer for unfair ranking complaint under eu rules?

Not for the initial evidence-gathering or the first internal complaint submission – a well-organized seller who understands the P2B and DSA framework can file a credible internal complaint. Legal input becomes genuinely important at two points: when drafting the complaint if self-preferencing under the DMA is part of the argument, because the evidentiary standard is higher; and before any escalation beyond the internal complaint, because mediation and regulatory referral processes have their own procedural requirements. For Amazon IT sellers whose revenue exposure is significant, attorney review at the complaint-drafting stage typically pays for itself in the quality of the record it produces.

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 practice covers the DSA, DMA, and P2B Regulation across Amazon's European surfaces, including Amazon IT. To discuss your situation, email info@tutamenlaw.com.

Page authored by Claire Donnelly, Arbitration & Disputes 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 Claire Donnelly, arbitration and disputes analyst at Tutamen.