Tag Archives: Inventory

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)
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