UnilyticExcel exports, case-ready
Every reconciliation view exports with its filters applied, so you can attach the exact rows behind a claim rather than a screenshot and an assertion.
Recover money
Find the claims worth filing.
Amazon reimburses a great deal of what it loses and damages — but not all of it, not always in full, and never with a summary of what it missed. Unilytic reconciles what was refunded against what came back, and what Amazon paid against what it should have paid, so you can see the money that is genuinely still owed.
Five reconciliation viewsShortfalls calculatedAged by claim windowExcel exports
Five ways money leaks
The gaps, separated by what caused them.
A single "money lost" figure is not actionable, because each kind of loss is chased differently. Unilytic splits reconciliation into five views: units you refunded a customer for that never physically came back; seller-fulfilled returns with the same problem; units damaged while in Amazon's custody; the reimbursements Amazon has actually issued; and the SKUs where the economics mean a return is not worth pursuing at all. Each one filters, sorts and exports independently.
- Refunded, not received — you paid the customer back and no unit returned.
- Damaged at FC — units lost or damaged while Amazon was holding them.
- Loss-making SKUs flagged separately, so you stop chasing returns that cost more than they recover.
Paid is not the same as settled
The reimbursement that arrived may still be short.
This is the part almost nobody checks. When Amazon reimburses a unit it should cover what you would have netted on it — the price, less Amazon's fees, less product tax. Unilytic computes that expected figure per line and compares it with what actually landed. Where the payment falls short, the difference is the shortfall, and it is money you can still ask for. Crucially, SKUs that would not have made money anyway are excluded from the flag: there is no shortfall on a unit that was never going to be profitable, and pretending otherwise would just waste your time.
- Expected net proceeds computed per line from price, fees and tax.
- Only genuine shortfalls flagged — break-even and loss-making lines are excluded by design.
- Partial payments counted properly, by the amount still outstanding rather than all-or-nothing.
In the product
This is the actual screen.
Captured from a live Unilytic workspace — not a mockup, and not a roadmap promise.
From evidence to claim
Receipts your finance team will accept.
Unilytic does not file claims on your behalf — Amazon requires that to come from you. What it does is make the case, with the numbers attached.
Trend, not just total
A returns analytics dashboard charts loss, recovery and their direction over time, broken down by the dimension you care about — so you can tell a bad month from a worsening pattern.
Catch it before it ages out
Outstanding amounts are bucketed by age, so the claims closest to falling outside Amazon's window are the ones you see first. A claim you file late is worth exactly nothing.
Why this matters
Amazon's mistakes are small, frequent, and yours to find.
No individual discrepancy here is dramatic. A unit refunded in March that never came back. Four units damaged at a fulfilment centre and reimbursed at a little under what they were worth. A seller-fulfilled return that a customer was credited for and never posted. Each is small enough to ignore and none of them will ever be pointed out to you. But they occur continuously, across every SKU and every fulfilment centre, and they compound — while the claim windows quietly expire in the background. The work is not filing the claim; it is knowing which claim to file.
Partial payments become visible
Every reimbursement is compared with the net proceeds it should have covered.
Effort goes where it pays
Loss-making SKUs are separated out, and outstanding amounts are ranked by how soon they expire.
The evidence is already assembled
Filtered Excel exports carry the exact rows behind each claim.
Common seller mistakes
- Assuming a reimbursement means the matter is closedAmazon paying something is not Amazon paying enough. Unless you compare the payment against expected net proceeds, a partial reimbursement looks identical to a complete one.
- Reconciling once a quarterClaim windows do not wait for your review cycle. By the time a quarterly reconciliation runs, some of what it finds is already unclaimable.
- Chasing every discrepancy equallySome returns cost more to pursue than they recover. Without loss-making SKUs marked out, effort goes to the cases least worth having.
- Filing a claim without the underlying rowsA claim asserted from a summary figure invites a rejection. The line-level evidence is what makes it straightforward to approve.
Questions
Reimbursements, answered.
How do I find FBA reimbursements worth claiming?01
Unilytic reconciles your returns and reimbursement data into five views: refunded-but-not-received units, seller-fulfilled returns with the same gap, units damaged at a fulfilment centre, the reimbursements Amazon has issued, and loss-making SKUs. It computes what each line should have been worth to you and shows where the money is genuinely outstanding.
Does Unilytic file the claim for me?02
No, and it is worth being clear about that. Amazon requires claims to be raised from your own seller account. Unilytic's job is to find the cases worth raising and hand you the line-level evidence — the SKU, the quantity, the dates, the expected value and what was actually paid — so filing is quick and the claim is well-founded.
How does Unilytic know a reimbursement was too small?03
It computes the expected reimbursement for the line — listing price, less Amazon's fees, less product tax, multiplied by the quantity — and compares it with the total Amazon actually paid. Where the payment falls materially short, the difference is flagged as a shortfall. SKUs that would not have been profitable are deliberately excluded, because there is no genuine shortfall on a unit that was never going to make money.
How much does Amazon owe me in total?04
A running total of the amount lost is shown across the reconciliation views, and outstanding amounts are also bucketed by age so you can see how much is still comfortably inside Amazon's claim window and how much is close to expiring.
Can I see reimbursement trends rather than just a list?05
Yes. A dedicated returns analytics dashboard charts loss, recovery and their trend over time, with drill-down by dimension and both chart and row exports.
Does this cover seller-fulfilled orders as well as FBA?06
Yes. Seller-fulfilled returns have their own reconciliation view, because a customer being refunded without returning the unit is just as much a loss when you shipped it yourself.
Explore more
Keep going.
Warehouse
Back to all featuresWarehouse returns
Scan returned units in, grade them and photograph the damage that supports a claim.
Capture the evidence AutomationAmazon sync & automation
The nightly returns and reimbursement feed that keeps this reconciliation current.
Keep it current AnalyticsSell-through analytics
The demand and margin picture that decides which SKUs are worth chasing at all.
See the numbersGet started
See what Amazon still owes you.
No card · Built for Amazon India · Email support from the founder.