Amazon added return-reason controls to FBA Partial Refunds, letting sellers decide more precisely when an eligible customer keeps an item and receives part of the purchase price back. The October 9 notice was detailed in subsequent reporting.

The setting worth checking immediately is the default: if you were already enrolled, all eligible reasons stay active until you change them.

What the New Controls Allow

Amazon's announcement covers the US, UK, Germany, France, Italy, Spain, and Canada. Sellers can configure return-reason percentages across all ASINs with up to three configurations, or upload an Excel file specifying selected products, reasons, and percentages. Products or reasons left out of that file follow the standard return process.

This updates an existing program rather than launching a new one. The new capability is distinguishing between reasons for the return request.

According to My Amazon Guy's breakdown, existing enrollment does not automatically become more selective. Review your preferences if you want to narrow which reasons receive an offer.

Compare the Refund Against Inventory Recovery

Start the comparison at the moment the customer wants to return an order. Product cost and the original outbound shipment have already happened under either route, so do not count those common costs twice.

Take a $50 order. A 30% partial refund costs $15, leaves you $35 of the sale, and returns no physical stock. Ignore tax and fee adjustments for this simplified version.

With a full refund, the $50 reverses. If the returned item would provide $22 in expected net recovery after condition, processing, and eventual resale costs, the partial-refund route leaves $13 more economic value: $35 against $22.

If expected net recovery were $40, the full-return route would be $5 better instead.

Those are hypothetical figures, not Amazon fee quotes. They show why the return reason and likely condition matter more than a general preference for fewer returned boxes. Replace the assumptions with your actual transaction adjustments and recovery data, and do not count every returned unit at its original selling price or every kept unit as an avoided total loss.

A Reason Code Needs a Condition Check

Start with a small set of products and compare the selected return reason against what actually comes back. Cosmetic packaging damage and a functional failure carry very different implications for recovery, customer satisfaction, and whether the product needs investigating.

A keep-the-item offer should not substitute for investigating safety complaints or repeated defects. If one reason rises sharply, check the affected model, batch, packaging, and listing before treating a refund percentage as the fix.

Record sample size too. A handful of returns can make a reason look unusually expensive or unusually recoverable. Review the underlying orders before applying that conclusion across a large catalog.

Amazon Still Controls Customer Eligibility

The notice says Amazon assesses eligibility using the customer's profile and purchase history. Ineligible customers continue through the normal return route.

Your settings define where an offer may apply. They do not guarantee every matching request becomes a partial refund.

That matters when estimating savings. Track offers accepted, refund amounts, physical returns, recovered inventory value, and support costs. A shift in the mix of returns can lower average refund cost without improving total contribution.

Save your existing settings before changing them. Pick an ASIN-and-reason group you can actually evaluate, document the financial assumptions, and set a review date. Expand only once the order records show improvement, with enough visibility to catch recurring product problems rather than just lower return-handling costs.