CRM for Ecommerce in South Africa: Customers, Couriers and Returns

Marketplace and own site are both real channels

Many retailers sell on a large marketplace and through their own store at the same time, with different margins, different customer data and different service expectations. Running them as two disconnected operations is how a genuinely loyal customer ends up looking like a series of unrelated first orders.

Delivery choice is part of the customer conversation

Shoppers choose between door delivery and collection points, and their questions are about a specific parcel rather than a general policy. Answering accurately requires the delivery method and status to be visible to the person replying, which is exactly what a separate courier dashboard prevents.

One customer view across channels, with the channel recorded on every order and conversation. Returns handled as owned tasks with due dates. Delivery outcomes reported by province, courier and method so the operational choice rests on evidence. A wholesale pipeline for stockist enquiries. Meeting the returns and cooling-off rights your online customers have remains your own legal obligation and sits outside the software.

Four questions. Can customer records span marketplace and own-site orders without becoming duplicates? Are returns owned tasks with due dates rather than email threads? Can delivery performance be compared by province, courier and method? And is pricing published per user, so a six-person team is not routed into an enterprise quote before seeing the product work.

A courier dashboard reports the parcel and a store platform reports the order. Neither one owns the stockist enquiry, the overdue return or the customer who has not bought since a bad delivery in March.

The clock starts before anyone reads the email

A return request that arrives on a Friday afternoon and is opened on Tuesday has already consumed a meaningful part of the period you have to handle it. That is why the request needs to become an owned task the moment it lands rather than a message in a queue. The owner, the due date and the order history in one place mean the decision is made on the facts, and the customer receives an answer while they are still reasonable about it.

Collection, refund and replacement are different paths

Treating every return as one process is what makes them slow. A faulty item, a change of mind, a wrong size and a parcel that never arrived need different evidence, different courier arrangements and different finance steps. Recording which path a request is on, with the step it is waiting at, means nobody has to reconstruct the story before acting, and a request stuck waiting on a collection is visibly stuck rather than silently ageing.

The pattern in the reasons is worth more than the individual case

One return is an incident. Twenty returns on the same product for the same reason is a listing problem, a sizing problem or a packaging problem, and it is costing far more than the refunds suggest. Because reasons are recorded in a fixed set rather than as free text, the pattern is visible in a month rather than discovered a year later when someone finally reads the notes.

Read more: industry pipelines, follow-up sequences, the shared chat inbox, AI lead scoring, CRM for small business, pricing.