Returns are a reimbursement surface, not just a refund report

Most teams review returns as a product-quality metric. That matters, but it is incomplete. Returns are also a reimbursement surface. After the refund, the unit still has to be received, inspected, dispositioned, and accounted for. Leakage happens anywhere in that chain.

Match every refund to a physical outcome

For each refunded FBA order, track whether the unit was returned, returned late, marked sellable, marked unsellable, reimbursed, or never resolved. A refund without a physical outcome is not closed. It is an exception.

The common patterns:

• customer refunded but unit never returned
• returned quantity lower than refunded quantity
• sellable unit incorrectly marked unsellable
• damaged unit not reimbursed
• reimbursement paid at an unexpected valuation

Separate policy from operations

Some concessions are legitimate and not recoverable. The operating process should not argue every refund. It should identify cases where the final state contradicts the expected state. That is a narrower and more useful queue.

Use deadlines

Return and reimbursement windows matter. A case found too late is just a lesson. Keep a deadline on every unresolved return exception and rank by expected recovery amount.

Feed the product loop

If a SKU has high return leakage, reimbursement recovery is only the downstream fix. The upstream action might be listing clarity, packaging improvement, supplier quality review, or ending FBA for the SKU.

Returns reconciliation turns a messy customer-service area into two useful outputs: recoverable claims and product decisions.

Review return cohorts by SKU

Account-level return metrics hide the real work. Review cohorts by SKU, purchase period, and return reason. A packaging change, listing update, or supplier lot should create a new cohort so the team can see whether the action changed outcomes. If old and new returns are blended together, successful fixes look weaker and failed fixes take longer to detect.

This is especially important when a SKU has both quality and expectation problems. A better listing may reduce "not as described" returns while a supplier defect continues to create damaged returns. Cohort review helps the team avoid declaring victory too early.

Tie recovery to disposition

Returned units should not sit between customer service, warehouse, and finance. Each unit needs a final state: sellable, unsellable with claim, unsellable without claim, missing, reimbursed, or written off. The final state should determine the next action. Sellable units return to inventory. Damaged units get evidence attached. Missing units move to the claim queue before the deadline.

When disposition and recovery share the same record, the team can measure both product health and cash recovery. That is the difference between a return report and an operating control.

Separate abusive patterns from normal friction

Some returns are normal customer friction. Others show patterns worth escalating: repeated missing-item claims, repeated returns from the same reason on high-value units, or units marked unsellable without matching evidence. The review should separate these cases from ordinary preference returns so operators do not waste time arguing unrecoverable refunds.

Abusive or inconsistent patterns need evidence. Keep order IDs, return reasons, condition notes, photos where available, and settlement outcomes. A claim without evidence is weak, but a pattern with evidence can support a stronger escalation or a change to packaging, listing, or fulfillment channel.

Review valuation

Even when Amazon reimburses a return-related issue, the amount can be wrong. Compare reimbursement value with the affected unit cost and current policy basis. If cost records are stale or tied to the wrong FNSKU, a paid claim may still leave money behind. Recovery is complete only when both quantity and valuation reconcile. Put valuation exceptions in the same queue as missing-unit exceptions so they receive ownership. Small underpayments can compound when the same stale cost basis affects many units.