Alert when a refund exceeds a written value limit, routed to whoever set that limit. The purpose is not oversight of the person issuing it. It is that decision limits only function if crossing one is visible, and that repeated large refunds against the same product tell you something no individual refund does.
Why this one is worth an interruption
Most stores either require approval for every refund, which makes the owner a bottleneck on a task that is usually obvious, or require it for none, which means nobody ever sees the shape of what is being refunded.
A written limit with an alert at the boundary gives you both: fast decisions below it, and visibility above it. It also means the person issuing refunds knows exactly where their authority ends, which is a kindness rather than a constraint.
The threshold
Set the limit high enough that most refunds pass without approval. A limit that stops everything gets bypassed, and a bypassed limit is worse than none.
| Condition | Set it to | Why that number |
|---|---|---|
| Standard limit | generous enough to cover most refunds | Below this, no approval, no alert |
| Alert threshold | at the limit | The boundary is the interesting event |
| Owner threshold | a much higher second figure | Genuinely unusual amounts |
| Pattern flag | 3 refunds on one product in 30 days | A product problem, not a refund problem |
| Repeat customer flag | 3 refunds by one customer | Worth understanding, not necessarily acting on |
Who should receive it
To whoever set the limit, which is what makes the limit real.
- Whoever owns the refund policy, usually the owner in a small store.
- Not the person who issued it. They already know; telling them again reads as suspicion.
- Whoever owns the product, on a pattern flag rather than a single refund.
What to do when it fires
- Do nothing for a single refund within policy. The alert is a record, not a task.
- On a pattern flag, look at the product rather than the refunds.
- Review the limit itself quarterly. A limit that never fires is set too high to be useful; one that fires constantly is set too low to be respected.
- If the limit is regularly being worked around, raise it rather than enforcing it harder.
When not to set this alert
Do not set this if you have no written refund limit. The alert has no boundary to fire against and becomes a running commentary on other people's work, which is corrosive and produces nothing.
Do not route it to the person who issued the refund. It reads as surveillance, and the honest version of that intent should be a conversation instead.
Common questions
What refund limit should a small store set?
High enough that most refunds pass without approval, so the rule is respected rather than bypassed. Set a second, much higher figure for genuinely unusual amounts.
Is this alert about trust?
It should not be. Routed to the person who issued the refund it reads as surveillance. Routed to whoever set the limit, it is what makes a written decision limit function.
What does a refund pattern tell me?
Several refunds on one product in a short window is almost always a product page problem: a misleading description, wrong sizing information, or an unrealistic delivery estimate.