Reserve after a chargeback spike: what it means for marketplace sellers

When a wave of chargebacks hits an Amazon UK selling account, the platform's automated risk controls move fast. Disbursements stop, a reserve calculation rises, and the seller is left staring at a balance they cannot access while invoices keep landing. The money is not gone – but recovering it requires understanding exactly what triggered the hold and what the procedural path actually looks like.

TL;DRA reserve after a chargeback spike is Amazon's mechanism for ring-fencing funds it may need to cover disputed transactions, A-to-z Guarantee claims, or refunds that follow a sudden rise in buyer complaints. On Amazon UK, the reserve typically adjusts automatically as chargeback rates normalise, but where the spike also triggers an Account Health review or a seller-verification request, the hold can persist far beyond what sellers expect – and doing nothing is the most expensive option.

This analysis covers what the reserve mechanism actually does, why a chargeback spike accelerates it, the procedural steps that move things forward, and the decision points that determine whether held funds come back quickly or remain frozen for months. It draws on the firm's experience representing Amazon UK sellers across frozen-funds, Account Health, and disbursement-hold matters.

What does a reserve after a chargeback spike actually mean on Amazon UK?

Amazon's reserve is not a penalty – it is a forward-looking estimate of the money the platform expects to pay out on the account's behalf over a defined rolling window. The reserve calculation rises when the system detects an elevated risk that future refunds, chargebacks, or A-to-z Guarantee claims will outpace the account's ability to absorb them from ongoing sales.

A chargeback spike is one of the clearest triggers. When a seller's chargeback rate climbs above Amazon's internal thresholds – which are not published but are consistent with the card-scheme rules that Visa and Mastercard impose on acquiring banks – the platform's automated systems flag the account for heightened reserve coverage. The reserve then expands to cover an estimated exposure based on recent order volume, average order value, and the rate at which claims are arriving.

On Amazon UK specifically, the disbursement cycle and the reserve interact in a way that is worth understanding. Amazon UK typically disburses on a rolling cycle, and the reserve is deducted before the disbursable balance is calculated. If the reserve covers most or all of the available balance, the disbursement is effectively zero even though the account is technically still active and processing orders. We regularly see sellers continue to generate sales – and therefore inventory and fulfilment costs – while receiving nothing from the platform for weeks.

There is a second layer that operators sometimes miss. A chargeback spike is not always caused by the seller's own conduct. Fraudulent orders placed with stolen cards, a batch of returns processed as card-scheme disputes rather than standard Amazon refunds, or a logistics delay that prompted buyers to escalate directly through their banks rather than through the A-to-z route – all of these can spike the chargeback rate without any underlying performance failure. The reserve treatment is identical either way, but the root cause matters enormously when it comes to addressing the hold.

Amazon's disbursement hold is distinct from a full account deactivation, though the two frequently arrive together. An account can remain active – listings live, orders processing – while a disbursement hold is in place. That combination is particularly damaging: the seller incurs FBA storage fees, shipping costs, and advertising spend against orders they are fulfilling, while receiving no cash from the sales. Understanding whether the freeze is a reserve adjustment, a disbursement hold triggered separately, or the result of a full deactivation is the first step, because each route to resolution is different.

Why does a chargeback spike affect disbursement so severely?

The severity of the disbursement impact depends on the interaction between three variables: the size of the spike, the account's historical reserve baseline, and whether the spike triggers any secondary Account Health action.

A modest spike – a handful of chargebacks on an account with strong prior performance – may do little more than widen the reserve by a small amount and resolve automatically as the rate falls back. A sharp spike, or one that pushes the account's chargeback rate above card-scheme thresholds, can produce a reserve that consumes the entire balance. The platform may also impose a funds-hold period that extends beyond the normal rolling reserve window.

The secondary Account Health action is where things become more complicated. If Amazon's systems conclude that the chargeback spike reflects a pattern – inauthentic items, a linked account with poor history, or repeated fulfilment failures – the Account Health Rating can drop into the "critical" zone. That triggers a separate review process and can result in deactivation under the Amazon Business Solutions Agreement (BSA). At that point, the reserve is no longer the only issue: the full account balance, including funds that were already in the disbursable pool, can be withheld under the BSA's provisions for post-deactivation holds.

In matters we handle, the most commercially damaging scenario is the one where a seller learns of a chargeback spike at the reserve-widening stage, takes no action because the account is still live, and then receives a deactivation notice weeks later when the secondary review concludes. By then, the reserve has consumed the rolling balance, the deactivation hold has frozen the rest, and the seller is managing two separate problems simultaneously – each with its own procedural path and timeline.

