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 ReturnsWe 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 dashboardReview product photos and the inspection result beside the return details. The evidence helps your team understand the case before deciding whether to approve it.
Learn more about IntelligenceBuild a rule around previous customer orders or the value of a return. You choose the conditions and what happens when they match, then review the rule before saving it.
Learn more about ExchangesNo. 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