Start a return
The customer finds their order by reference and postcode and selects the items coming back — no account required.
Return Platform
A returns portal your clients' customers think is your clients'.
When you handle returns on behalf of other companies, the returns journey carries their brand, not yours. The portal, the labels, the messages and the tracking page are configured per client — while routing, inspection and refund decisions stay under your control.
What the customer sees
A return journey, in the client's name.
The customer starts a return without knowing who runs the warehouse. Every step below is configured per client rather than hard-coded, which is what lets one operation serve several brands without several processes.
Reason and resolution
Quantity, reason and the resolution the customer wants, captured as structured data rather than a free-text note somebody has to interpret.
Shipping method and drop-off
The available return methods for that client, with the nearest drop-off location and a label the customer can download.
Tracking
Return status visible to the customer from the moment it is booked to the moment it is resolved.
What you control
The operation behind the portal.
Portal customisation
Branding, journey steps and messaging configured per client, so the portal reflects their brand and their returns policy.
First-mile routing rules
Which carrier, which service and which destination apply, decided by carrier, country, parcel value or weight rather than by an operator's judgement.
Admin panel
Returns and orders in one place: edit a return request, assign it to an operator, and see what is outstanding.
Inspection at the hub
Weighing, inspecting, palletising and scanning at the first hub, with the condition recorded against the return.
Refund approval
The refund decision made after inspection rather than on the customer's word, which is the difference between a returns process and a refund process.
Reporting
Return volumes by client and period, and the billing statements that follow from them.
How it is delivered
Three shapes, depending on what you already have.
White-label platform
The full portal and back office under your brand, configured per client.
API only
A returns API for retailers and platforms that already have their own customer interface and only need the returns engine behind it.
Hub equipment integration
Robots, volumeters and scanners in the returns hub working from the same records as the portal.
Running returns for more than one brand?
Tell us how many clients you handle returns for and how their policies differ. We will show you what the portal looks like per client, and where the operational work actually lands.
Book a free automation review