What decides which scenario plays out? Mostly the speed and quality of the response in the first few days after the spike appears in Account Health. A seller who identifies the root cause quickly – whether it is a batch of fraudulent orders, a carrier dispute, or an isolated fulfilment failure – and moves to document and address it is in a materially different position to one who waits for the automated review to run its course.

What is the realistic procedural path after a chargeback spike reserve hold?

The procedural path depends on whether the account is still active or has been deactivated. Each route involves different tools, different timelines, and different decision points for the seller.

Active account, reserve hold only. Where the account remains live and only the reserve has expanded, the primary lever is the Account Health dashboard and, where available, the Account Health Assurance (AHA) program. The seller can review the specific claims driving the spike, identify whether any are disputable – fraudulent orders placed with stolen cards are a clear example – and submit documentation to Amazon's seller-support and Account Health teams. FBA reimbursement claims for inventory affected by the associated fulfilment issues should be mapped and filed separately; they do not resolve automatically and are frequently overlooked while the seller is focused on the reserve itself.

Active account, secondary Account Health review in progress. This is the most time-sensitive phase. Amazon's Account Health team may reach out for information, request documentation about inventory sourcing, or seek verification of the seller's business identity. Responding promptly and accurately – without overstating or understating the operational picture – is critical. A poor response at this stage frequently converts a reserve-hold situation into a full deactivation, at which point the recovery path is longer and more complex.

Account deactivated, funds withheld. Once deactivation occurs under the BSA, the funds-recovery path separates from the reinstatement path. Reinstatement typically requires a Plan of Action (POA) that addresses the root cause, corrective measures, and preventive steps. Funds recovery involves mapping every held balance – the reserve, the disbursable balance held post-deactivation, and any pending FBA reimbursements for lost, damaged, or disposed inventory. Amazon's standard post-deactivation hold period under the BSA extends the reserve window, and disbursements do not resume until the review concludes or the account is reinstated. These are qualitatively different claims and are pursued through different channels within Amazon's seller-support and payment structures.

For our complete breakdown of the funds-hold process, see our guide to frozen funds recovery for sellers, which covers each balance type and the tools available for each.

The BSA also sets out a dispute-resolution path for sellers who disagree with Amazon's decision to withhold funds or deactivate an account. The path available – informal resolution, a Notice of Dispute, pre-arbitration demand, or arbitration under AAA rules – depends on the BSA version that applies to the account, which we check at the outset of every matter. Assuming a single standard route applies to all Amazon UK accounts is one of the more costly mistakes sellers make.

What should sellers do in the first 72 hours after identifying the hold?

Speed matters, but speed without direction is counterproductive. The first 72 hours after a reserve-hold or disbursement-hold notification should be spent on information-gathering, not on sending messages to Seller Central that make the problem harder to fix.

The practical steps are as follows. First, document the Account Health dashboard in full – screenshots of the current rating, the Order Defect Rate, and the specific chargeback or A-to-z claim entries. The Account Health snapshot changes; capturing the state at notification creates a factual record that is useful both for the POA and for any subsequent dispute process.

Second, run the order-level data. Which orders generated chargebacks? When were they placed, fulfilled, and when did the disputes arrive? This timeline frequently reveals whether the spike is concentrated in a specific time window – often correlated with a carrier failure, a batch of fraudulent orders, or a promotion that attracted high-risk buyers.

Third, map the balance. The current reserve amount, the disbursable balance, the current FBA reimbursement position, and any pending removal orders all represent distinct pools of money with separate recovery paths. Treating them as a single lump makes it harder to pursue each effectively.

Fourth – and this is where we consistently see the most preventable errors – do not file a generic appeal or send a message to Seller Central that admits to a performance failure that did not occur. If the chargebacks were driven by fraudulent orders or a third-party payment issue rather than a genuine defect rate problem, framing the response as a performance remedy will anchor Amazon's review on the wrong root cause. That makes the overall resolution slower and, in some cases, triggers additional review flags.

For sellers who have already received a deactivation notice alongside the reserve hold, the step-by-step guide to handling held funds during an investigation sets out the parallel process for reinstatement and funds recovery in more detail.

What are the seller's real decision points and trade-offs?

Every seller facing a reserve after a chargeback spike arrives at a set of genuine decisions, not all of which have obvious answers. Understanding what each choice costs – in time, money, and probability of recovery – is the core of what we assess at the outset of a matter.

