Unfair ranking complaint under EU rules: what to do, step by step

A sudden drop in visibility on Amazon Italy can cost a seller weeks of revenue before anyone names the cause. When the cause is an undisclosed ranking change rather than a policy breach, the loss feels both unfair and irreversible. It is neither. EU law gives marketplace sellers a concrete set of rights against platforms, and those rights apply directly to Amazon IT listings. The question is whether you use them in the right order before the window closes.

TL;DRAn unfair ranking complaint under EU rules is a formal challenge to a marketplace's ranking practices based on the Platform-to-Business (P2B) Regulation and, for large platforms like Amazon, the Digital Services Act (DSA). On Amazon IT, sellers may demand an explanation of the main parameters that determine ranking, invoke the platform's internal complaint-handling system, and – if that fails – escalate through mediation or regulatory channels. The key is building a documented record from the first step, because later escalation depends entirely on what you filed earlier.

This guide walks through the exact step sequence, explains where sellers typically go wrong, and identifies the decision points that determine which path is worth taking.

What an unfair ranking complaint under EU rules actually covers on Amazon IT

The P2B Regulation imposes disclosure obligations on all marketplaces operating in the EU: sellers have a legal right to know the main parameters that determine how their listings are ranked and the relative importance of those parameters. That right is not a courtesy; it is enforceable. Amazon IT, as an EU-based marketplace surface, is bound by P2B regardless of where the seller is incorporated.

What sellers often miss is the scope of what "ranking" covers here. It is not only the organic search result order. The term extends to the prominence given to listings in any compared presentation, the treatment of sponsored versus non-sponsored items in those results, and – crucially – any differentiated treatment Amazon gives its own retail offers relative to third-party sellers. That last point is where the Digital Markets Act (DMA) gatekeeper obligations layer on top of P2B.

In matters we handle, the practical trigger for an unfair ranking complaint on Amazon IT tends to fall into three patterns: a seller's listings have dropped without any policy notice; a competitor's listings appear to benefit from a structural advantage that is not explained; or a seller discovers that Amazon's own private-label products consistently rank above comparable third-party offers in the same category. All three patterns can support a P2B-based complaint, and the DMA's self-preferencing prohibition makes the third pattern the most legally significant at this moment.

A P2B complaint is not an account deactivation appeal. There is no 48-hour clock and no "Plan of Action" format. It is a rights-enforcement process, and it runs on a different timeline and through different channels. Confusing the two is the most common early mistake.

Step one: document the ranking change and gather your baseline evidence

Before filing anything, build the evidentiary record that every later step depends on. This is where most solo attempts fail – sellers submit a complaint describing what they noticed, without the data that makes it verifiable.

The documentation task has four components. First, capture screenshots of the current search result pages for the relevant keywords on Amazon IT, with date and time stamps, showing your listing's position relative to Amazon's own offers and to competitors. Second, pull your Account Health and Sales Dashboard data for the period surrounding the ranking change – a sudden change in sessions and conversion rate with no change in your policy standing is useful evidence that the shift was externally imposed rather than performance-driven. Third, retrieve any communications from Amazon about ranking methodology for your category, including any Seller Central notifications about search algorithm updates or policy changes to listing eligibility. Fourth, document the relative treatment of comparable Amazon retail or Amazon private-label offers in the same category during the same period.

The standard of "comparable" matters. The P2B Regulation requires disclosure of the main ranking parameters and the relative importance of those parameters. Your documentation needs to show that your listing and the comparator listing are similar enough that a difference in ranking treatment requires an explanation. Category, price band, fulfillment method (FBA vs. Merchant Fulfilled), and review volume are the most defensible comparison axes.

This documentation phase typically takes several days of careful capture. Rushing it to file faster is a trade-off that rarely pays off.

Step two: make a formal ranking transparency request through Seller Central

The P2B Regulation requires Amazon to explain the main ranking parameters in its general terms. Amazon IT publishes a general statement in its Seller Central terms that nominally satisfies this. The problem is that a general statement does not tell you why your specific listings were affected by a specific change. You need to make the transparency request specific.

The formal channel for this on Amazon IT is a Seller Central case, directed to the Selling Partner Support team and explicitly framed as a request under the Platform-to-Business Regulation. The framing matters: a generic "why did my rankings drop" ticket is treated as a performance support query. A P2B-framed request is, in principle, a compliance matter and should reach a different tier of review.

In practice, the first response is often a templated reply pointing to Amazon's published ranking guidelines. Do not treat that as the end. The P2B Regulation requires Amazon to provide enough specificity for you to understand whether your listing is being treated consistently with the stated parameters. A response that does not address your specific situation does not satisfy that requirement. Reply in the same case, citing the regulation by name, asking for confirmation that the response is Amazon's complete answer to your P2B inquiry, and requesting the name of the internal complaint team responsible for P2B matters.

