FBA reimbursement denial: what to do, step by step

TL;DRAn FBA reimbursement denial means Amazon has reviewed a claim for lost, damaged, or disposed inventory and rejected it – leaving the seller without the credit they are owed for goods that are no longer sellable or recoverable. The denial is not necessarily final. A structured, evidence-led response can reopen the claim, but the window is limited and a poorly framed second attempt often closes the door permanently. The steps below walk through what the process actually looks like and where sellers most often lose ground they did not need to lose.

The money is held while inventory and ad bills keep coming due. That is the reality of an FBA reimbursement denial: it is not an abstract accounting dispute. It is a specific balance missing from a disbursement cycle while the rest of the business keeps running. And the longer it sits unresolved, the harder it becomes to reconstruct the evidence trail Amazon's review team actually needs to reverse course.

This guide covers the exact step sequence – from reading the denial notice correctly to deciding whether to escalate – and flags the specific points where sellers working alone most often derail a claim that had every reason to succeed.

What an FBA reimbursement denial actually is – and why it happens

A denial is Amazon's formal determination that a reimbursement claim does not meet the criteria it applies to a specific category of inventory loss or damage. It is not a blanket refusal to engage; it is a decision about a particular claim, made on the documentation submitted at the time. Understanding the difference matters, because it means the denial can often be revisited if the documentation changes.

Amazon's FBA reimbursement system covers several distinct scenarios: inventory lost in the fulfillment center, inventory damaged before or after shipment, items disposed of without authorization, and inbound shipment discrepancies. Each scenario has its own evidentiary requirements. A claim for inbound shipment discrepancies, for example, typically requires reconciliation data from the shipping carrier and the FBA inbound shipment record – not just the seller's own shipment log. When the documentation submitted does not match what Amazon's system expects for that category, the denial follows almost automatically.

In the matters we handle, the most common denial reasons fall into three groups. First, the claim is filed under the wrong category – a fulfillment-center loss claim filed as an inbound discrepancy claim, or vice versa. Second, the supporting documentation is incomplete or in the wrong format. Third, the claim has aged past a threshold Amazon uses internally, which reduces the reviewer's discretion even when the underlying loss is real.

A note on the marketplace field in your case: the MARKETPLACE entry here is Etsy. Etsy does not operate its own FBA-style fulfillment program. The reimbursement concepts in this guide apply to Amazon's FBA service, which is the industry reference point for this type of claim. If your Etsy business ships through a third-party warehouse or uses Amazon Multi-Channel Fulfillment, the principles of claim documentation and denial response overlap substantially, but the specific procedural path runs through whichever fulfillment platform was used. The steps below follow the Amazon FBA path – the most detailed and most litigated version of this process.

Step 1: Read the denial notice precisely before doing anything else

The denial notice tells you the specific reason Amazon rejected the claim, and that reason dictates everything that follows. Reading it imprecisely – or treating it as a generic rejection – is the first and most damaging mistake sellers make.

Amazon's denial communications typically cite one of several categories: insufficient documentation, claim already resolved, ineligible ASIN or condition, outside the claim window, or no discrepancy found. Each of these points to a different response path. "No discrepancy found" means Amazon's system does not show the units as missing in its records – which requires a reconciliation response, not a documentation response. Submitting more receipts in reply to a "no discrepancy found" denial accomplishes nothing and consumes the one or two reopening attempts Amazon typically allows.

Pull the original shipment records alongside the denial notice. Compare the units shipped, the units received as logged in Seller Central, and the units Amazon's system shows as current inventory or disposed. The gap between those three numbers is what the claim is actually about. If Amazon says there is no gap and your records show there is, the response is a reconciliation document – a structured comparison of carrier data, delivery confirmation, and Amazon's receive log. If Amazon says the documentation is insufficient and you submitted the wrong document type, the response is the correct document.

In our practice, we regularly see sellers respond to a "no discrepancy found" denial with a lengthy letter explaining the value of the missing inventory. That letter does not move the claim. What moves it is a table showing, line by line, that the units Amazon says it received do not match the units the carrier shows as delivered and signed for.

Step 2: Reconstruct the complete evidence file

Before filing any response, assemble every document that touches the specific shipment or loss event. Responding piece by piece – submitting one document, waiting, then submitting another – fragments the record and signals to the review team that the claim is not ready for a decision.

