How to handle damages in a marketplace dispute: a step-by-step guide
A flat rejection from Amazon UK support feels like the end of the road. The dispute team sends a form reply, the account health dashboard shows no movement, and the inventory loss or revenue shortfall keeps growing. That feeling is understandable – but it is also the moment where the real path to recovering damages usually begins, not ends.
TL;DRRecovering damages in a marketplace dispute on Amazon UK requires a structured sequence: document the loss with precision, identify the contractual or policy basis for the claim, send a formal Notice of Dispute under the applicable Business Solutions Agreement terms, attempt informal resolution, and – if that fails – escalate to a pre-arbitration demand or formal arbitration proceeding. Each step is a decision point, and the choices made early determine what remains possible later.
This guide walks through that sequence step by step. It covers what "damages" actually means in an Amazon UK context, where sellers most often go wrong, and the trade-offs at each stage – so that the decision to proceed, negotiate, or settle is made on accurate information rather than frustration.
What does "damages" actually mean in an Amazon UK marketplace dispute?
Damages in a marketplace dispute is a broad term covering several distinct categories of loss, and identifying which category applies is the first task – because each one follows a different procedural track.
The most common categories an Amazon UK seller might pursue include: direct financial losses from an erroneous account deactivation (lost sales during the downtime window), inventory losses where Amazon is responsible for goods damaged, lost, or disposed of in an FBA fulfilment centre, wrongful withholding of disbursements beyond the reserve period permitted by the Business Solutions Agreement (BSA), and losses flowing from a rights-owner complaint that turns out to be unfounded or retracted after the fact.
A "damages claim" is not simply a complaint to Seller Central. It is an assertion of a legal or contractual entitlement – usually grounded in the BSA that every Amazon seller signs, or in applicable UK consumer and commercial law where Amazon's own conduct is the cause. The distinction matters because the remedy mechanism differs: BSA-based claims run through the dispute-resolution process in the agreement; statutory claims may run through English courts or, in some cases, arbitration under the agreement's own terms.
In matters we handle, sellers often arrive believing their entire loss is one undifferentiated claim. Separating the FBA reimbursement element from the lost-revenue element from any payment-hold element, and pricing each category with evidence, typically triples the credibility of the demand before a single formal step is taken.
Step 1 – Build your damages log before anything else
The quality of a damages claim is almost entirely determined by the documentation assembled in the first 48 to 72 hours after a problem is identified. Waiting until an appeal fails to start collecting evidence means working backward through Seller Central records that may become harder to access.
The core log should contain, at minimum:
- A timestamped record of every deactivation notice, policy warning, or support interaction – downloaded as PDFs from Seller Central, not screenshot jpegs that can be challenged on legibility.
- A line-by-line inventory reconciliation for FBA: what was sent in, what was sold, what is showing as on-hand, and what is showing as discrepant. Amazon's Inventory Ledger report in Seller Central is the primary source.
- A revenue baseline. For a lost-sales claim, you need to show what the account was earning before the event and what it earned (or failed to earn) after. Export order data for a comparable prior period – typically the same calendar quarter in the preceding year, adjusted for any obvious seasonal variance.
- All account reserve and disbursement records: the transaction ledger, the reserve policy notification if one was issued, and every payment statement.
- Any rights-owner complaint details, including the complaint ID and any communications about retraction or counter-notice.
What goes wrong here is predictable: sellers assemble a broad narrative and attach screenshots without any organizing logic. A damages claim is not a story – it is an arithmetic table with supporting citations. A claim that says "we lost approximately £40,000 in revenue" without a month-by-month table cross-referenced to order reports will not survive informal review, let alone a formal proceeding.
Step 2 – Identify the legal and contractual basis for the claim
Once the loss is documented, the next step is identifying which provision of the BSA, Amazon's FBA Service Terms, or applicable law creates the entitlement to recover it. This is where sellers handling matters alone most often make a critical error: they frame the claim as a policy complaint rather than a contractual one.
Amazon's BSA and its supplementary service terms impose obligations on Amazon as well as on sellers. FBA inventory that is lost or damaged while in Amazon's possession may engage Amazon's own published reimbursement policy – but that policy operates within the contractual framework of the FBA Service Terms, which means the ceiling on what is reimbursable, and the procedure for claiming it, is set by contract. Knowing whether your specific loss falls within the published reimbursement schedule or whether it requires a separate contractual claim changes the route entirely.
For lost-revenue claims tied to a deactivation, the analysis is harder. Amazon's standard position is that it may deactivate accounts for policy violations without liability for consequential losses. Whether that position holds under English contract law – particularly where the deactivation was the result of an error, an erroneous complaint, or an automated enforcement decision that was later reversed – is a substantive legal question. It turns on the specific facts and the BSA version in effect at the time of the deactivation.
Our practice routinely begins with a review of the deactivation notice language alongside the applicable BSA version, because the argument that is available to a seller depends entirely on which version governs the account and what it actually says about Amazon's liability for enforcement errors.
For detailed background on the full scope of pre-arbitration options, the complete guide to arbitration and pre-arb demand for sellers explains how the BSA's dispute-resolution mechanics interact with substantive damages claims.
Step 3 – Send a Notice of Dispute
The Notice of Dispute is the formal trigger for the BSA's dispute-resolution process, and it is a required step before arbitration is available under most BSA versions. Skipping it – or sending an informal "formal complaint" that does not actually comply with the notice requirements – can reset the clock and give Amazon grounds to argue that the pre-arbitration requirements were not satisfied.
A properly drafted Notice of Dispute typically identifies: the seller (account name and merchant token); the specific losses claimed and their documentary basis; the BSA or service-term provisions engaged; the remedy sought (a specific sum, a specific action, or both); and the deadline for Amazon's response before the next escalation step is taken.
The informal resolution period that follows a Notice of Dispute is a genuine negotiation window, not a formality. In matters we handle, a well-evidenced Notice of Dispute with a specific, credible demand often produces a response from Amazon's legal or seller trust team that is more substantive than anything that came through Seller Central support. The reason is structural: support teams operate within policy guardrails; a formal legal notice routes differently inside Amazon.
The CTA below the next section is a practical note about where to get a first read on your claim before this step.
The steps above describe the standard path. Your situation turns on the exact wording of the notice, the account history, and timing – which is what we review first. If you have reached the point of a flat rejection from support and want a clear read on what a Notice of Dispute might achieve for your specific loss, email info@tutamenlaw.com.
Step 4 – Evaluate the pre-arbitration demand option
If the informal resolution period following the Notice of Dispute does not produce an acceptable outcome, the next decision point is whether to file for arbitration or to send a pre-arbitration demand – a structured legal letter that sets out the claim in full, demands a specific remedy within a defined window, and makes clear that arbitration (or litigation) follows if the demand is not met.
The pre-arbitration demand is not the same as a strongly-worded support ticket. It is prepared as a legal document, typically on firm letterhead, and it communicates that the seller is represented and the matter has moved beyond informal channels. In a significant share of the matters we handle at this stage, a well-constructed pre-arbitration demand produces a resolution without the need to file.
Why does this work? Amazon's economics are not uniform. The cost of defending an arbitration – in AAA filing fees, in legal preparation, in internal resource – varies by claim size and claim type. For a mid-range inventory reimbursement claim or a payment-hold matter where Amazon's position is not airtight, a credible pre-arbitration demand changes the internal calculus. It signals that the cost of not settling is real.
The decision to send a pre-arbitration demand rather than proceed directly to filing is a trade-off between speed and leverage. A demand that is sent and ignored is not a wasted step – it becomes evidence of good-faith engagement when you do file. But if Amazon's position is clearly entrenched and the claim is large, some matters benefit from moving directly to filing after the notice period expires rather than giving additional time for Amazon to prepare its defence.
The piece on demand letters for marketplace sellers facing brand damage illustrates how this step functions in practice when the underlying claim involves reputational or brand-level harm alongside the financial loss.
Step 5 – Decide whether to file for arbitration
Filing for arbitration under the BSA's dispute-resolution terms is a significant escalation, and it is the right tool in some matters – but not all. The decision to file turns on four practical factors: claim size, claim type, evidentiary strength, and the costs of the proceeding relative to the likely recovery.
On claim size: the American Arbitration Association (AAA) administers a substantial portion of BSA-referenced arbitrations. Its consumer and commercial arbitration rules carry filing fees and administrative costs that are only proportionate above a certain claim threshold. Below that threshold, a pre-arbitration demand or – in some cases – a UK small claims track or the UK courts may be a better route. The path depends on the BSA version that applies to the account, which we check first.
On evidentiary strength: the arbitration process requires the seller to prove the claim, not merely assert it. The damages log built in Step 1 is the foundation. A claim with a clean inventory reconciliation and a clear before-and-after revenue comparison is materially stronger than a claim built on estimates. Weak documentation going into arbitration is expensive to remedy.
On costs: sellers frequently assume that pursuing marketplace arbitration means a costly, multi-year process. That is a myth worth examining carefully. Many marketplace arbitration matters resolve at the demand stage, at the preliminary conference stage, or in mediation before a hearing is ever held. The timeline and cost depend on the specific facts, the claim size, and whether Amazon engages constructively. A matter that proceeds to a full evidentiary hearing is the exception, not the rule.
A home-goods FBA seller on Amazon UK (winter 2025) came to us after a series of unresolved FBA inventory discrepancies spanning several fulfilment cycles. We mapped the full inventory ledger, identified the specific periods where Amazon's records and the seller's inbound shipment data diverged, and drafted a pre-arbitration demand that quantified the shortfall across each SKU. The matter resolved during the informal resolution period that followed, without the need to file. The seller had previously spent several months in Seller Central support channels without any quantified response.
For sellers who have already had a first attempt at resolution rejected, a second read on the file is often where the specific reason for the failure – and what is still recoverable – becomes clear. If a Notice of Dispute or earlier filing has already come back without resolution, contact info@tutamenlaw.com for a review of what the next step looks like.
Where does this process go wrong?
What are the failure points that end a recoverable claim before it reaches the right forum? In matters we work on across the arbitration and pre-arb practice, the same patterns appear repeatedly.
Delay in documentation. Seller Central data is not archived indefinitely. Order-level data, inventory ledger records, and account health history have access windows. Sellers who wait until a dispute is firmly joined to collect this data sometimes find that the most granular records are no longer exportable. The 48-to-72-hour assembly window in Step 1 is not arbitrary – it reflects what we have seen happen to evidence.
Framing the claim as a policy complaint. Amazon's support teams are trained to respond to policy complaints. A message that says "you deactivated me wrongly and I want compensation" reads as a policy complaint and gets a policy response. A Notice of Dispute that identifies a specific BSA provision, cites a specific loss with a specific sum, and invokes the dispute-resolution mechanism routes differently. The framing determines where it lands.
Making the first demand too low. Sellers understandably want to appear reasonable. The result is sometimes an initial demand that is lower than the documented loss, which sets an anchor that is difficult to move upward later in the process. The first formal demand should reflect the full, well-evidenced loss. Negotiation can move it down; it rarely moves it up.
Treating a rejection as final. A rejection from Seller Central is not a legal determination. It is an operational response. A Notice of Dispute, a pre-arbitration demand, and a properly filed arbitration claim are separate from anything that happened in the support queue. Sellers who treat the support rejection as the end of the road foreclose options that are still open.
An apparel brand owner selling on Amazon UK (spring 2026) came to us after a rights-owner complaint had resulted in listing suspensions and, consequently, a period of lost sales across multiple parent ASINs. The complaint was later retracted, but Amazon had not reinstated the listings automatically, and the revenue loss during the suspension window remained unaddressed. We separated the lost-revenue claim from the FBA reimbursement components, documented the sales baseline against the suspension window, and sent a Notice of Dispute that identified both the contractual basis and the specific loss figure. The matter advanced to a pre-arbitration demand and resolved at that stage.
To understand how attorney fee recovery fits into a marketplace arbitration proceeding – and when it changes the economics of filing – the guide on how one seller resolved attorney fees in marketplace arbitration covers the relevant considerations in detail.
Decision matrix: which path applies to your situation?
If the notice or the underlying problem involves FBA inventory discrepancies – goods lost, damaged, or disposed of while in Amazon's possession – the primary route is the FBA reimbursement claim process, followed by a Notice of Dispute if the automated reimbursement result is incorrect or incomplete. The timeline from claim submission to resolution varies from a matter of weeks for straightforward cases to several months where the discrepancy spans multiple shipments or fulfilment centres.
If the notice cites a policy violation that has since been reversed, or if an erroneous deactivation caused a documented revenue loss, the route is a Notice of Dispute grounded in the BSA's terms, with a pre-arbitration demand following if the informal period does not resolve it. This path tends to require stronger legal framing – and a clear theory of why Amazon bears liability for the loss – before it produces movement.
If the loss flows from an intellectual property complaint that has been retracted or challenged, the IP and damages questions run in parallel: clearing the listing is Step 1, and the damages claim follows once the listing is restored and the sales gap can be measured. Filing a damages claim before the IP issue is resolved tends to dilute both tracks.
If the claim is below the threshold where AAA arbitration is cost-proportionate and the BSA version in effect is relevant to your account, English small claims or a county court track may be the more efficient route. This is a fact-specific analysis that depends on the BSA version, the claim amount, and the seller's jurisdiction within the UK. We check the applicable BSA version at the outset of any engagement, because it determines which options are actually open.
Related areas
- Arbitration & Pre-Arb Demand – full overview of the dispute-resolution process for marketplace sellers
- Account Reinstatement – when an account deactivation is the source of the underlying loss
Frequently asked questions
How long does resolving damages in a marketplace dispute usually take on Amazon UK?
The timeline depends on which stage the matter reaches. A well-documented FBA reimbursement claim handled entirely within Amazon's own process can resolve in a matter of weeks. A claim that requires a Notice of Dispute and informal resolution period typically takes several weeks to a few months, depending on how Amazon engages. A matter that proceeds to a formal pre-arbitration demand takes additional time for the demand window to run. Full arbitration, where it is needed, is the longest path and can take many months to over a year from filing to a decision. The majority of claims in our practice that are well-documented and correctly framed resolve before a formal arbitration hearing is ever scheduled.
What are the main risks if I handle damages in a marketplace dispute alone?
The main risks are procedural and evidentiary. Sellers handling disputes alone frequently miss the documentation window, frame the claim as a policy complaint rather than a contractual one, and make initial demands that anchor the negotiation too low. A formal notice that does not comply with the BSA's requirements can reset the timeline or give Amazon grounds to argue pre-arbitration steps were not satisfied. The dispute-resolution provisions in the BSA are drafted by Amazon's legal team; a seller engaging with those provisions without legal review is working at a structural disadvantage, particularly on claims above a modest threshold.
Do I need a lawyer for damages in a marketplace dispute?
For very small FBA reimbursement claims that fall squarely within Amazon's published reimbursement policy, a lawyer is not always necessary. For any claim that involves a Notice of Dispute, a pre-arbitration demand, or arbitration filing – and for any lost-revenue claim arising from an erroneous deactivation – legal representation materially changes the outcome in many cases. A lawyer who handles marketplace disputes regularly knows which BSA provisions apply to a specific account, which documentation is most persuasive at each stage, and when the economics of arbitration favour settling versus pressing forward. Fixed-fee engagement for the pre-arb demand stage means the cost of getting advice is predictable and often proportionate to the claim.
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 arbitration and pre-arb practice covers damages claims, FBA reimbursement disputes, and wrongful payment-hold matters across Amazon's UK and international surfaces. To discuss your situation, email info@tutamenlaw.com.
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.
Page authored by James Whitlock, Reinstatement & Funds Analyst, Tutamen.
Talk to a partner
Tell us what the marketplace sent you — we reply within one business day.