RMA
Return Merchandise Authorization
RMA (Return Merchandise Authorization) is a structured process for handling product return or exchange requests. The typical flow: the customer submits a request with a reason, the business approves or rejects it per its returns policy, a return label is generated, the item is received at the warehouse and inspected, and finally a refund or exchange is issued. A return rate of 5-15% is considered normal for a general eCommerce store, but categories like apparel and fashion can see 30-40% due to sizing issues. A slow or opaque RMA process — for example, a return request that takes two weeks to approve — creates frustration and negative public reviews. Conversely, a fast, clear, and courteous RMA process can turn even a disappointed customer into a repeat buyer. In StoreChart, RMA requests from every sales channel are managed in one place, with inventory automatically updated once a returned item is back in stock.
A well-run RMA process protects margin on both ends of the transaction: it prevents customers from returning items outside policy (past the return window, missing original condition) while also making the approved cases fast and low-friction, since a slow or confusing return process is a common source of negative reviews even when the original product was fine. Tracking RMA reasons systematically (wrong size, damaged in transit, not as described) also feeds directly back into product listings and quality control — a spike in one reason code for one SKU is an early warning sign worth acting on before it shows up in the review section.
Within StoreChart's orders-management module, an RMA request is tracked against the original order record, so a return's status and reason code stay attached to the exact transaction and customer it belongs to — feeding directly into the same customer/CRM history and profitability reporting rather than existing as a disconnected spreadsheet a support agent tracks separately from the order system itself.
A store without a formal RMA process often discovers the cost of that gap only in hindsight, when a pattern of fraudulent or out-of-policy returns has already accumulated — requiring a return authorization before a customer ships an item back is a simple control that catches most of those cases upfront.
The reason code captured at RMA time is only useful if it's specific enough to act on — a generic 'customer didn't want it' bucket hides whether the real driver was sizing, misleading photos, shipping damage, or genuine change of mind, each of which points to a completely different fix.
Frequently asked questions
Usually the original order number, the specific item being returned, and a reason code — this lets the business verify the item is within the return policy window and route it to the correct next step (refund, exchange, or repair).
Most structured return policies require one so the business can track and approve returns before an item is shipped back, preventing customers from sending items that don't qualify and reducing disputes about whether a return was authorized.
By revealing patterns — if a specific SKU generates a disproportionate number of 'wrong size' or 'not as described' RMAs, that's a signal the product listing, sizing chart, or photos need correction before more customers hit the same issue.