Tag Archives: Tax

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 Order Total Doesn’t Add Up? Fixing Coupon, Tax, Shipping and Currency Mismatches

Every WooCommerce order should satisfy a simple equation:

Items − discounts + shipping + fees + tax = order total = amount charged

Most of the time it does. But WooCommerce lets dozens of plugins change those numbers: coupons, dynamic pricing, tax services, shipping calculators, payment fees, currency switchers, gift cards. Any one of them can leave an order where the parts don’t add up to the whole, or where the whole doesn’t match what the customer was actually charged.

Nothing alerts you when this happens. The order looks normal. You only find out when an accountant can’t reconcile a month, a tax report is off, or a customer points out they were overcharged.

This guide covers the six common causes, how to find affected orders, and how to keep totals honest.

Two different problems

It helps to separate:

  1. The order doesn’t add up internally. Line items, shipping, fees and tax don’t sum to the stored order total.
  2. The order adds up, but the charge was different. The order is internally consistent, but the gateway took a different amount.

The first can be found by inspecting your own database. The second can only be found by comparing with the gateway.

The six common causes

Six causes of WooCommerce total mismatches: coupon or pricing plugin failures, tax plugin misfires, missing shipping or fee lines, currency rounding, manual edits after payment, and prices changing mid-checkout.

1. A coupon or discount plugin failed part-way

Advanced coupon, BOGO and dynamic pricing plugins modify cart items and totals during checkout. If one fails mid-calculation (an error, a timeout, a conflict with another pricing plugin), the stored line items and the stored total can disagree. Sometimes the customer is charged the discounted price but the items show full price, or vice versa.

2. A tax plugin misfired

External tax services calculate tax by calling an API at checkout. If the call times out or fails, some plugins fall back to WooCommerce’s built-in rates, to zero, or to a cached value. The order may then show tax that doesn’t match the address, or a total that doesn’t include the tax lines shown.

3. Shipping or fee lines didn’t apply

Shipping and payment fee plugins add lines to the order. If a line fails to save while the total was calculated with it (or the reverse), the order is out of balance. Often this means you undercharged for shipping.

4. Currency switcher rounding

Multi-currency plugins convert prices and round them. Rounding each line separately versus rounding the total can produce small, persistent differences, often a cent or two per order. Individually trivial; across thousands of orders, it’s a reconciliation headache. Worse, if the plugin and the gateway disagree about the currency or amount, the charge can differ from the order.

5. Manual order edits

Editing an order after payment (adding an item, changing a quantity, adjusting shipping) and clicking Recalculate can change the total, while the payment stays the same. Editing without recalculating can leave the total stale. Either way, the order no longer matches the charge.

6. Prices changed between page load and payment

Scheduled sales starting, coupons expiring or dynamic pricing rules changing while the shopper is on the checkout page can create mismatches. WooCommerce’s documentation notes that from WooCommerce 11.1, block-based checkout stops an order if the total increases between page load and Place order, asking the customer to refresh. Decreases still go through. That’s a welcome safeguard, but it doesn’t cover classic checkout, plugins that modify totals after the order is created, or the other causes above.

A worked example

Worked example: items $50, discount $5, shipping $6.95, fees $0, tax $4.16, so the expected total is $56.11. Two mismatches: a stored total of $51.11 caused by a hidden discount, and a gateway charge of $61.11 caused by a surcharge with no fee line.

Here’s a real-looking order that doesn’t add up, to show how small the signals can be.

Line Amount
T-shirt × 2 @ $25.00 $50.00
Coupon SPRING10 (10%) −$5.00
Shipping: Standard $6.95
Tax (8% on items after discount + shipping) $4.16
Expected total $56.11
Stored order total $51.11

The difference is exactly $5. On investigation, a second discount plugin also applied a $5 “first order” discount to the total, but didn’t add a visible line for it. The customer was charged $51.11, which is fine for them, but your sales report shows $50 of items, a $5 coupon, $6.95 of shipping and $4.16 of tax, which adds up to $56.11, so $5 of revenue that never existed. Multiply by every first-time customer for a quarter, and your books are noticeably wrong.

Now the opposite case: the order lines add up to $56.11, the stored total is $56.11, but the gateway shows $61.11. A payment fee plugin added a $5 surcharge at the gateway step without recording a fee line. The customer was overcharged by your records’ standards, and won’t be pleased if they notice.

Neither order would look strange in the orders list.

Multi-currency: why cents go missing

Currency switchers convert each price from your base currency and round it. The problem is where the rounding happens:

  • Convert and round each line, then add: €22.73 + €22.73 + €6.32 = €51.78
  • Add in base currency, then convert and round once: €51.77

Both are defensible. But if the plugin calculates one way and your tax report, the gateway, or a later recalculation uses the other, every order carries a cent or two of drift. Tax is particularly sensitive, because tax rounding rules (per line or per order) are set in WooCommerce → Settings → Tax and interact with the currency plugin’s own rounding.

