Every return scored before it's approved.
The instant a return is submitted, a shared risk engine scores it 0–100 and assigns a level. Scoring runs before your automation rules, so a rule can hold or decline based on the score. Because the dashboard and the rules engine use the same engine, they never disagree.
- 0–100 risk score computed at submit time
- Low / medium / high risk level
- Flags for wardrobing, return velocity, and value concentration
- Flags for address mismatch and serial bracketing
- Deterministic engine shared by the dashboard and rules
One shopper, many accounts — linked.
Returner builds a tenant-local identity cluster that links the same person across different emails, phone numbers, and addresses. At scoring time it counts how many accounts a shopper is connected to and aggregates their whole history, so spreading returns across throwaway accounts no longer hides the pattern.
- Links emails, phones, and addresses into one identity
- Cluster-wide 90-day return count
- 7-day return velocity across the cluster
- Declined count and account age
- Counts linked accounts at scoring time
Your thresholds. Your call.
Risk controls stay in your hands. Flip the master toggle on, set the high-risk threshold, and decide what happens next: auto-flag high-risk returns for review, or — when you're ready — auto-block them outright. Risk conditions are also available inside the automation rules, and you can flag individual customers by hand.
- Master risk toggle
- High-risk threshold, 0–100 (default 70)
- Auto-flag high-risk returns for manual review
- Optional auto-block of high-risk returns (off by default)
- Use risk conditions inside automation rules
- Manual per-customer flags