The evidence file for a typical FBA loss or damage claim should contain:

• The original FBA shipment ID and inbound shipment report from Seller Central
• The carrier's proof of delivery with a unit count, not just a tracking event
• The box-level content list uploaded at the time of shipment (not reconstructed after the fact)
• Amazon's receive confirmation showing the units logged as received
• The inventory event detail report covering the period from receipt to the date of the claimed loss
• Any removal order records or disposal notifications if the claim involves disposed inventory

The box-level content list is frequently missing because many sellers upload it as a standard upload rather than confirming it was logged against the specific shipment ID. Amazon's system can show the shipment as received without showing the box-level breakdown. That gap is exploitable – it allows Amazon's automated review to mark a discrepancy claim as unverifiable. Confirming the box-level content list is attached to the right shipment ID before submitting is a step that eliminates a significant class of denials.

For damage claims – especially for items damaged after receipt, which Amazon calls FC damage (fulfillment-center damage) – the evidence set expands to include customer return records, condition-upon-return data, and, where available, photos from the return processing center. FC damage reimbursements are calculated differently from inbound discrepancy reimbursements: Amazon uses its own valuation formula tied to the item's sell price, not the seller's cost. Understanding which type of damage triggered the claim is essential before building the response, because the evidence required is different for each.

Step 3: Frame the response to match Amazon's review criteria – not your own narrative

This is where a large share of meritorious claims fail. The seller frames the response as an explanation of what happened from their perspective. Amazon's review team is working from a checklist of what a valid claim looks like according to Amazon's own policy. Those two framings are often misaligned.

A well-framed response for an FBA reimbursement denial follows a specific structure. It begins with the shipment or event ID, states the exact discrepancy in units and the dollar amount calculated per Amazon's valuation method, identifies the category of claim being made, and then presents the supporting documents in the order that matches Amazon's evidentiary checklist for that category. It does not include background on the seller's business, the seller's relationship with Amazon, or the impact of the denial on the seller's cash flow. None of that is part of the reviewer's criteria.

What sellers working alone often submit instead is a narrative email explaining the situation in full detail. That email may be factually accurate. It will often be denied anyway, because the reviewer is not evaluating the seller's account history – they are checking whether the documents submitted match the required format and confirm the claimed discrepancy. The response has to speak that language.

Consider the path that worked for a home-goods seller on Amazon US (spring 2026): they came to us after two consecutive denials on an inbound discrepancy claim covering a full pallet of fragile goods. The original filings had been detailed letters explaining how the shipment was packed and why they were confident the units had been delivered. We rebuilt the response as a structured reconciliation document – carrier manifest against Amazon receive log, unit by unit – and filed it under the correct claim category. The claim was reviewed and the balance was returned to the seller's disbursement account. No new facts changed. The framing changed.

Step 4: File the response through the correct channel, in the correct format

Amazon's FBA reimbursement process has specific filing channels, and using the wrong one – submitting a reimbursement dispute through a general Seller Support ticket rather than the FBA reimbursement case log, for example – routes the matter to a team that lacks the authority or the tools to review the underlying inventory data. The response disappears into a general queue and comes back as a non-answer.

The correct starting point for a reimbursement dispute is the FBA reimbursement case opened directly against the specific shipment or inventory event in Seller Central. If that case has already been denied and closed, the escalation path goes to a dedicated FBA reimbursement escalation contact – not general Seller Support. Many sellers do not know this path exists, and Amazon does not prominently advertise it. In the matters we handle, identifying the correct escalation channel often makes the difference between a claim that sits unanswered and one that reaches a reviewer with decision-making authority.

Format matters as much as channel. Amazon's review systems work best with structured attachments – spreadsheets or tables, PDFs with clear labeling – rather than inline text or scanned documents with poor resolution. If a carrier delivers a proof of delivery as a photo scan, that scan should be cropped, labeled with the shipment ID and date, and submitted as a labeled PDF. Unlabeled or bulk-attached documents require the reviewer to spend time identifying what they are looking at. That time is rarely available, and the claim gets marked incomplete instead.

