Most Amazon sellers know they can file for FBA reimbursements when inventory goes missing or gets damaged. What they don't know is which reimbursement opportunities are sitting in their account right now, invisible in standard Seller Central reports. This checklist organizes every recoverable FBA issue by how difficult it is to find—so you can run an efficient monthly audit that catches both obvious problems and hidden money.
Why standard Seller Central reports miss reimbursable issues
Amazon processes millions of FBA transactions daily. Their automated reconciliation catches some discrepancies—but not all. Three categories of issues slip through:
- Timing gaps: Your inventory arrives at a fulfillment center, but the receiving log doesn't update for 72 hours. If a unit goes missing during that window, there's no record to trigger an automatic reimbursement.
- Multi-leg transactions: Customer returns get marked "sellable" but never re-enter available inventory. Amazon's system logged the return but didn't complete the inventory adjustment.
- Cross-facility transfers: Units move between fulfillment centers. The sending facility logs them out, the receiving facility never logs them in. Both systems show internally consistent records, so no discrepancy flag appears.
Standard reports like "Inventory Adjustments" only show what Amazon's system already knows about. Your job during an audit is finding discrepancies between what should exist and what actually exists—problems Amazon's automated reconciliation hasn't detected yet.
How to use this checklist efficiently
This audit framework has three tiers based on how hard each issue type is to discover:
Tier 1 (Visible issues): Problems you can spot in 15-20 minutes using basic Seller Central reports. Check these monthly.
Tier 2 (Semi-hidden issues): Require cross-referencing multiple reports or downloading data exports. Budget 30-45 minutes monthly if you have 50+ SKUs, or quarterly if you're below that threshold.
Tier 3 (Hidden reconciliation issues): Require manual data analysis or are only detectable through automated software. Most individual sellers skip these entirely or use third-party audit tools. Check quarterly if doing manually.
Start with Tier 1 every month. Add Tier 2 once you've recovered your first few claims and understand the process. Consider Tier 3 only if you have significant volume (500+ monthly orders) or technical skill with spreadsheet reconciliation.
Tier 1: Visible issues (check monthly, 15-20 minutes)
Customer return reimbursements
Amazon's policy: if a customer returns an item that FBA marks as "unsellable," and the item was returned outside the 30-day return window, Amazon owes you a reimbursement at the item's selling price minus your referral fee.
Where to check: Seller Central → Reports → Fulfillment → Customer Returns. Download the last 30 days.
What to look for: Filter for "Defective" or "CustomerDamaged" in the return reason column. Cross-check the order date against the return date. If more than 30 days elapsed, Amazon should automatically reimburse—but they don't always.
How to verify: Search your Reimbursements report (Reports → Payments → All Statements → Transaction View, filter by "Reimbursement") for matching order IDs. If a return shows defective/damaged and outside 30 days, but no corresponding reimbursement exists, file a claim.
Time window: You have 180 days from the return completion date to file. Prioritize returns from 150+ days ago first.
Warehouse damaged inventory
Amazon damages units during receiving, stowing, or picking. When this happens, they're supposed to automatically mark the unit as "warehouse damaged" and reimburse you. Sometimes the damage gets logged, but the reimbursement doesn't process.
Where to check: Seller Central → Reports → Fulfillment → Inventory Adjustments. Download 30-90 days depending on your volume.
What to look for: Filter the "Reason" column for "WAREHOUSE_DAMAGE" or "DAMAGE." Each line represents a unit Amazon acknowledged damaging.
How to verify: Note the damaged unit's FNSKU and date. Check your Reimbursements report for a matching entry with reason code "WAREHOUSE_DAMAGE" and the same FNSKU. If the damage appears in Inventory Adjustments but not in Reimbursements, file immediately.
Common miss: Multi-unit damage. If Amazon damages a case pack of 6 units, you should see 6 individual reimbursements (or one reimbursement line for quantity 6). Verify the quantities match.
Lost inbound shipment units
You send 100 units in a shipment. Amazon receives 97. If the discrepancy stays unresolved for 30 days after the shipment's "Checked-In" date, Amazon owes you reimbursement for the 3 missing units.
Where to check: Seller Central → Inventory → Manage FBA Shipments. Look at shipments from 30-180 days ago with status "Closed" or "Checked-In."
What to look for: Click into each shipment. Compare "Shipped" quantity to "Received" quantity for each SKU. Note any discrepancies.
How to verify: Check whether Amazon auto-reimbursed by searching your Reimbursements report for the shipment ID. If 30+ days have passed since closure and no reimbursement exists, file a claim using the shipment ID and specific FNSKU.
Policy note: Amazon investigates for 30 days after shipment closure. Don't file before that window ends—your claim will be rejected as "under investigation."
Tier 2: Semi-hidden issues (check monthly or quarterly, 30-45 minutes)
Removal order discrepancies
You request removal of 50 units. Amazon's removal report confirms they disposed of or returned only 47 units. Those 3 units vanished between your removal request and the fulfillment of that request—Amazon owes reimbursement.
Where to check: Seller Central → Reports → Fulfillment → Removal Order Detail. Download orders from the last 90 days.
What to look for: For each removal order, compare "Requested Quantity" to "Cancelled Quantity" + "Disposed Quantity" + "Returned Quantity." If the math doesn't add up, units are missing.
How to verify: Search Reimbursements for the removal order ID. If no reimbursement exists for the quantity gap, file a claim with the removal order ID and specify "removal fulfillment discrepancy."
Why this is semi-hidden: Amazon's removal report doesn't highlight the discrepancy. You have to manually calculate requested vs. fulfilled quantities.
Customer return not received by FBA
Amazon's system shows a customer initiated a return and received a prepaid return label. But the package never arrived back at the fulfillment center, or it arrived and was never scanned in. After 45 days, if the unit didn't re-enter your inventory, Amazon should reimburse you.
Where to check: Cross-reference two reports. First, pull Customer Returns (Reports → Fulfillment → Customer Returns) and filter for return status "Return initiated" or "Return label generated." Then pull Inventory Ledger (Reports → Fulfillment → Inventory Ledger) to see if those units ever came back into inventory.
What to look for: Returns older than 45 days where the Inventory Ledger shows no corresponding "Customer Return" transaction adding the unit back to available stock.
How to verify: Check Reimbursements for the order ID. If more than 45 days have passed since the return was initiated, and the unit never re-entered available inventory, and no reimbursement exists, file a claim with the order ID and note "return not received after 45 days."
Why this matters: This scenario is common. Customers print return labels and never ship, or carriers lose the package. Amazon's system assumes the return completed because a label was generated, but no unit actually came back.
Inventory found but never credited
Occasionally Amazon locates "lost" inventory during a fulfillment center audit and adds it back to your available stock weeks or months after it went missing. If you already filed a reimbursement claim for those units and got paid, Amazon will deduct the reimbursement when they re-add the inventory. That's correct. But sometimes Amazon re-adds units you never got reimbursed for—giving you back inventory that was missing but not compensating you for the time it was unavailable.
Where to check: Inventory Ledger → filter "Event Type" for "Found." Download 90 days of data.
What to look for: Each "Found" entry represents inventory Amazon thought was lost but later located. Note the FNSKU and date of the original disappearance (you may need to cross-reference Inventory Adjustments to find when it first went missing).
How to verify: Check whether you ever received a reimbursement for that FNSKU during the time it was missing. If the unit was out of stock for 30+ days, you're entitled to either compensation for lost sales opportunity or a reimbursement for that period.
Realistic note: Amazon rarely approves "lost sales opportunity" claims unless the item was consistently selling and went out of stock due to their error. This check is more about ensuring you didn't get shortchanged on units that stayed missing long-term before being found.
Multi-channel fulfillment (MCF) lost or damaged units
If you use FBA to fulfill orders from other sales channels (Shopify, eBay, your own website), those MCF orders are also eligible for reimbursement when FBA loses or damages the inventory. But MCF reimbursements don't automatically appear in the same reports as standard FBA reimbursements.
Where to check: Seller Central → Reports → Fulfillment → Multi-Channel Fulfillment Orders. Download 30-90 days.
What to look for: MCF orders with status "Unfulfillable" or "Cancelled" due to inventory issues. Also check for orders that show "Shipped" but your off-Amazon customer reported never receiving.
How to verify: For cancelled MCF orders, check whether Amazon returned the allocated inventory to your available stock. If not, and 30 days have passed, file a claim with the MCF order ID.
Why this is semi-hidden: MCF reimbursements follow the same policy as regular FBA, but they require separate tracking because MCF order data doesn't integrate into standard FBA reports.
Tier 3: Hidden reconciliation issues (quarterly check, 60+ minutes or use software)
Stranded inventory that disappeared
Units get marked "stranded" (not available for sale due to listing issues). While stranded, the units should remain in your FBA inventory count. Sometimes stranded units vanish entirely—Amazon's system shows zero available, zero inbound, zero unfulfillable. The units are just gone, and because they were stranded when they disappeared, no automated reimbursement triggers.
Where to check: Manually track your stranded inventory weekly using the "Fix Stranded Inventory" dashboard. Export a snapshot each week and compare unit counts over time.
What to look for: SKUs that showed stranded inventory in one snapshot and zero inventory (across all categories) in the next, without any removal orders or inventory adjustments in between.
How to verify: Pull Inventory Ledger for that FNSKU and confirm no disposition events (removal, disposal, customer order) explain the disappearance. File a claim noting "stranded inventory disappeared without inventory event."
Realistic note: This is rare but happens often enough that high-volume sellers see it quarterly. It's nearly impossible to catch without historical snapshots or automated tracking.
Fee reimbursements for incorrect charges
Amazon occasionally charges the wrong FBA fee—usually because they measured or weighed your product incorrectly, or applied the wrong product size tier. When this happens, you can request a fee reimbursement for the overcharged amount on every affected order.
Where to check: Reports → Payments → Date Range Reports → Transaction View. Download 90 days, filter for "FBA fees."
What to look for: Compare the fees charged per unit to Amazon's fee schedule for your product's size tier and weight. If the fee charged exceeds the official rate, something is miscategorized.
How to verify: Go to Inventory → Manage Inventory, find the ASIN, and check the "Product Dimensions" and "Item Package Dimensions" Amazon has on file. If these don't match your actual product specs, open a case to correct the dimensions. Once corrected, request reimbursement for all orders charged the wrong fee in the past 90 days.
Why this is Tier 3: Requires knowing the fee schedule and doing manual math per SKU. Most sellers only discover this when they notice one product has unusually low margins.
Reconciling inventory ledger against sales and receipts
This is the most comprehensive—and most time-intensive—audit method. You're manually verifying that every unit Amazon says left your inventory actually corresponds to a customer order, removal order, or documented adjustment.
Process:
- Download Inventory Ledger for 90 days
- Download All Orders report for the same period
- Download Inventory Adjustments and Removal Order Detail reports
- In a spreadsheet, sum all "in" transactions (receipts, customer returns, found inventory) and all "out" transactions (customer orders, removals, adjustments, damage)
- Compare the net change to your actual starting and ending inventory on the first and last day of the 90-day window
What to look for: Discrepancies where the math doesn't reconcile. For example, you started with 500 units, received 200, sold 350, removed 50. You should have 300 remaining. If Amazon shows 290, ten units are unaccounted for.
How to verify: Drill into the specific FNSKU with the discrepancy. Check whether any Inventory Ledger transactions are missing corresponding source documents (orders, adjustments, etc.). File a claim with a summary: "Reconciliation shows [X] units unaccounted for, FNSKU [Y], between [date] and [date]."
Realistic note: This level of audit is why most sellers with significant catalog size use reimbursement software. Doing this manually for 50+ SKUs monthly is prohibitively time-consuming. But if you have 5-10 SKUs and high unit velocity, quarterly manual reconciliation can catch systemic issues.
Setting up a monthly audit schedule
Here's a realistic monthly workflow for a seller with 20-50 SKUs:
Week 1 of each month:
- Run Tier 1 checks (15-20 minutes): customer returns, warehouse damage, inbound discrepancies
- File any obvious claims immediately
Week 2:
- Run Tier 2 checks (30-45 minutes): removal orders, unreceived customer returns, MCF if applicable
- Track stranded inventory snapshot for later comparison
End of quarter (every 3 months):
- Review stranded inventory changes (Tier 3)
- Spot-check fee accuracy on your top 5 SKUs by revenue
Every 6 months:
- Full ledger reconciliation for your top 3 SKUs (the ones with highest unit velocity and therefore highest discrepancy risk)
Adjust frequency based on your volume. Sellers with 500+ orders per month should run Tier 1 checks weekly. Sellers with under 100 orders per month can consolidate Tier 1 and Tier 2 into one monthly session.
When to file claims vs. when Amazon auto-reimburses
Amazon's system automatically processes some reimbursements without requiring you to file. Understanding the difference saves time:
Amazon usually auto-reimburses within 30-45 days for:
- Customer returns marked defective/damaged that Amazon receives back and destroys
- Warehouse damage documented during receiving or fulfillment
- Lost units during inbound shipment (after their 30-day investigation period)
You must manually file for:
- Customer returns that exceed 30-day return window
- Units that went missing during cross-facility transfers
- Removal order discrepancies
- Fee overcharges
- Any discrepancy Amazon's system didn't detect (which is most of Tier 2 and all of Tier 3)
The practical rule: if 45 days have passed since the issue date and no reimbursement appeared, file manually. Don't wait for Amazon to catch it on their own.
Critical policy constraints
Three Amazon policies directly affect what you can recover:
180-day filing window: You have 180 days from the date of the underlying issue (not the date you discovered it) to file a reimbursement claim. After that, Amazon will reject as "outside filing window." This makes old claims unrecoverable—prioritize recent issues first, then work backward.
One claim per issue: If you file a claim for a missing unit and Amazon denies it, you cannot refile the same claim unless you have new evidence. Make your first submission complete—include the shipment ID, order ID, FNSKU, date, and any supporting screenshots from Inventory Ledger or shipment tracking.
No reimbursement for customer-caused damage: If a customer returns an item damaged, and Amazon determines the damage was customer-caused (not in-transit or warehouse damage), you get the unit back as "unfulfillable" inventory but no reimbursement. You can remove it and attempt to resell it elsewhere, but Amazon won't pay you for customer abuse of the product.
What to do with approved reimbursements
Once a claim is approved, Amazon credits your account balance within 1-3 business days. The reimbursement appears in your Payments → All Statements under "Reimbursement" transaction type.
Two things to track:
Reimbursement amount: Amazon reimburses at the item's selling price minus referral fee. Verify this matches what you were actually selling the item for at the time of the loss. If the reimbursement is significantly lower, Amazon may have used an outdated or incorrect price. You can dispute by opening a case and providing proof of the selling price (screenshot of your offer at that time).
Tax treatment: Reimbursements are considered income for tax purposes. They're not returns or refunds—they're Amazon paying you for lost or damaged inventory. Make sure your bookkeeping system categorizes reimbursements as revenue, not as adjustments to cost of goods sold.
When manual auditing stops making sense
Two inflection points where most sellers stop manual auditing:
Above 100 SKUs: Tier 1 checks become impractical to do manually every month. The time spent downloading, filtering, and cross-referencing reports exceeds the value of recoverable claims for many catalog mixes.
Above 1,000 orders per month: Even if you have a narrow catalog, transaction volume makes manual reconciliation prohibitively slow. At this scale, small percentage discrepancies (0.5% of orders affected) translate to meaningful dollar amounts that justify software costs.
If you're below these thresholds, manual monthly audits using this checklist will catch the majority of recoverable issues. If you're above them, the choice is either (a) accept that you'll miss some reimbursements or (b) use third-party audit software that automates Tier 2 and Tier 3 checks.
