UnilyticRecover the money Amazon already owes you.
Units get lost in the fulfilment network. Units get damaged in Amazon's custody. Customers get refunded for products that never physically come back. Amazon reimburses some of this automatically — but not all of it, and not always at the right value. The gap is invisible unless someone reconciles it, which is why most sellers write it off as a cost of doing business.
You are probably here because one of these happened.
- You know some units go missing every month but have never put a number on it.
- Refunds are issued to customers for items that never physically arrive back at a fulfilment centre.
- Damaged units pile up with no clear process for deciding which are worth claiming.
- You have filed claims before, been partly reimbursed, and never checked whether the amount was right.
- The reports you would need to reconcile this live in three different Seller Central exports.
- Claim windows close before anyone gets round to filing.
Why it keeps happening.
The data is deliberately fragmented
Inventory movement, returns and reimbursements arrive as separate reports with no shared key. Matching a refunded order to a physical return to a reimbursement is manual work, and it scales linearly with your order count.
Partial reimbursements look like resolved ones
A claim marked reimbursed is easy to treat as closed. If the amount credited is below what the unit was actually worth, the shortfall stays invisible unless the value is independently estimated and compared.
Not every loss is claimable
Units returned in sellable condition, or SKUs whose fees already exceed their sale price, are not worth pursuing. Without a way to separate those out, sellers either chase everything and waste hours, or chase nothing.
Claim windows expire quietly
Amazon's filing windows are finite. A case that was worth real money in March is worth nothing once the window shuts, and nothing in Seller Central prompts you as that deadline approaches.
How Unilytic handles it.
Reconcile returns against refunds automatically
Connect SP-API or upload your returns and reimbursement reports. Unilytic matches refunds against physically received returns and surfaces the refunded-not-received units — the ones where a customer was made whole but the product never came back.
Estimate what each case is actually worth
Every flagged unit carries a value estimate: your sale price minus Amazon's fees and the 0.1% TDS Amazon withholds. It is clearly labelled as an estimate, because the final figure is always Amazon's decision when you file. Cases where Amazon owes nothing are deliberately excluded so the list stays worth reading.
Catch under-reimbursement, not just non-reimbursement
For units lost or damaged in Amazon's custody, the reimbursed amount is compared against the estimated value. Where the credit falls short of a break-even floor, the case is flagged as under-reimbursed rather than silently treated as settled.
Scan returns at your own warehouse
If returns come back to your own facility, scan them in by Airway Bill or removal-order LPN on any phone. Amazon's details fill in automatically. Grade each unit OK or damaged with photo proof, so a claim carries evidence rather than an assertion.
File with the receipts attached
Export a case-ready Excel sheet with the units, values and supporting detail. You file from your own Seller Central account — Unilytic requests read-only SP-API scope and can never act on your account. The claim-aging chart shows what is still claimable before each window closes.
Answered.
How much money is typically recoverable?
It varies far too much by catalogue, return rate and fee structure for an honest blanket figure, and anyone quoting you a fixed percentage is guessing. What Unilytic gives you is your own number: the estimated value at risk across your actual flagged units, so you can judge whether pursuing it is worth the effort before committing any time.
Does Unilytic file the claims for me?
No. Unilytic identifies what is worth claiming, values it, and exports a case-ready sheet. The claim itself is filed from your own Seller Central account. We request read-only SP-API scope deliberately, which means Unilytic can read your inventory and returns data but cannot place orders, change listings or write anything to your account.
Is the value estimate what Amazon will actually pay?
No, and it is labelled as an estimate throughout. It is your sale price minus Amazon fees and the 0.1% TDS withheld — a reasonable basis for deciding whether a case is worth filing. The final reimbursement is determined by Amazon when you file, and can differ.
What counts as under-reimbursed?
The flag is specific rather than broad: it fires for units lost or damaged in Amazon's custody where the amount reimbursed falls below the estimated value, after a break-even floor is applied. Units returned in sellable condition and SKUs whose fees already exceed their price are excluded, because Amazon does not owe you anything on those.
How far back can I reconcile?
As far back as the data you upload, though Amazon's own claim windows are the real constraint. Filing deadlines are finite, so the practical answer is that recent cases are the ones worth prioritising — which is exactly what the claim-aging view is for.
Related.
Reimbursement tracking
The full feature: claim types, damage reasons, aging and Excel export.
Explore the feature FeatureWarehouse returns scanning
Scan customer returns and removal orders at your own warehouse, with photo proof.
See scanning ToolReimbursement calculator
Estimate what Amazon may owe you for a lost or damaged unit — no sign-up.
Open the calculatorFind what you are owed, then go and claim it.
No card · Built for Amazon India · Email support from the founder.