Keep every ticket number and every written response. That paper trail is the foundation of the next step.

Step three: escalate to Amazon's internal complaint-handling system

The DSA requires Very Large Online Platforms (VLOPs) – and Amazon is designated as a VLOP under the DSA – to maintain an internal complaint-handling system that sellers can use to challenge decisions affecting them. This applies to ranking decisions that restrict a seller's access to consumers, not only to content-moderation decisions.

Amazon's internal complaint system is accessible through Seller Central, and the entry point is typically the Account Health section or the case escalation path for unresolved seller-support issues. The complaint should be filed in writing, in Italian if you are operating on Amazon IT (or with an Italian version accompanying an English version), and should state explicitly that it is filed under Article 20 of the DSA as an internal complaint against a ranking decision.

The DSA requires VLOPs to process internal complaints within a reasonable time and to provide a reasoned decision. A "reasoned decision" means more than a templated response – it should address the substance of the complaint. If Amazon's internal complaint system produces a reasoned decision that addresses your P2B and DSA arguments, you have a document you can work with. If it produces a non-response or a template, that non-response is itself evidence of inadequate compliance with the DSA's complaint-handling obligations.

We regularly see sellers skip this step because it feels bureaucratic. That is a serious mistake. Regulatory escalation – to national authorities or to the DSA enforcement body – requires proof that you have exhausted or attempted the internal complaint route. Skipping it forecloses options.

For sellers also facing broader account or listing issues on Amazon IT, our guide to a seller's path through German marketplace suspension illustrates how EU-based procedural escalation works in a parallel context, and many of the sequencing lessons carry directly across marketplace surfaces.

Step four: assess whether the DMA's self-preferencing rules add a separate ground

If your ranking complaint involves Amazon ranking its own retail offers or private-label products above comparable third-party listings on Amazon IT, the DMA's self-preferencing prohibition is a separate and potentially stronger legal ground. Amazon is designated as a gatekeeper under the DMA, and gatekeepers are prohibited from treating their own services or products more favorably in ranking than third-party services or products on the same terms.

The practical question is whether you have evidence of systematic differentiated treatment – not a single keyword result, but a pattern across categories, time periods, and comparable listings. The DMA enforcement process runs through the European Commission, not through national authorities, and it operates on a regulatory timetable that is measured in months to years rather than days. A DMA complaint is not a fast path to restored rankings.

What a well-documented DMA complaint can do is create regulatory pressure that makes a commercial resolution more attractive to the platform. In our practice, the decision to file a DMA-grounded complaint is often more about creating leverage in parallel commercial negotiation than about expecting a Commission enforcement decision within a commercially useful timeframe. That trade-off is worth understanding before you invest the effort.

Our analysis of self-preferencing complaints under the DMA covers the grounds and process for that route in detail. It is worth reading before deciding whether to run both tracks in parallel.

Step five: mediation and out-of-court resolution

The P2B Regulation requires Amazon to identify, in its terms, at least two mediators it is willing to use for disputes with business users. That obligation gives sellers a contractual and regulatory right to request mediation before going to national courts or regulators.

Mediation under P2B is underused – partly because sellers do not know it exists, and partly because it requires preparation that most sellers do not have when they first discover a ranking problem. A mediation request that arrives with full documentation of the ranking change, the P2B transparency request, the internal DSA complaint, and a clear articulation of the commercial harm is in a very different position from one that arrives as a general complaint.

A mediator in a P2B dispute can compel Amazon to engage substantively with a seller's specific ranking concern in a way that Seller Central support cannot. The process is not fast – several weeks to several months is a realistic expectation – but it is orders of magnitude faster than litigation, and it does not require establishing a court with jurisdiction over a global platform.

The decision to request mediation turns on two things: the commercial materiality of the ranking impact (is the lost revenue significant enough to justify the time and effort?), and the quality of your documentation (do you have a record that supports a specific, verifiable claim?). If both answers are yes, mediation is the most cost-proportionate escalation path.

For the broader regulatory and procedural map of EU marketplace rights, the complete guide to EU marketplace regulation for sellers provides the full framework within which these individual steps operate.

If your situation involves a potential account-level suspension on top of the ranking complaint, the two processes interact in ways that require careful sequencing. Filing a ranking complaint while an account health issue is open can, in some circumstances, affect how Amazon processes both. This is one of the most common areas where handling the matter without specialist input creates avoidable complications.

Before the FAQ, it is worth noting where this process most frequently goes wrong. Sellers who handle this alone often fail at step two – they file a support ticket that gets triaged as a performance inquiry, receive no substantive response, and then escalate to mediation without the required internal complaint record. Mediation bodies and regulators expect to see evidence that internal channels were tried and were inadequate. Arriving without that record forces the mediator or regulator to send you back to complete the process, losing months.

