Every month, FBA damages and returns a slice of your inventory — and the reimbursements you could claim quietly slip by if no one is watching. Unilytic reads your Amazon returns and reimbursement reports and surfaces every damaged or unreturned unit by warehouse, type, and SKU — with an estimated value at risk — so you know which claims are worth filing.
Amazon's own reports tell you a unit came back damaged — they just don't add it up, file it for you, or flag it as worth claiming. Unilytic reads your returns reports and sorts every unit into the five categories Amazon uses: customer damaged, warehouse damaged, distributor damaged, carrier damaged, and defective. Each is counted by warehouse and over time, with per-SKU drill-down, so a recurring problem at one facility doesn't slip past quarter close.
A damaged unit is easy to miss in a raw report. Unilytic's Returns Reconciliation view estimates the value lost on each return — using your real sale price, Amazon fees, and the 0.1% TDS Amazon withholds — and skips the cases where Amazon owes nothing, such as units that came back sellable or SKUs whose fees already exceed their price. Sort by warehouse to find the facility eating your margin, or by SKU to spot the product that's damaged on every inbound, and decide which claims are worth your time.
The dedicated Returns Analytics dashboard turns your returns and reimbursement data into charts you can act on. Up top, the numbers that matter — total ₹ lost, recovered, still at risk, damaged units, and SKUs affected. Below, damaged inventory is broken down by warehouse, category, and damage condition; a worst-offender view ranks the SKUs costing you most by units, ₹ lost, and returns; and a claim-aging chart shows how much is still claimable before Amazon's window closes. Filter by date range, category, or warehouse, switch the trend interval between daily, weekly, and monthly, and export any chart to Excel.
The hard part of a claim isn't spotting it — it's proving it. Unilytic keeps the paper trail so a reimbursement case writes itself.
Export any filtered view — date range, warehouse, damage type — as a clean Excel sheet with SKU, date, quantity, and the estimated value lost. Hand it to finance or use it as the basis for a Seller Central case without re-keying a thing.
Watch damaged returns move over time. A spike in carrier-damaged units at one warehouse is a conversation with Amazon; a steady climb in customer damage is a packaging fix. The timeline tells you which.
Amazon's reimbursement claim windows are limited, so the longer a damaged unit sits unnoticed, the likelier it is to expire. Reviewing your returns regularly in Unilytic means losses surface while there's still time to act on them.
Connect SP-API or upload your Amazon returns and reimbursement reports, and Unilytic surfaces every damaged or unreturned unit sorted by warehouse, SKU, and damage type. Its Returns Reconciliation view also estimates the value lost on each return (your sale price minus Amazon fees and the 0.1% TDS Amazon withholds), so you can see which cases are worth filing instead of scrubbing raw reports by hand.
It shows an estimate of the value at risk — your sale price minus Amazon fees and the 0.1% TDS Amazon withholds, clearly marked as an estimate — not a guaranteed payout. It deliberately excludes cases where Amazon owes nothing, such as units returned in sellable condition or SKUs whose fees already exceed their price. The final reimbursement is always determined by Amazon when you file.
No — Unilytic identifies and documents what's worth claiming and exports a case-ready Excel sheet, but the claim is filed from your own Seller Central account. We request read-only SP-API scope, so Unilytic can read your inventory and returns data but cannot act on your account.
Yes. Every FBA warehouse and your own locations are tracked side by side. Group by warehouse to find the facility with the most damage, or by SKU to catch a product that's damaged on every inbound.
Yes — the Returns Analytics dashboard puts it on one screen: KPIs for ₹ lost, recovered, at-risk, damaged units, and SKUs affected, plus breakdowns by warehouse, category, damage condition, and return reason, a worst-offender SKU ranking, and a claim-aging chart that shows how much is still claimable before Amazon's window closes. Filter by date range, category, or warehouse, switch the trend interval between daily/weekly/monthly, and export any chart to Excel.
Track every FBA warehouse and your own locations side by side, with local-stock netting.
Right stock, right warehouse AnalyticsSee what's selling and what's stalling across 7/14/30/60/90-day windows.
Read the demand signal AlertsGet the right alert in the right place — scheduled digests and instant event alerts.
Stay in the loopNo card · Read-only SP-API · Email support from the founder.
Unilytic