Tag Archives: Approval Rules

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

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.