Alert on return requests by exception rather than individually: high-value items, repeated returns by one customer, and above all concentration on a single product within a short window. Individual returns are routine operational work. Concentration is the only pattern that tells you something you can fix.
Why this one is worth an interruption
Alerting on every return converts a routine process into a notification stream and teaches people to skim. The information worth interrupting somebody for is the pattern, not the event.
Concentration nearly always points at the product page rather than the product: a description that oversells, a missing or wrong size guide, images misrepresenting colour or scale, or a delivery estimate that was never realistic. All of those are cheap to fix and keep costing until somebody does.
The threshold
Exception-based. The individual return goes in the queue, not in an alert.
| Condition | Set it to | Why that number |
|---|---|---|
| Product concentration | 3 returns on one line in 14 days | The signal actually worth acting on |
| Value flag | above a value floor | Worth a person rather than a process |
| Customer pattern | 3 returns by one customer | Worth understanding, not necessarily acting on |
| Reason flag | faulty or not as described | Different problem from unwanted |
| Everything else | the returns queue, not an alert | Routine work belongs in a queue |
Who should receive it
Concentration goes to whoever owns the product page. The rest goes to whoever processes returns.
- Whoever owns product content, on the concentration trigger.
- Whoever processes returns, on value and faulty flags.
- Not the whole team. Returns are normal and broadcasting them is noise.
What to do when it fires
- On concentration, read the actual reasons given rather than the count.
- Look at the product page before looking at the product. Description, sizing and images explain most concentrated returns.
- On faulty flags, check whether it is one batch, which is a supplier conversation rather than a product one.
- Fix the page, then watch whether the rate falls. That is the only confirmation the diagnosis was right.
When not to set this alert
Do not alert on individual returns. They are routine work and belong in a queue, where they can be processed in batches.
Do not set the customer-pattern trigger if it would be used to refuse service without review. It is context for a conversation, and a customer returning often may simply be buying often.
Common questions
Should I be alerted about every return?
No. Individual returns are routine work for a queue. Alert on exceptions: concentration on one product, high value, or a faulty reason code.
What does a cluster of returns on one product mean?
Almost always a product page problem rather than a product problem: an inaccurate description, missing or wrong sizing guidance, or images that misrepresent colour or scale.
Is a customer who returns often a problem?
Not necessarily, and the pattern is context rather than a verdict. Frequent returners are often frequent buyers, and the net position matters more than the return count.