Planning returns and warranties before you launch.

Project Atlas · Field guide 05 · Reviewed 21 July 2026

Returns and warranties are usually treated as an after-sales detail. In South Africa they are a launch decision. The Consumer Protection Act gives every consumer a warranty you cannot switch off, and the party selling to that consumer carries it whether or not a returns process exists. Building the path before the first order is the difference between an orderly cost and an operational scramble.

The six-month implied warranty, in plain terms

Sections 55 and 56 of the Consumer Protection Act give every consumer sale an implied warranty of quality. Goods must be reasonably suitable, of good quality, in working order and free of defects. If a defect appears within six months of delivery, the consumer may return the goods — at the supplier's risk and expense — and choose the remedy: repair, replacement or a refund. The choice is the consumer's, not the seller's. This is separate from, and on top of, any voluntary manufacturer warranty. It is the baseline every seller in the country operates against.

Why you cannot contract out

The implied warranty is non-excludable. A blanket "no returns" notice or a voetstoots (sold as-is) clause against a consumer is void, so a returns policy that tries to refuse defective-goods returns simply does not hold. Liability is also joint and several across the chain: the importer, the distributor and the retailer can each be held responsible, which means the South African-facing seller cannot push the obligation entirely upstream to a foreign manufacturer. Section 61 adds strict product liability for harm caused by unsafe or defective goods, again shared across the supply chain. In practice, whoever sells to the consumer in South Africa owns the returns and defect obligation, regardless of what the supply agreement says.

Why returns design precedes launch

Because the obligation attaches from the first sale, the returns path has to exist before the first sale — not be assembled after complaints arrive. Designing it early also shapes earlier decisions. It affects the price waterfall, because the cost of returns, testing and repair has to be funded somewhere. It affects the operating model, because the party carrying the warranty needs to be settled deliberately. And it affects channel choice, because each marketplace has its own returns handling and timelines layered on top of the legal minimum. Treating returns as a launch workstream, rather than a support ticket, keeps all three decisions honest.

What a local returns path looks like

A workable local returns operation moves a returned unit through a defined sequence, capturing evidence at each step so cost and cause can be attributed correctly:

• Return authorisation — the customer request is logged and approved against the policy and the legal right.
• Receipt and evidence capture — the unit is received, identified and photographed, with its condition recorded.
• Triage — each unit is routed to an outcome: unopened restock, test, repair, replace, quarantine, or dispose and return to supplier.
• Warranty administration — the claim is assessed against the implied warranty and any manufacturer warranty terms.
• Repair coordination — units needing repair go to an approved repair path rather than being written off by default.
• Customer communication — the customer is kept informed and the chosen remedy is delivered.
• Supplier reporting and cost attribution — outcomes and costs are reported back so the manufacturer sees defect patterns and carries the agreed share.

The value of the sequence is not just compliance. Good evidence capture turns returns into a feedback loop: it separates genuine defects from buyer's remorse, surfaces recurring faults early, and gives the manufacturer the data to improve the product or the packaging.

Implied warranty versus manufacturer warranty

These two things coexist and are easy to confuse. The implied warranty is the statutory six-month floor that no seller can remove. A manufacturer warranty is a voluntary promise — often twelve or twenty-four months — that sits on top and can offer more. A local returns operation has to administer both: honour the statutory right regardless of the manufacturer's terms, and separately process manufacturer-warranty claims where they extend cover. The manufacturer remains responsible for funding an approved warranty policy unless the contract explicitly allocates it otherwise.

Data and cost sit behind the counter

Returns generate personal information — names, addresses, order histories — so the seller is the responsible party for that data under POPIA, and any fulfilment, repair or marketplace partner acts as an operator under a written agreement. The responsible party stays liable for an operator's breaches, so data handling in the returns path needs the same care as the goods handling. On cost, the returns line is real money: it should appear in the price waterfall and in the operating agreement, with a clear rule for who pays for defective-goods returns, who pays for change-of-mind returns, and how repair and write-off costs are shared.

A pre-launch returns checklist

• Confirm who is the South African-facing seller and therefore carries the implied warranty.
• Write a returns policy that meets the statutory minimum and never tries to exclude it.
• Define the return address, receiving process and evidence-capture standard before the first order.
• Agree the triage outcomes and an approved repair path for your product.
• Fund the returns cost in the price waterfall and allocate it in the operating agreement.
• Put an operator agreement in place for any partner that handles customer data.
• Have consumer-facing returns and warranty wording reviewed by a qualified adviser before publishing.