Tag Archives: Recirco

Should You Auto-Approve Returns? Building Return Approval Rules for WooCommerce

Every growing store hits the same fork in the road with returns.

Option A: approve everything by hand. Safe, but slow. Customers wait days to hear back, your team spends hours clicking “approve” on routine requests, and the queue balloons every January.

Option B: auto-approve everything. Fast and cheap, until you notice the same handful of customers buying, wearing and returning, or a high-value item approved and refunded before anyone looked at it.

A discussion on Reddit about automating ecommerce returns summed up where most experienced operators land: the best systems “automate the obvious cases and smoothly escalate everything else to humans”, with context attached. Commenters agreed on the tension: auto-approving without any checks invites fraud, but demanding photos for every return slows down simple cases that carry no fraud risk at all. One suggested routing by order value and customer history: auto-approve small returns from trusted customers, flag risky ones for review. Another pointed out the payoff depends on volume. At a low return rate manual handling may be fine; at high volumes automation becomes essential.

This guide turns that consensus into a practical framework: which returns to automate, which to review, how to write rules that don’t surprise you, and how to set them up in WooCommerce.

The automation spectrum

Spectrum from fully manual (more control, slower) through assisted manual and rules-based to fully automatic (faster, more abuse risk). Rules-based, where routine returns are decided automatically and the rest are held or flagged, is the target for most stores.

Level What happens Good for
Fully manual Every request reviewed by a person Very low volume; very high-value goods
Assisted manual Every request reviewed, but with filters, bulk actions, and history at hand Small stores growing quickly
Rules-based Routine requests decided automatically; the rest held or flagged for a person Most growing stores
Fully automatic Everything approved automatically Very low-value goods, very low abuse risk

For most WooCommerce stores, rules-based is the right target: speed for the 80–90% of routine returns, human judgment for the rest.

What can be safely automated

These returns are usually safe to approve without a human:

  • Exchanges for a different size or colour. You keep the revenue, and the risk is low.
  • Low-value items, where the cost of reviewing exceeds the cost of a mistake.
  • Inside the return window, for eligible products: the system has already checked the policy.
  • Common, low-risk reasons such as “too small”, “too large” or “changed my mind” on unworn items.
  • Trusted customers with a good history.
  • Clear store errors (wrong item sent), where you’d approve anyway and delay only annoys.

What should go to a human

  • High-value returns, above a threshold you set.
  • Damage and fault claims, especially without detail or photos.
  • Customers with several recent returns, or with past returns refused on inspection.
  • Categories prone to wardrobing: occasion wear, event equipment, cameras.
  • Unusual combinations: returning most of a large order, or the same item repeatedly.
  • Anything your rules don’t recognize. The default should be “hold”, not “approve”.

What can be automatically rejected

Automatic rejection should be reserved for clear-cut policy cases, and always with a specific reason sent to the customer:

  • Outside the return window (if not already blocked at submission)
  • Non-returnable products (if not already excluded)
  • Duplicate requests for units already returned

Be cautious: an automatic rejection the customer doesn’t understand quickly becomes a complaint or a chargeback. If in doubt, flag instead of reject.

Four actions, not two

Good rule systems offer more than approve/reject:

Action Meaning Use for
Approve Decision made; customer gets next steps Routine, low-risk returns
Reject with reason Decision made; customer told why Clear policy violations
Flag Proceed normally, but mark for attention Mild risk signals you want to watch
Hold Stop; wait for a person High value, high risk, missing evidence

Flag is underrated. It lets you approve quickly while keeping an eye on patterns, for example customers whose returns you want to inspect carefully on arrival.

Signals worth building rules on

Whatever tool you use, rules are only as good as the signals they can see. The most useful ones, roughly in order of value:

  • Return value: the single strongest predictor of how much a wrong decision costs.
  • Return type: exchange, store credit or refund. Exchanges keep revenue and carry less risk.
  • Reason: sizing reasons are low risk; damage and “not as described” deserve evidence.
  • Whether an explanation or photos were provided for reasons that need them.
  • Product or category: occasion wear and high-value electronics behave differently from basics.
  • Customer history: number of recent returns, past refusals on inspection, lifetime spend.
  • Order age: requests near the end of the window are slightly more likely to be wardrobing.
  • Order size: returning most of a large order is worth a look.

You don’t need all of them. Value, type and reason alone cover most of the benefit for most stores.

How to write rules that don’t surprise you

Use “first match wins” ordering

Ordered rule list checked top to bottom: hold returns over $300, hold damage claims with no explanation, flag customers with many recent returns, approve exchanges, approve returns under $50, hold everything else. A $400 exchange is held by rule 1 even though exchanges are usually approved.

When rules are checked in order and the first one that matches decides, you can reason about them like a checklist:

  1. Hold if the return value is over $300
  2. Hold if the reason is “Damaged” or “Faulty” and no explanation was given
  3. Flag if the customer has had several returns recently
  4. Approve if it’s an exchange
  5. Approve if the return value is under $50
  6. Hold everything else

Put the most cautious rules first. A $400 exchange should be held (rule 1) even though exchanges are normally approved (rule 4).

Always have a default

The last rule should catch everything not matched above. Hold is the safe default while you’re learning; switch it to approve once you trust your rules.

Record which rule decided

When a customer asks “why was my return approved instantly but my friend’s wasn’t?”, or when you’re auditing a bad decision, you need to know which rule made the call. Without that, rules become a black box nobody trusts.

Start strict, then loosen

Begin with a narrow set of auto-approvals (exchanges, low-value items) and a default of hold. Review a month of held returns: if you approved 95% of them anyway, add a rule to approve that type automatically. Loosen with evidence, not hope.

Review monthly

Look at:

  • What share of returns were decided automatically
  • Average time to decision for automated vs held returns
  • How many auto-approved returns turned out to be problems on inspection
  • How many held returns you approved without changes (candidates for new auto-approve rules)

Telling customers about automated decisions

Customers don’t need to know a rule decided their return, but they do need the decision to feel fair and fast:

  • Instant approvals should read like any approval: clear next steps, the label, the deadline.
  • Held returns deserve a short, honest message: “Thanks, we’ve received your request. Because of the item’s value, a member of our team will review it personally within one working day.” That turns a delay into a sign of care rather than suspicion.
  • Automatic rejections must give the specific reason and a way to reply. If a customer can’t understand why a machine said no, they’ll ask their bank instead.
  • Flags are internal only. The customer’s experience shouldn’t change.

When a customer queries a decision, the activity log’s record of which rule decided makes the answer quick and consistent.

A worked example

A clothing store processing 400 returns a month starts fully manual. Two people spend about 15 hours a month approving requests, and customers wait an average of two days for a decision.

They introduce rules:

  • Hold anything over $200
  • Hold “Damaged” claims without photos
  • Flag customers with 4+ returns in 90 days
  • Approve all exchanges
  • Approve “Too small”/”Too large” under $200
  • Hold everything else

After a month, about 70% of returns are approved automatically within seconds, most of them exchanges and sizing returns. The remaining 30% are held or flagged, and the team reviews them properly instead of rushing. Average decision time drops from two days to a few hours, and the team spends a fraction of the time on approvals. Because flagged customers’ returns are inspected carefully on arrival, two cases of repeated wardrobing are spotted in the first month.

(Illustrative example; your mix of returns will differ.)

Common rule-writing mistakes

  • Approve-all default. If your last rule approves everything, any gap in your rules becomes an automatic approval. Default to hold until you trust the set.
  • Too many rules. Twenty overlapping rules are impossible to reason about. Most stores need five to eight.
  • Rules nobody owns. Someone should be responsible for reviewing and changing them, or they drift out of date as products and prices change.
  • Thresholds that never move. A $50 auto-approve limit set three years ago may no longer fit your average order value.
  • Silent rejections. Automatic rejections without a reason the customer can understand generate complaints and disputes.
  • Forgetting seasonality. A rule set tuned for July may hold far too much in January. Review before holiday returns season.

Approval is only one step

Automating approval speeds up the front of the process. Make sure the rest keeps up:

  • Labels generated on approval, so an instant approval comes with an instant label.
  • Restocking on arrival, after inspection, not on approval, so automated approvals don’t put unchecked items back on sale.
  • Refund after arrival for anything held or flagged.
  • Clear emails at each step, so customers know what happens next. ([Templates](/blog/woocommerce-return-email-templates/))

Setting it up with Recirco

Recirco – Returns & Exchanges for WooCommerce (free) handles the policy layer and the assisted-manual level:

  • Return window, eligible statuses and excluded products/categories are enforced at submission, so ineligible requests never reach the queue.
  • Per-unit eligibility blocks duplicate requests for the same units.
  • Reasons with optional required explanations, so the information needed to decide arrives with the request.
  • An admin queue with search, filters, status counts, a pending badge and bulk approve, reject, mark received and delete, for fast manual review.
  • An activity log on every return.

Recirco Pro adds conditional approval rules, the rules-based level described above:

  • Seven conditions and four actions: approve, reject with reason, flag, and hold
  • First match wins, so rules behave like the ordered checklist above
  • The activity log names the deciding rule on every return, so automated decisions are explainable to your team and your customers
  • Which signals you can use depends on the seven conditions Recirco Pro supports. Check the Recirco documentation for the current list and map the example rules in this article to them. Anything the conditions can’t express can still go to the hold default for a person to decide.
  • Works alongside Pro’s exchanges, store credit, Shippo labels generated on approval, photo uploads for claims, and analytics (including average days to resolve) to measure the effect of your rules

WooCommerce Return Email Templates: 6 Messages Customers Actually Read (Copy and Paste)

Return emails are some of the most-read messages your store sends. A customer waiting for a refund opens every one, often more than once. Yet most stores either send nothing between “I’d like to return this” and the refund, or send generic messages that leave the customer with more questions than answers.

Good return emails do three jobs:

  1. Tell the customer exactly where things stand, so they don’t email to ask.
  2. Tell them exactly what to do next, so the return arrives correctly and quickly.
  3. Protect the relationship, so a return becomes a reason to buy again, not a reason to leave.

The stakes are real: the NRF found 71% of shoppers are less likely to shop with a retailer again after a poor returns experience (NRF, October 2025).

Below are six templates covering the full return lifecycle, with subject lines, the reasoning behind each, and the mistakes to avoid. Copy them, adjust the tone to your brand, and replace the bracketed placeholders.

The six emails a return needs

Six return emails: request received (confirm and set timing), admin alert (team acts), approved (how to send it), rejected (why and options), completed (amount, date and timing), and customer note (explain anything unusual). All six are built into free Recirco.

# Email Sent when Main job
1 Request received Customer submits a return Confirm, set expectations
2 Admin alert Customer submits a return Get your team to act
3 Approved You approve Explain how to send it back
4 Rejected You decline Explain why, kindly, with options
5 Completed / refunded Refund or exchange is done Confirm the money, close the loop
6 Customer note Anything unusual Explain in plain words

Some stores add a “received” email when the parcel arrives. If your process has a gap of more than a day or two between arrival and refund, add one. It’s the best single defence against “did you get my parcel?” emails. ([More on that](/blog/where-is-my-refund-tickets/))

Principles for every return email

Annotated example refund email: the return number is in the subject line, the status comes first, the exact amount, payment method and date are listed, and it ends with honest bank timing and an invitation to reply.

  • Put the return number in the subject line. Customers search their inbox for it.
  • Lead with the status. “Your return is approved”, not “Thank you for contacting us regarding…”
  • One clear next step, in bold or as a button.
  • Specific over vague. “Within one working day”, not “soon”. “$24.30 to your Visa”, not “your refund”.
  • Plain text-friendly. Many people read on phones; keep layout simple.
  • Human tone. Returns aren’t a failure on the customer’s part. Never make them feel judged.
  • Same voice as your marketing. A playful brand shouldn’t suddenly sound like a bank.

Template 1: Request received

Subject: We’ve got your return request: [RETURN NUMBER]

Hi [First name],

Thanks, we’ve received your return request for order #[Order number].

Return number: [RETURN NUMBER]
Items: [Item list with quantities]

We’ll review it within one working day and email you with next steps. You can check the status any time in My Account → Returns.

Changed your mind? You can cancel the request from the same page.

[Store name]

Why it works: instant reassurance that the request went through, a reference number, a time commitment, and a place to look. It prevents the “did my request work?” email entirely.

Avoid: “Your request is being processed.” It says nothing.

Template 2: Admin alert (internal)

Subject: New return request [RETURN NUMBER]: [Customer name], [value]

A new return request needs review.

Customer: [Name], [email]
Order: #[Order number], placed [date]
Items: [Item list]
Reason(s): [Reasons + customer explanation]
Return value: [Amount]

