Consumer cancellation information for online sales

Many online consumer contracts carry cancellation rights, but the rules vary with the goods, services or digital content supplied and the applicable exceptions. Identify the transaction type and provide required information before the contract is made. Do not copy a blanket no-refunds statement into every checkout.

The usual cancellation framework often involves a fourteen-day period, with different starting points and conditions. Starting services early or supplying digital content can require specific requests or acknowledgements. Distinguish cancellation rights from remedies for faulty goods or poor services; a cancellation exception does not remove every consumer right.

Classify each part of the transaction

Identify whether the customer is a consumer and whether the sale concerns goods, services, digital content or a combination. A downloadable course with live coaching may need separate analysis for its components. Do not assume one checkout means one cancellation rule. Map what is supplied, when performance or delivery begins and which parts can realistically be separated if the customer exercises a right.

Check the applicable exceptions carefully against the actual product. Personalisation, perishability and other categories can have specific conditions; a business's preference to avoid returns is not an exception. The current GOV.UK distance-selling information provides a starting point for consumer information and cancellation. ^[1] Keep a product-level decision record so a new item is not automatically assigned the policy used for a different type of supply.

Give information before agreement and preserve it

Explain how to cancel, relevant timing and the practical return or refund arrangements before the contract is made. Make the information easy to find in the purchase journey and include the required confirmation in an appropriate durable form. Save the version supplied with the transaction. A later website update cannot establish what an earlier customer was told when deciding to buy.

Check order buttons, confirmation emails and support instructions together. If the checkout promises a flexible refund but the terms contain a different rule, resolve the inconsistency before launch. Do not rely on customer support to explain away contradictory wording after payment. A clear summary should accurately introduce the fuller terms rather than making a stronger promise that the operational team cannot honour.

Handle early services and immediate digital supply correctly

Starting work during a cancellation period requires careful treatment of the customer's request and relevant information. For immediate downloads or streaming, GOV.UK describes agreement and acknowledgement requirements connected with loss of the cancellation right when supply begins. ^[2] Build those steps into the actual delivery flow rather than inserting a sentence into general terms and assuming every purchase satisfies them.

Record the relevant choices and supply event without collecting unnecessary personal information. Test what happens if the customer does not request immediate supply: the system should follow the intended alternative instead of releasing content regardless. For mixed products, ensure one digital choice does not silently remove rights relating to a separate service. Obtain specific review where pricing or delivery makes the components difficult to distinguish.

Give support a request and refund workflow

Recognise a clear cancellation request even when it does not use the business's preferred wording. Record when it arrived, what was supplied and which policy version applies. Distinguish cancellation from a complaint about faulty goods or an unsatisfactory service. A transaction outside a change-of-mind cancellation right can still involve other consumer remedies; a no cancellation conclusion should not end the complaint assessment automatically.

Allocate responsibility for returns, payment refunds and access changes. Check how the payment provider reports a refund and how duplicate requests are prevented. Give customers accurate information about the outcome and any next step. Do not impose an unexplained account closure or remove access to unrelated purchases merely because one order is being reviewed.

For Website terms and cookie review, provide the product list, checkout screens, confirmations and sample cancellation cases. Use Online terms for a subscription service where recurring subscriptions add renewal questions and Contract terms for software-as-a-service suppliers if a software supplier controls digital delivery or refunds. Ask for a transaction-specific specification that developers and support staff can apply. Recheck the journey after changes in product bundles or the legal framework, because old wording may no longer match the current supply.

Give support staff a transaction timeline

When a cancellation arrives, gather the order date, the information supplied, delivery or service dates and any recorded request for early performance. Keep these facts together before deciding the response. A product label in the shop catalogue may not explain whether the customer bought goods, a service, digital content or a combination.

Use the timeline to identify the applicable rules and any unresolved evidence. Avoid asking staff to choose a standard refusal simply because an item was opened or a service account was activated. Where the position needs review, explain the next step to the customer and track the query. The response should remain consistent with the actual agreement and the legally relevant events.

Illustrative scenario

A business sells a downloadable course and a separate live consultation. It reviews each component rather than assuming the same cancellation wording applies to both. The checkout and confirmation capture the information and choices required for the actual supply, and the support team has a clear process for requests.

Preparation checklist

• Identify goods, services and digital content separately.
• Check the applicable period, start event and exceptions.
• Review early performance requests and required acknowledgements.
• Keep the pre-contract information and confirmation supplied to the customer.