Performance-based deactivation: a seller's checklist

The account is down, the listings are dark, and the cash flow has stopped. For Amazon DE sellers hit by a performance-based deactivation, the instinct is to respond immediately – to write something sincere, to promise improvement, and to hit send. That instinct is the most common reason a first appeal fails. Performance-based deactivations on Amazon Deutschland follow a specific logic, and Amazon's review process rewards precision over apology. This checklist walks through every phase, from reading the notice correctly to deciding when escalation or legal action makes sense.

TL;DRA performance-based deactivation on Amazon DE is triggered when a seller's Account Health metrics – Order Defect Rate, Late Shipment Rate, or Pre-fulfillment Cancellation Rate – breach Amazon's thresholds. Reinstating the account requires a Plan of Action that diagnoses the exact metric failure, explains its root cause, and shows concrete corrective steps already taken. A generic apology does not meet that standard and will typically be rejected without substantive review.

This checklist is organized into five phases: reading the notice; auditing the performance data; building the Plan of Action; filing and tracking the appeal; and deciding when to escalate. Each phase carries specific checks. Work through them in order – skipping ahead almost always creates problems downstream.

Phase 1: Read the deactivation notice carefully before doing anything else

The notice tells you which metric triggered the deactivation and which policy the breach maps to – and that is the exact scope of your Plan of Action.

Performance-based deactivations are distinct from policy-violation deactivations. The former are metric-driven; the latter follow a separate procedural path. Confusing the two is a surprisingly common error. In matters we handle on Amazon DE, sellers regularly arrive with a plan of action that addresses a policy concern when the notice clearly names a performance metric – and vice versa. The result is a misaligned appeal that does not speak to what Amazon's review team is actually looking at.

Checks for Phase 1:

• Confirm the notice identifies the account as deactivated under performance grounds – look for explicit references to Order Defect Rate (ODR), Late Shipment Rate (LSR), or Pre-fulfillment Cancellation Rate (PCR).
• Note the specific metric cited and, if stated, the threshold it breached. Amazon DE applies the same core performance thresholds as the global programme, enforced through Seller Central's Account Health dashboard.
• Check whether the notice also contains a secondary policy-violation component. Occasionally a performance notice bundles a related policy flag. If it does, both issues must be addressed – separately – in the Plan of Action.
• Identify the response route the notice specifies: Seller Central Appeal button, an email reply, or a different path. Filing through the wrong channel can lose time or create a duplicate record that confuses the queue.
• Record the date and time you received the notice. The appeal window, while not publicly fixed to a hard number of days, is finite. Delays compound the problem.
• Save the full notice text and any linked Account Health notifications. You will need them when reconstructing the timeline.

One thing to clarify at this stage: if you sell on both Amazon DE and other Amazon EU marketplaces (Amazon FR, Amazon IT, Amazon ES), a deactivation on one marketplace does not automatically cascade to others. The account-level versus marketplace-level distinction matters for how you frame the appeal and which Seller Central interface you use to file it. For a broader map of how reinstatement works across surfaces, see our complete guide to reinstatement on online marketplaces.

Phase 2: Audit your performance data before writing a single word of the appeal

The Plan of Action must reference your actual data – not what you assumed happened, and not a general description of your operations.

A common mistake is to start drafting the Plan of Action before pulling the underlying order data. The appeal will read as vague and unconvincing if it cannot point to specific transactions, time windows, or operational events that explain the metric failure. Amazon's review teams on the DE marketplace read a large volume of appeals. The ones that move quickly are built on traceable, specific facts.

Checks for Phase 2:

