Handcrafted Beautiful Bootstrap HTML Templates for your Business Website.
A return touches four different things at once:
1. The order in WooCommerce
2. The payment in your gateway (Stripe, PayPal, etc.)
3. The stock in your inventory
4. The customer, via email
When returns are handled by email and memory, those four drift apart. The refund goes through twice. The item comes back but nobody restocks it. The order says one thing, the gateway says another, and the customer has heard nothing for a week.
This guide sets out a clean RMA (Return Merchandise Authorization) workflow for WooCommerce, the mistakes it prevents, and how to make the store enforce it.

A returned item comes back, gets put on a shelf, and is never added back to stock in WooCommerce. Over time your counts drift: products show out of stock when you have them, and your reorder decisions are based on wrong numbers.
The opposite happens too: stock is restocked when the return is requested, and the item never actually comes back.
There are three places to issue a refund: the gateway dashboard, the WooCommerce order, and (if you use a returns tool) the return itself. When two people use two different places, the customer gets refunded twice. Refunds made only in the gateway may also never reach WooCommerce, so your records still show the order as paid.
Without a system checking dates, late returns get approved to avoid arguments.
Without a recorded reason on every return, you can’t see that one product’s sizing is wrong or one supplier’s quality has dropped.
The return conversation is in email, the refund in Stripe, the stock change in a spreadsheet, and the order in WooCommerce. Answering “what happened with this return?” means checking four places.
Here’s a workflow that avoids all five. The key idea: one record per return, moving through fixed statuses, with refunds and stock changes triggered from that record.
(Setting this up from scratch? Follow our step-by-step returns portal guide.)
The customer requests a return from My Account, choosing the order, items, quantities and a reason. The system checks eligibility: inside the window, not already refunded, not an excluded product. An RMA number is issued.
Your team reviews the request in a queue, sees the order history and reason, and approves or rejects with a note. The customer is emailed either way. If approved, they get the return address.
The customer ships the item and adds a tracking number.
The item arrives and is inspected. This is usually the right moment to restock, because you only add back stock you physically have, in sellable condition.
The refund is created from the return record, as a proper WooCommerce refund that is optionally sent to the gateway in the same step. Because it’s linked to the return, the system can prevent a second refund for the same items.
The return is closed, the customer is notified, and the full history stays in an activity log.

If you’re not sure, use on arrival.
A few things worth knowing about how WooCommerce refunds work:
The free Recirco – Returns & Exchanges for WooCommerce plugin is built around exactly this workflow:
It writes to your orders only when you tell it to.
Recirco Pro adds automation on top: conditional approval rules, carrier return labels via Shippo generated on approval (cheapest rate by default, with manual label upload as a fallback), exchanges, store credit, analytics, and warranty claims with serial numbers and photos.
If you answered “no” to two or more, a structured RMA workflow will save you time and money.
| Restock timing | Good for | Risk |
|---|---|---|
| Never (automatic) | Items that can’t be resold; manual inspection | You must remember to restock by hand |
| On approval | Very fast-moving stock, trusted customers | Stock shows available before it’s back |
| On arrival | Most stores | Small delay before stock is available |
| On completion | Stores that inspect thoroughly before closing | Longest delay |
What is RMA in WooCommerce?
RMA (Return Merchandise Authorization) is the process of approving and tracking a return, usually with a unique RMA number. WooCommerce doesn't include it natively; plugins like Recirco add it.
How do I avoid refunding a customer twice?
Issue return refunds from one place only, ideally from the return record or the WooCommerce order, not the gateway dashboard, and use a system that blocks a second refund for the same items.
When should returned items be restocked in WooCommerce?
For most stores, when the item arrives and passes inspection ("on arrival").
Does a WooCommerce partial refund include tax?
It can and should. Refund the line's net amount and its share of tax so your tax reports stay accurate. Recirco splits net and tax from the original line automatically.