Responding to account-level reserve after deactivation the right way

TL;DRAn account-level reserve after deactivation is Amazon's mechanism for withholding a seller's available balance while it assesses potential liabilities – refunds, A-to-z Guarantee claims, chargebacks, and policy exposure. On Amazon UK, the reserve can persist for an extended period after deactivation, even when the underlying appeal succeeds. The funds are not gone, but accessing them requires a separate, deliberate sequence of steps that runs alongside – and often outlasts – the reinstatement process itself.

This guide maps that sequence. It explains what the reserve actually is, why it behaves differently from a standard payment hold, where sellers go wrong at each stage, and what the realistic decision points look like. If the deactivation is still fresh, the next section is the one to read first. If you have already been rejected once, start at the section on what to do after a failed appeal.

What account-level reserve after deactivation actually is on Amazon UK

Account-level reserve is not a penalty. It is a protective measure Amazon applies to every UK seller account when disbursements are paused – typically because a deactivation has severed the normal disbursement cycle. Understanding that distinction matters, because the way you address a penalty and the way you address a risk-management hold are entirely different.

When an Amazon UK seller account is deactivated, Seller Central stops the regular disbursement cycle. Any balance that had not yet been transferred sits in the account balance. On top of that settled balance, Amazon calculates a reserve: an amount it judges sufficient to cover outstanding buyer claims, pending A-to-z decisions, and any refunds that could arise from orders fulfilled before deactivation. The reserve sits on top of whatever is in the balance – it is not the whole balance – and the two figures move independently as claims resolve.

Sellers frequently conflate the reserve with the disbursement hold, which creates a strategic error early on. The disbursement hold is the mechanism; the reserve is the amount. A disbursement hold can lift while a reserve remains, meaning a portion of funds is released but a material sum stays back. In matters we handle involving Amazon UK deactivations, sellers often discover this distinction only after receiving a partial disbursement that leaves a significant sum still locked.

The reserve is also separate from FBA reimbursement claims – for lost, damaged, or disposed inventory. Those claims travel through a different process entirely and can continue even after the account-level reserve is resolved. It is worth mapping both positions before deciding how to sequence your response, because the FBA reimbursement balance can sometimes exceed the reserve itself. For a full breakdown of the components involved, the detailed analysis of funds held after suspension covers each element separately.

Why does the reserve stay in place even after reinstatement?

Reinstatement and reserve release are procedurally independent. That is the single most common misunderstanding we encounter, and it costs sellers weeks of unnecessary delay.

When Amazon reactivates an account following a successful Plan of Action, it restores selling privileges. It does not automatically release the reserve. The reserve release requires Amazon to be satisfied that the liability window has closed – meaning outstanding buyer claims have resolved, the chargeback period has run, and no enforcement action is pending. On Amazon UK, the timelines governing that window are set by Amazon's internal policies, which it does not publish in full, and by the Consumer Rights Act obligations that flow through to the seller.

In practice, what this means is that a seller who receives a reinstatement decision should immediately file a separate, explicit request for reserve review – not assume the money will follow automatically. That request is different in tone and substance from the reinstatement appeal. It addresses the liability exposure directly: what claims have resolved, what the current order defect position is, and why the remaining balance exceeds any realistic future liability. Failing to file it is the single biggest source of extended reserve holds in matters we handle.

There is a second reason the reserve can persist even after reinstatement: a related-account flag or ongoing policy review. If Amazon's systems flag a connection to another account under investigation, the reserve on the reinstated account can be extended administratively, independent of the appeal outcome. Identifying and addressing that flag is a different task from the standard reserve-release request, and conflating the two produces a circular response that Amazon's review teams simply reject.

The realistic procedural path – step by step

The sequence below describes the standard path for an Amazon UK seller working through account-level reserve after deactivation. Your specific path will depend on the exact wording of the deactivation notice, the account history, and the nature of any pending claims – which is what a detailed review establishes first.