• Download your Order Defect Rate report from Seller Central for the period that corresponds to the metric breach. Identify the specific orders that drove the defect rate above the threshold – A-to-z Guarantee claims, negative feedback, and credit-card chargebacks are the three components.
• For Late Shipment Rate breaches: pull the late-shipment report and identify the window – was it a carrier delay, a fulfilment centre issue, or a process failure at your end? Was this FBA or FBM? The answer changes the root-cause narrative entirely.
• For Pre-fulfillment Cancellation Rate: identify the SKUs and the period. Stockout? System error? A supplier failure? Each has a different corrective action.
• Cross-reference the defect orders with any customer messages or A-to-z claims in your Seller Central inbox. What was the stated reason for each claim or negative feedback?
• Check whether any of the defect orders are eligible for removal from the ODR calculation – for example, a resolved A-to-z claim where Amazon determined the seller was not at fault, or a buyer-fault chargeback. Identify these before filing. Do not assume Amazon's system has already removed them.
• Map the timeline: when did the metric first begin trending toward the threshold? What operational event coincides with that date? The answer to that question is the root cause of your Plan of Action.
• If you use a third-party order management or repricing system, pull any error logs or configuration changes that fall in the relevant window. Automation failures are a legitimate root cause but must be documented.

What surfaces consistently in the matters we handle is that sellers who skip this audit produce Plans of Action built on assumptions. The assumptions are often close to correct – but "close" is not what Amazon's review process accepts. A one-week audit phase almost always produces a stronger appeal than a same-day filing built on memory.

Phase 3: Build the Plan of Action – structure, language, and what Amazon is actually checking

A Plan of Action that gets reinstated contains three elements in the correct sequence: the precise root cause of the metric failure; the corrective actions already taken (not planned); and the preventive measures that make recurrence unlikely.

That three-part structure – root cause, corrective actions, preventive measures – is not a formality. It is the evaluative grid that Amazon's Account Health team uses to assess whether an appeal addresses the actual problem. An appeal that leads with apology, or that spends most of its length on business history, does not map onto that grid and will likely be auto-rejected or returned for more information.

Checks for Phase 3:

• Root cause: write one clear paragraph that states what went wrong, when, and why. It must connect directly to the specific metric cited in the notice. "We had high ODR because we experienced a surge of A-to-z claims in October 2025, driven by a supplier shipping a defective batch of units across 14 orders" is a root cause. "We did not manage our account properly" is not.
• Corrective actions already taken: list only things you have actually done, with evidence. If you removed the defective inventory from FBA, say so and include the removal order number. If you terminated the supplier relationship, state the date. Amazon's review team is alert to plans that describe future intentions as if they are past actions – this is a fast path to rejection.
• Preventive measures: describe the process change that ensures the root cause cannot recur. For a supplier-quality failure: what is the new incoming-inspection step? For a late shipment surge from a carrier problem: which backup carrier or fulfilment method is now in place? Be specific.
• Keep the total Plan of Action to a readable length. There is no fixed word count, but a three-to-five section document with clear headers is substantially more readable than a wall of text. Amazon DE's review team reads German-language accounts as well as accounts managed in English. Either is acceptable, but be consistent throughout the appeal.
• Do not include irrelevant facts about your business history, your customer satisfaction scores on other platforms, or your years of selling. These are not factors in a performance-based appeal and they dilute the document.
• Do not apologize in lieu of analysis. The phrase "we sincerely apologize and promise this will not happen again" is the single clearest signal to a review team that the underlying root cause has not been identified. It is also the myth many sellers carry into their first appeal – that sincerity alone can substitute for a documented diagnosis. It cannot.
• Attach supporting documents. The specific documents depend on the root cause: carrier delay confirmations, supplier correspondence, FBA removal records, updated process SOPs. The Plan of Action should reference each attachment by name so the reviewer can locate it easily.

The decision at this phase is whether to file once with a well-prepared document or to file quickly and iterate. In our practice, a strong first appeal on a performance-based deactivation on Amazon DE produces better outcomes than a sequence of weak attempts. Multiple rejected appeals build a record that can make later filings harder to succeed with. If the data audit in Phase 2 is not yet complete, delay filing until it is.

To understand how the Plan of Action requirements differ between performance-based and policy-violation deactivations – and where the procedural paths diverge – see our analysis of policy-violation deactivations and what has changed.

Phase 4: File the appeal and track what happens next

