Returns run through the same flow.
A return is just a shipment going the other way. Motho treats it that way — raised against the original order, rated across your partners, booked and tracked in the same dashboard.
Every courier has a different way of taking a parcel back.
Forward shipping is the part everyone builds for. The moment something comes back — a customer return, a failed delivery, a wrong address — you're out of the system and into email threads with whichever courier happened to carry it.
That's where the cost hides: the parcel sits somewhere, the customer waits for a refund, and nobody can say where it is.
The parts that do the work.
Raised against the original order
A return starts from the order it belongs to, so the address, contents and original shipment stay attached to it.
Rated like any other shipment
The return leg is quoted across your connected partners rather than defaulting to whoever delivered it.
Return waybill generated
The paperwork is produced and can go straight to the customer, instead of being requested from a courier by email.
Failed deliveries in the same place
Failed handovers and undeliverable parcels appear alongside customer returns, so nothing is only tracked in someone's inbox.
Placeholder figures — to be replaced with verified platform data
Note for review: this page describes the returns flow conservatively, as a reverse shipment raised against the original order. Confirm exactly what the live returns capability does today and we'll tighten the copy to match.
Make a return boring.
Connect a store and handle the next return without opening a courier portal.
Start shipping with Motho