A tolerance-based check is the practical answer: ignore differences of a cent or two, and investigate anything bigger. That’s why Ordafide’s total check has a configurable rounding tolerance rather than demanding exact matches.

Questions to ask before installing a pricing or tax plugin

  • What happens to an order if your plugin errors mid-checkout? Does checkout stop, or continue with partial data?
  • Do you add visible order lines for every discount or fee you apply?
  • Is your plugin compatible with both block and classic checkout, and with HPOS?
  • How do you handle rounding in other currencies?
  • What does your plugin do when its external API is unreachable?

A vendor who answers these clearly is much less likely to leave you with mismatched totals.

Symptoms you might be seeing

  • Accountant reports WooCommerce revenue ≠ gateway deposits by more than fees
  • Tax reports that don’t match what was collected
  • Customers saying their coupon wasn’t applied, or they were charged more than the order email shows
  • Orders where shipping shows $0 but the customer chose a paid method
  • A steady trickle of one-cent differences in multi-currency stores

How to find affected orders

Manual spot check

Open a sample of recent orders and add up items, minus discounts, plus shipping, fees and tax. Compare with the total. Then compare the total with the amount shown in the gateway for that transaction ID.

It works for a handful of orders. It isn’t practical for hundreds, and it’s the kind of job that never gets done in a busy month.

Automatic check with Ordafide (free)

Ordafide Order Integrity for WooCommerce includes an “Order total does not add up” check. For each recent order it compares items + shipping + fees + tax with the stored total and flags any order that’s out by more than a rounding tolerance you configure. That tolerance matters for multi-currency stores, so a cent of rounding doesn’t flood you with findings while real errors still show up.

Findings come with the numbers side by side and are sorted by money at risk, so a $40 missing shipping line ranks above a 2-cent rounding difference. The check reads only your own database, sends nothing anywhere, and never changes your orders.

Comparing with what was actually charged (Pro)

If an order adds up internally but the gateway took a different amount, only the gateway knows. Ordafide Pro reconciles orders against Stripe, PayPal, Square, Mollie and Razorpay with read-only API keys and flags amount disagreements between the order and the charge, alongside money with no order, paid orders with no payment, and refunds missing in WooCommerce. For accountants, Pro’s CSV/JSON audit export covers any date range.

Fixing affected orders

  1. Decide which number is right. Usually the gateway charge is the truth about money; the line items are the truth about what was sold.
  2. If the customer was undercharged: decide whether it’s worth recovering. For small amounts, often not. Add a note and fix the cause.
  3. If the customer was overcharged: issue a partial refund through the order screen (Refund via [gateway]) for the difference and apologize.
  4. If it’s a records-only problem (the charge was right, the order lines are wrong): correct the lines carefully and add a note explaining why. Avoid hitting Recalculate unless you understand what it will do with taxes and coupons.
  5. Tell your accountant about any systematic issue and when it started.

Explaining it to your accountant

When mismatches turn up, your accountant needs three things: how many orders, how much money, and since when. A clear note might read:

“Between 3 March and 18 April, a discount plugin applied an extra $5 first-order discount without recording a line. 214 orders are affected. Customers were charged correctly; our reports overstate revenue by $1,070. The plugin was removed on 18 April. Order IDs attached.”

That turns a confusing reconciliation gap into a known, bounded adjustment. It’s only possible if you can list affected orders quickly, which is exactly what an automated total check gives you. Without one, the investigation itself becomes the expensive part.

Keep a short log of pricing, tax and currency plugin changes (what changed, when, and why). When a mismatch appears, the first question is always “what changed around then?”, and the log answers it.

Preventing mismatches

  • Minimize overlapping pricing plugins. Two plugins that both change prices or discounts are the most common source of trouble.
  • Test checkout with every coupon type after updating coupon, pricing or tax plugins.
  • Check tax plugin failure behaviour. Know what your tax plugin does when its API is unreachable, and prefer plugins that block checkout over ones that silently charge the wrong tax.
  • Configure multi-currency rounding deliberately and check the gateway receives the same currency and amount as the order.
  • Lock down post-payment edits. Agree a process for editing paid orders, including whether and when to recalculate, and always add a note.
  • Use block checkout where it fits, to benefit from the total-increase protection in recent WooCommerce versions.
  • Scan regularly. A weekly Ordafide scan or its weekly summary email shows new mismatches while they’re still easy to explain.

A note for agencies

Total mismatches often start right after a client installs “just one more” discount or upsell plugin. Ordafide’s WP-CLI commands (`wp ordafide scan`, `wp ordafide findings`) let you include an order-total check in your maintenance scripts across client sites, and Ordafide Pro’s multi-store dashboard puts every store’s findings on one screen.