Decision 1: Handle it internally or bring in external help? For a straightforward active-account reserve hold with a clear root cause, an experienced operations manager who knows Amazon UK's Account Health system well can often work through the process without outside assistance. The risk is in misjudging the complexity. If the spike has already generated a secondary Account Health review or a deactivation notice, the margin for error narrows sharply. A poorly framed POA does not just fail to reinstate – it can close off the informal route entirely and push the matter into the formal dispute path, which is more expensive and slower.

Decision 2: Wait for the review to resolve or intervene? Amazon's automated reserve systems do adjust downward as chargeback rates normalise. For a seller whose account is healthy in all other respects and whose spike was a one-time anomaly, waiting can be a reasonable choice. But the hold carries a real cash cost – inventory bills, FBA fees, advertising spend – that accumulates daily. In matters we handle, sellers who waited for an automated resolution on a complex hold frequently found that the hold had expanded rather than contracted by the time a human review began, because new claims continued to arrive during the waiting period.

Decision 3: Seek reinstatement first or pursue funds simultaneously? These are not mutually exclusive, but they consume different resources and run on different timelines. Reinstatement typically moves faster when it is the single focus – a well-constructed POA that addresses the specific Account Health flags is more likely to succeed than a partial one drafted alongside a parallel funds claim. On the other hand, the FBA reimbursement claims for lost or damaged inventory have their own filing windows; waiting for reinstatement to conclude before filing reimbursement claims can mean some claims are time-barred by the time they are submitted.

Decision 4: Appeal within Amazon's system or use the BSA dispute path? This is the most consequential decision. The appeal-and-POA route is faster and less adversarial when it works. The formal dispute path – Notice of Dispute, pre-arbitration demand, and if necessary AAA arbitration – is slower and more resource-intensive, but it carries legal weight that the internal appeal process does not. In our practice, the pre-arbitration demand sometimes resolves a matter that internal appeals had not moved, because it changes the decision-making context on Amazon's side. The path depends on the BSA version that applies to the account, the amount at stake, and the history of prior internal appeals.

If your platform is Walmart rather than Amazon, the reserve and chargeback mechanisms are structurally similar but the procedural path differs in important ways. Our guide to handling a frozen Seller Wallet on Walmart covers those differences for cross-platform operators.

Common mistakes sellers make when handling a chargeback spike reserve alone

There is a persistent belief among marketplace sellers that held funds after a chargeback spike are simply gone once an account is deactivated. This is one of the most costly myths in marketplace operations. Amazon's BSA and the payment structures underlying the UK marketplace create multiple obligations – contractual and regulatory – that the platform must satisfy before funds can be permanently withheld. Understanding this changes both the tone and the strategy of the response.

The practical errors we see most often are these. Submitting a root-cause Plan of Action that attributes the chargeback spike to a performance failure the seller did not actually have – because a template said to "take responsibility" – is the single most common. It anchors the review on the wrong question and, where the actual cause was fraud or a carrier failure, creates a factual record that contradicts the seller's own order data.

Filing FBA reimbursement claims too late is the second. The reimbursement process for lost, damaged, or disposed FBA inventory runs on its own schedule, and the filing windows are not indefinite. A seller who focuses exclusively on reinstatement and defers the reimbursement claims often finds that a meaningful portion of the recoverable balance is no longer accessible by the time reinstatement is achieved.

Treating every communication with Amazon's Seller Support as equivalent is the third error. The Account Health team, the reinstatement review team, and the payments team are separate internal functions. A message sent to general Seller Support about a disbursement hold frequently goes to the wrong queue and generates an automated response that gives no information about the actual state of the review. Routing communications correctly – and documenting that routing – is a procedural discipline that has a direct effect on timeline.

Finally, sellers who escalate too early to the formal dispute process – before exhausting the internal appeal path in a structured way – can find that the goodwill needed for an informal resolution has been consumed. The BSA dispute path is a tool of last resort, not a first response to a disbursement hold.

How Tutamen approaches reserve and chargeback-spike matters on Amazon UK

Tutamen's work on reserve-after-chargeback-spike matters is attorney-led and structured around the specific facts of each account. There is no generic template; the root cause of the spike – fraudulent orders, carrier failures, a specific fulfilment batch, an Account Health review that predated the spike – changes the strategy materially.

