Ecommerce platforms market entry checklist for England

Most rules cited here apply across the UK; the England references are about where the merchant is established. Use this ecommerce platforms market entry checklist before an England merchant signs, configures or migrates an ecommerce service. A single failure can justify hold. Supplier assurances and a polished demonstration do not replace evidence from the merchant's exact journey.

What to take away

A single failure in the merchant journey can justify holding the platform entry.
Supplier assurances and demonstrations do not replace evidence from the merchant's exact journey.
Reconcile test orders across platform, processor, fulfilment and ledger without live customer funds.
Record a publication-day recheck for controller-processor contract guidance after the Data (Use and Access) Act.
Issue go only when every required owner signs dated evidence for the same configuration.

Define the operation

Name the legal merchant, trading name, England establishment evidence, customer population, goods or services, sales territories and contracted parties. For a limited company, check its Companies House entry and company number.
Map direct storefront, marketplace, payment, fulfilment, marketing, analytics and support systems separately.
Record the exact supplier edition, research date, currency, VAT basis, billing unit, term, limits, connected services and unknowns.

Compare platform candidates

Use the same evidence sheet for each shortlisted candidate. Shopify and BigCommerce are hosted ecommerce platforms; WooCommerce is an open-source ecommerce plugin for WordPress; Wix and Squarespace combine hosted site-building with commerce. These are examples, not a ranking: compare each supplier's current edition, contracting party, checkout, exports, integrations, accessibility, security, support and exit terms.

How the named platforms compare against the checklist

The platform model decides which checklist items sit with the supplier and which sit with you.

Shopify and BigCommerce.Both host the store and checkout, so one supplier is the contracting party for storefront and checkout. Check the payment route (their own payment service or a third-party gateway), the export formats and the data processing terms.
WooCommerce.The plugin is free software, so the contracts are separate: your host, payment provider and extensions. Hosting, security, backups and accessibility of the theme are yours to prove.
Wix and Squarespace.Both combine hosted site building with commerce. One supplier is the contracting party, but exports and checkout customisation are narrower, so test exit and checkout wording early.

On any of them, run the same journey tests and keep the dated evidence sheet.

GOV.UK's online and distance selling guidance is a starting point for seller information, payment action and order-step requirements. Check the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 and the Consumer Rights Act 2015 against the actual offer and territorial scope; qualified counsel must assess how they apply.

Prove the catalogue and customer journey

Trace every sampled description, price, promotion, image, stock state and delivery promise to an owner and dated source.
Link regulated or safety-sensitive goods to product, supplier and corrective-action evidence.
Run synthetic cases for browse, basket, checkout, confirmation, cancellation, return, refund and complaint. Test the displayed total, delivery charges, payment options, order-button wording and failed-payment route; save expected and actual results.

The Office for Product Safety and Standards business guidance addresses safe products and traceability, with a Great Britain and Northern Ireland distinction. For consumer-facing claims and omissions, check the CMA's unfair-practices guidance and the relevant provisions of the Digital Markets, Competition and Consumers Act 2024.

Separate payment and tax evidence

Identify the legal payment provider, settlement account, relevant authorisation or registration record, deductions, reserves, refund states, disputes and failure route.
Test the provider's applicable Strong Customer Authentication (SCA) flow, including 3-D Secure where used, and the failed-authentication route.
Reconcile each test order across platform, processor, fulfilment and ledger records without live customer funds.
Ask qualified advisers to record VAT, customs, accounting and invoice assumptions. Do not accept a platform tax setting as a conclusion.

The FCA explains how to check non-bank payment providers: use the FCA Register, also known as the Financial Services Register, to check a provider's status where relevant and confirm what protections apply. HMRC VAT Notice 700/21, Keeping VAT records, gives the accounting owner guidance on required VAT records.

Control data, tracking and rights

Map purposes, lawful bases, controller and processor roles, sub-processors, transfers, retention, deletion and incident contacts against the UK GDPR.
Inventory cookies, pixels, scripts and tags. Check applicable Privacy and Electronic Communications Regulations 2003 (PECR) requirements and verify that configured choices match actual behaviour.
Check whether the organisation must pay the ICO data protection fee; verify its status in the ICO's Register of Fee Payers where required.
Export catalogue, orders, customer records, preference evidence and content in usable formats. Keep the statutory personal-data portability test separate from commercial export promises.
Record ownership or permission for copy, photography, code, themes, databases and trade marks.

The ICO's storage and access guidance supplies the tracking review baseline. Its controller-processor contract guidance is under review after the Data (Use and Access) Act, so record a publication-day recheck.

Test accessibility, security and exit

Complete representative keyboard, screen-reader, zoom, error-recovery and assisted-support tasks across the whole purchase route; use WCAG 2.2 AA as a practical test benchmark.
Restrict administrator access, enable suitable authentication, protect recovery routes and retain an independent emergency contact.
Restore an authorised export into a controlled environment and reconcile sampled counts.
Document support severity, evidence owner, escalation, supplier failure, termination, deletion, archive and restart authority.

The Equality Act 2010 is relevant to accessibility in service provision. WCAG 2.2 AA is a practical benchmark, not a substitute for legal advice. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 apply to public sector bodies, not ordinary private ecommerce shops. The NCSC's secure online-service guidance covers identity, logging, incident management and secure disposal.

Issue go only when every required owner signs dated evidence for the same configuration. Issue hold for a remediable gap with an owner and retest date. Stop if seller identity, product evidence, payment control, customer information, data roles, accessibility, recovery or export cannot be demonstrated.

Before you act

Name the legal merchant, trading name and England establishment evidence.
Trace every sampled description, price and delivery promise to a dated source.
Identify the legal payment provider and reconcile test orders across records.
Map data purposes, lawful bases, controller and processor roles.
Complete keyboard, screen-reader and zoom tasks across the purchase route.
Document support severity, escalation, termination and deletion authority.

Common questions

What should a merchant do before signing or configuring an ecommerce service?

Use the platform entry checklist before signing, configuring or migrating. Define the operation, prove the catalogue and customer journey, separate payment and tax evidence, control data and tracking, and test accessibility, security and exit. A single failure can justify hold.

How should payment and tax evidence be handled?

Identify the legal payment provider, settlement account and relevant authorisation or registration record. Reconcile each test order across platform, processor, fulfilment and ledger records without live customer funds. Ask qualified advisers to record VAT, customs, accounting and invoice assumptions rather than accepting a platform tax setting.

When should a merchant issue go, hold or stop?