Most customers who return something are not a problem. A small number return so often, or in such a specific way, that they cost you more than they spend. Here is how to tell the difference, what patterns to look for, and what to do once you find one.
Frequent is not the same as abusive
A high number of returns alone does not make someone a serial returner. A loyal customer who orders every month and sends back one item in five can still be among your most profitable. Look at what the customer keeps, not only at what comes back.
- Net spend: Total paid minus total refunded, over a fixed period
- Return share: Items returned divided by items ordered
- Cost per return: Shipping, handling and any stock you could not resell
Patterns worth a closer look
No single signal proves abuse. Each of these is a reason to open the customer's order history and read it, not a reason to refuse a return.
- Bracketing: The same item ordered in several sizes or colors, with most sent back
- Worn and returned: Items come back used, often soon after a weekend or an event
- Reason mismatch: "Defective" or "not as described" claims on items nobody else complains about
- Missing items: Parcels that arrive lighter than expected or with a different item inside
- Many accounts: Several customer records that share an address
Build the list from your own data
Your orders already hold what you need. Pick a period, such as the last twelve months, and work out the numbers per customer. Review the top of the list by hand before you act on anyone.
| What to pull | Why it helps |
|---|---|
| Orders and refunds per customer | Shows net spend and return share |
| Return reasons | Shows repeated or unlikely claims |
| Condition notes from inspection | Shows wear, missing tags or missing parts |
| Shipping addresses | Shows linked accounts |
Respond in proportion
Start with the lightest response that fixes the problem. Keep the firmer steps for clear, repeated abuse.
- Fix the cause: Add a size guide or fit notes where bracketing clusters
- Change the outcome: Offer an exchange or store credit in place of a refund, if your policy allows it
- Review manually: Move the customer's future requests to a manual check
- Decline: Refuse returns that fall outside your written policy, and say which clause applies
For choosing between outcomes, see refund, exchange or store credit.
Put it in your policy and apply it evenly
You can only enforce what your policy says. State that you inspect returned items and may refuse returns that show wear or fall outside the terms. Consumer protection and return rules vary by country and US state, so check what applies where you sell before you limit or refuse returns for a customer. Apply the same test to everyone, based on behavior and order history, and keep a dated note of why each decision was made.
See how to write a Shopify return policy for the wording.
Doing this at scale
ReturnSage reads your full return policy plus the order and customer context for each return request created in Shopify. It recommends approve, exchange, store credit, deny or escalate, with a confidence score, risk flags, the policy clauses it relied on and a draft reply. You decide with one click, and every decision is logged. See ReturnSage.