Filing the appeal is not the end of the process – it is the beginning of a review cycle that requires active monitoring and, in many cases, a prepared response to a follow-up request.

Amazon's Account Health team may respond with one of several outcomes: reinstatement, a request for additional information, a rejection with comments, or – on some accounts – no substantive response for a period. Each outcome has a different next step, and treating a request-for-information response as a rejection is a common error that causes sellers to refile prematurely or escalate before the original review is complete.

Checks for Phase 4:

• File through the channel the notice specified. Confirm the appeal has been received and is reflected in your Seller Central account communications. Screenshot or save the submission confirmation.
• Set a monitoring schedule. Check Seller Central notifications and your registered email address at least twice daily. Amazon's response windows vary; a response may arrive within days or may take longer depending on appeal volume and account complexity.
• If Amazon responds with a request for additional information: treat this as a positive signal. It means the review team read the appeal and has a specific question. Answer the question directly – do not resubmit the entire Plan of Action. Identify the exact question and address it precisely.
• If Amazon responds with a rejection that includes comments: read those comments carefully before doing anything else. The rejection comments often identify what the review team found insufficient. Your second filing should address that specific gap – not simply elaborate the original appeal.
• Track every communication in a running log: date, channel, summary of content, your response. This log becomes the factual record if the matter escalates to a formal dispute or requires legal involvement.
• If the account held FBA inventory at the time of deactivation, check the status of your FBA balance and any removal orders. Deactivation does not automatically trigger inventory liquidation, but storage fees continue to accrue. Initiating a removal order for slow-moving or high-storage-cost inventory during the appeal period is a legitimate operational step.
• Check whether any funds disbursements have been suspended. A performance-based deactivation often coincides with a payment hold. The hold and the deactivation are related but procedurally separate – resolving the deactivation does not automatically release a separately applied reserve. Keep track of both.

A micro-case from our practice: an electronics accessories seller on Amazon DE (winter 2025) came to us after a second rejection on a performance-based deactivation tied to an Order Defect Rate spike. The original Plan of Action had identified the correct root cause – a batch of units from a contract manufacturer returned at an elevated defect rate – but the corrective-action section described steps the seller intended to take, not steps already completed. The rejection comments flagged exactly this. We rebuilt the Plan of Action around actions already executed, added supplier correspondence and incoming-inspection records, and the account was restored on the third filing.

Phase 5: Decide when to escalate – and what escalation actually looks like

If the standard appeal route has not produced reinstatement after a reasonable number of good-faith attempts, escalation options exist – but they carry their own trade-offs, and the right path depends on the specific facts of the account.

Escalation on a performance-based deactivation on Amazon DE can take several forms. Within the Amazon system, there are escalation paths through the Account Health Support team and, in some cases, a higher-tier review. Outside the Amazon system, the options include using the Platform-to-Business (P2B) Regulation's requirements, which impose obligations on Amazon as a business-to-business online intermediary – including requirements around statement of reasons and access to an internal complaint-handling system. The Digital Services Act (DSA), under which Amazon operates as a Very Large Online Platform in the EU, adds a further layer of procedural rights for DE-based sellers.

Checks for Phase 5:

• Assess the grounds: is the deactivation well-founded on the data, or is there a factual or procedural basis to challenge the metric calculation itself? If the ODR calculation includes claims that should have been excluded, that is a substantive ground. If the Late Shipment Rate spike was caused by a carrier outage verifiable through carrier data, that is documentable.
• Consider the P2B Regulation route. Amazon is required under P2B to provide a statement of reasons for deactivation and access to an internal complaint-handling mechanism. If that process has not been properly invoked, it is a procedural lever worth using before moving to external dispute resolution. This is particularly relevant for DE sellers given the German regulatory environment and the Bundeskartellamt's active interest in platform conduct.
• Review the dispute-resolution options available under the Amazon Business Solutions Agreement (BSA). The BSA governs the seller-Amazon relationship and includes provisions for how disputes are handled. The path depends on the BSA version that applies to the account – which we check first when a matter reaches us at this stage.
• Evaluate the cost of delay against the cost of legal involvement. For an account generating meaningful monthly revenue, even several weeks of downtime represents a material financial impact. Legal representation on a performance-based reinstatement matter typically involves a fixed fee, quoted after a short review. That cost should be weighed against the revenue loss of continued deactivation and the risk that further self-filed appeals build an unfavorable record.
• If the account has a related-account deactivation component layered on top of the performance-based grounds – a situation we see with some frequency on Amazon DE – the escalation path changes. The two issues require separate treatment, and conflating them in a single appeal is a structural error. See what to know about related-account deactivation for how that issue is handled on Amazon's EU surfaces.
• If you have reached the point where direct seller-account communication with Amazon has stalled, document that stall – dates of filings, dates of responses, content of any rejection comments. That record is the starting point for any escalation, whether through Amazon's own mechanisms or through external channels.