1. Obtain and read the deactivation notice in full. Amazon UK deactivation notices identify the policy or performance trigger. The trigger determines whether the reserve is tied to a specific enforcement concern (e.g., product authenticity, related account) or to a general policy deactivation. The two paths diverge immediately.
2. Map the financial position. Before drafting anything, list every component: the available balance, the reserve amount, any pending A-to-z claims, any open reimbursement claims, and any outstanding removal orders. These figures change daily as claims resolve. Working from an outdated snapshot produces a reserve-release request that Amazon can immediately undercut by pointing to unresolved claims.
3. File the Plan of Action addressing the deactivation trigger. The reinstatement appeal and the reserve release are separate, but the POA must succeed before the reserve release has any traction. A POA that addresses the wrong root cause – the most common failure mode – extends both the reinstatement timeline and the reserve hold. The POA must identify the actual cause (not the proximate one), the corrective steps already taken, and the preventive measures that make recurrence unlikely.
4. Monitor claim resolution in parallel. While the POA is under review, track every A-to-z and chargeback decision. Each resolved claim reduces the theoretical liability that justifies the reserve. Documenting these resolutions, with dates and amounts, is the evidentiary foundation for the subsequent reserve-release request.
5. File the reserve-release request after reinstatement – or in parallel if reinstatement is delayed. This is a separate communication to Seller Central, distinct from the appeal. It presents the financial map from step 2, the resolved-claims evidence from step 4, and a reasoned argument that the remaining reserve exceeds foreseeable liability. If reinstatement has not yet occurred but the account has been deactivated for an extended period, the reserve-release case can sometimes be filed concurrently – the timing depends on the reason for deactivation.
6. Escalate if the reserve-release request is ignored or denied. Amazon's initial response to a reserve-release request is frequently a form letter citing the standard reserve policy. A properly reasoned follow-up, referencing the specific liability position and the resolution of the claims that justified the hold, produces a different outcome in many matters. If that too is rejected, the escalation options include the Notice of Dispute process and, on Amazon UK, the Platform-to-Business (P2B) Regulation complaint pathway.
7. Resolve outstanding FBA reimbursement claims separately. Once the reserve releases, open reimbursement claims for lost or damaged FBA inventory should be pursued through the standard reimbursement process. These do not resolve automatically on reserve release and can represent a significant portion of the seller's total recovery.

The realistic time from deactivation to full fund recovery varies considerably. It depends on the deactivation type, the volume of pending claims, and how quickly Amazon's review teams process escalations. The complete guide to frozen funds recovery sets out the broader context for sellers trying to understand where their situation sits on that spectrum.

Where this goes wrong – the most common failure points

The procedural path above is logical in sequence. It breaks down in predictable places, and knowing those places in advance is the difference between a matter that resolves in weeks and one that drags for months.

Wrong root cause in the POA. This is where most self-represented sellers lose the most time. The deactivation notice gives a category – "related account" or "inauthentic items" – but the root cause is more specific. A POA that addresses the category rather than the specific trigger reads as generic to Amazon's review team and is rejected. A related-account flag that came from a shared IP address requires a different root cause narrative than one that came from a shared payment method. The specifics matter.

A practical illustration: a kitchenware FBA seller on Amazon UK came to us in winter 2025 after two POA rejections. The deactivation notice cited a related account. Both previous POAs addressed "unintentional account linking" in general terms. When we reconstructed the account history, the flag was traceable to a former business partner who had listed on the seller's account years earlier. The third POA addressed that specific connection with documentary evidence. The account was restored.

Filing the reserve-release request too early. A request filed while material A-to-z claims are still pending gives Amazon a simple basis for denial: outstanding liabilities. Waiting until the claims window has substantially cleared, and presenting that evidence, produces a stronger submission. The impatience is understandable – the money is held while inventory and ad bills keep coming due – but a premature filing often resets the internal review clock.

Accepting a partial disbursement as final. Amazon sometimes releases a portion of the balance as claims resolve. Sellers occasionally treat this as the end of the process and stop following up. The remaining reserve does not release automatically; it requires a further, explicit request. In many matters, a significant sum stays locked simply because the seller stopped pressing after the first partial release.