Our practice maps every held balance and reserve before a filing goes in, and we press each disbursement and reimbursement claim through the specific path that matches its category. That mapping step – which sellers often skip because it is tedious – is what prevents a strong evidence file from being filed through the wrong door. For a broader view of how frozen funds and recovery work across a full account hold, the guide to frozen funds recovery for sellers covers the full picture.

Step 5: Track and respond to follow-up requests within the stated window

When Amazon's review team reopens a denied claim, they frequently issue a follow-up request for additional documentation. That request comes with a response window. Missing the window – even by a day or two – typically closes the case without a decision and requires starting the escalation path from the beginning, if it can be restarted at all.

The follow-up request often asks for something very specific: the carrier's delivery confirmation for a particular box, or the weight and dimension report for a particular ASIN. Responding with general documentation that does not match the specific request fails the same way the original filing failed. The request should be read as precisely as the original denial notice.

If the follow-up request asks for something that does not exist – a delivery confirmation that the carrier never generated, or a weight scan that Amazon's own system conducted but did not record accurately – the response is not "we cannot provide this document." The response is a written explanation of why the document cannot exist, supported by evidence that the underlying fact it was meant to confirm can be established by other means. That is a more complex response to draft, but it is the correct response. A simple statement that the document is unavailable gets treated as an incomplete filing.

Related to this is the issue of FBA fee overcharges, which sometimes arise alongside reimbursement disputes when incorrect weight or dimension data affects the fee basis for an ASIN. If your situation involves both a reimbursement denial and a fee discrepancy, the guide to resolving an FBA fee overcharge refund covers the parallel process. The two paths can run concurrently, but they must be filed separately and tracked independently.

Where this goes wrong: the five points sellers most often lose ground

In the matters we handle, the same failure points appear repeatedly. Most of them are procedural, not factual – the underlying loss or damage is real, the documentation exists, but the claim is lost on the path between the seller and the reviewer.

Filing too late. Amazon's reimbursement claim windows are time-bounded. A claim filed after the window closes is ineligible regardless of its merits. The window varies by claim type, and sellers who do not know the specific window for their category often discover the eligibility issue only after the denial comes back. If a reimbursement claim is on your radar, the time to file is immediately, not after a few weeks of internal review.

Conflating claim categories. A seller who lost units in an inbound shipment and also had units disposed of without notice files one combined claim. Amazon's system evaluates each category separately. A combined filing that mixes categories either gets processed under only one of them or gets rejected in full as non-conforming. File each category as a separate case.

Responding to the denial instead of to the criteria. The denial notice is a signal about what was missing. It is not an invitation to argue about why the loss was real. The response addresses what was missing – full stop.

Using Seller Support as an escalation tool. General Seller Support cannot override an FBA reimbursement decision. It does not have access to the systems involved. A Seller Support agent may tell you to refile, which creates another paper trail and another denial. The escalation path for reimbursement disputes bypasses general Seller Support entirely.

Assuming the first denial is final. It is not – unless the claim window has expired or the correct escalation path has been exhausted. Many valid claims are reinstated on a second, properly framed filing. The myth that held funds are gone for good once a denial comes back is exactly that – a myth. The practical question is whether the evidence and the framing are right, and whether the window is still open.

Weight and dimension data is a related trigger for FBA fee disputes that often surfaces during the reimbursement review process. If incorrect product dimensions are part of your account history, the analysis of how weight and dimension fee overcharges happen and how sellers respond is a practical companion read.

The seller's decision points: when to escalate, when to accept, when to call a lawyer

Not every FBA reimbursement denial justifies the same level of response. The correct path depends on what is at stake, what stage the denial is at, and whether the evidence necessary to succeed exists.

If the denied claim involves a small number of units and the evidence file is incomplete or unrecoverable – because the carrier documentation no longer exists, for example – the realistic assessment is that escalation may not be cost-effective. Filing a poorly evidenced escalation also consumes the escalation attempts available for that claim, which forecloses the path for better-evidenced future claims on the same account.

If the denial involves a significant balance – what might constitute a mid-four-figure or larger recovery – and the evidence file is substantially complete, escalation through the correct channel with a properly framed response is almost always worth the effort. In our experience, the proportion of properly filed escalations that result in at least a partial recovery is meaningfully higher than the proportion of initial self-filed claims that succeed. The difference is the framing and the channel, not the merits.

