You sent 600 units to FBA. Amazon's receiving summary says 592, the sellable count says 587, and your 3PL swears it shipped 600. Nobody at Amazon flags the gap — the units simply disappear from your ledger, along with the money you paid for them. An FBA inventory reconciliation service exists for exactly this moment: finding every point where your counts and Amazon's diverge, then turning that evidence into recoveries before the claim window closes.
Here is how the mismatch happens, where it hides, and how a reconciliation service closes it.
- Count mismatches are normal; unrecovered mismatches are not. Amazon's scale guarantees some units get lost — the question is whether anyone claims them.
- Most discrepancies cluster in four places: inbound receiving, customer returns, removal and disposal events, and inter-warehouse transfers.
- Reimbursement eligibility expires, so reconciliation has to run on a schedule, not whenever someone remembers.
- A service adds three things: detection cadence, evidence quality, and claim follow-through that spreadsheets rarely sustain.
- Prevention counts too: carton content accuracy and clean shipment documentation shrink next quarter's gap.
- What Is an FBA Inventory Reconciliation Service?
- Why Your Counts Stop Matching Amazon's
- The Six Discrepancies That Show Up Most
- How a Reconciliation Service Works
- What You Can Check Yourself First
- Red Flags When Hiring a Reconciliation Service
- FAQ
What Is an FBA Inventory Reconciliation Service?
An FBA inventory reconciliation service is a managed process that compares the inventory you shipped, sold, returned, and removed against Amazon's own records, identifies every unit-level discrepancy, and files reimbursement claims for units Amazon cannot account for.
The service works from Seller Central's fulfillment reports: received-inventory records, inventory adjustments, reimbursement records, removal and disposal records, and customer returns data. It outputs two things — a claim pipeline for recoverable units, and a short list of process fixes that stop the same loss from repeating. Done properly, it is continuous rather than a one-off cleanup.
Why Your Counts Stop Matching Amazon's
Amazon's sellable count is the output of thousands of scans, moves, and status changes across multiple fulfillment centers. Every one of those steps is a chance for a unit to be recorded differently than reality — and occasionally to not be recorded at all.
Some discrepancies resolve themselves. A unit in transfer reappears a week later; a "lost" carton surfaces during a bin re-count. The dangerous ones are the discrepancies that age into permanence: units lost at receiving that were never reconciled, returns processed as unsellable without a reimbursement, disposals that produced no credit. Those do not self-heal, and Amazon will not volunteer the correction. Ongoing reimbursement management exists because the gap between "temporarily wrong" and "permanently gone" is only visible if someone keeps watching.
The Six Discrepancies That Show Up Most
| Discrepancy | Typical symptom | Where to verify | Path to recovery |
|---|---|---|---|
| Inbound shortage | Shipment shows "closed" with fewer units than shipped | Shipment receive summary vs. your 3PL manifest | Shipment reconciliation claim with proof of contents |
| Return never restocked | Refund issued, unit never reappeared as sellable or unsellable | Customer returns report vs. inventory adjustments | Reimbursement claim for the lost return unit |
| Return not reimbursed | Unit marked unsellable or disposed, no credit posted | Reimbursements report vs. removal/disposal records | Claim referencing the disposal or adjustment event |
| Disposal without reimbursement | Removal order closed, units destroyed, no credit | Removal order records vs. reimbursement records | Claim for units removed and not reimbursed |
| Transfer loss | Units stuck "in transit" between FCs, then vanishing | Inventory adjustment events at both FCs | Lost-in-transfer claim once the aging threshold passes |
| Unexplained sellable decline | Sellable count drops with no matching order or removal | Inventory adjustments with no visible cause | Investigation, then a claim or an internal process fix |
Two of these — inbound shortages and lost returns — account for the majority of what experienced reconcilers find, because they are the highest-volume handoff points in the network.
How a Reconciliation Service Works
- Baseline pull. Export a defined look-back window of fulfillment reports: shipments, receipts, adjustments, reimbursements, removals, and returns.
- Event-level matching. Pair every unit movement on your side with its counterpart in Amazon's records — shipped vs. received, returned vs. restocked, removed vs. reimbursed.
- Aging analysis. Classify each open discrepancy by age, because units missing for a short period may still surface, while old gaps are effectively permanent and claimable.
- Evidence assembly. Attach shipment IDs, manifests, adjustment references, and prior case numbers to each finding so the claim stands on documents, not assertions.
- Claim filing and tracking. Submit cases through Seller Central, log every response, and escalate rejections with the evidence pack already referenced.
- Prevention feedback. Report which SKUs, FCs, or shipment patterns generate the most discrepancies, so packaging, labeling, or routing changes can shrink the problem at the source.
What You Can Check Yourself First
Before hiring anyone, spend one afternoon on these five checks:
- Compare the units-shipped and units-received lines on your ten largest inbound shipments of the past quarter.
- Open the reimbursements report and confirm it contains an entry for every removal order you closed.
- Pull the customer returns report and spot-check five refunded units for a matching restock or reimbursement.
- Scan inventory adjustments for events with no visible cause, especially on your highest-value ASINs.
- Note anything that looks wrong, with dates — that list becomes the service's starting brief, or your own claim backlog.
If all five checks come back clean, your exposure is probably modest. If two or more surface discrepancies, the pattern usually continues further back than one quarter.
Red Flags When Hiring a Reconciliation Service
- Guaranteed recovery amounts or percentages. Nobody can promise what Amazon will reimburse before the evidence is reviewed. Guarantees are a sales tactic, not an operating capability.
- Requests for permissions beyond what the work needs. Reconciliation is read-and-file work. Be wary of anyone who wants broad account control to do it.
- No rejection-handling process. First submissions get rejected routinely; a service without an appeal workflow recovers a fraction of what it finds.
- Fee structures nobody will put in writing. Whether contingency, flat fee, or retainer, the math should be explicit before any claim is filed.
- One-and-done cleanups sold as ongoing coverage. Inventory discrepancies recur by nature; a single pass leaves next quarter's losses unclaimed.
FAQ
How do I know if I have an inventory problem at all?
Run the five self-checks above. Shipment-level shortages and missing return reimbursements are the fastest to spot. If either shows a gap, treat it as a sample, not the total — the same pattern is usually spread across the full report history.
How far back can discrepancies be claimed?
Claim windows vary by claim type, and Amazon has shortened several of them over time. Treat most windows as months, not years, and check current Seller Central guidance before relying on any specific deadline. Practically: reconcile sooner rather than later.
Will reconciliation change my listings or account settings?
No. FBA inventory reconciliation is analysis plus case filing. It does not touch listings, pricing, or account configuration. Any service proposing otherwise is describing a different job than the one you asked for.
Could the discrepancies be my own team's fault?
Sometimes, and a good reconciliation tells you so. Carton content errors at your 3PL, mislabeled prep, or short-picked shipments all look identical to Amazon-side loss until the manifests are compared. The value of a reconciliation is that it distinguishes the two.
How is this kind of service usually priced?
Commonly a percentage of recovered funds, a flat monthly fee, or a line item inside a broader management retainer. Percentage pricing is common across the industry, so compare the rate against the actual hours of claim work involved, not just the headline number.
Next Step
Unmatched counts are not a bookkeeping curiosity — they are inventory you paid for and never got back. Tim's Amazon Lab provides a dedicated FBA inventory reconciliation service through its Cases & Reimbursements service line, with claims filed and tracked by a dedicated account manager rather than a rotating ticket queue.
Want a professional pair of eyes on your account?
Tim's Amazon Lab offers a free account audit — a dedicated account manager reviews your account health, listings, and reimbursements, and tells you exactly what needs fixing. No contract, no pressure. Start your free audit →
Related Reading
- FBA Audit Service: Settlement, Inventory, and Fee Audits Explained
- FBA Recovery Service: Getting Back Lost Inventory, Refunds, and Overcharged Fees
- FBA Reimbursement Checklist
- A side-by-side graphic of "your ledger vs. Amazon's ledger" with mismatched unit counts highlighted. Alt text: "FBA inventory reconciliation comparing seller counts with Amazon records".
- A map-style diagram of the four loss points: receiving, returns, removals, transfers. Alt text: "where Amazon inventory discrepancies occur in FBA fulfillment".
- A mock reimbursement case with an evidence pack attached. Alt text: "FBA inventory discrepancy claim with shipment evidence attached".