Missing the P2B escalation pathway. Amazon UK sellers have rights under the Platform-to-Business Regulation that sellers on other surfaces do not. The P2B Regulation requires Amazon to provide a statement of reasons for restricting or terminating access, and it establishes an internal complaint mechanism that is separate from the standard appeals process. Sellers who exhaust the standard appeals process without considering P2B may be leaving a material escalation lever unused. The rules governing this pathway are set out in EU and UK regulation – and for sellers on Amazon's EU surfaces, the Digital Services Act creates parallel obligations.

Conflating the reserve release with FBA reimbursement. These are different processes. Resolving one does not resolve the other. We regularly see sellers who successfully recover their reserve balance but have open FBA inventory claims – for units Amazon lost or disposed of during the deactivation period – that they never filed. Those claims have their own timelines and, if not filed, are simply not paid.

What the seller's decision points look like

At each stage, the seller faces a genuine choice. The path is not automatic, and understanding the trade-offs at each fork is what determines how much is ultimately recovered and how quickly.

Decision 1: appeal now or investigate first? The instinct after a deactivation is to file immediately. That instinct is almost always wrong. A POA filed within hours of a deactivation notice, without a thorough account review, is almost certainly addressing the wrong root cause. In matters we handle, a two-to-three day delay for a proper account reconstruction routinely produces a first-time reinstatement that a hasty POA does not. The cost of investigation is measured in days; the cost of a failed first POA is measured in weeks of extended hold.

Decision 2: reinstatement first, or reserve release in parallel? For most deactivations, the reinstatement appeal must succeed before the reserve-release request has traction. But for deactivations that are extended or where reinstatement prospects are genuinely uncertain, it is sometimes worth building the reserve-release case independently – particularly where the seller can demonstrate that the reserve amount materially exceeds any realistic liability. If the notice cites a clear policy violation with a straightforward correction → focus on the POA first, then file the reserve request immediately on reinstatement. If the notice is vague, involves a related-account flag, or has been under review for an extended period → map the financial position and consider whether a parallel filing makes sense.

Decision 3: standard escalation or P2B complaint? The internal escalation path – follow-up communications to Seller Central – is usually the right first step. It is faster and lower cost. The P2B complaint mechanism is more formal and takes longer. But where Amazon's review team is not engaging substantively, the P2B pathway creates a procedural obligation on Amazon that the standard appeals process does not. For Amazon UK sellers, understanding when to switch from one to the other is a judgment call that depends on the specific response pattern from Amazon and the amount at stake.

Decision 4: Notice of Dispute and arbitration? For larger balances, the Notice of Dispute and the dispute-resolution process in the Amazon Business Solutions Agreement may be appropriate. The path depends on the BSA version that applies to the account, which requires a careful read before any Notice is filed. This option is discussed in detail in the guide on responding to a rolling reserve increase, where the escalation options and trade-offs are mapped out for a closely related scenario.

Is arbitration always the right escalation for a frozen balance? Not automatically. For mid-range balances, a well-structured pre-arbitration demand that makes the cost-benefit calculation clear to Amazon's legal team often produces a resolution without formal proceedings. The right tool depends on the amount, the account history, and the strength of the reserve-release argument.

What a well-evidenced reserve-release request contains

A reserve-release request that produces a result is not a complaint or a demand. It is a structured financial and procedural argument. The components that matter are consistent across matters we handle.

First, a precise account of the current financial position: the reserve amount as of the filing date, the settled balance, and any pending claims that have not yet resolved. This needs to be current – pulled from Seller Central within twenty-four hours of filing.

Second, a resolved-claims schedule: a list of every A-to-z claim and chargeback that has closed since deactivation, with the decision and date for each. This is the evidence that the liability exposure Amazon was protecting against has materially diminished.

Third, a liability projection: a reasoned calculation of the maximum realistic future liability from the remaining open orders and the applicable refund window. This is where sellers who lack a legal or accounting background often underestimate their own argument – Amazon's reserve is sized against a worst-case liability, but the realistic liability, evidenced by the actual claim rate, is usually significantly lower.

Fourth, a regulatory reference where applicable. For Amazon UK sellers, the P2B Regulation and, for accounts also active on EU surfaces, the Digital Services Act provide a durable legal basis for requesting a statement of reasons and engaging the internal complaint mechanism. Citing the relevant obligation – not just the policy – shifts the tone of the request from a seller complaint to a compliance engagement.

