Stopping Serial Returners

Serial returners — customers who refund a high proportion of what they buy — are the most common form of customer-side abuse for WooCommerce stores. This walkthrough shows how to use TrustLens to identify them, calibrate scoring to your industry, take action on existing ones, and prevent new ones from establishing the pattern. Estimated time: 30 minutes to set up; ongoing weekly review.

---

The Problem #

A serial returner places 20 orders and refunds 15 of them. Each refund individually looks legitimate — there’s a reason (sizing, color, “didn’t fit”) — but the pattern across all 20 reveals the customer is using your store as a free showroom. They cost you:

• Shipping costs (outbound and return)
• Restocking labor
• Inventory damage from used items
• Refund processing fees on credit-card transactions
• Opportunity cost on stock tied up in the cycle

Industry data suggests serial returners cost stores anywhere from 1% to 10% of gross revenue, depending on category.

---

Step 1: Identify Existing Serial Returners #

After Historical Sync completes, TrustLens has already analyzed your past orders. To find the worst offenders:

1. Open TrustLens → Customers
2. Sort by Return Rate column descending
3. The top of the list is your serial returners

Click into each customer’s profile. The signal breakdown shows their return rate signal magnitude. Look for:

• Very high rate (60%+) — the Returns module fires -40
• Wardrobing signal — 90%+ of refunds are full refunds, additional -10
• Frequency signal — 10+ total refunds, additional -5

A customer with all three signals has a combined Returns penalty of -55, putting them deep in the Risk or Critical segment.

---

Step 2: Calibrate Thresholds to Your Industry #

Before acting, verify the thresholds make sense for your category. From Settings → Modules → Returns:

Your Industry	Recommended High Threshold	Recommended Critical Threshold
General retail / Electronics	40% (default)	60% (default)
Apparel / Shoes / Fashion	50–55%	70–75%
Beauty / Cosmetics	30%	50%
Home / Bulky items	45%	65%

If your customer base is largely apparel and the defaults flag too many customers, raise the thresholds. The goal: top 5–10% of customers (by return rate) should fall into the flagged tiers, not the median customer.

---

Step 3: Investigate the False-Positive Risk #

Before blocking anyone, sanity-check the top of the list:

• Defective-batch returns: Cross-reference the Category Abuse Stats card. If a category shows store-wide elevated returns, the issue is the product, not the customers.
• Single-large-refund customers: A customer with 4 orders and 1 large refund shows 25% rate — could be legitimate B2B return.
• Recent recoveries: A customer who had a bad stretch but has placed clean orders since is reforming. Check the score trend chart.

For each top-of-list customer, the profile tells you whether the signals are real abuse or false positives. Spend an hour on the top 20 to calibrate.

---

Step 4: Decide Per-Customer Action #

Customer Profile	Suggested Action
Critical, multiple signals, no offsetting positives	Block at checkout
Risk, single dominant signal (return rate), no other modules	Hold orders for manual review
Caution, recent spike, customer has tenure	Watch; no action
Risk, defective-batch context	Allowlist temporarily until product issue resolves
Risk, legitimate B2B / drop-shipper	Allowlist

---

Step 5: Enable Checkout Blocking #

If you’ve marked customers as blocked, enforce it:

1. Settings → General → Enable checkout blocking → turn on
2. Verify the block message is neutral
3. Leave Blocked Checkout Alert email notification enabled to catch any attempt

Now any customer marked as blocked cannot complete checkout. Pre-existing orders are unaffected.

---

Step 6: Automate (Pro) #

For ongoing serial-returner detection, build a Pro automation rule:

• Trigger: Customer Score Changed
• Conditions: return_rate > 50 AND total_orders > 5 AND segment in [risk, critical]
• Actions: Block customer; Send email to fraud team with link to profile

This catches new serial returners as they cross the threshold without requiring weekly manual review.

---

Step 7: Refine With Pro Notifications #

Enable the Repeat Refunder Alert (Pro) at Settings → Notifications → Pro Notifications. It fires whenever a customer’s return rate crosses your configured threshold — gives you early visibility before the customer becomes a serial returner.

---

What to Expect #

In the first month after enforcement:

• Blocked customers may attempt checkout 2–5 times before giving up
• You’ll receive Blocked Checkout Alert emails for each attempt
• A small fraction (typically < 10%) will contact support to appeal — handle out-of-band
• Refund rate at the store level drops 1–3 percentage points (industry typical)
• Some legitimate customers may be falsely caught — handle individually, allowlist, refine

---

Ongoing Maintenance #

• Weekly: Review the Risk + Critical segment customers; act on new entries
• Monthly: Audit your allowlist; remove dormant entries
• Quarterly: Review return-rate thresholds against your customer base; tune if distribution has shifted

---

Metrics to Track #

• Total customers in Risk + Critical (target: 1–5% of scored base)
• Blocked checkout attempts per week (declining = effective deterrent)
• Store-wide return rate trend (target: declining or stable)
• Allowlist false-positive rate (audit quarterly)