Midrand returns calm

What this project solved

Online sales in South Africa lead to returns, but most reverse routes break down when the details go missing. This Midrand project focused on making returns feel fair for everyone, from the customer who hands over the parcel, to the office team logging the reason, to the courier floor checking paperwork under spotlights. We worked with a courier outfit serving national retail and ecommerce labels, building a returns bay that worked even during load-shedding. Each handover ran with a documented reason code and a process built for South African shopping weeks: Black Friday peaks, awkward Highveld rains, and the everyday admin gaps between teams.

Who this returns approach fits, and where it doesn’t

If your team needs fair, transparent returns you can track from Midrand or any regional hub, this approach fits. We built it for owner-operators, SME retailers, or regional heads who want a tidy lane, not a ballooned system with every feature under the sun. If you expect a massive seasonal wave (like mass electronics recalls) or need custom integrations on day one, this may not be enough for you. It shines for regular returns, shoes, phones, office hardware, where paperwork must match parcel and customer comms need to stay practical. Teams used to going off WhatsApp alone won't get the full benefit.

How it works in practice

Each return is logged at a bench near the dispatch bay, using printed cards kept on a wall checklist. A reason code matching the customer story is assigned, wrong size, damaged, not collected, or other common cases. Operator and sender both sign off, so everyone knows the parcel’s story. Updates go to the customer in clear, local language, no walls of cryptic scan codes or tracking errors. Daily standups keep the checklist owned. The paper survives power cuts better than any tablet. In most weeks, returns are linked to outbound lanes for easier follow-up. We measured what mattered: documents attached, cards owned, and follow-up booked through the returns process. For an idea of how it looks, see how our Bakery morning Johannesburg and Cold short-hop Durban runs keep lane logic tight.

A short worked example

A customer at a mall counter in Midrand returns a parcel, wrong size, not used. The floor operator checks the parcel, marks the reason code on the printed card, and pops the card into the day’s checklist. The parcel is moved to the hub bench, where a courier confirms paperwork, updates the tracking, and flags a follow-up for the next available outbound lane. The customer gets a simple update by sending us a message with its reason code, not a dump of fifteen scan events. By Friday, the office team can see on paper and in the system which parcels need action, which are complete, and which ones are still in hand. Every return keeps a clear owner.

What to prepare before you message

For a similar calm returns run, get these ready before sending us a message. It speeds up planning and means you spend less time stuck in phone loops. When you are set, send a message through our contact form with subject “Project like Midrand returns calm” and your city.

Include a quick description of what you move, how many returns you handle most weeks, where your team is based (Midrand, Sandton, Edenvale, etc.), and what’s tripped you up before, lost paperwork, late communication, unclear handoffs. It helps us match moves and lanes to your operation, not just drop in a template.

• List your typical parcel types and volumes per week.
• Note your main hubs or collection points (mall counter, office, depot).
• Describe your current returns paperwork (cards, book, digital or none).
• Share any pain points, load-shedding, lost returns, missed handovers.
• Name who owns returns (role, not person) and their contact details.

Common pitfalls and how to dodge them

South African returns fall over when teams forget to assign lane ownership or try add new kit before the basics are stable. We saw this in Midrand, every time a checklist lost focus or someone tried to make Saturday a ‘returns catch-up’, parcels went missing. Don’t let returns become just another Saturday afterthought. Keep your scope tight, stick to reason codes customers will accept, and update with plain status notes. If power fails, paper still runs. For more on practical playbooks, see our guides to Checklists, Rhythms, and how Updates should work for local teams.