[Review in admin →]

Why it works: your team can triage from the email: reason, value, customer. The faster this is acted on, the faster email 3 goes out.

Tip: send it to a shared inbox or channel, not one person, so holidays don’t stall returns.

Template 3: Return approved

Subject: Your return [RETURN NUMBER] is approved. Here’s how to send it

Hi [First name],

Good news: your return for order #[Order number] is approved.

What to do next

  1. Pack the item(s) securely, ideally in the original packaging, with tags attached.
  2. Write your return number [RETURN NUMBER] on a note inside the parcel.
  3. Send it to:
    [Return address]
    [Or: Your prepaid label is attached. Print it and drop the parcel at any [carrier] location.]
  4. Please send it within 14 days.

Once it’s on its way, add your tracking number in My Account → Returns so we can watch for it.

What happens next: when your return arrives we’ll check it within [2] working days and then [refund you / send your replacement].

[Store name]

Why it works: numbered steps, the address or label right there, a deadline, and a preview of what happens next. It answers “where do I send it?”, “how?”, “by when?” and “then what?” in one go.

For exchanges: replace the last paragraph with “Your replacement [item/size] will ship [as soon as your return arrives / today].”

Avoid: burying the address in a footer, or attaching a label without saying which carrier accepts it.

Template 4: Return rejected

This is the hardest email to write well, and the one most likely to become a complaint or chargeback if written badly.

Subject: About your return request [RETURN NUMBER]

Hi [First name],

Thanks for your return request for order #[Order number]. Unfortunately we can’t accept this return because [specific reason, e.g. “the order was delivered on 2 October, outside our 30-day return window” / “personalized items can’t be returned”].

We know that’s not the answer you were hoping for. Here’s what we can do:

  • [If faulty: “If the item is faulty or damaged, please submit a new request choosing ‘Faulty’ and we’ll look at it under your warranty rights.”]
  • [Optional goodwill: “As a thank-you for being a customer, here’s 10% off your next order: [CODE].”]

If you think we’ve got something wrong, just reply to this email. A real person will read it.

[Store name]

Why it works: a specific reason the customer can understand and check, an acknowledgement that it’s disappointing, an alternative path (especially for faults, which may have legal protection beyond your return window), and a human route to appeal.

Avoid: “Your return does not meet our policy.” No reason, no options, no human: that’s a template for a chargeback.

Template 5: Return completed / refunded

Subject: Your refund of [amount] is on its way: [RETURN NUMBER]

Hi [First name],

Your return [RETURN NUMBER] is complete.

Refund: [$24.30]
Refunded to: [Visa ending 4242 / PayPal / store credit]
Date issued: [14 January]

Most banks show refunds within 5–10 working days. If you can’t see it after that, reply to this email and we’ll send you the refund reference to give your bank.

[If partial: “This covers [items]. [Short explanation of any difference].”]

Thanks for shopping with us. We hope to see you again soon.

[Store name]

For exchanges:

Subject: Your replacement is on its way: [RETURN NUMBER]

Your exchange is complete and your [new item, size] has shipped. Tracking: [link]. There’s nothing to pay.

For store credit:

We’ve added [$27.50] store credit to your account (including a [10]% bonus). It’s ready to use at checkout. See your balance in My Account → Store credit.

Why it works: the amount, method and date answer “where’s my money?” before it’s asked, and an honest bank timeframe stops the day-three panic.

Template 6: Customer note (anything unusual)

Use this whenever something needs explaining: a partial refund, a condition issue, a delay, a question.

Subject: A quick update on your return [RETURN NUMBER]

Hi [First name],

[Plain explanation, e.g. “Your parcel arrived today, thank you. One of the two shirts was missing its tags, so under our returns policy we’ve refunded the other shirt ($22.50) and will send the untagged one back to you at no cost.”]

[What happens next / what they can do.]

Any questions, just reply.

[Store name]

Why it works: customers accept almost any outcome if it’s explained before they discover it on a statement.

Adapting the tone to your brand

The templates above use a neutral, friendly tone. Adjust it to match how the rest of your store sounds:

  • Playful brands can lighten the approved email (“It’s not you, it’s the size. Let’s fix that.”) but should keep the steps and numbers plain.
  • Premium brands can be warmer and more personal (“A member of our team will personally inspect your item”), and may offer a callback for high-value returns.
  • Technical or B2B stores can be more concise and include order and SKU references in a short table.

Whatever the tone, keep three things constant: the return number, the next step, and the specific amounts and dates. Personality goes around the facts, never in place of them.

If you sell in several countries, translate return emails rather than relying on English everywhere. A customer anxious about their money will read every word, and it helps if they’re in their own language.

Mistakes that create complaints

  • No return number in the subject: customers can’t find the thread.
  • Different numbers in different places (order number in one email, RMA in another, with no link between them).
  • Vague timing (“soon”, “shortly”) that invites “how soon?” emails.
  • Rejections without reasons.
  • Refund emails without the amount.
  • Marketing-heavy footers on a rejection email. Not the moment for “You might also like…”.
  • Sending from no-reply addresses while telling people to reply.

Setting these up in WooCommerce

WooCommerce sends a refund email, but has no return request, approval, rejection or note emails, because it has no concept of a return.

Recirco – Returns & Exchanges for WooCommerce (free) adds all six:

  • Request received, admin alert, approved, rejected, completed and customer note
  • Each editable, in HTML and plain text, so you can paste in the wording above and match your brand
  • Sent automatically as the return moves through its statuses, so nobody has to remember
  • Customer notes written on the return can be emailed directly, covering Template 6
  • Each return has an RMA number with your own prefix, so subject lines and references are consistent

Recirco also gives customers a live status page in My Account with the return address, labels when available, the tracking number they added, and the current status, so the emails and the page always tell the same story.

Recirco Pro adds what the exchange and credit versions of Template 5 rely on: exchanges that create a zero-total replacement order, store credit with a bonus percentage and a balance page in My Account, plus carrier labels via Shippo generated on approval, so the “your prepaid label is attached” line in Template 3 becomes automatic.

Stop the ‘Where’s My Refund?’ Emails: How to Keep WooCommerce Customers Informed During Returns

Look through any store’s support inbox in January and you’ll find the same handful of messages over and over:

  • “I sent my return last week. Did you get it?”
  • “Where’s my refund?”
  • “Is my return approved? Where do I send it?”
  • “I’ve heard nothing since I asked to return this.”
  • “My bank says nothing has come in.”

In retail support these are often called WISMR tickets (“where is my refund?”), a cousin of the “where is my order?” tickets that flood inboxes before delivery. They’re frustrating for everyone: the customer feels ignored, and your team spends hours answering questions a status update could have answered automatically.

