Ecommerce returns without the chaos: from enquiry to close

A returns process runs from the customer’s first question to a closed case. It needs one shared record, a named owner for each step, a decision on whether the customer is changing their mind or reporting a fault, and a status the customer can see. Without these, every return is handled from scratch. A customer emails on Monday at nine: ‘I want to return my jacket. I bought it two weeks ago but I don’t know where to send it.’ By Friday the same case has three threads in the inbox: one about size, one about the returns address, one about the refund. Nobody on the team knows whether anyone has replied. When someone finally rings, the customer says they have already booked a courier themselves, using a returns label they generated in case the shop did not reply. That scene is not an exception. In many ecommerce businesses it is the default: each return is handled as if it were the first.

This is the crux. Returns chaos does not come from the number of returns. It comes from the lack of a set sequence. A return has a clear start (the customer’s question), defined legal requirements (statutory timescales) and a natural end (a close with an explicit status). When the team knows these points and can tell which steps are routine and which need a human decision, handling a return stops being improvisation. This article walks through that sequence step by step: from the customer’s question, through identifying the order and the returns policy, to the notice, the exception, the status and the close.

Cancellation or complaint: the distinction that sorts everything out

Before any process is designed, the team needs to answer one question: is the customer cancelling the contract, or complaining about the goods? These are two different legal routes with two different procedures, although they look identical in the inbox: ‘I want to send it back’.

Cancellation (returning goods without giving a reason) is the customer’s right after buying at a distance: online, by phone or from a catalogue. Under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, the customer generally has 14 days from the day the goods come into their physical possession to cancel, and does not need to give a reason. The seller must refund within 14 days of receiving the goods back, or of receiving evidence that they have been sent back, and may hold the refund until then. The customer must send the goods back without undue delay, and no later than 14 days after giving notice of cancellation.

Complaint (goods that do not match the contract) is a separate route under the Consumer Rights Act 2015. Goods must be as described, of satisfactory quality and fit for purpose. A fault can come to light after the cancellation window has closed, and it is handled under different rules.

The distinction has direct operational consequences. In a cancellation, the team does not assess the reason, because the customer does not have to give one. In a complaint, it collects a description of the fault and assesses the claim. A customer who writes ‘the jacket is falling apart after a week’ does not need information about the cancellation window; they need the complaints route. A team that does not make this distinction sends customers down the wrong process and wastes time on both sides.

From enquiry to close: seven steps for a return

The seven steps below are a framework that can be adapted to any shop, whatever the platform, size or range.

1. The customer’s enquiry. A return starts with a question, not a parcel. The channel can be anything (email, phone, live chat, social media), but everything that comes in should go into one shared log of cases, not into private inboxes. The question ‘where do I send it?’ matters as much as the formal notice, because it is usually the first chance to set expectations.

2. Identifying the order. The team links the order to the customer: order number, purchase date, delivery date, items and payment. Without these it is impossible to tell whether the 14-day cancellation window is still running or has already passed. This step also checks proof of purchase and whether the order belongs to the person making the request, which protects against returns from people who are not entitled to them.

3. Rules and policy. Here the team consults not memory but the returns policy: what can be returned, who pays for postage, what the exceptions are, and how to send the item back (address, drop-off point, courier). A good policy is published in the same version that staff work from, so the team points customers to terms it knows and understands rather than answering from memory. A shop without a written returns policy pushes all of its questions onto customer service.

4. Receiving the notice. A cancellation is a unilateral statement that does not need the seller’s agreement. The GOV.UK guide to online and distance selling for businesses sets out the rules, including how cancellation works. The refund deadline runs from when the goods come back or when proof of return arrives, so log both dates.

5. Exception or escalation. Not everything is routine. The team meets disputes about the item’s condition, a missing proof of purchase, a deadline that has passed where the customer acted in good faith, or a personalised product. Categories of exception must be defined in advance, with a clear route to whoever decides. An exception is not a failure of the process; it is part of it, but it must have an owner and a deadline.

6. Status. The customer should know where their case stands: notice received, parcel on its way, goods received, refund initiated. Status is visible to the customer and to the team. Without it, every team member answers the customer with a different version of events, and the customer, knowing nothing, starts writing again across other channels with growing frustration.

7. Close. A return is only finished when the refund has gone back and the case has an explicit closed status, with a message to the customer and an internal note. Closing is not only about money. It also gives feedback to buying and the warehouse (what came back and why), which over time says more about the range than any sales report.

The whole process can be summed up in one sentence: a return is not one decision but seven small situations, each with a defined input, output and owner.

A returns policy that takes pressure off customer service

A returns policy is not a document for lawyers. It is an operational tool. If it answers customers’ questions before they ask them, enquiry volume drops and the team’s replies stay consistent. The minimum it should contain:

• The cancellation window (14 days) and how it is counted: from the day the customer receives the goods.
• How to give notice (form, email or another route) and how the customer gets confirmation that it was received.
• Return costs: who pays (by default the customer, unless you have agreed to pay) and the preferred return method.
• Refund timing (within 14 days of receiving the goods back, or proof of return) and the refund method.
• Exceptions to the right to cancel under the Regulations, such as goods made to the customer’s specification or clearly personalised, goods that deteriorate rapidly, and sealed goods that are unsealed after delivery and are not suitable for return for health or hygiene reasons.
• A separate complaints route with its own timescales, so a customer with a faulty item does not end up in the returns process.

Exceptions and escalations: where the routine ends

Most returns are routine: the window is still open, the item can be sent back, and the refund goes out on time. The rest are situations a template cannot close, and these are what determine the quality of service. A few categories are worth defining in advance.

Dispute about the condition of the item. A customer returns worn boots and the seller wants to reduce the refund for loss of value. Under the Regulations, a refund can be reduced for diminished value caused by handling beyond what is needed to check the goods (GOV.UK). Deciding what counts as beyond what is needed belongs to a person, not a template. Such a case goes to the decision-maker, and the customer receives the reasoning in writing.

Deadline passed. The notice arrived after the 14 days, but the customer was in a dispute with the courier, and there is evidence of it. The process must include a place for a decision: accept the cancellation despite the deadline, or refer the case on. Without that route, the team either refuses automatically, which causes disputes, or accepts everything, which sets a precedent.

Returns outside the process. A parcel arrives with no notice, with a sender’s address but no order number. This is not a reason to send it back. It is an exceptional case with its own route: identify the sender, try to match the parcel to an order, and decide whether to accept it.

A complaint dressed up as a return. The customer writes ‘I want to return this’, but the description reveals a fault. A team that knows the distinction from the first section redirects the matter onto the complaints route, rather than applying the cancellation window by mistake.

Every escalation has three elements: an owner (a named person, not a team), a deadline (when the reply will come) and a reason (why this is an exception). Without them, ‘escalated’ simply means the case is sitting in someone’s inbox.

A return only closes with an explicit status. ‘Closed’ means the refund has gone back, the customer knows, the team knows, and the log entry says what happened. That is the close, and only then does the team release the case. Without it, the return comes back every week in the form of a question: ‘where is my money?’

Returns handling is a process that can be described, checked and made repeatable, just like any other process in a business. If you would like to talk about tidying it up for your ecommerce operation, get in touch.

Sources: Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, Consumer Rights Act 2015, GOV.UK — online and distance selling for businesses. This article describes the rules and the operational process; it is not legal advice or a promise of results.