A second practical illustration: a consumer-electronics reseller on Amazon UK (spring 2026) contacted us after a deactivation tied to a product authenticity complaint. The reserve was substantial and had remained in place through two reinstatement cycles. When we mapped the claim position, the active A-to-z exposure was a small fraction of the reserve. A reserve-release request presenting that analysis, with the resolved-claims schedule, led to a phased release of funds over several weeks. The FBA reimbursement claims for inventory disposed of during the deactivation period were filed separately and are ongoing.

What sellers assume that is not true

The most persistent myth in this area is that held funds are gone for good once an account is deactivated. That is not how the mechanism works. Amazon holds the funds to cover liabilities; it does not forfeit them. The legal and contractual relationship between the seller and Amazon under the Business Solutions Agreement preserves the seller's claim to the net balance after legitimate deductions. The funds remain the seller's property. The task is demonstrating, on the evidence, that the liability exposure has resolved to a level that permits release.

The second myth is that a deactivation appeal and a reserve-release request are the same communication. They are not. Conflating them – addressing both in a single POA – is a common error that produces a response that addresses only the reinstatement question and ignores the financial one. Amazon's review teams handle these as separate queues.

The third myth is that only very large sellers need professional assistance for this. In matters we handle, the cases where a seller attempts the process alone and loses significant time are not clustered at the large end. Mid-market sellers – those running a significant FBA business but without dedicated account-health staff – are the most common profile. The process is procedurally precise, and a single mischaracterization in a POA or a poorly timed reserve-release request can extend the hold substantially.

The steps above describe the standard path. Your situation turns on the exact wording of the notice, the account history, the composition of the reserve, and the timing of your claims – which is what we review first. For a read on your specific position, email info@tutamenlaw.com.

Related areas

• Frozen Funds & Recovery – full practice hub for disbursement holds, reserves, and FBA reimbursement claims
• Account Reinstatement – Plan of Action drafting and appeal strategy for deactivated Amazon accounts

Frequently asked questions

How long does resolving account-level reserve after deactivation usually take on Amazon UK?

The timeline depends on the deactivation type, the volume of pending A-to-z claims, and whether Amazon's review team engages substantively on the reserve-release request. In matters we handle, a straightforward deactivation with few pending claims can see a reserve release in several weeks after reinstatement, provided the reserve-release request is filed promptly and is well evidenced. Where claims are still open, or where the deactivation involves a related-account flag or ongoing enforcement review, the timeline extends. Filing the reserve-release request at the right moment – after material claims have resolved but without waiting indefinitely – is the main factor within the seller's control.

What are the main risks if I handle account-level reserve after deactivation alone?

The most common risks are: filing a POA that addresses the wrong root cause, which leads to repeated rejection and an extended hold; filing the reserve-release request while significant claims are still pending, giving Amazon a straightforward basis for denial; accepting a partial disbursement as final and stopping follow-up before the full balance is released; and missing the P2B escalation pathway that Amazon UK sellers have available under applicable regulation. Each of these errors is recoverable, but each adds time – and time is the primary cost when inventory and operating bills keep running.

Do I need a lawyer for account-level reserve after deactivation?

Not every case requires legal representation. A seller with a clear deactivation trigger, no pending claims, and a straightforward account history may work through the process without assistance. The cases where professional involvement adds the most value are those involving a wrong-root-cause POA rejection, a related-account or enforcement flag, a reserve that has persisted well beyond reinstatement, or a balance large enough to justify formal escalation through a Notice of Dispute. If a first attempt has already been rejected, a review of what went wrong and what is still available is usually worth the time, regardless of whether you proceed with or without representation.

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 after a short review of your account and notice. We act for founders, brand owners and in-house teams who need a specialist for a marketplace dispute. To discuss your situation, email info@tutamenlaw.com.

About the author: Claire Donnelly is Tutamen's arbitration and disputes analyst, focusing on reserve recovery, pre-arbitration demand strategy, and BSA dispute-resolution matters for Amazon UK and EU sellers.

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.