And they matter beyond support cost. The NRF found 71% of consumers are less likely to shop with a retailer again after a poor returns experience, and four in five would share a bad returns experience with friends and family ([NRF, October 2025](https://nrf.com/media-center/press-releases/consumers-expected-to-return-nearly-850-billion-in-merchandise-in-2025)). A customer who’s anxious about their money is one quiet week away from calling their bank.

This guide identifies the moments where customers go looking for information, what to tell them at each, and how to automate it in WooCommerce so the questions stop arriving.

Why WISMR tickets happen

Every one of these emails has the same root cause: the customer doesn’t know what’s happening, and has nowhere to look.

With email-based returns, the process is invisible to the customer. They send a request into the void, ship a parcel into the void, and wait for money to appear. Every gap in communication becomes a ticket.

WooCommerce alone makes this harder:

  • There’s no return record for the customer to look at. Only the original order.
  • There’s no “return received” or “return approved” email. WooCommerce has a refund email, but nothing before it.
  • Partial refunds don’t change the order status, so even the order page gives no clue anything happened.

The five moments that create tickets

Timeline of five moments that create support tickets: request sent (did it go through?), approved (where do I send it?), shipped (did you get it?), refunded (where's my money?), and anything unusual (why is it less?). Answer each with an email and a status page.

Map your return process and you’ll find customers need information at five points. Miss any one, and tickets follow.

Moment 1: “Did my request go through?”

When: immediately after they ask to return something.
What they need: confirmation it was received, a return number, and when they’ll hear back.
Ticket if missing: “I filled in your form, did it work?”

Moment 2: “Is it approved? What do I do now?”

When: when you approve (or reject) the return.
What they need: the decision, where to send the item, the return number to include, how to package it, the label if you provide one, and any deadline.
Ticket if missing: “Where do I send it?” / “Is it approved yet?”

Moment 3: “Did you get my parcel?”

When: after they’ve shipped it.
What they need: reassurance that you know it’s on the way, and confirmation when it arrives.
Ticket if missing: “I posted it a week ago, has it arrived?”

Moment 4: “Where’s my money?”

When: after the item arrives and is inspected.
What they need: confirmation of the refund amount, the method, the date it was issued, and how long their bank typically takes to show it.
Ticket if missing: “Where’s my refund?” This is the big one, and the one most likely to turn into a dispute.

Moment 5: “Anything else I need to know?”

When: whenever something unusual happens: a partial refund, a deduction, a delay, a question about condition.
What they need: a clear, human explanation, before they notice something unexpected on their statement.
Ticket if missing: “Why was I refunded less than I paid?”

Templates for each moment

Adapt these for your emails and status page.

Moment 1: Request received

We’ve got your return request for order #6120 (return number RET-1043). We’ll review it within one working day and email you with next steps. You can check its status any time in My Account → Returns.

Moment 2: Approved

Good news: your return RET-1043 is approved. Please send the item(s) to [address] within 14 days, with your return number inside the parcel. [Your prepaid label is attached.] When you’ve sent it, add your tracking number in My Account → Returns so we can watch for it.

Moment 3: Received

Your return RET-1043 has arrived. We’ll check it within [2] working days and then process your refund.

Moment 4: Refunded / completed

We’ve refunded $24.30 to your original payment method today. Most banks show refunds within 5–10 working days. Your return RET-1043 is now complete. Thanks for shopping with us.

Moment 5: Something unusual

We’ve received your return RET-1043. One of the two items was returned without its tags, so under our returns policy we’ve refunded $22.50 for the other item. If you have any questions, just reply to this email.

Two ways to answer: push and pull

Customers get information in two ways:

  • Push: emails sent at each moment. Proactive, but easy to miss or land in spam.
  • Pull: a status page they can check whenever they want. Always there, always current.

You need both. Emails tell people something changed; the status page answers the question at 11 p.m. on a Sunday when they wonder, again, whether you’ve received the parcel.

What a good return status page shows

Mock-up of a return status page in My Account showing the return number, an Approved status badge, the order and item, return address, prepaid label, a field for the customer's tracking number, refund details, a team note and a cancel button, with a checklist of what a good status page includes.

  • Return number and the order it belongs to
  • Items being returned, with quantities and reasons
  • Current status in plain words (“Approved: please send your item”, “Received: being checked”, “Refunded on 14 Jan”)
  • Next step for the customer, if any
  • Return address and any label
  • Tracking number they’ve added (and a way to add one)
  • Refund amount and date once issued
  • Notes from your team, where relevant
  • A way to cancel the request if they change their mind

Writing refund timing honestly

The most common WISMR trigger is the gap between “we refunded you” and “the money appears”. Card refunds commonly take several working days to show on a statement, depending on the bank. Say so explicitly in the refund email:

“We’ve refunded $54.20 to your Visa ending 4242 today, 14 January. Most banks show refunds within 5–10 working days. If you can’t see it after that, reply to this email and we’ll send you the refund reference to give your bank.”

Specific amount, specific method, specific date, an honest timeframe, and a clear next step. That one paragraph prevents more tickets than anything else in this guide.

Before and after: a week of return tickets

Before: a store processing about 60 returns a week by email receives roughly 45 return-related emails on top of the requests themselves: “did you get my request?” (10), “where do I send it?” (8), “did my parcel arrive?” (12), “where’s my refund?” (13), “why is my refund less?” (2). At around five minutes each to find the order and reply, that’s nearly four hours a week of answering questions about things that already happened.

After: requests are made in a portal that confirms them instantly; approval emails include the address and label; customers add tracking numbers and see “Received” on their status page; the refund email states the amount, date and expected bank timing. Most of those 45 emails never get written. The ones that remain are genuine exceptions that deserve a human.

The difference isn’t working harder. It’s that every question now has an answer waiting before it’s asked.

Internal service levels that prevent tickets

Customer-facing updates only help if the steps behind them happen on time. Agree internal targets:

  • Approve or reject within one working day of the request.
  • Mark received the same day the parcel arrives.
  • Refund within two working days of arrival (or on arrival for low-risk returns).
  • Reply to customer notes within one working day.

Track them. When a step slips, the “where’s my refund?” emails come back.

Setting it up with Recirco

Recirco – Returns & Exchanges for WooCommerce is free, and is built to cover all five moments without extra tools.

Pull: a status page in My Account

  • A Returns tab in My Account listing each return with its RMA number.
  • Live status for every return, enforced by a seven-status workflow, so what the customer sees always reflects where the return really is.
  • Your return address and policy text on the page; labels displayed when available.
  • Customers can submit a tracking number themselves and cancel their own request.
  • Customer-visible notes from your team appear alongside the return.

Push: six editable emails

  • Request received (moment 1)
  • Approved and Rejected (moment 2)
  • Completed (moment 4)
  • Customer note (moment 5): send a message to the customer straight from the return
  • Admin alert, so your team knows a request is waiting

All six are editable in HTML and plain text, so you can add the refund-timing wording above. Your team gets an admin queue with a pending badge, status counts, filters and bulk actions, so requests are approved quickly and moment 2 isn’t delayed.

Refunds are created from the return as real WooCommerce refunds, so the refund in the customer’s account, the refund at the gateway and the return’s status all agree. There’s no “the system says refunded but the money hasn’t moved” confusion.

Recirco Pro reduces ticket volume further:

  • Carrier labels via Shippo, generated on approval, so customers get a tracked label instead of asking how to send it.
  • Conditional approval rules for instant decisions on routine returns: moment 2 happens in seconds.
  • Exchanges and store credit with a balance page in My Account, so credit customers can check their balance themselves.
  • Analytics including average days to resolve, the number that predicts WISMR volume.

Don’t forget the team side

Customers aren’t the only ones who need visibility. Your team needs to see, at a glance, which returns are waiting on them: requests to approve, parcels arrived but not checked, refunds not yet issued. A queue with status counts and a pending badge does this. Without it, steps slip quietly, and the customer-facing updates stall with them.

When several people handle returns, a shared view also stops two people answering the same customer, or one promising something the other contradicts. Internal notes on each return keep the story consistent: whoever picks it up next can see exactly what was said and done.

Measuring success

Track these monthly:

  • Return-related tickets per 100 returns. The headline number. It should fall sharply once status pages and emails are in place.
  • Average days to resolve. Faster returns mean fewer “where’s my refund?” messages.
  • Time from arrival to refund. The gap most likely to cause anxiety.
  • Disputes on returned orders. Should approach zero.

Return Shipping Labels for WooCommerce: Who Pays, Which Carrier, and How to Automate It

After “can I return it?”, the next question every customer asks is: “How do I send it back, and who pays?”

It sounds like a logistics detail. It’s actually one of the most important decisions in your returns policy. It affects whether people buy in the first place, how quickly returns reach you, how many arrive with a tracking number, and how much each return costs you.

The NRF found 82% of consumers say free returns are a major purchase consideration, up from 76% the year before (NRF, October 2025). Loop’s 2026 survey found 92% say return fees influence how they shop (Loop Returns, July 2026). But free returns cost real money, and for a small WooCommerce store, paying for every return label can eat a large part of the margin on the original sale.

This guide works through the options, the true costs, the policies that balance customer expectations with margin, and how to stop emailing labels by hand.

The four return shipping models

Comparison of return shipping models for a store with 1,000 orders a month: customer arranges ($0, weakest experience), customer-paid label (about $0, good), free label for all ($1,050 a month, best), free for exchanges and store errors ($525 a month, good).

Model How it works Customer experience Your cost Your control
Customer arranges and pays Customer ships to your address their own way Weakest None Low: any carrier, often no tracking
Customer pays via your label You provide a label; its cost is deducted from the refund Good Low (admin) High: your carrier, tracked
Free prepaid label You provide and pay for the label Best Full label cost High
Conditional free returns Free for some cases (exchanges, faults, loyalty), paid for others Good Partial High

Model 1: Customer arranges and pays

The traditional default for small stores: here’s our address, send it back however you like.

Upside: no cost, no setup.
Downside: customers pick the cheapest untracked option, parcels get lost, and you argue about whether something was sent. Returns arrive unpredictably, sometimes without any reference. And many customers find the hassle a reason not to buy.

Model 2: Customer-paid label (deducted from refund)

You generate a tracked label on your carrier account and deduct its cost (or a flat fee) from the refund.

Upside: tracked returns on your carrier at your negotiated rate; the customer doesn’t need to visit a carrier counter to buy postage; low cost to you.
Downside: still a fee, which customers notice.

Model 3: Free prepaid label

You generate the label and pay for it.

Upside: the experience customers increasingly expect; converts better; returns arrive faster and tracked.
Downside: cost. If your average order is $40 and a return label costs $8, free returns on a 20% return rate add a meaningful percentage to your costs across all orders.

Model 4: Conditional free returns

Free labels where it pays for itself or where fairness demands it; paid elsewhere. Common conditions:

  • Free for exchanges, paid for refunds. This nudges customers toward keeping the revenue, and was among the incentives consumers said could steer them away from refunds in Loop’s survey (a waived exchange fee, 36%).
  • Free when it’s your fault: damaged, defective or wrong item.
  • Free for loyalty members or orders above a certain value.
  • Free during holiday season for gift purchases.

For most growing WooCommerce stores, Model 4 is the sweet spot: customers get free returns for the cases that matter most, and you avoid subsidising every change of mind.

Working out what return shipping really costs you

A quick calculation helps make the decision on numbers rather than gut feeling:

Monthly return shipping cost = orders per month × return rate × share of returns you pay for × average label cost

Example: 1,000 orders × 15% return rate × 60% you pay for (exchanges + faults) × $7 label = $630 a month.

Then set that against what free returns gain you: higher conversion (82% of shoppers weigh free returns when buying), more exchanges instead of refunds, faster returns that get stock back on sale sooner, and fewer support tickets about lost parcels.

Comparing the models on the same store

Take a store with 1,000 orders a month, a $50 average order, a 15% return rate (150 returns), and a $7 average label cost. Suppose 40% of returns are exchanges, 10% are damaged or wrong items, and 50% are change-of-mind refunds.

Model Labels you pay for Monthly cost Notes
Customer arranges 0 $0 Untracked parcels, lost returns, worst conversion
Customer-paid label 0 (fee recovered) ≈ $0 Tracked; fee visible to customers
Free for everything 150 $1,050 Best experience; highest cost
Free for exchanges + store errors 75 $525 Half the cost; nudges toward exchanges

Conditional free returns halve the cost of fully free returns in this example, while still giving free returns to the customers you most want to keep (exchanges) and the ones you owe (your errors). And because some change-of-mind refunds will become exchanges to get a free label, the real cost often ends up lower still, with more revenue kept.

Choosing a carrier and label approach

Things to look for in your return label set-up:

  • Tracking on every return label
  • Rates that reflect your volume (multi-carrier platforms often have discounted rates)
  • Label format customers can use: printable PDF, and ideally QR codes for printer-less drop-off where the carrier supports it
  • Drop-off convenience for your customers’ locations
  • Pay-on-use options, where you only pay for labels that are actually scanned (offered by some carriers and platforms, so worth asking about)
  • Generation at the right moment. On approval, not before, so you don’t pay for labels for returns you reject.

Multi-carrier platforms such as Shippo give you access to several major carriers through one account and API, and can compare rates for each label.

Packaging and drop-off instructions

A label is only half the job. Returns arrive damaged or unidentifiable surprisingly often, because customers weren’t told how to send them. Include short instructions in the approval email and on the return status page:

  • Use the original packaging if possible, or a sturdy box or mailer.
  • Include the return number on a slip inside the parcel (or print it on the label).
  • Remove or cover old shipping labels so the parcel doesn’t go back to the customer.
  • Keep the drop-off receipt until the refund arrives.
  • Send within [14] days of approval.

International returns

If you sell abroad, return shipping gets harder:

  • Cross-border labels cost more, and some carriers can’t produce return labels from every country.
  • Customs: returned goods may need paperwork marking them as returns rather than new imports, otherwise you may be charged duties on your own goods.
  • Long transit times mean more “where’s my refund?” contact.

Common approaches: offer prepaid international labels only for higher-value orders; let international customers ship at their own cost with tracking; or, for low-value items, refund without requiring a return. State your international rules separately in your policy.

The manual way (and why it doesn’t scale)

Without automation, the label process typically looks like:

  1. Customer emails asking to return.
  2. You approve by email.
  3. You log in to your carrier or shipping platform, enter the customer’s address and parcel details, buy the label, download the PDF.
  4. You email the PDF to the customer.
  5. You note the tracking number somewhere, usually not against the order.
  6. You watch for the parcel.

At five returns a week it’s tolerable. At fifty, it’s hours of copy-paste a week, with addresses mistyped and tracking numbers lost.

Automating labels with Recirco

Flow: request, approve, label generated through Shippo at the cheapest rate, customer ships and adds tracking, item received and refunded. Generating labels before approval wastes postage on rejected returns; generating on approval means only approved returns cost postage.

Recirco – Returns & Exchanges for WooCommerce (free) already removes most of the manual steps around the label:

  • Customers start returns from My Account → Returns, choosing items and reasons.
  • On approval, customers see your return address and RMA number on the return’s status page and in the approval email.
  • Customers can add their own tracking number to the return, so you know what’s in transit.
  • If a label exists, Recirco can display it to the customer. The free plugin shows labels but doesn’t generate them.

Recirco Pro adds carrier label generation:

  • Shippo integration, using the cheapest available rate by default.
  • Labels generated automatically on approval, so you never pay for a rejected return.
  • Manual label upload, for when you create a label elsewhere or use a carrier outside Shippo.
  • A provider interface for other carriers, so the label step isn’t locked to one service.

Combined with Pro’s conditional approval rules, you can implement Model 4 cleanly. For example, auto-approve exchanges and fault claims (label generated immediately, free to the customer), while holding change-of-mind refunds for review. And with analytics on value returned and reasons, you can see exactly which return types your label spend goes on.

Policy wording for each model

Customer-arranged:

Please return items to [address] using a tracked service, quoting your return number. Return postage is your responsibility, and we can’t accept responsibility for parcels lost in transit without tracking.

Customer-paid label:

Once your return is approved, we’ll email you a prepaid tracked label. [$6.95] will be deducted from your refund to cover it.

Free label:

Returns are free. Once your return is approved, we’ll email you a prepaid tracked label.

Conditional free:

Exchanges and returns of damaged, faulty or incorrect items are free: we’ll email you a prepaid label when your return is approved. For other refunds, [$6.95] is deducted from your refund for the prepaid label, or you can return the item at your own cost using a tracked service.

Reviewing your label spend

Once labels are automated, review the spend quarterly. Which reasons drive the most labels? Are exchanges growing as a share of returns? Is one product generating a disproportionate share of return shipping? Often the cheapest way to cut label cost is fixing the product page that causes the returns.

Mistakes to avoid

  • Generating labels before approval. You pay for labels on returns you then reject.
  • No tracking requirement. Lost returns turn into disputes.
  • Hidden fees. Deducting a label fee the customer didn’t know about invites complaints and “credit not processed” disputes.
  • Same rules for every reason. Charging customers to return your mistake (wrong item, damaged) is a fast way to a bad review, and in many places it isn’t allowed for faulty goods anyway.
  • Ignoring the data. If return shipping is a large cost, the best saving is often fewer returns. Look at your reasons. (Reduce your return rate)

Holiday Returns Season: How to Prepare Your WooCommerce Store for the January Surge

Every store owner plans for Black Friday. Far fewer plan for what comes after it.

Holiday purchases come back at a higher rate than the rest of the year. The NRF and Happy Returns expected 17% of holiday merchandise to be returned in 2025, against 15.8% of retail sales across the whole year (NRF / Retail Insight Network, October 2025). Gifts don’t fit, duplicates arrive, impulse sale purchases look less exciting in January.

For a WooCommerce store this creates a predictable crunch. Returns pile up in the slowest sales weeks of the year, often while your team is on holiday. Gift recipients who aren’t your customers try to return things. Extended holiday windows get applied inconsistently. And the revenue you worked so hard for in November leaks out in January.

This guide covers how to prepare: the policy decisions to make now, how to handle gift returns, how to turn holiday returns into exchanges rather than refunds, and how to keep the operation running when volume peaks.

What makes holiday returns different

Illustrative chart of sales and returns from October to February: sales peak in November and December while returns peak in January. About 17% of holiday purchases are expected to be returned (NRF and Happy Returns, 2025).

  1. Volume is concentrated. Returns from November and December purchases cluster in late December and January.
  2. Many returners didn’t buy the item. Gift recipients have no account, no order number, and no idea what was paid.
  3. Return windows get confusing. An item bought on 20 November with a 30-day window expires before Christmas, before the gift is even opened.
  4. Expectations are higher. Shoppers check holiday return policies before buying gifts, and generous policies sell.
  5. Your team is smaller. Holidays mean fewer people to process more returns.
  6. Fraud ticks up. Wardrobing around parties and events, and “gifts” bought specifically to return.

Decision 1: Extend your return window for holiday purchases

Most retailers extend returns for holiday purchases, typically letting items bought from early November be returned until mid or late January. It’s become a standard expectation and a genuine selling point in gift-buying season.

How to set it up well:

  • Decide the dates now. For example: “Items bought between 1 November and 24 December can be returned until 31 January.”
  • Publish it on product pages, the cart, checkout and your returns policy page from early November. It’s a conversion tool, so use it in your Black Friday messaging.
  • Make sure your system enforces it. If your returns system uses a fixed number of days, temporarily raise it to cover the latest date you’ll allow, then lower it again afterwards. Note the dates in your calendar so the change isn’t forgotten.
  • Remember the legal minimum still applies. EU and UK customers have at least 14 days from delivery regardless; your extended window simply goes further.

Communicate holiday dates in the right places

Customers need to see your extended window when they buy, not just when they return. Put it:

  • in a site-wide banner during November and December (“Gifts bought now can be returned until 31 January”)
  • on product pages, near the add-to-cart button
  • in the cart and checkout, where gift buyers hesitate
  • in order confirmation emails for orders placed in the holiday period
  • on your returns policy page, with exact dates

Decision 2: How you’ll handle gift returns

Gift returns: when a gift doesn't fit and the recipient has no account, either the giver starts the return from their account, or the recipient contacts you with the gift slip order number. Best outcome is an exchange or store credit, not a refund to the giver.

Gift returns are where most holiday friction lives. The person returning the item:

  • probably doesn’t have an account with you,
  • doesn’t have the order number,
  • shouldn’t see what the giver paid,
  • and usually wants an exchange or store credit, not a refund to the giver’s card.

Common approaches:

Approach How it works Trade-off
Giver handles it The original buyer requests the return from their account Simple and secure; awkward for the recipient
Gift receipt / gift order number Recipient contacts you with a gift reference; you process manually Friendly; manual work for your team
Exchange or credit only for gifts Gift returns become exchanges or store credit, never refunds to the giver Keeps revenue; avoids revealing the price; needs clear policy

Whatever you choose, write it down. “Gift returns: please ask the person who bought the gift to start the return from their account, or contact us with the order number from the gift slip and we’ll arrange an exchange or store credit.”

Recirco note: the current version of Recirco requires returns to be requested from a customer account, so gift returns work through the giver’s account or through your team handling the recipient’s request. Plan your gift-return wording around that.

Decision 3: Make exchanges and credit the easy option

January is when keeping revenue matters most: sales are slow, and every refund comes straight off the best quarter you’ve had. Holiday returns are also unusually well suited to exchanges: wrong size, wrong colour, duplicate gift.

Loop’s 2026 survey found that while 75% of consumers prefer a refund by default, 87% would consider an exchange if it were easy enough, and 39% could be swayed by bonus store credit (Loop Returns, July 2026]).

For the holiday window:

  • Show exchange first in the returns flow.
  • Offer bonus store credit (say 10%) instead of a refund, especially for gift returns.
  • Ship exchanges fast. Speed is one of the top reasons people choose exchanges.

(More on exchanges vs refunds])

Write the holiday messages now

You won’t want to write customer communications on 27 December. Draft these in advance:

Auto-reply for the support inbox:

Thanks for getting in touch. Our team is back on [date] and we’re replying in order. If you’d like to return or exchange something, you can start it now from My Account → Returns; it takes about two minutes and you’ll get your return number and address straight away. Holiday purchases can be returned until 31 January.

Approval email addition (holiday period):

Because it’s our busiest returns season, refunds may take up to [5] working days after your return arrives. Exchanges ship as soon as your return is approved.

Gift-return reply:

Thanks for letting us know. If the gift doesn’t fit, the easiest option is an exchange or store credit, so you can choose something you love. Please ask the person who sent the gift to start the return from their account, or reply with the order number on your gift slip and we’ll take care of it.

Decision 4: Staffing and service levels

Work out roughly how many returns to expect. Take your November–December order count, multiply by your normal return rate, and add a margin for the holiday uplift. Then plan:

  • Who processes returns between Christmas and mid-January, and how many hours that needs.
  • What you’ll automate. Approving routine returns automatically is the biggest time saver.
  • Target times: for example, approve within one working day, refund within three working days of arrival.
  • A holiday auto-reply that points people to the self-service returns page and states realistic timings.

A quick volume estimate

Say you shipped 3,000 orders in November and December, and your normal return rate is 12%. Holiday uplift (using the NRF’s 17% holiday figure against a 15.8% full-year rate as a rough guide) suggests your holiday rate could run around 13%. That’s roughly 390 returns, most of them landing between 26 December and the end of January, about five weeks.

That’s around 75–80 returns a week. If each takes 6 minutes to approve, receive, inspect, restock and refund by hand, that’s 8 hours a week, during a period when you may have half your normal team. Automating approvals for routine returns and using bulk actions for receiving can cut that substantially. Knowing the number in advance is what lets you plan.

Decision 5: Warehouse and restocking

  • Inspect and restock fast. January returns are often your best January stock. Items back on sale quickly can be resold, especially in clearance.
  • Restock on arrival, not on approval, so stock levels reflect what’s physically there.
  • Batch processing: set aside fixed times each day for receiving returns rather than handling them ad hoc.

Decision 6: Watch for abuse without slowing everyone down

Holiday season brings wardrobing (party outfits, event equipment) and “buy to return” behaviour. Flag rather than block: hold returns of high-value occasion items or from customers with many recent returns for a closer look, and approve the rest. (Return fraud guide)

Turning January returns into January sales

Returned holiday stock is often in perfect condition. Get it back on sale fast, ideally in your January clearance, and you recover margin from inventory that would otherwise sit in a back room until spring. A clear rhythm helps: receive in the morning, inspect and restock by lunchtime, and let your clearance pages reflect the restocked sizes the same day.

Setting it up with Recirco

Recirco – Returns & Exchanges for WooCommerce (free) handles the core of holiday returns:

  • Self-service returns portal in My Account: customers start returns themselves, any time, including when your team is off.
  • Configurable return window in days, counted from the completed, paid or created date. Raise it for the holiday period and lower it again in February.
  • Custom policy text in the portal, where you can state your holiday dates and gift-return rules.
  • Approval queue with bulk approve, reject and mark received, plus filters, search and a pending badge, built for clearing a backlog quickly.
  • Restock timing (on arrival recommended) and refunds from the return with correct tax.
  • Six editable emails so customers get updates without emailing you.

Recirco Pro adds the tools that keep holiday revenue and save time:

  • Exchanges and variant swaps: customers pick the replacement in the portal; a zero-total replacement order is created in Processing on completion.
  • Store credit with a bonus percentage and optional expiry, applied at checkout. Ideal for gift returns.
  • Conditional approval rules to auto-approve routine returns over the holidays and hold high-value or high-risk ones.
  • Carrier return labels via Shippo, generated on approval.
  • Analytics with 7/30/90/365-day ranges to compare this January with last.

Holiday returns timeline

October / early November

  • [ ] Holiday return dates decided and published
  • [ ] Gift return process written down
  • [ ] Exchange and store credit options switched on and tested
  • [ ] Return window setting adjusted (and a reminder set to change it back)

Late November – December

  • [ ] Holiday returns policy highlighted in sale messaging
  • [ ] Staffing rota for 26 December – mid January agreed
  • [ ] Auto-approval rules reviewed
  • [ ] Holiday auto-reply drafted

January

  • [ ] Daily returns processing slots
  • [ ] Restock on arrival, quickly
  • [ ] Monitor exchange vs refund share

February

  • [ ] Return window restored to normal
  • [ ] Review: volume, top reasons, exchange share, time to resolve

Return Fraud and Serial Returners: Protecting Your WooCommerce Store Without Punishing Good Customers

A post on Reddit’s ecommerce communities captured a frustration a lot of store owners share. An apparel merchant, about two years in, noticed a small group of customers who kept buying, returning, and apparently wearing items before sending them back. Returns were auto-approved with no flags and no customer history, so the pattern only became obvious after it had cost real money. Their question: how do you spot repeat return abuse before approving the refund?

The replies were revealing. Some said ban them. Some said charge for returns. One commenter claimed that “90% of problems often come from about 2% of customers”. Others pushed back: frequent returns might mean the sizing is wrong, not that the customer is dishonest.

Both sides are right, and that’s the challenge. The NRF and Happy Returns estimated that 9% of all returns in 2025 were fraudulent (NRF, October 2025). That’s a real cost. But the other 91% are honest, and the same report found 71% of shoppers are less likely to buy again after a poor returns experience. Clamp down on everyone and you lose more good customers than you stop bad ones.

This guide covers the common types of return fraud and abuse, the signals that identify them, and how to set up WooCommerce so risky returns get a closer look while honest customers sail through.

The main types of return fraud and abuse

Six return abuse types and signals: wardrobing, serial returning (often a sizing problem), empty box or item swap, false damage claims, claiming non-delivery despite delivery, and double-dipping with both a refund and a chargeback. About 9% of US returns in 2025 were estimated to be fraudulent.

Type What happens Typical signal
Wardrobing Item bought, worn or used once (an event, a photo shoot), then returned Fashion, occasion wear, cameras; returns just inside the window; signs of wear
Serial returning A customer returns a very high share of what they buy High return rate per customer over time
Empty box / wrong item returned Box returned empty, or with a cheaper or counterfeit item Weight mismatch; inspection finds wrong item
False damage claims Item claimed damaged or defective when it wasn’t Vague descriptions; no packaging photos; repeat claims
“Item not received” while receiving it Customer claims non-delivery to get a refund, or disputes with their bank Delivery confirmed; history of similar claims
Return outside the policy Late returns, used items, excluded products, pushed through by persistence Requests outside window; excluded categories
Refund double-dipping Customer requests a return refund and files a chargeback Dispute on an order already refunded

Not all of these are “fraud” in a legal sense. Serial returning and late returns are often policy abuse, and sometimes not abuse at all. Your process should treat them differently.

Step 1: Separate honest-but-expensive from abusive

Before tightening anything, look at why your heavy returners return.

  • If a customer returns lots of items with “Too small” / “Too large” reasons, your size guide may be the problem. Fix the product page and offer exchanges instead of refunds. (See reducing your return rate with reason data.)
  • If they consistently return items after events or weekends, in visibly used condition, that’s wardrobing.
  • If returns come with “Damaged” claims and no evidence, that needs scrutiny.

Return reasons and history turn a vague suspicion into a clear picture. Without them, you’re guessing, and guessing usually means treating everyone the same.

Three high returners, three different answers

Customer A has returned 6 of 9 orders this year. Every return reason is Too small, mostly on one brand of jeans. Items come back unworn with tags. Not abuse. That brand runs small. Add a sizing note to those product pages, offer an exchange, and Customer A will likely become a profitable regular.

Customer B has returned 5 of 7 orders, mostly dresses and occasion wear, each requested on a Monday or Tuesday, close to the end of the return window. Two arrived with makeup marks and creased fabric. Likely wardrobing. Hold their future returns for inspection, refund only after arrival, and enforce the condition rules in your policy.

Customer C has made three “arrived damaged” claims in two months on different products, each with a one-word description and no photos, while other customers ordering the same products report no damage. Suspicious. Require photos of the item and packaging for future claims, and hold them for review.

Three customers with high return rates, and only two of them are a problem. Reasons and history are what tell them apart.

Step 2: Make the policy do the work

Most abuse thrives on ambiguity: late returns that get approved because nobody checked the date, used items accepted because the policy didn’t say “unused”, gifts kept because nobody asked for them back. Tighten the policy text, then enforce it automatically so no one has to argue:

  • Return window counted from delivery or completion, enforced by the system rather than staff.
  • Condition rules: unworn, unwashed, tags attached, original packaging. Consider non-removable tags for occasion wear.
  • Excluded categories: final sale, personalized, intimate apparel, opened hygiene products.
  • Evidence for claims: photos required for damage and fault reasons.
  • Consequences stated plainly: “Items returned used or incomplete may be refused or refunded partially.”

([Return policy template](/blog/woocommerce-return-policy/))

Step 3: Route by risk, not by rule-for-everyone

Routing diagram: a return request goes to approve (exchanges, low value, trusted customers), flag (several recent returns, inspect on arrival), hold (high value, damage claim without detail), or reject with reason (outside window, excluded item).

The best idea from that Reddit thread, and from others like it, was risk-based routing: automate the obvious cases, and send the rest to a human with context.

Return Route
Low value, trusted repeat customer, normal reason, inside window Auto-approve
Exchange for a different size Auto-approve (revenue kept, low risk)
High-value order Hold for manual review
Customer with several recent returns Flag for review
Damage claim without detail Hold; request evidence
Outside window or excluded item Reject with a clear reason (or flag if you allow exceptions)

This keeps the experience fast for the large majority while focusing your attention where risk actually is.

Step 4: Inspect what comes back

For anything above a low-value threshold:

  • Weigh parcels against expected weight.
  • Check SKU, serial number and condition before refunding.
  • Restock only after inspection. If you restock on approval, abuse gets into your sellable stock.
  • Refund after arrival for higher-risk returns, not on approval.

A simple inspection checklist

Keep it next to wherever returns are unpacked:

  1. Match the return number to the parcel and the request.
  2. Check the item and SKU match what was ordered and requested.
  3. Check the serial number for warranty products.
  4. Check condition: tags attached, unworn, unwashed, no marks, odours or damage.
  5. Check completeness: accessories, parts, manuals, packaging.
  6. Photograph anything that fails inspection before you do anything else.
  7. Record the outcome on the return (accepted, partially accepted, refused) with a note.
  8. Restock only accepted items.

It takes a minute per parcel and gives you evidence if a customer disputes a refused or partial refund.

Step 5: Keep a record, and act on patterns

Every return should record the customer, items, reason, description, condition on arrival, decision and who made it. Patterns then become visible:

  • Customers whose returns are repeatedly refused on inspection
  • The same serial number appearing in more than one claim
  • Damage claims that cluster on one customer rather than one carrier

For genuine, repeated abuse, many stores’ terms reserve the right to refuse future orders or returns. Use it sparingly, based on records rather than hunches.

When a refund becomes a chargeback

One form of abuse sits between returns and payments: the customer requests a return, gets refunded, and disputes the original charge with their bank. Without records, you can end up refunding twice. Your defence is documentation: the return record, the refund in WooCommerce, the gateway refund ID, and the customer emails. Respond to the dispute with that evidence promptly.

What not to do

  • Don’t hide the return policy or make returns deliberately painful. You’ll lose honest customers at the checkout before any fraudster is deterred.
  • Don’t treat every high returner as a fraudster. Check reasons first.
  • Don’t refund before inspecting high-value returns.
  • Don’t let staff judge exceptions differently. Inconsistency is what serial abusers exploit.
  • Don’t refund in two places. Double refunds aren’t customer fraud, but they’re just as expensive. (See refund status mismatches.)

Setting it up in WooCommerce with Recirco

WooCommerce has no returns system, so out of the box there’s no window enforcement, no reasons, no history and no approval step. Recirco – Returns & Exchanges for WooCommerce adds them for free:

  • Return window enforcement in days, measured from the order’s completed, paid or created date. Late requests simply can’t be submitted.
  • Eligible order statuses and excluded products and categories, so final-sale and hygiene items are never offered as returnable.
  • Per-unit eligibility, so the same unit can’t be returned twice.
  • Reasons on every return, each optionally requiring an explanation, so damage claims arrive with detail.
  • Approval queue with search, filters and bulk actions. Nothing is refunded until someone approves it (unless you enable auto-refund on completion).
  • Restock timing: on arrival or on completion is the safe choice for abuse-prone categories.
  • Activity log and notes on every return: an evidence trail if a customer later disputes the charge.
  • Refunds from the return, designed to prevent duplicate refunds for the same return.

Recirco Pro adds the risk-routing layer:

  • Conditional approval rules: a set of seven conditions and four actions (approve, reject with reason, flag, hold). The first matching rule wins, and the activity log names the deciding rule, so every automated decision is explainable. Auto-approve the routine, hold the risky. (Check the Recirco documentation for the exact conditions available and map your risk signals to them.)
  • Photo uploads with claims (up to 5 photos, 5 MB each) and warranty serial-number registration, which deters false damage and warranty claims.
  • Exchanges and store credit, which give honest “wrong size” returners a better path than a refund and reduce the incentive for refund abuse.
  • Analytics: reasons ranked by count and value, most-returned products, value returned. That separates product problems from customer problems.

Note: the current version of Recirco requires customers to have an account to request a return. For abuse prevention that’s a benefit: every return is tied to a known customer and their history.

A balanced anti-abuse policy (template)

Fair returns

We want returns to be easy for our customers. To keep them that way:

  • Returns must be requested within [30] days of delivery from My Account → Returns.
  • Items must be unworn, unwashed and returned with all tags and packaging.
  • [Final-sale, personalized and hygiene items] can’t be returned.
  • Damage and fault claims need a short description and photos.
  • We inspect every return. Items returned used, damaged by the customer or incomplete may be refused or partially refunded.
  • We may decline future orders or returns where we see repeated misuse of this policy.
  • This doesn’t affect your statutory rights.

Damaged, Defective or Under Warranty: Handling WooCommerce Claims With Photos and Serial Numbers

Not every return is a change of mind. Some of the most important ones are claims:

  • “It arrived smashed.”
  • “It stopped working after three weeks.”
  • “This isn’t what I ordered.”
  • “It’s still under warranty and the motor has failed.”

These are the returns where getting it right matters most. The customer has a genuine grievance, often a legal right, and usually a short fuse. Handle it well and you keep a customer who trusts you. Handle it badly (slow, sceptical, endless emails asking for photos) and you get a chargeback, a public review, or both.

They’re also the returns most open to abuse. “Damaged on arrival” is an easy claim to make and a hard one to disprove without evidence.

This guide sets out a claims process for WooCommerce that’s fast for genuine claims, consistent for your team, and evidence-based enough to deter abuse.

Four kinds of claim (and why they need different handling)

Four claim types and evidence: damaged in transit needs item and packaging photos; faulty on arrival needs photos or video and a description; wrong item needs a photo of the item and label; warranty claims need serial number, purchase date, fault description and photos. Don't block fault claims because they're outside the return window.

Claim Typical timing Key evidence Usual resolution
Damaged in transit Days after delivery Photos of item and packaging Replacement or refund; carrier claim
Defective / faulty on arrival First days or weeks Photos/video of fault; description Replacement, repair or refund
Wrong item sent Days after delivery Photo of item and label/SKU Correct item sent; return or keep the wrong one
Warranty claim Months later Proof of purchase, serial number, fault description, photos Repair, replacement, or refund per warranty terms

Mixing them into one generic “return” flow causes problems. A warranty claim 11 months after purchase shouldn’t be rejected because it’s outside your 30-day return window. A damaged-in-transit claim shouldn’t wait until the broken item is posted back before you act.

Know your obligations first

Your warranty and your return window are not the only rules that apply. In many markets, consumer law gives buyers rights for faulty goods regardless of your policy:

  • EU: sellers are generally liable for lack of conformity that becomes apparent within at least two years of delivery (the legal guarantee), separate from the 14-day withdrawal right.
  • UK: the Consumer Rights Act gives a short-term right to reject faulty goods (30 days), then rights to repair or replacement, and further remedies after that.
  • Australia: the Australian Consumer Law’s consumer guarantees mean a major fault entitles the customer to a repair, replacement or refund, whatever your policy says.
  • US: implied warranties under state law, plus the terms of any written warranty you offer.

 This is general information, not legal advice. Check the rules for each market you sell to.

The practical takeaway: your claims process should never block a legitimate fault claim just because it’s outside your change-of-mind return window.

Designing the process

1. Let customers start a claim themselves, with the right reason

A customer with a broken item shouldn’t have to compose an email. Offer clear reasons in your returns portal:

  • Damaged in transit
  • Faulty / not working
  • Wrong item received
  • Warranty claim

Make a description required for each, so you get “the left hinge snapped when opening the box” rather than “broken”.

2. Ask for photos up front, once

The single biggest time-waster in claims handling is the follow-up email: “Could you send a photo?” Ask for photos as part of the claim, and say exactly what you need:

  • The item showing the damage or fault
  • The outer packaging (for transit damage, essential for carrier claims)
  • The shipping label (for wrong-item claims)
  • The serial number plate (for warranty claims)

3. Capture serial numbers for warranty products

For electronics, appliances, tools and anything with a meaningful warranty, record serial numbers. They let you:

  • confirm the item was bought from you, and when
  • check it’s still inside its warranty period
  • spot the same serial being claimed twice
  • identify batches with recurring faults

4. Decide when you need the item back

Collecting a broken $15 item can cost more in shipping than the item is worth. Set a threshold:

  • Below the threshold: photo evidence is enough; send a replacement or refund; customer keeps or disposes of the item.
  • Above it: item comes back (with a prepaid label) for inspection, repair or a supplier claim.

5. Respond fast to transit damage and wrong items

These are almost always your problem (or your carrier’s), and the customer did nothing wrong. Aim to approve within one working day and ship the replacement promptly. Use the photos to file the carrier claim yourself.

6. Record everything against the order

Reason, description, photos, serial number, decision, who made it, and what was sent or refunded. When the same customer claims again, or a supplier asks for evidence, it’s all in one place.

7. Feed the data back

Claims are product feedback with photos. If one product has repeated “faulty” claims, talk to the supplier. If “damaged in transit” clusters on one carrier or one packaging type, change it.

What a good claim looks like when it arrives

Compare two versions of the same claim reaching your team.

Email version: “Hi, my order arrived broken. Please help.” No order number, no photos, no detail. Your team replies asking for the order number and photos. The customer replies two days later with one blurry photo. You ask for a photo of the packaging. They’ve thrown it away. Five emails and a week later, you send a replacement anyway, without evidence for a carrier claim.

Portal version: order #7731 selected automatically from the customer’s account; item “Ceramic table lamp”; reason “Damaged in transit”; required description “Base cracked into two pieces, box crushed on one corner”; four photos attached: lamp, crack close-up, outer box, shipping label. Your team approves in two minutes, ships a replacement the same day, and files the carrier claim with the photos already in hand.

Same customer, same broken lamp. The second version took a fraction of the time, kept the customer happy, and recovered the cost from the carrier.

Using claims data to fix problems upstream

Every claim is a data point. Reviewed monthly, claims data answers questions that are otherwise expensive to investigate:

  • Is one product failing more than others? A spike in “faulty” claims on one SKU or one batch of serial numbers points at a supplier problem. Raise it with photos and serials as evidence.
  • Is one carrier or service damaging more parcels? Compare “damaged in transit” rates by shipping method.
  • Is packaging good enough? If damage clusters on fragile categories, change the packaging for those products before changing carriers.
  • Are “wrong item” claims rising? That’s a picking problem: check labelling, bin locations and new staff training.

A claims process that captures structured reasons, photos and serials turns this from guesswork into a ten-minute monthly review.

Working with your carrier on damage claims

When an item is damaged in transit, the cost usually belongs to the carrier, if you can prove it. Carriers typically want the claim filed within a set period, photos of the damaged item and the packaging, the tracking number, and proof of the item’s value. Some want the packaging kept for inspection. Because a good claims process collects photos and the order details at the moment the customer reports the damage, you can file the carrier claim the same day instead of chasing evidence weeks later.

Deterring abuse without punishing honest customers

A good claims process deters most abuse simply by asking for specific evidence consistently. Beyond that:

  • Packaging photos make “it arrived broken” harder to fake.
  • Serial number checks stop claims for items bought elsewhere and repeat claims on one unit.
  • Warranty dates from the purchase date stop out-of-warranty claims passing as in-warranty ones.
  • Rules that flag rather than reject, such as several claims from one customer in a short period, or very high-value claims, send those cases to a human without slowing everyone else.

What you shouldn’t do is make every customer jump through hoops because of a few bad actors. (More on this in return fraud and serial returners.)

Setting it up with Recirco

Claims flow: reason, required description, up to five photos, serial number for warranty products, then approval rules. Outcomes: a replacement order, a refund created from the return, or a carrier claim using the photos already collected. Everything stored on the return's activity log.

Recirco – Returns & Exchanges for WooCommerce (free) gives you the foundation:

  • A self-service returns portal in My Account, where customers pick the order, items and a reason. Recirco ships with six seeded reasons you can edit, and each reason can require an explanation. Set “Damaged”, “Faulty” and “Wrong item” to require details.
  • An admin queue with search, filters and bulk actions, so claims don’t get lost among change-of-mind returns.
  • Internal notes and customer notes, plus an activity log on every return.
  • Restock timing you choose. For damaged and faulty items, you’ll typically restock never (automatically) and decide after inspection.
  • Refunds from the return, with net and tax split correctly.

Recirco Pro adds the claims-specific tools:

  • Warranty management: set a warranty length per product, let customers register serial numbers, and calculate cover from the purchase date, so warranty claims are judged on warranty terms, not your return window.
  • Photo uploads: customers attach up to 5 photos per claim (5 MB each) when they submit, so the evidence arrives with the claim.
  • Conditional approval rules: automatically approve, reject with a reason, flag or hold claims based on conditions, with the first matching rule winning and the deciding rule recorded in the activity log. Fast-track low-value transit damage; hold high-value warranty claims for inspection.
  • Exchanges: send a replacement of the same or a different variant as a zero-total order in Processing.
  • Carrier labels via Shippo, generated on approval, for claims where you want the item back.
  • Analytics: reasons ranked by count and value, and the most-returned products. Your early-warning system for supplier quality problems.

A claims policy you can adapt

Damaged, faulty or wrong items

If your order arrives damaged, faulty or isn’t what you ordered, start a claim from My Account → Returns within [7] days of delivery. Choose the matching reason, describe the problem, and attach photos of the item and its packaging. We’ll respond within one working day and send a replacement or refund at no cost to you. For items under [$25], you won’t need to send anything back.

Warranty claims

Products marked with a warranty are covered for [12 months] from the date of purchase. Register your serial number in your account. To claim, choose “Warranty claim”, enter the serial number, describe the fault and attach photos. If we need the item back, we’ll email you a prepaid label.

This policy doesn’t affect your statutory rights.

How Much Should You Refund? Returns on Coupon, Discounted, BOGO and Free-Shipping Orders

Returning a full-price item from a single-item order is easy: refund what they paid.

Now try this one. A customer used a 20% off coupon on a three-item order that qualified for free shipping over $75. They return one item. The remaining two now total less than $75. How much do you refund?

Or: a buy-one-get-one-free deal, and they return the paid one. Or the free one. Or a gift-with-purchase promotion where they keep the gift and return the purchase.

These questions trip up store owners and support teams every day, and the answers you give can quietly cost you money (over-refunding) or customers (under-refunding and arguing). This guide works through the common discount scenarios, the principles behind fair refunds, and how to make the right amount the default.

This is practical guidance, not legal advice. Consumer law in some places sets rules on refund amounts, especially for faulty goods and statutory withdrawal rights. Check the rules where you sell.

The core principle: refund what was actually paid for the item

The fairest, most defensible rule is simple:

Refund the amount the customer actually paid for the returned item, after its share of any discount, plus or minus any shipping your policy says.

Not the list price. Not the order total divided by the number of items. The item’s share of what was paid.

The good news: WooCommerce already works this way for coupons. When a coupon is applied, WooCommerce spreads the discount across the eligible line items and stores each line’s subtotal (before discount) and total (after discount). The refund form pre-fills from the line total, the discounted amount actually paid for that line. As long as you refund through the line items rather than typing an amount, you start from the right number.

Scenario 1: Percentage coupon on the whole order

Order: 3 items at $40 each = $120. Coupon 20% off → $24 discount. Paid: $96.
Return: 1 item.

WooCommerce allocates the discount to each line: each item’s line total is $32.
Refund: $32 (plus that line’s tax, if any).

Common mistake: refunding $40, the shelf price. That over-refunds by $8 per item, and on a busy sale weekend that adds up.

Scenario 2: Fixed-amount coupon on the cart

Diagram: a $10 cart discount on an $80 item and a $20 item is spread proportionally, $8 to the first and $2 to the second, so the items cost $72 and $18. Returning the $20 item refunds $18.

Order: Item A $80 + Item B $20 = $100. Coupon $10 off cart. Paid: $90.
Return: Item B.

WooCommerce spreads a fixed cart discount across the eligible items in proportion to their price: A gets $8 of the discount, B gets $2. B’s line total: $18.
Refund: $18.

Why proportional is fair: if you gave B the whole $10 discount, you’d refund only $10 and the customer would feel cheated. If you gave none, you’d refund $20 and lose the $2 they never paid.

Scenario 3: The return breaks a minimum-spend discount

Order: 3 items at $30 = $90. Coupon “$15 off orders over $75”. Paid: $75.
Return: 1 item. The remaining $60 no longer qualifies for the coupon.

Two defensible approaches:

  • Proportional (simplest, most common): refund the returned line’s discounted amount: $25. The customer keeps the full benefit on the remaining items.
  • Recalculate (strict): the customer would have paid $60 for the two items they kept, without the coupon. They paid $75. Refund $15.

The strict approach is logically defensible, but customers often see it as a penalty, and it generates complaints. Many stores choose proportional for goodwill and simplicity. Whichever you choose, put it in your return policy (“Discounts that depended on a minimum spend may be adjusted if items are returned”) so it isn’t a surprise.

Scenario 4: Buy one, get one free (BOGO)

Order: 2 items at $30, “buy one get one free”. Paid: $30.
Return: 1 item.

How the BOGO plugin recorded the discount decides the default:

  • If it put a $30 line and a $0 line, refunding the free one gives $0 and refunding the paid one gives $30. The customer effectively gets the “free” one for nothing either way.
  • If it spread the discount (two lines at $15), each item refunds at $15.

Fair approach: treat BOGO as 50% off each item. Returning one item refunds half of what was paid ($15). The customer keeps one item for $15, which is fair since they no longer meet the “buy two” condition.

Policy tip: state it plainly: “Items bought on multi-buy offers are refunded at the price paid per item under the offer.”

Scenario 5: Bundles and kits

Order: “Starter kit” bundle of 3 products for $99 (worth $130 separately).
Return: 1 product from the kit.

If the bundle is sold as a single product, you either accept only whole-kit returns, or refund a defined portion. If it’s sold as separate line items with a bundle discount, refund the returned line’s share of the discounted price, like Scenario 2.

Policy tip: many stores make bundles returnable only as complete bundles. If that’s your rule, enforce it by making individual bundle components non-returnable through your returns system rather than arguing case by case.

Scenario 6: Gift with purchase

Order: $70 serum + free travel bag (gift with purchases over $60). Paid: $70.
Return: the serum, keeping the bag.

Fair approaches: ask for the gift back too, or deduct its value from the refund, or let it go for low-value gifts. Most stores let low-value gifts go to avoid friction, and state that gifts over a certain value must be returned with the qualifying item.

Scenario 7: Free shipping threshold

Order: 2 items totalling $80 with free shipping over $75. Paid: $80.
Return: a $30 item. The kept item ($50) wouldn’t have qualified.

Options:
– Ignore it (most common): shipping was free, nothing to adjust.
– Deduct standard shipping from the refund, since the customer no longer qualifies. This is legitimate if stated in your policy, but it’s a frequent source of complaints.

Also decide whether you refund shipping paid by the customer when they return everything. In the EU, a consumer withdrawing from a distance contract is generally entitled to a refund of the standard delivery cost (not premium delivery they chose). Elsewhere it’s your policy choice.

Scenario 8: Store credit or gift card used as payment

If part of the order was paid with store credit or a gift card, refund in the same proportions by default: card portion back to card, credit portion back as credit. That stops customers converting non-refundable credit into cash through returns.

Why getting this right matters more than it looks

The difference between refunding list price and refunding the price paid seems small on one return. Across a sale season it isn’t.

Suppose you run a 25%-off Black Friday sale, sell 2,000 items averaging $40, and see a 15% return rate: 300 returned items. If each is refunded at the $40 list price instead of the $30 actually paid, you’ve given away $3,000 you never received. That money comes straight out of margin, on top of the cost of handling the returns.

The opposite mistake costs too. Under-refund (deduct discounts the customer doesn’t understand, or argue over pennies) and you buy yourself support tickets, bad reviews and occasionally a “credit not processed” chargeback, which costs a dispute fee on top of the refund you end up giving anyway.

Consistent, explainable rules avoid both.

Explaining an adjusted refund to the customer

When your policy means refunding less than the customer expects, say so before they’re surprised by their bank statement. A short note works:

“We’ve refunded $25.00 for the returned item. That’s the amount you paid for it after your 20% discount code. The other two items keep their discount. Your refund should appear within 5–10 working days.”

Customers rarely argue with a clear explanation. They argue with a number they don’t understand.

Turning rules into defaults

Refund cheat sheet: percentage coupon, refund the line total after discount; fixed cart coupon, the line's proportional share; broken minimum spend, the discounted price or a stated recalculation; BOGO, the per-item price under the offer; bundles, whole bundle only or its share; gifts, let low-value ones go; free-shipping threshold, usually ignore.

The scenarios above are manageable when one experienced person handles every return. They fall apart when several people handle returns, each doing their own arithmetic.

Three practices keep refunds consistent:

  1. Always refund through line items, never by typing an amount into the total. WooCommerce’s line totals already include coupon allocation, and the refund form splits net and tax.
  2. Write the edge cases into your policy: minimum-spend discounts, BOGO, bundles, gifts, free-shipping thresholds. Then support can point to it.
  3. Create refunds from the return record, so the system that knows which units came back also creates the refund for those units.

How Recirco helps

Recirco – Returns & Exchanges for WooCommerce is a free returns portal and approval queue that takes the arithmetic out of individual hands:

  • Customers return specific items and quantities, chosen from their order in My Account → Returns. Only eligible units are offered.
  • Refunds are created from the return as genuine WooCommerce refunds for the returned lines, with net and tax split from the original line, so they start from the discounted amount actually paid, not the shelf price. You can still adjust the amount before refunding when your policy says so (for example, deducting a broken minimum-spend discount). Send it through the gateway or record it manually.
  • Excluded products and categories, so bundles you only accept as complete sets, final-sale items or gifts can be made non-returnable in the portal itself.
  • Duplicate-refund prevention, so the same returned unit can’t be refunded twice.
  • Notes: internal for your team, or sent to the customer, so you can explain any adjustment in writing.
  • Policy text shown in the portal, so customers see your rules on discounts and gifts before they submit.

Recirco Pro adds exchanges (often the best answer for discounted items, since a size swap keeps the original deal intact), store credit with optional bonus, and conditional approval rules to flag returns from high-value or heavily discounted orders for a closer look.

Policy wording you can adapt

Returns on discounted and promotional orders

  • Refunds are for the amount you paid for each item after any discount.
  • If a discount depended on a minimum spend or number of items and your return takes the order below it, [we’ll still refund the full amount you paid for the returned items / the refund may be adjusted to reflect the discount you no longer qualify for].
  • Items bought on multi-buy offers (e.g. buy one, get one free) are refunded at the price paid per item under the offer.
  • Bundles can only be returned complete.
  • Free gifts worth more than [$20] must be returned with the item that qualified for them.
  • Free shipping is [not deducted / deducted at our standard rate] if a return takes your order below the free-shipping threshold.

Partial Returns in WooCommerce: Refunding One Item Without Breaking Status, Tax or Stock

A worked example

Full returns are simple: everything comes back, everything is refunded, the order is closed.

Most real returns aren’t like that. A customer orders three shirts and sends one back. They order a set and return one piece. They keep the jacket but return the belt they bought with it. Partial returns are the everyday reality of returns, and they’re where WooCommerce’s refund system surprises people most.

Store owners on the WordPress.org support forums regularly run into the same confusions: a partial refund that leaves the order stuck On hold, a status change that suddenly refunds the whole order, a second refund email the customer didn’t expect, tax reports that don’t match. This guide explains how WooCommerce actually handles partial refunds, the traps to avoid, and a clean process for partial returns.

How WooCommerce handles a partial refund

On the order screen, clicking Refund opens a refund form against the order’s line items. For a partial refund you:

  1. Enter the quantity being refunded on each line (for example, 1 of 3 shirts).
  2. WooCommerce fills in the line total and tax for that quantity. You can override them.
  3. Optionally enter amounts against shipping and fee lines.
  4. Tick Restock refunded items if the goods are coming back into sellable stock.
  5. Add a reason (stored on the refund, optionally visible to the customer).
  6. Choose Refund via [gateway] to send the money, or Refund manually to only record it.

WooCommerce then creates a refund record linked to the order and to those specific line items.

What it doesn’t do for a partial refund is change the order status. That’s deliberate, and it’s the source of most confusion.

Trap 1: The status doesn’t change

Partial refunds create a refund record but leave the order status unchanged, with no partially refunded status. Then setting the status to Refunded treats the whole order as refunded, can record an extra refund and send a second email. Use a return record to describe the return.

A partially refunded order keeps whatever status it had: Processing, Completed, or On hold. There’s no built-in “Partially refunded” status.

In one WordPress.org thread, WooCommerce support confirmed this behaviour with a bank-transfer order: after a partial refund, the order stayed On hold. The store owner expected it to move on and couldn’t make it change without refunding everything.

Why it matters: anyone scanning the orders list sees a normal Completed order and has no idea part of it was returned. Reporting by status undercounts refunds.

What to do:

  • Look at refund lines on the order (shown in red under the items), not the status, to know whether something was refunded.
  • If your team relies on statuses, consider adding a custom “Partially refunded” status with an order-status plugin, as suggested in that thread.
  • Better: track the return itself as its own record (see below), so the order doesn’t have to carry that meaning.

Trap 2: Setting “Refunded” refunds everything

The same thread uncovered a second trap. For manual refunds, changing the order status to Refunded told WooCommerce the entire order was refunded. That recorded a refund for the remaining amount and triggered another refund email to the customer.

Rule: never set Refunded on a partially returned order to “tidy it up”. Refunded means the whole order.

Trap 3: Tax that doesn’t match the item

If you type a refund amount into the total box instead of using the line-item quantities, WooCommerce can’t tell which item or how much tax you refunded. Your tax reports may then show the wrong tax refunded.

Rule: always refund through the line items, using quantities, so net and tax are split correctly. If you change an amount, change the line’s net and tax fields, not just the total.

Trap 4: Discounts spread across items

If the order had a coupon, the discount is spread across the items. Refunding one item at its full list price over-refunds the customer. WooCommerce’s line totals already reflect the discount, so using the line item’s actual paid amount (which the refund form pre-fills) is safer than typing the shelf price. More on this in how much to refund on discounted orders.

Trap 5: Shipping

When one of three items comes back, do you refund any shipping? Most stores don’t: shipping was a cost to deliver the whole order. Some refund it when the return is the store’s fault (damaged, wrong item). Whatever your policy, apply it consistently and say so in your return policy. If you do refund shipping, enter it on the shipping line rather than inflating the item refund, so your shipping revenue reports stay accurate.

Trap 6: Restocking the right thing, at the right time

Restock refunded items increases stock when the refund is recorded. If you refund before the item has actually arrived, you’ve added phantom stock. If you refund after it arrives but forget the tick, stock stays low.

Rule: decide when restocking should happen (usually when the item arrives and passes inspection) and make sure only one step does it.

Trap 7: Refunding twice from two places

Partial returns are where double refunds happen most: one person refunds the item in the Stripe dashboard, another records it in WooCommerce via gateway. The customer gets the item’s value twice.

Rule: one place to refund, always the WooCommerce order (or a returns system that creates the WooCommerce refund for you).

A worked example

Worked partial refund: three T-shirts paid $67.50 after a coupon; refunding one gives $22.50. Tax of $5.40 gives a $1.80 refund share. Shipping of $5.95 isn't refunded by policy. Total refund $24.30 of a $78.85 order. Refund through line quantities, not the total box.

Trap 1: The status doesn’t change’ an

Order #6120: 3 × T-shirt at $25 = $75, 10% coupon (−$7.50), shipping $5.95, tax 8% on goods only ($5.40). Total paid: $78.85.

The customer returns one T-shirt because it’s too small.

Wrong way: a team member clicks Refund, types $25 in the refund amount box, ticks restock, and refunds via Stripe. Problems: the customer paid $22.50 for that shirt after the coupon, so they’re over-refunded by $2.50. No tax was refunded on the line, so your tax report still shows $5.40 collected on goods that partly came back. And the refund isn’t tied to a line item, so reporting can’t tell which product was returned.

Right way: click Refund, enter quantity 1 on the T-shirt line. WooCommerce pre-fills the line’s share: $22.50 net plus $1.80 tax. Shipping stays at 0 (your policy doesn’t refund shipping on partial returns). Restock ticked because the shirt arrived in sellable condition. Refund via Stripe: $24.30.

Result: the customer paid for what they kept, tax is accurate, the T-shirt is back in stock, and reports show one shirt returned. The order stays Completed, which is correct, because most of it was kept.

Partial returns over time

Customers sometimes return items from the same order in two or three separate batches. Each partial return should be checked against what’s already been returned, not just against the original order. Otherwise a customer can request a return for an item they’ve already sent back and been refunded for, and a busy team member approves it.

This is another reason to track returns as their own records: the system can see “2 of 3 already returned” and only offer the one remaining unit.

A clean partial-return process

  1. The customer requests a return for specific items and quantities, with a reason for each. Not “I’d like to return something from order #4102” by email.
  2. Eligibility is checked per item. Is each one inside the return window, not excluded, not already returned or refunded?
  3. The return is approved, and the customer gets a return number and address.
  4. The items arrive and are inspected. Restock now, only what came back in sellable condition.
  5. The refund is created from the return, through the line items, using paid amounts with net and tax split, sent through the gateway. One refund, in one place.
  6. The order keeps its status, but the return record shows exactly what came back, when, why and how much was refunded.
  7. The customer is told at each step, so nobody emails asking “did you get it?”

The key idea is to stop asking the order to describe the return. Orders describe sales. Let a separate return record describe returns.

How Recirco handles partial returns

Recirco – Returns & Exchanges for WooCommerce is free and built around exactly that idea:

  • Per-unit eligibility in the customer portal. In My Account → Returns, customers choose the order, then the specific items and quantities they’re returning, each with a reason. Only eligible units are offered: inside your return window, not already refunded, not on your excluded products or categories list. A customer who already returned one shirt can’t request the same unit twice.
  • A return record per request with its own RMA number, status and activity log, plus a panel on the order edit screen so you see the order and its returns together.
  • Restock timing you choose: never, on approval, on arrival, or on completion. Set it once, and the right step does the restocking.
  • Refunds created from the return. Recirco creates a real WooCommerce refund for the returned lines, with net and tax split from the original line, optionally sent through your gateway. Auto-refund on completion is available but off by default, and the plugin is designed to prevent duplicate refunds for the same return.
  • Seven statuses enforced by a guarded state machine, so a return can’t skip from “requested” to “refunded” by accident.
  • Six editable emails (received, admin alert, approved, rejected, completed, customer note) keep the customer informed at each step.

Your order statuses stay meaningful, your tax and stock stay right, and “what happened with this return?” has a single place to look.

Recirco Pro adds exchanges (so a partially returned item can be swapped for a different variant instead of refunded), store credit as a refund alternative, conditional approval rules, carrier return labels, and analytics on value returned and the products most often sent back.

Partial refund cheat sheet

Situation Do this Avoid this
One of several items returned Refund via line-item quantity Typing an amount in the total box
Order had a coupon Use the pre-filled paid line amount Refunding at list price
Shipping not refundable Leave shipping line at 0 Including shipping in the item amount
Shipping refundable (your error) Enter it on the shipping line Inflating the item refund
Item not back yet Wait, or refund without restocking Restocking before arrival
Want order to look “done” Leave status; check refund lines Setting status to Refunded
Money already returned elsewhere Refund manually to record it Refund via gateway (double refund)

Customer Ordered the Wrong Size? How to Handle an Exchange in WooCommerce (3 Methods)

It’s the most common return in fashion, footwear and anything with variations: the customer loves the product but ordered a medium when they needed a large.

They don’t want their money back. They want the right size. You want to keep the sale. It should be the easiest transaction in retail.

Then you open WooCommerce and look for the exchange button. There isn’t one.

You’re not alone. On the WordPress.org support forums there’s a thread from a store owner whose customer bought the wrong size and returned it for an exchange. They asked a simple question, how to edit the order to remove the wrong item and add the right one, and the thread closed with zero replies. It’s a common problem with surprisingly little good guidance.

This guide covers three ways to handle a size or colour exchange in WooCommerce, the trade-offs of each, and the mistakes that cause stock and reporting problems.

Why exchanges are awkward in WooCommerce

WooCommerce models a sale as an order with a payment. It supports two ways to change what happened afterwards:

  • Editing the order (only practical before payment or for small corrections), and
  • Refunding all or part of it.

An exchange is neither. The original sale stands: same price, same customer, same payment. But one unit of stock comes back and a different unit goes out. WooCommerce has no record type for “this item was swapped for that one”, so every method is a workaround or needs a plugin.

What a good exchange needs to get right

Whatever method you use, check it against these five requirements:

  1. Stock in: the returned variation goes back into stock, once it physically arrives and is sellable.
  2. Stock out: the replacement variation’s stock goes down.
  3. Money: the customer isn’t charged again (for a like-for-like swap), and your revenue isn’t counted twice or refunded by mistake.
  4. Fulfilment: the replacement appears in your normal picking and shipping process, with the right address.
  5. Records: anyone looking later can see what happened: what came back, what went out, and why.

Method 1: Edit the original order (small stores, low volume)

How it works: you change the line item on the original order from the wrong variation to the right one.

Steps:

  1. Wait until the original item has arrived back (or decide to ship first, see the note below).
  2. Open the order. Note: WooCommerce only lets you edit line items when the order is in an editable status (Pending payment or On hold). For a Processing or Completed order, you’d need to change the status to On hold temporarily, which may trigger emails depending on your setup.
  3. Remove the wrong item and add the correct variation at the same price. Don’t click Recalculate if it would change tax or discounts on a paid order. Adjust the line total if needed so the order total stays the same.
  4. Adjust stock manually: add one to the returned variation, subtract one from the new one (line edits don’t always adjust stock the way you’d expect).
  5. Return the order to Processing so it’s picked and shipped again.
  6. Add a clear order note: “Exchanged M → L on [date], original received [date].”

Pros: no extra orders; reports show one sale.
Cons: fiddly; easy to get stock wrong; status changes can trigger confusing emails; the history of what was originally shipped is lost except in notes; doesn’t scale.

Best for: occasional exchanges on a small store, handled by one careful person.

Method 2: Refund and reorder (the most common workaround)

How it works: refund the original item and create a new order for the replacement.

Steps:

  1. Receive the returned item.
  2. Refund the item from the original order (Refund via [gateway]) with Restock refunded items ticked.
  3. Either ask the customer to place a new order, or create one for them manually in WooCommerce → Orders → Add order, which means taking payment again or marking it paid.

Pros: stock and records are correct; uses only standard WooCommerce features.
Cons: the customer gets money back and has to buy again, and many won’t. The “exchange” quietly becomes a refund. Card fees on the original sale usually aren’t returned. If you create the new order manually and mark it paid without payment, your reports show revenue twice. And the customer waits for both the refund and the new order.

Best for: price-different exchanges where money genuinely needs to move, or when you don’t mind losing some exchanges to refunds.

Method 3: Zero-total replacement order (the clean approach)

How it works: the original order is left untouched. The returned item comes back into stock. A new order for the replacement at zero cost is created, linked to the original, and goes through your normal fulfilment.

Steps (manually):

  1. Receive the returned item and add it back to stock.
  2. Create a new order for the customer containing the replacement variation, with the line price set to 0.
  3. Set it to Processing so it’s picked and shipped like any other order. Stock for the replacement reduces normally.
  4. Add a note on both orders linking them (“Exchange for #4102” / “Replaced by #4188”).

Pros: no refund, no second charge; stock correct on both sides; replacement flows through normal shipping; clean records; revenue counted once.
Cons: manual effort per exchange; easy to forget the cross-reference notes; still depends on someone remembering to restock.

Best for: any store doing more than a handful of exchanges, especially once automated.

Comparing the three methods

Comparison of three exchange methods: editing the order, refunding and reordering, and a zero-total replacement order, across whether the customer is charged again, risk of losing the exchange to a refund, stock accuracy, revenue counting, audit trail and scalability. The zero-total replacement scores best.

Edit order Refund + reorder Zero-total replacement
Customer charged again? No Yes (or manual “paid” order) No
Risk of exchange becoming a refund Low High Low
Stock accuracy Manual, error-prone Good Good
Revenue reporting Good Risk of double-counting Good
Audit trail Notes only Two separate orders Two linked orders
Effort per exchange High Medium Medium (manual) / Low (automated)
Scales No Somewhat Yes (automated)

Ship first or wait for the return?

A policy decision you need to make:

  • Wait for the return (safest): the replacement ships once the original arrives. No risk of losing both items, but the customer waits longer, often a week or more.
  • Ship immediately (fastest): the replacement ships when the exchange is approved. Customers love it, but you carry the risk of the original never coming back.

Many stores ship immediately for repeat customers or low-value items, and wait for new customers or high-value items. Whatever you choose, apply it consistently. If you ship first, track unreturned originals and follow up.

Speed matters more than you might think. In Loop’s 2026 survey of consumers in the US, UK and Australia, speed (35%) and ease of processing (37%) were the top factors in whether people preferred an exchange over a refund, and 87% said they’d consider an exchange if the experience were easy enough ([Loop Returns, July 2026](https://www.loopreturns.com/blog/returns-revenue-gap/)).

Common exchange mistakes

  • Restocking twice. Restocking when the exchange is approved and when the item arrives.
  • Forgetting to restock at all. The returned medium sits on a shelf while WooCommerce says you’re out of mediums.
  • Charging shipping twice without telling the customer, or refunding the original shipping when you didn’t intend to.
  • Losing the link between the original and replacement orders, so nobody can answer “what happened with my exchange?”
  • Treating price-different exchanges as like-for-like. If the replacement costs more or less, money needs to move: charge or refund the difference explicitly.
  • No reason recorded. “Wrong size” exchanges are your best sizing data. If you don’t record the reason, you can’t fix the size guide.

Exchanges and your numbers

Exchanges confuse reporting if you don’t think about them up front. A few points to agree with whoever does your books:

  • Revenue: with a zero-total replacement order, the original sale is the only revenue. The replacement adds an order to your order count, but not to revenue. If your team measures performance by order count, separate exchange orders out (a consistent order note or tag helps).
  • Cost of goods: you’ve shipped two units and received one back. If the returned unit is resellable, cost of goods is unchanged; if not, it’s a write-off. Track it.
  • Shipping cost: the replacement shipment and any return label are real costs of the exchange. Many stores absorb them because the alternative, a refund, costs more.
  • Exchange rate as a KPI: the share of returns that end as exchanges rather than refunds is one of the best indicators of how much revenue your returns process keeps. Measure it monthly.

Automating size exchanges with Recirco

Flow: the customer picks a replacement size in My Account, the exchange is approved, the original returns and is restocked, the return completes, and a zero-total replacement order is created in Processing. Stock goes up for the returned medium and down for the new large. No refund, no second charge.

Recirco – Returns & Exchanges for WooCommerce gives you a free self-service returns portal in My Account, an admin approval queue, return windows, reasons and restocking rules. That covers the “item comes back” half: the customer requests the return, picks a reason such as Too small, ships it with the RMA number, and the item is restocked at the point you choose (on approval, on arrival or on completion).

Recirco Pro adds the “replacement goes out” half with exchanges and variant swaps, which is Method 3 done automatically:

  1. In the returns portal, the customer chooses exchange and picks the replacement, such as a different size or colour, themselves.
  2. You approve it in the queue (or let a conditional approval rule approve it automatically).
  3. When the return is completed, Recirco creates a zero-total replacement order in Processing, so it flows into your normal fulfilment.
  4. The returned item follows your restock setting; the replacement reduces stock like any normal order; both are tied together in the return’s activity log.

No refund, no second charge, no manual order entry, no lost link between orders, and the customer never has to place a new order themselves.

Because every exchange records a reason, Recirco Pro’s analytics then show which products and reasons drive exchanges, so you can see that, say, one style’s mediums are coming back as “too small” far more than others. That’s the cue to update the size guide. (See how to reduce your return rate using reason data.)

A simple exchange policy you can publish

Exchanges

Ordered the wrong size or colour? Request an exchange from My Account → Returns within [30] days of delivery, choose the replacement you’d like, and send the original back using the return number we give you.

Same-price exchanges are free. We’ll ship your replacement [as soon as your return is approved / as soon as your return arrives].

If the item you’d like costs more or less, we’ll [charge / refund] the difference.

How to Reduce Your WooCommerce Return Rate Using Return Reason Data

How to Reduce Your WooCommerce Return Rate Using Return Reason Data

Most advice on reducing returns is generic: “add better photos,” “include a size chart,” “write detailed descriptions.” All true. But it doesn’t tell you which products need better photos, which size chart is wrong, or whether your returns problem is actually a product problem, a shipping problem, or a fraud problem.

The answer is already in your returns. You just need to collect it and look at it.

This guide shows how to measure your WooCommerce return rate, capture useful return reasons, and turn them into fixes that bring the rate down.

What’s a “normal” return rate?

Bar chart: NRF estimated 19.3% of online sales and 15.8% of all retail sales were returned in 2025. Return reasons mapped to fixes: too small or large, add size notes and measurements; not as described, use true-to-life photos and specs; damaged, review packaging, carrier and supplier; wrong item, add barcode checks at packing.

It varies hugely by category. Apparel and footwear sit far higher than electronics accessories or consumables. As a broad benchmark, the National Retail Federation estimated 19.3% of online sales would be returned in 2025, against 15.8% for retail overall (NRF, October 2025).

Your own trend matters more than the industry average. A store going from 12% to 9% has saved real money, whatever the benchmark says.

How to calculate your return rate

Use one of these consistently:

  • By units: units returned ÷ units sold × 100
  • By value: value returned ÷ value sold × 100
  • By orders: orders with a return ÷ total orders × 100

Value-based is usually the most useful for decisions, because returning one $300 jacket matters more than returning one $8 accessory. Calculate it per product and per category, not just store-wide. Averages hide the two or three products causing most of the problem.

Step 1: Collect a reason on every return

You can’t fix what you can’t see. If returns arrive by email, reasons are scattered across threads, inconsistent, and often missing.

A good reason list is short, specific and actionable. For example:

  • Too small
  • Too large
  • Not as described / looks different from photos
  • Damaged or defective
  • Wrong item sent
  • Changed my mind / no longer needed
  • Arrived too late

Make detail required for reasons you can act on (“Damaged”: what was damaged? “Not as described”: what was different?) and optional for the rest.

One caution: shoppers don’t always tell the truth about why they return. Loop’s 2026 survey found only 39% always give the true reason for a return (Loop Returns, July 2026). “Changed my mind” is often under-reported because people pick a reason that sounds more legitimate. Look for patterns across many returns, not individual answers.

Step 2: Find your problem products

Rank products by:

  1. Number of returns
  2. Value returned
  3. Return rate (returns relative to sales, so best-sellers don’t dominate unfairly)

Then look at the reasons for the top 10. You’ll usually find a small number of products with a very clear, dominant reason.

Step 3: Match each reason to a fix

Dominant reason Likely cause Fix
Too small / too large Sizing runs off, unclear size guide Product-specific size notes (“runs small, size up”), measurements in cm/in, fit photos on models with heights
Not as described Photos or copy mislead (colour, material, scale) True-to-life photos, scale references, accurate material and dimension details
Damaged or defective Packaging, carrier, or supplier quality Better packaging; compare by carrier; raise with supplier
Wrong item sent Picking errors Barcode checks, clearer SKUs, review fulfilment process
Arrived too late Shipping estimates too optimistic Honest delivery estimates, especially near holidays
Changed my mind Impulse buying, unclear expectations Better product info, reviews, comparison content

Step 4: Fix the product page, then measure again

Make one change per product, note the date, and compare that product’s return rate and reasons over the next 30–90 days. Return data lags sales, so give it time.

Step 5: Keep an eye on speed and cost

Two more metrics worth tracking:

  • Average days to resolve a return. Slow returns create support tickets, chargebacks and unhappy customers. 71% of consumers say they’re less likely to shop with a retailer again after a poor returns experience (NRF).
  • How returns end: refund vs exchange vs store credit. Reducing returns is one lever; keeping revenue from the returns you do get is the other. (See Exchanges vs refunds.)

Don’t reduce returns by making them harder

It’s tempting to cut returns by hiding the policy, shortening the window, or making the process painful. It works briefly and costs more in the long run: fewer first-time buyers, more chargebacks, and more negative reviews. Shoppers check return policies before buying, and a hostile one loses you the sale before a return ever happens. The goal is fewer unnecessary returns, not fewer possible returns.

Collecting and analysing return reasons in WooCommerce

WooCommerce doesn’t record return reasons or track returns as their own records, so there’s nothing to report on natively.

Recirco – Returns & Exchanges for WooCommerce (free) captures a reason on every returned item through a self-service portal in My Account. It comes with six reasons pre-loaded that you can edit, and each can require an explanation. Every return is stored as a structured record in your own database, so the data is there from day one.

Recirco Pro turns that data into returns analytics:

  • Requests over time (a gap-free daily series, so quiet days show as zero rather than disappearing)
  • Value returned
  • Average days to resolve
  • Reasons ranked by count and by value
  • Most-returned products
  • Date ranges of 7, 30, 90 and 365 days

That’s exactly the data you need for steps 2 to 5: which products, which reasons, how much money, and how fast you’re resolving them.

A monthly returns review (30 minutes)

Six-step monthly loop: measure return rate by value, rank the top five returned products, read their dominant reason, fix one thing per product, wait 30 to 90 days for data, then check whether the rate dropped.

  1. Check your overall return rate by value against last month.
  2. List the top 5 most-returned products and their dominant reasons.
  3. Pick one product and make one fix.
  4. Check last month’s fix: did that product’s rate or reason mix change?
  5. Check average days to resolve, and whether it’s getting slower.
  6. Check the share of returns ending as exchange or store credit.
WooCommerce RMA Workflow: Process Returns Without Duplicate Refunds or Wrong Stock

WooCommerce RMA Workflow: Process Returns Without Duplicate Refunds or Wrong Stock

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.

The five most common return-processing mistakes

Hub diagram: one return record connected to the order (risk: wrong status), the payment (risk: refunded twice), the stock (risk: never restocked) and the customer (risk: chasing updates).

1. Inventory drift

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.

2. Duplicate refunds

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.

3. Unenforced return windows

Without a system checking dates, late returns get approved to avoid arguments.

4. No data on why items come back

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.

5. Fragmented records

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.

A clean WooCommerce RMA workflow

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.

1. Request

(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.

2. Review and approve (or reject)

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.

3. In transit

The customer ships the item and adds a tracking number.

4. Received

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.

5. Refund (or exchange, or credit)

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.

6. Completed

The return is closed, the customer is notified, and the full history stays in an activity log.

When should you restock?

Return status timeline from requested to approved, in transit, received, refunded and completed, with four restock options: never (restock by hand), on approval (fastest but stock shows before it's back), on arrival (recommended), and on completion (slowest).

If you’re not sure, use on arrival.

Getting refunds right in WooCommerce

A few things worth knowing about how WooCommerce refunds work:

  • Refund from the order, not the gateway. On the order screen, Refund via [gateway] sends the money and records the refund in WooCommerce. A refund made only in the gateway dashboard may never be recorded in WooCommerce.
  • “Refund manually” records a refund in WooCommerce without sending money. Use it when the money was already returned another way (for example, already refunded in the gateway).
  • Partial refunds need the tax split. If you refund one line item, the refund should include the correct share of that line’s net amount and tax. Getting this wrong makes your tax reports inaccurate.
  • “Restock refunded items” on the WooCommerce refund screen adjusts stock at the moment of refund. If your returns tool already restocked on arrival, don’t restock again.
  • Fully refunded orders should move to Refunded. A fully refunded order still sitting in Processing can get shipped by mistake.

Making WooCommerce enforce the workflow

The free Recirco – Returns & Exchanges for WooCommerce plugin is built around exactly this workflow:

  • Seven statuses enforced by a guarded state machine. A return can only move to a valid next status, so steps can’t be skipped or reversed by accident.
  • Restock timing you choose: never, on approval, on arrival, or on completion.
  • Refunds from the return: creates a real WooCommerce refund, optionally sent to the gateway, with net and tax split from the original line. Auto-refund on completion is optional and off by default, and the plugin is designed to prevent duplicate refunds for the same return.
  • Admin queue with search, filters, status counts, a pending badge and bulk approve, reject, mark received and delete.
  • Activity log on every return and a panel on the order edit screen, so the order and its return are in one place.
  • Internal notes or notes emailed to the customer.
  • Six editable emails covering every step.
  • Return windows, eligible statuses, excluded products/categories and reasons.
  • HPOS compatible, data in three dedicated custom tables, and no outbound calls.
  • 26 documented actions and 29 filters for developers who want to connect returns to an ERP, warehouse or helpdesk.

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.

Is your current process leaking? A quick audit

  • [ ] Can you list every open return and its status in under a minute?
  • [ ] Is there exactly one place your team issues return refunds?
  • [ ] Are returned items restocked at a consistent, defined moment?
  • [ ] Does every return have a recorded reason?
  • [ ] Can a customer see their return’s status without emailing you?
  • [ ] Are late returns rejected by the system, not by a person?

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