
Rules and ethics
How UK consumer law and CMA online sales rules change checkout and returns on each platform
Choosing an online store builder means mapping UK cancellation rights, returns windows and CMA pricing rules onto templates and refund apps.
What to take away
- An online store builder must let you show pre-contract information and cancellation rights before the customer pays.
- The Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 give a 14-day cancellation right for most online sales, and missing information extends it.
- The Consumer Rights Act 2015 sets a 30-day short-term right to reject faulty goods, separate from contract cancellation.
- The CMA enforces consumer law under the Enterprise Act 2002 and expects clear pricing, including delivery charges, from the first price shown.
- Refund apps handle labels and workflows but do not write your legal wording or fix missing checkout fields.
- Compare platforms on the fields they exposecancellation text, returns windows, delivery charge display and evidence logs.
The rules that shape checkout before any template is chosen
Consumer law in the United Kingdom sets the sequence of a checkout before design does. The customer must see certain information before they place an order. That includes your business identity, the total price with taxes, delivery costs and the cancellation right.
Pre-checkout compliance fields
- Cancellation notice before payment
- Returns address shown
- Delivery estimate at basket
- Total price with taxes
- Record of consent
A template that hides delivery costs until the final step creates a compliance problem. The CMA treats drip pricing as a misleading practice when the first price shown is not the full price. Your online store builder needs a delivery charge field that appears at the basket stage, not only at payment.
Platforms differ in where they let you place legal text. Some allow a custom block above the pay button. Others bury policy links in the footer. The right choice depends on how the platform handles pre-contract information as a checkout step, not as a static page.
For checkout fields, Shopify Plus allows checkout UI extensions for a custom block above the pay button. Lower Shopify plans offer a terms of service checkbox, order notes and footer policy links. Wix Stores and Squarespace provide a terms of service checkbox and order notes.
WooCommerce needs Checkout Field Editor or custom code. BigCommerce exposes checkout SDK fields on higher plans. Adobe Commerce includes terms and conditions.
If you sell to consumers in England, Scotland, Wales or Northern Ireland, the same core rules apply. Regional differences matter more for enforcement patterns and for returns logistics, such as postage from the Highlands or Northern Ireland.
Before choosing a platform, list the fields you must expose: cancellation notice, returns address, delivery estimate, total price and a record of consent. Then test each candidate against that list. That is the practical work behind mapping each rule to your checkout.
Consumer Contracts Regulations 2013: cancellation rights and pre-contract information
The Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 set the default cancellation period at 14 days from delivery. The trader must give clear pre-contract information, including the cancellation right, before the customer is bound.
Cancellation period and extension
- Delivery14-day cancellation period starts
- No cancellation infoperiod extends up to 12 months
If you fail to give the cancellation information, the cancellation period can extend by up to 12 months. That is why a platform's ability to show a cancellation notice at checkout matters more than the wording on a separate returns page.
Pre-contract information includes the main characteristics of the goods, the total price inclusive of taxes, delivery charges, payment arrangements and the complaint handling policy. It also includes the conditions for cancellation, including who pays return postage.
For digital content, the rules are tighter. If a customer downloads immediately, you need express consent and acknowledgement that they lose the cancellation right. A platform that cannot capture that consent in the checkout flow leaves you exposed.
Distance selling cancellation rights apply to most online sales, but there are exceptions. Bespoke goods, sealed hygiene products and event tickets are common examples. Your platform should let you flag non-cancellable items without breaking the checkout for the rest of the basket.
The regulations also ban pre-ticked boxes for extra charges. A platform that adds a default tick for insurance or a donation is not compliant. You need a checkout that requires an active choice.
Use the legislation as your baseline when you write the checkout copy. The 2013 Regulations are the source for the 14-day rule and the extended period.
Consumer Rights Act 2015 and how returns windows map onto platform templates
The Consumer Rights Act 2015 gives consumers a 30-day short-term right to reject goods that are faulty, not as described or unfit for purpose. This is separate from the 14-day cancellation right under the Consumer Contracts Regulations.
Two returns windows
14-day cancellation
- Trigger
- Change of mind
- Window
- 14 days
- After window
- No statutory right
30-day faulty goods
- Trigger
- Faulty or misdescribed
- Window
- 30 days
- After window
- Repair or replacement
A common mistake is to merge the two into one returns window. A platform template that offers only a 14-day returns window can mislead customers about their statutory rights for faulty goods.
Your returns policy should state both windows. The 14-day cancellation right applies to a change of mind. The 30-day right applies to faulty or misdescribed goods. After 30 days, the consumer may still have a repair or replacement right.
Platform templates often have a single returns window field. You can work around this by adding a custom block that explains the two windows. Check whether the template allows conditional text based on the reason for return.
For returns windows, Shopify has no native split for the 14-day cancellation and 30-day faulty goods windows. WooCommerce has no native returns window and needs RMA plugins. Squarespace and Wix have no native returns portal. Adobe Commerce has native RMA with return reasons and windows. BigCommerce has control panel returns reasons and statuses.
Refund apps can automate the label and the refund, but they usually do not distinguish between cancellation and faulty goods. You may need to set up separate return reasons so that the correct window is applied.
The Act also implies terms about goods matching the description, being of satisfactory quality and being fit for purpose. Your product pages must not contradict those terms. A store disclosure policy helps assign who writes and checks those claims.
For a worked example, imagine a customer buys a coat online and finds a broken zip after 20 days. They can reject it under the 30-day right. If they simply change their mind after 10 days, the 14-day cancellation right applies. Your checkout and returns flow must handle both.
CMA online sales rules and enforcement powers under the Enterprise Act 2002
The Competition and Markets Authority (CMA) enforces consumer protection law across the United Kingdom. Its powers come partly from the Enterprise Act 2002, which allows it to investigate and take action against unfair commercial practices.
The CMA can seek undertakings from a business or apply to court for an enforcement order. It can also issue fines under newer consumer powers. For online sellers, the practical effect is that checkout and returns processes are subject to active enforcement.
CMA online sales rules focus on transparency. Prices must be clear from the start. Delivery charges must not appear only at the final step. Returns policies must not mislead about statutory rights.
The CMA has published guidance for businesses on consumer protection. The Consumer protection guidance for businesses - GOV.UK collection brings together its advice on pricing, cancellations and unfair terms.
Enforcement can follow a pattern of complaints. If your returns page says "no refunds" without explaining statutory rights, that is a red flag. The CMA can require you to change the wording and to compensate affected customers.
Your platform should make it easy to update legal text across all storefronts. If you operate in multiple regions, such as Greater London and Scotland, you need one source of truth for the wording. This is where customer events, clocks and blank thresholds help you log when a customer saw which version.
Unfair trading rules and price claims at checkout
The Consumer Protection from Unfair Trading Regulations 2008 prohibit misleading commercial practices. That includes false price claims, fake urgency and hidden charges. The regulations apply to online retail as much as to physical shops.
Honest price display checks
- Reference price was genuinely offered
- Delivery charge shown before final step
- No hidden mandatory fees
- Countdown timers accurate
- Reviews verified
A common problem is a reference price that was never actually offered. If you show a "was" price, it must be genuine. The CMA and the Advertising Standards Authority (ASA) both watch these claims.
Checkout price claims include delivery charges, taxes and any mandatory fees. If you add a booking fee at the last step, that can be a misleading omission. The total price must be clear before the customer commits.
Countdown timers and stock messages must be accurate. A timer that resets on refresh is a misleading practice. A platform that offers these tools should let you set honest rules or disable them.
Your online store builder comparison should include how each platform handles price display. Look for fields for unit price, delivery charge, tax and any surcharges. Also check whether the platform logs the price shown at the time of order.
The 2008 Regulations also cover reviews and endorsements. Fake reviews are a misleading practice. If your platform imports reviews, you need a process to verify them.
Where refund apps help and where they leave gaps
Refund apps automate returns labels, refund processing and customer notifications. They can reduce manual work and improve the customer experience. But they do not write your legal wording or fix a checkout that hides delivery charges.
A refund app can enforce a returns window if you configure it. For example, you can set a 14-day window for change-of-mind returns and a 30-day window for faulty goods. The app can then apply the correct rule based on the reason selected.
Gaps appear when the app treats all returns the same. If it cannot distinguish between cancellation and faulty goods, you may deny a statutory right. You need to test the app against the Consumer Rights Act 2015 scenarios.
Another gap is pre-contract information. Refund apps operate after purchase. They cannot show cancellation rights at checkout. That remains a platform and theme responsibility.
Integration matters. A refund app that does not sync with your platform's order data can create mismatched records. For compliance, you want a log of what the customer was told and when they returned the item.
Use refund apps for the mechanical parts: labels, tracking, refunds. Use your platform and custom blocks for the legal parts: cancellation notice, returns policy and price display.
An online store builder comparison on cancellation, returns and pricing fields
When you compare online store builders for the United Kingdom market, focus on the fields that affect compliance. The table below sets out what to check. The platforms covered in this comparison are Shopify, WooCommerce, BigCommerce, Wix, Squarespace and Adobe Commerce.
Platform compliance fields to test
Feature
- Pre-contract block
- Custom block above pay button?
- Delivery charge field
- Shown at basket stage?
- Returns windows
- Two windows by reason?
- Refund app
- Reads return reason?
- Consent capture
- Records express consent?
- Evidence log
- Logs checkout version?
What to test
- Pre-contract block
- Delivery charge field
- Returns windows
- Refund app
- Consent capture
- Evidence log
| Platform feature | Why it matters | What to test |
|---|---|---|
| Pre-contract information block | Shows cancellation rights before payment | Can you place a custom block above the pay button? |
| Delivery charge field | Avoids drip pricing | Does the basket show delivery before the final step? |
| Returns window settings | Maps to 14-day and 30-day rights | Can you set two windows by return reason? |
| Refund app integration | Automates labels and refunds | Does the app read the return reason? |
| Price display fields | Supports honest price claims | Can you show unit price and total price? |
| Consent capture | Required for digital content | Can you record express consent for immediate download? |
| Evidence log | Supports enforcement defence | Does the platform log the checkout version shown? |
Use this table as a checklist when you demo a platform. Ask the vendor to show you each field in a test checkout. Do not accept a marketing page as evidence.
The table below gives per-platform specifics to test before you shortlist.
Pre-contract checkout fields
- Shopify
- Lower plans: terms of service checkbox, order notes and footer policy links. Shopify Plus: checkout UI extensions for a custom block above the pay button.
- WooCommerce
- Open source. Checkout Field Editor or code adds fields. Terms of service checkbox is native.
- BigCommerce
- Checkout SDK and custom fields on higher plans. Order comments available.
- Wix
- Wix Stores checkout has a terms of service checkbox and custom fields.
- Squarespace
- Checkout has a terms of service checkbox and order notes.
- Adobe Commerce
- Checkout custom fields and terms and conditions.
Returns windows
- Shopify
- No native split for the 14-day cancellation and 30-day faulty goods windows.
- WooCommerce
- No native returns window.
- BigCommerce
- Control panel returns reasons and statuses.
- Wix
- Returns managed in the order panel.
- Squarespace
- No native returns portal.
- Adobe Commerce
- Native RMA with return reasons and windows.
Typical returns tooling
- Shopify
- Loop Returns or Return Prime. Typical app pricing ranges from free to several hundred GBP per month.
- WooCommerce
- RMA plugins, for example Return Merchandise Authorization extensions.
- BigCommerce
- Customer-facing self-serve returns may need a returns app.
- Wix
- Add a returns app for self-serve labels.
- Squarespace
- Handle returns manually or via an app.
- Adobe Commerce
- RMA is built in, setup is heavier.
Typical returns app pricing ranges from free to several hundred GBP per month, depending on order volume and features.
- Pre-contract information appears before the pay button
- Delivery charges show at the basket stage
- Cancellation notice uses the 14-day wording
- Returns policy states the 30-day faulty goods right
- Refund app distinguishes cancellation from faulty returns
- Price claims have a genuine reference price
- Consent for digital content is captured and logged
A worked example: a small retailer in the West Midlands sells cosmetics online. Some items are sealed for hygiene, so they are exempt from cancellation. The platform must let the retailer flag those items at checkout without disabling cancellation for the rest of the basket.
The refund app must apply the 30-day faulty goods window for those items if they arrive damaged. The retailer uses a custom block to explain both rules, and that setup meets the Consumer Contracts Regulations and the Consumer Rights Act 2015.
When you assess platforms, also consider how they handle service standards. A store needs clear clocks for refunds and replacements. The customer events, clocks and blank thresholds approach helps you define when a refund is due and when a breach occurs.
Finally, document your decisions. If the CMA asks why your checkout showed a particular price, you need a record. A platform that logs checkout versions and consent is easier to defend than one that does not.