In practice, the work involves reviewing the deactivation or hold notice, reconstructing the account timeline from the order and Account Health data, and then deciding which tracks to run simultaneously. Where reinstatement is needed alongside funds recovery, we separate the POA work from the reimbursement and disbursement-claim work so that neither delays the other. Where the internal appeal path has already been tried and rejected, we assess what the formal dispute path – Notice of Dispute, pre-arbitration demand – adds and whether the amount at stake justifies it.

A mid-market apparel seller on Amazon UK (winter 2025) came to us after a chargeback spike driven by a batch of fraudulent orders had triggered an Account Health review that escalated into a Section 3 deactivation. The spike had nothing to do with the seller's fulfilment practices, but the first POA – drafted without that analysis – had framed it as a performance issue. We reconstructed the order timeline, identified the fraudulent-order cluster through the order-ID data, and refiled the POA on the actual root cause. The account was restored, and the disbursement hold released, within the period Amazon's standard review timeline allows. Separately, we mapped and filed the FBA reimbursement claims for the inventory that had been misprocessed during the review period – claims the seller had not yet filed.

A second matter involved a home-goods FBA seller on Amazon UK (spring 2026) where the chargeback spike was caused by a carrier partner's processing failure: a batch of deliveries had been marked undelivered at the carrier's end, prompting a wave of buyer chargebacks through the card scheme before the seller or Amazon's system could process the delivery confirmations. The disbursement hold had been in place for several weeks by the time the seller contacted us. We identified the carrier evidence, mapped the order-level delivery data, and pressed the disbursement and reimbursement claims through the Account Health and payments channels concurrently. The hold released following the corrected delivery reconciliation.

Our fees for reserve and disbursement-hold matters are quoted up front after a short review, typically on a fixed-fee basis. For funds-recovery work where the primary track is recovery of a held balance rather than reinstatement, a success-based component may apply alongside a fixed engagement fee. We explain the model at the outset, before any work begins.

If a first appeal or POA has already been submitted and came back rejected, that is not the end of the road. A rejected appeal tells us specifically which root-cause framing Amazon's system did not accept, which often narrows what needs to change in a second filing – or points toward the formal dispute path. To discuss the position on your account, email info@tutamenlaw.com.

Related areas

• Frozen Funds & Recovery – recovering held balances, disbursements, and FBA reimbursements across Amazon and Walmart
• Account Reinstatement – Plan of Action drafting and appeal strategy for deactivated Amazon seller accounts

Frequently asked questions

How long does resolving reserve after a chargeback spike usually take on Amazon UK?

The timeline varies materially depending on whether the account remains active or has been deactivated alongside the reserve hold. For an active account with a straightforward spike and a clear root cause, a reserve adjustment can begin resolving within a few weeks as chargeback rates normalise and supporting documentation is reviewed. Where the spike has triggered a full Account Health review and deactivation, the reinstatement and funds-release process typically runs for several weeks to a few months, with the funds-disbursement track sometimes trailing reinstatement by an additional period. The single largest driver of timeline is how quickly and accurately the root cause is identified and communicated to Amazon's review teams – a misframed first POA can add weeks to the process.

What are the main risks if I handle reserve after a chargeback spike alone?

The primary risks are framing the root cause incorrectly in a Plan of Action, missing the FBA reimbursement filing windows for inventory affected during the hold period, and routing communications to the wrong Seller Central team – all of which can extend the hold and, in some cases, close off options that were available at the start. Sellers who submit a generic "take responsibility and improve" POA when the spike was actually caused by fraudulent orders or a carrier failure often receive a rejection that does not explain what went wrong, making the second attempt harder to calibrate. An additional risk is escalating to the formal BSA dispute path before the internal appeal process has been properly exhausted, which can consume goodwill needed for an informal resolution.

Do I need a lawyer for reserve after a chargeback spike?

Not in every case. A seller with strong Account Health experience, a clear root cause, and an active account may be able to work through a reserve adjustment without outside help. Where the situation is more complex – a deactivation notice alongside the hold, a rejected first appeal, a significant frozen balance, or a chargeback spike caused by fraud rather than a seller performance issue – the value of attorney-led representation lies in correctly identifying the root cause, structuring the POA and documentation, and knowing when and how to use the formal BSA dispute path. Tutamen's work is quoted at a fixed fee up front, so the cost-benefit decision can be made clearly at the outset rather than after the matter has become more expensive to resolve.

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 with direct attorney involvement and full confidentiality from the first contact. To discuss your situation, email info@tutamenlaw.com.

By Helena R. Voss – Partner, Reinstatement

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.