Returns reason codes

Request a Hello Logistics version through our contact form.

What returns reason codes are and who uses them

Returns reason codes are a short list of accepted codes that explain why a parcel or item did not reach its intended recipient. SME courier teams across Gauteng, Cape Town, Durban, Bloemfontein, and regional hubs use these codes to keep returns simple and avoid long explanations. Most often, these codes help teams moving under twenty bags a day with real collections and deliveries. If you run a studio, shop, or factory with regular customer handovers or collection runs, these codes will keep your paperwork short and your reasons clear.

If you need extensive returns tracking, large batch processing, or detailed photographic evidence for every return, you will need a more detailed process. Returns reason codes work best for practical, human-paced operations rather than multi-site warehouses with automated returns. Use them to orient new drivers, brief temp teams, or keep school-run logistics moving. Larger 3PL providers and teams with formal legal reviews may need a more detailed process.

How returns reason codes work on real South African floors

Each code stands for a familiar reason: customer not home, incorrect address, cancelled order, or refused on arrival. At the end of a delivery run in Germiston, Gqeberha, or Polokwane, the operator marks the return with its reason code, updates the lane card, and logs the exception. This saves time compared to typing out a long note or chasing a customer for extra detail.

For many SMEs, a simple printed list of codes pinned to a bay or taped to a clipboard works best. Mark the line that fits, strike out what does not, and move forward. No need for apps or updated software during Highveld load-shedding or coastal storms. An sent copy through our contact form keeps your move linked to your moves hub card. Operations that handle sensitive items or need to cross municipal boundaries may need to add special codes for SARS, fragile, or restricted items - send us a message for guidance before you start.

• Use codes after every failed or returned delivery.
• Mark the code on the parcel, lane card, or delivery manifest.
• Log exceptions each Friday to spot recurring issues.
• Review with the team to stop patterns before they cost you time.

Short example: returns codes in a Gauteng ops week

On Tuesday, a courier operator in Edenvale sets out with a van of parcels. By mid-morning, three packages cannot be delivered: one customer is not home, one address is missing a unit number, and one recipient cancels by phone. Back at the workshop, the operator marks each return with a code: NH (not home), IA (incorrect address), and CA (cancelled arrival). The team reviews these exceptions at the end of the week. They spot that the IA code keeps appearing in a new Polokwane housing development and ask the sales office for clearer address notes next time.

The marked return sheet is summarised in a short message through our contact form. There is no need for a detailed message trail. The office receives a tailored response, confirming if any extra action is needed for SARS paperwork or out-of-area returns.

How to prepare before sending for a tailored code pack

Start by reviewing your current returns process before sending a message through our contact form. Count the number of weekly handovers, note the types of exceptions you face, and list any sensitive goods or municipal paperwork requirements, such as for high-value, fragile, or regulated items. We recommend starting with the generic code pack, then adjusting it after your first review cycle.

It helps to include your city in the first line of your message, as returns handling can differ between Gauteng and coastal regions due to humidity, municipal office hours, or extra paperwork. Attach a photo of your latest marked returns sheet or describe the most common reasons for returns in your business. This speeds up the tailoring process.

• City or region where you operate.
• Number of returns per week.
• Most common return reasons.
• Any special requirements (fragile, perishable, SARS forms).
• Photo of your marked checklist, if possible.

Common pitfalls and how to keep reason codes useful

Returns reason codes only work if you keep the process visible and updated. Many teams print a new sheet, pin it next to the manifest, and forget it by Wednesday. Instead, date each print, name an owner for the week, and review exceptions every Friday. If Gauteng load-shedding or coastal storms disrupt your week, protect the checklist first - don't wait to update until everything else is done.

Common mistakes include inventing new codes without recording them, skipping the review, or letting one operator carry the whole process. Strong South African teams make the codes a habit, not a chore. For related processes, see our lane card template, handover script sheet, or fragile orientation marks.