Do you mostly trust Amazon to catch everything automatically, or do you still check things like lost units, damaged inventory, inbound discrepancies, refunds without returns, fee jumps, rejected claims, or missing payouts?
I’m trying to understand the real-world workflow.
Do you use spreadsheets, a VA, Sellerboard, Getida, Helium 10, or do you just check when something looks wrong?
What part is the most annoying: finding the issue, gathering proof, knowing if it’s claimable, following up after rejection, or tracking whether the payout actually landed?
Amazon misses more than most sellers realize, lost units, inbound gaps, refunds with no return. We stopped relying on their system years ago.
The hardest part isn’t finding issues. It’s knowing what’s actually claimable and following up after a rejection without losing track of where each case stands.
A structured weekly audit beats any reactive approach. What’s your current cadence?
Most sellers don’t fully rely on Amazon, they use tools like Sellerboard, Helium 10, Getida or a VA to track lost units, fees, refunds and reimbursements. Amazon catches some issues but many are missed. The hardest part is not finding problems, it’s dealing with claims, proof, rejections and getting the final payout.
From what most high-volume FBA sellers say, very few rely fully on Amazon’s automatic reimbursements anymore because too many discrepancies get missed or underpaid. The usual workflow is a mix of software + manual review. Sellerboard, Getida, and Helium 10 are commonly used to flag lost inventory, inbound shortages, damaged units, fee changes, and refund issues, while larger sellers often add a VA to audit claims and follow up on rejected cases. The most frustrating part is usually not finding the issue, software can do that, it’s dealing with rejected claims, inconsistent support responses, and verifying whether Amazon actually paid the reimbursement correctly. Many sellers also underestimate how much money quietly disappears through small inventory and fee discrepancies over time.
Makes sense. Quick question, in your experience, where do things usually break first in that process? Is it missing evidence, or just not being able to track what actually got paid vs what was expected?
That’s interesting, when a claim gets rejected, is it usually unclear why Amazon denied it, or more that the follow-up process just becomes too time-consuming to keep pushing?
Both. Amazon’s denial reasons are often vague enough that you’re left guessing, AND the follow-up process is exhausting by design. They make it just painful enough that most sellers give up.
That’s actually a tactic worth knowing about. Keep escalating, document everything, and if Seller Support keeps looping you, go straight to the Executive Seller Relations team or file a complaint through the BBB. Amazon responds a lot faster when there’s external pressure.
From what I’ve seen, the process usually breaks at the reconciliation stage, tracking what Amazon actually paid versus what should have been reimbursed. Sellers often deal with partial reimbursements, delayed payouts, or cases marked as “resolved” where the credit never fully appears in settlement reports. Missing proof can also be a problem, especially with inbound shipment claims, but most experienced sellers already keep documentation. The harder part is connecting all the different Amazon reports and verifying that the reimbursement amount was correct, which is why many high-volume sellers rely on tools like Sellerboard or GETIDA to audit and reconcile everything properly.
Most FBA sellers use tools like Getida, Sellerboard, or Helium 10 to track reimbursement issues as amazon doesn’t catch everything automatically. The most annoying part is often gathering proof and following up after claim rejections.
That’s interesting, when you say the hardest part is after rejection, is it usually more the proof gathering or the back-and-forth with Amazon support that slows things down?