Handle Cancellation Exceptions Without Blocking Faulty-Goods Returns

A reason-led returns workflow helps UK ecommerce teams apply distance-selling cancellation exceptions consistently while preserving customers’ separate rights when goods are faulty.

Identify the right type of return first

A customer may contact a retailer because they have changed their mind, because an item is faulty or not as described, or because both issues appear to overlap. Those routes should not be collapsed into a single eligible or ineligible decision. GOV.UK says online, mail and telephone customers generally have a limited right to cancel even when an item is not faulty, but it also states that a full refund must be offered where an item is faulty, not as described or does not do what it is supposed to do. The reason for the request therefore matters before an exception is considered.

Give customer-service staff a short triage sequence: record what the customer says is wrong, when the goods were received, when cancellation or rejection was communicated, and whether any seal was present and opened. Do not make the customer select a legal label. Their description of the facts should be enough to route the case for assessment. If a defect or description mismatch is alleged, move the request into the faulty-goods workflow rather than refusing it solely because the product is personalised, perishable or unsealed.

Apply each cancellation exception narrowly

Regulation 28 of the Consumer Contracts Regulations lists circumstances in which the cancellation provisions do not apply. For goods, these include items made to the consumer’s specifications or clearly personalised, goods liable to deteriorate or expire rapidly, and several other defined categories. It also says cancellation rights cease for sealed goods that are unsuitable for return for health-protection or hygiene reasons if they become unsealed after delivery. That wording points to specific facts; it is not a general licence to mark an entire product category as non-returnable.

Build exception reasons that mirror the factual tests your catalogue actually needs. For a personalised product, retain the order specification and the point at which production became customer-specific. For a rapidly deteriorating item, identify the relevant shelf-life or handling characteristic. For a hygiene-sensitive product, record whether it was sealed on dispatch, why it is unsuitable for return once unsealed, and what evidence shows that the seal was opened after delivery. These records support a consistent operational decision without pretending that a checkbox settles every legal question.

Keep product pages and portal wording precise

Broad statements such as no refunds on personalised goods or hygiene items can mislead customers because they fail to distinguish a change-of-mind cancellation from a problem with the goods. GOV.UK warns that restricting or taking away customers’ rights, or misleading them about those rights, is unlawful. Safer wording explains the relevant change-of-mind exception in plain language and immediately adds that this does not affect the customer’s rights if the item is faulty, not as described or otherwise fails to conform to the contract.

Show important limitations before purchase, then repeat them in the returns policy and the portal at the point they become relevant. A portal should let a customer report a fault even when the order is flagged as customised or the item is recorded as unsealed. Avoid an automated dead end that merely displays ineligible. Instead, state which cancellation exception may apply, summarise the recorded facts and provide a route for the customer to correct an inaccurate seal, product or personalisation record.

Create evidence and escalation controls

Use structured fields rather than free-text notes alone. Useful fields include the customer’s stated reason, product type, personalisation details, dispatch seal status, customer-reported seal status, delivery and contact dates, photographs supplied, decision route, staff member and the wording sent to the customer. Restrict access to what staff need, and follow the organisation’s retention schedule; the aim is a proportionate decision record, not an indefinite collection of customer data.

Sample refusals by exception code and review them with support, ecommerce and fulfilment teams. Look for categories where the same item is treated differently, faulty-goods reports are being misrouted, seals are not reliably checked before dispatch, or website wording promises more than the workflow delivers. Escalate ambiguous cases instead of stretching an exception to fit. This is an operational framework based on current official guidance and legislation, not legal advice; businesses should obtain advice for disputed or unusual cases.

Practical next steps