Returns are a fact of ecommerce life - UK fashion return rates run at 20-40 percent - and the difference between a returns process and a returns workflow is whether each return costs you five minutes or twenty-five. Adobe Commerce’s RMA (Return Merchandise Authorization) system gives returns a proper lifecycle. Here is how to configure and operate it.
The RMA Lifecycle
An RMA moves through statuses you configure:
- Requested: customer picks items, quantity, reason, resolution (refund/exchange/credit) from their account
- Authorized: your team approves, and the customer gets the returns label/instructions
- Received/Approved: goods arrive, are inspected, condition recorded
- Closed: resolution executed - refund issued, exchange shipped, credit applied
Configure reasons (too small, faulty, wrong item) with resolution options per reason, and condition tracking for warehouse triage. The reason data is gold: a rising “faulty” trend on one SKU is a product problem visible in RMA reports before it is visible in reviews.
Configuration Essentials
- Enable RMA under Stores > Configuration > Sales > RMA Settings, scoped per store
- Define which products are returnable (per-product attribute) - custom-made and hygiene-sealed items should be non-returnable at the data level, not just in the policy page
- Set the returns window (e.g. 30 days from dispatch) - enforceable in the workflow, not just text
- Wire resolutions to real actions: refund triggers the payment refund path; store credit resolution should apply credit, not promise it manually
The Operational Reality
The RMA screen is only half the workflow; the warehouse half decides quality:
- Inspection discipline: condition recorded at receipt drives refund-vs-reject decisions and dispute defence
- Restocking rules: what goes back to saleable stock, what goes to seconds, what is written off - MSI source adjustments should follow automatically from the RMA resolution, not a separate spreadsheet
- SLA targets: authorised-to-refunded in under five working days. Slow refunds generate chargebacks; fast refunds generate loyalty
Policy Design
The workflow encodes policy, so decide policy first: free returns or customer-paid, original-packaging requirements, exchange-vs-refund preference. UK distance-selling rules set the statutory floor (14-day cancellation for most goods); your policy can be more generous, and generosity is a conversion feature - “free 60-day returns” on the product page measurably lifts add-to-cart.
Measure It
Track return rate by SKU, reason mix over time, refund cycle time, and refund-to-credit uptake. Returns will never be eliminated - but the data the RMA system collects turns them from a cost centre into product and merchandising intelligence. That shift, more than the workflow itself, is the real return on setting RMA up properly.