If the claim has been denied twice and the evidence is strong, the question becomes whether there is a legal avenue beyond Amazon's internal process. Amazon's dispute-resolution path for claims of this nature is governed by the Business Solutions Agreement (BSA). The path available under the BSA depends on the version that applies to the account – which we check first before advising on whether arbitration or a pre-arbitration demand makes sense. The path varies, and assuming one version of the BSA applies when another does can lead to a filing that is procedurally invalid from the start.

The first CTA window is here: the steps above describe the standard sequence. Your situation turns on the exact wording of the denial notice, the state of the evidence file, and the age of the claim – which is what we review first when a seller brings a denied reimbursement matter to us.

To have a practitioner review your denial notice and evidence file, email info@tutamenlaw.com. Fixed fee, quoted after a short review.

Micro-case: a winter 2025 inbound discrepancy recovery on Amazon UK

An electronics accessories seller on Amazon UK came to us after a denial on a mid-five-figure inbound discrepancy claim. The shipment had arrived during a period of high fulfillment center volume, and Amazon's receive log showed significantly fewer units than the carrier's delivery manifest. The seller had filed the original claim with their own spreadsheet of what was shipped. Amazon denied it twice, citing insufficient documentation.

We reviewed the denial notices precisely. The second denial was categorized as "no discrepancy found" – meaning Amazon's system, at that point, was not showing the gap the seller's records reflected. That was a different problem than insufficient documentation. It required a reconciliation response: a structured comparison of the carrier's unit-level delivery data against Amazon's own receive confirmation, submitted as a labeled table under the inbound discrepancy case, not as a general appeal.

We reconstructed the evidence file from the carrier's archive, obtained the unit-level delivery confirmation (which the seller had not previously requested in that format), cross-referenced it against the FBA shipment receive report, and filed a formatted reconciliation document through the FBA reimbursement escalation channel. The claim was reopened, reviewed, and a substantial portion of the claimed balance was credited to the seller's disbursement account. The seller's original evidence had been accurate. The response format had not matched what Amazon's review system required.

Related areas

• Frozen Funds & Recovery – full-account hold, disbursement disputes, reserve policy challenges
• Amazon Account Reinstatement – deactivation, Plan of Action drafting, Section 3 response

If a first response or escalation has already been denied, a second read of the notice often reveals the specific reason it failed and whether a corrected filing is still viable. Email info@tutamenlaw.com with the denial notice and a summary of what was filed.

Frequently asked questions

How long does resolving an FBA reimbursement denial usually take on Etsy?

The timeline varies by claim category, the completeness of the evidence file, and whether the correct escalation channel is used on the first response. A well-evidenced, correctly filed reimbursement dispute typically reaches a decision within several weeks of the escalation filing. Cases that require multiple rounds of documentation requests or that escalate to a BSA dispute path take longer – often several months. Filing promptly and completely is the most reliable way to keep the timeline short. There is no guaranteed outcome or timeline; the realistic range depends on the specifics of each claim.

What are the main risks if I handle an FBA reimbursement denial alone?

The primary risk is consuming the available filing or escalation attempts with a response that is framed for the wrong denial reason or filed through the wrong channel. Amazon's reimbursement process is not forgiving of procedural missteps – a second denial on a badly structured escalation can effectively close the claim window even when the underlying loss is real and documented. A secondary risk is missing the response window on a follow-up request, which closes the active case. Sellers working alone also frequently conflate claim categories, which produces a combined filing that gets evaluated under only one of the applicable criteria.

Do I need a lawyer for an FBA reimbursement denial?

Not in every case. A single-unit denial involving a small amount and clear documentation is something many sellers can handle with careful reading of the denial notice and the right supporting documents. The cases where legal representation adds the most value are: denials involving significant balances where an evidence file needs reconstruction; situations where two or more consecutive denials have been issued; claims that may require escalation under the BSA's dispute-resolution path; and accounts where a reimbursement denial is part of a broader account health or disbursement-hold problem. Attorney-led representation is confidential and works on fixed fees quoted up front – so the cost-benefit assessment is straightforward before any work begins.

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 reimbursement and frozen-funds practice is attorney-led, and every engagement is treated as confidential from the first inquiry. 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.