Every return request is screened before it is approved, and anything suspicious is raised to your team with a clear reason attached, instead of passing quietly and eating your margin.
The difference between a loss and a held claim is timing. Every return passes a risk check before any credit is issued or any label is created, so you stop the case while it is still in your hands rather than chasing it afterwards.
Learn more about ReturnsA hold pauses the decision for a person to look at, and the final call is yours.
We do not ask your team to review every return. Ordinary cases flow through automatically under your policy, and only the ones carrying risk signals wait for a human decision, with the reason for the flag written out in front of the agent.
See the dashboardOnly the flagged row waits for a person, the rest cleared under your own rules.
Every flagged case shows what the assessment was built on: unusual frequency, a high value, multiple addresses, items that always come back with no clear reason. You make the call, and the decision and its record stay with you.
Learn more about IntelligenceEvery signal is shown with its source and the decision is yours. Flagging a case raises it for review, it does not settle it.
Tightening the rules on everyone drives good customers away before it stops a single abuser. Screening separates a customer with a clean buying history from a repeated abuse pattern, so the experience stays easy for the people who earned it.
Learn more about ExchangesRefunding before the parcel arrives is your call, and you can cap it by order value.
Screening targets repeated exploitation, not ordinary returns. A customer with a clean record clears straight through without review, and if the store is at fault the return is accepted with no fee whatever the risk score says.
Read about eligibilityThe window applies to every category by default. Exceptions and extensions are set in the rules engine.
60 days for exchanges and store credit, because neither one takes revenue out of the store.
No. It raises suspicious cases for your team with the reason for the flag. Automatic rejection is an option you enable yourself, for specific cases, if you want it.
Behavioural patterns such as unusual return frequency, inconsistent addresses, high values, and products returning at an abnormal rate. The list evolves as your own return data grows.
No. Screening targets repeated exploitation alone, and store-at-fault cases are accepted with no fee. An ordinary return clears on your rules like any other.
It starts on baseline rules from day one, and sharpens as your store's return history accumulates and the patterns become clearer.
Book a demo and see how a flagged case appears to your team, and what options they have when it does.
Book a demo