A second micro-case: a fashion accessories seller on Amazon DE (spring 2026) had a performance-based deactivation that they had been attempting to resolve for several months through self-filed appeals. The rejection record showed a pattern: each rejection pointed to the same gap in the corrective-action section, which the seller had not identified because the rejection comments were brief and generic. When we reviewed the full communication log, we identified a P2B-based internal complaint right that had not been invoked and used it to re-open the review on different grounds. The account was restored.

The decision to handle a performance-based deactivation alone versus engaging a specialist is a legitimate trade-off, not a self-serving one. Many sellers do resolve these matters without legal help. The cases where professional involvement consistently adds value are: multiple rejected appeals with no clear explanation; a deactivation that also involves a fund hold; a layered notice combining performance and policy grounds; or a situation where the account generates revenue that makes each additional week of downtime significantly costly.

The steps above describe the standard path through a performance-based deactivation. Your situation turns on the exact wording of the notice, the specific metric data, and what prior filings – if any – have already been made. Those are the three things we review first. To get a read on where your appeal stands, email info@tutamenlaw.com.

Related areas

• Amazon seller account reinstatement – full practice overview for deactivation, appeals, and Account Health
• Frozen funds recovery – when deactivation coincides with a payment hold or reserve

Frequently asked questions

How long does resolving performance-based deactivation usually take on Amazon DE?

There is no fixed timeline. A well-prepared first appeal on a straightforward performance-based deactivation can produce a response within days; a matter involving multiple prior rejections, a layered notice, or an escalation through Amazon's internal complaint-handling system typically takes several weeks. The single biggest variable is the strength and completeness of the initial Plan of Action. A weak first filing that gets rejected and requires a second or third attempt extends the timeline materially. German sellers operating under the P2B Regulation have additional complaint-handling channels that can affect how long the process runs.

What are the main risks if I handle performance-based deactivation alone?

The primary risk is building a rejection record that makes later filings harder. Each rejected appeal is visible to the review team handling subsequent attempts. A plan of action that misidentifies the root cause, describes intended rather than completed corrective actions, or addresses the wrong grounds signals to reviewers that the underlying problem has not been resolved. A second risk is missing a procedural window – either within Amazon's system or under applicable EU regulations like the P2B Regulation or the Digital Services Act. Those windows, once missed, can close or narrow the available options.

Do I need a lawyer for performance-based deactivation?

Not in every case. Sellers with a clear single-metric failure, a documented root cause, and no prior rejected appeals can often resolve a performance-based deactivation through a well-constructed self-filed Plan of Action. Legal representation adds consistent value when there are multiple prior rejections with unclear feedback; when the deactivation is layered with a policy-violation or related-account component; when a fund hold runs concurrently; or when escalation through P2B or BSA dispute-resolution channels is needed. In those situations, the practical cost of continued downtime typically exceeds the cost of professional involvement.

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 Amazon DE and other EU surfaces draws on familiarity with the P2B Regulation, the Digital Services Act, and the procedural expectations of Amazon's European Account Health teams. To discuss your situation, email info@tutamenlaw.com.

By Noah Brennan – federal litigation & disputes analyst, Tutamen.

Published March 13, 2026.

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.