What does a realistic outcome look like here? The P2B and DSA processes can result in a written explanation of ranking parameters that, at minimum, helps you understand whether your listings are being treated consistently with Amazon's stated rules. In some cases, that explanation reveals a configuration error in the listing or a category reclassification that can be corrected directly. In others, the process produces a record of inadequate response that supports the next escalation. What it does not do is guarantee an immediate ranking restoration. Managing that expectation from the outset is important.

If a first attempt at the internal complaint already came back with a template response or no substantive engagement, a second read of that response can often identify the specific ground on which it failed to satisfy the DSA's reasoned-decision requirement. That is not a reason to repeat the same complaint – it is a reason to reframe it with greater specificity and to route it more precisely. To discuss whether your record supports escalation to mediation or a DMA referral, contact Tutamen at info@tutamenlaw.com.

Where this process goes wrong: the most common mistakes

The most reliable predictor of a failed ranking complaint is a weak paper trail at step two. Sellers who treated the initial Seller Central ticket as informal lose the ability to show regulators or a mediator that Amazon's internal channels were genuinely inadequate – because there is no clear record of what was asked and what was refused.

The second most common mistake is conflating a ranking complaint with a listing suppression or account health dispute. They are separate processes. A listing may be suppressed for a policy reason that Amazon will disclose through Account Health. A ranking change may be the result of an algorithmic adjustment that Amazon has no obligation to reverse but does have an obligation to explain. Mixing the two in a single complaint dilutes both claims and confuses the forum.

The third mistake is underestimating the commercial specificity required. Saying "my ranking dropped" is not a complaint. Saying "my listing for ASIN X, category Y, on Amazon IT dropped from position 3 to position 28 in keyword search Z between date A and date B, while Amazon's own comparable listing remained at position 1–3 throughout the same period, despite no change in my listing quality, pricing, or fulfillment performance" – that is a complaint. The difference in specificity determines whether the internal complaint system and any mediator take the matter seriously.

A common objection we hear from sellers who have already tried once is this: "I filed the complaint and got nothing, so EU rules must not actually give sellers any leverage." That objection reflects the myth that EU marketplace law is decorative. In reality, the P2B and DSA obligations on Amazon IT are enforceable, and the enforcement process has teeth – but only if the internal record demonstrates that the platform was given the opportunity to comply and did not. A rejected or ignored internal complaint, properly documented, is the entry ticket to escalation. A complaint filed carelessly and dismissed is not.

Related areas

• EU Marketplace Regulation – legal rights for EU sellers facing platform enforcement actions
• DMA Self-Preferencing Complaints – grounds and process for gatekeeper challenges on Amazon
• EU Marketplace Suspension Defense – procedural path for sellers suspended on EU marketplace surfaces

Frequently asked questions

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

Timelines vary significantly depending on which path is pursued and how well-prepared the initial complaint is. An internal DSA complaint through Seller Central may receive a substantive response within several weeks, though non-substantive or templated responses are common and extend the process. P2B mediation typically runs several weeks to a few months from the filing of a mediation request to a concluded process. Regulatory escalation through national authorities or the European Commission operates on a much longer timetable, measured in months to years. The practical lesson is that the fastest outcomes come from the most carefully prepared complaints – a well-documented internal complaint is more likely to produce a response that resolves or advances the matter quickly.

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

The principal risk is creating a procedural record that forecloses later options. Sellers who file informal Seller Central tickets without explicitly invoking P2B or the DSA, who accept templated responses without documenting their inadequacy, or who skip the internal complaint step and go directly to a mediator or regulator typically find that the next forum requires them to complete the steps they missed – at the cost of months. A second risk is conflating different legal grounds: running a ranking complaint and a listing suppression appeal in the same filing tends to weaken both. Third, the commercial specificity required for a meritorious complaint is higher than most sellers expect, and a vague complaint may be dismissed in a way that prejudices a subsequent, better-prepared filing on the same facts.

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

You are not legally required to use a lawyer, but the process benefits materially from specialist input at two points: framing the initial P2B and DSA requests with the correct regulatory language so that they reach the right tier of Amazon's compliance function, and assessing – before you file – whether the documentation you have is sufficient to support mediation or regulatory escalation. Sellers who handle the early steps carefully can often reach a resolution through Amazon's internal complaint system without full legal representation. Where attorney involvement typically pays for itself is in situations where the internal complaint has already been rejected, the commercial stakes are material, and the question is whether escalation to mediation or a DMA referral is the right tool. For a fixed-fee review of your situation, contact Tutamen at info@tutamenlaw.com.

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 P2B transparency rights, DSA internal complaint processes, DMA self-preferencing complaints, and regulatory escalation on Amazon IT and other EU surfaces – at a fixed fee, quoted after a short review of your situation. To discuss your situation, email info@tutamenlaw.com.

Written by Claire Donnelly, arbitration and disputes analyst at Tutamen.

Published: March 10, 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.