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 the Rate (return rate) column descending, or use the Return rate ≥ filter
3. The top of the list is your serial returners

Click into each customer’s profile. The Signal impact panel shows the Returns penalty and the reasons behind it. The Returns module builds one penalty from several pieces of evidence, then scales it by product risk and by how much order history the customer has (confidence), up to a maximum of −50:

• Return rate — at or above your critical threshold (default 60%) adds the most, the high threshold (default 40%) less, and 25% a little; rates far above your store’s own average count too
• Refund value — refunds worth 30%, 50%, or 75%+ of what the customer bought add more
• Full refunds after delivery — 2 or more delivered orders refunded in full (wardrobing)
• Other patterns — high partial refunds, returns late in the return window, the same refund reason repeated, refunded coupon orders, and linked accounts that also refund

A customer showing several of these patterns, with enough history for full confidence, lands 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 → Refunds → Return Risk Thresholds (High risk 10–90%, Critical risk 20–100%):

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: Check which products the top refunders returned. If the same product or category dominates refunds across many customers, the issue is the product, not the customers — adjust that category under Product Risk by Category on Settings → Refunds.
• 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 profile’s Recent activity and order-cohort return rate 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 Blocking → turn on
2. Verify the block message is neutral
3. Turn on Enable Notifications and leave the Blocked Checkout Alert on (Settings → Alerts & Reports → Notifications) 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 Pro automation rules. Each rule has one action, so use two rules with the same trigger and conditions:

• Trigger: Score Updated
• Conditions: Return Rate > 50 AND Total Orders > 5 AND Trust Score < 30 (Risk or Critical with the default segment cutoffs)
• Rule 1 action: Block Customer
• Rule 2 action: Send Email Notification, with your fraud team’s address as the recipient — the email links to the customer’s 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 → Alerts & Reports → Notifications → Pro Notifications. It fires when a customer has refunds on a set number of orders within a set number of days (default 3 within 30 days) — 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)