Registered office
20 Wenlock Road
London N1 7GU
Registered office
20 Wenlock Road
London N1 7GU

See what changes e-commerce website cost in the UK, from platform and catalogue to payments, shipping, integrations, migration, testing and ongoing care.
An e-commerce website costs more than a brochure site because it must support products, checkout, payments, tax, shipping, stock, orders and post-launch operations. ACA Tech Solutions currently publishes simple catalogue-store starting points of about £2,900 for Shopify and £2,400 for WooCommerce, with standard migrations from about £1,200. These are ACA examples, not market averages or final quotations.
Reviewed: 9 September 2026
| Example | Published starting point | Scope assumption |
|---|---|---|
| Shopify entry store | From about £2,900 | Theme setup, catalogue, payments, shipping, basic apps and launch |
| WooCommerce entry store | From about £2,400 | WordPress setup, theme, catalogue, core plugins and launch |
| Standard migration | From about £1,200 | Mapped products, customers, orders, redirects and test runs |
| Advanced or custom store | Scoped quotation | APIs, subscriptions, complex logic or operational integrations |
Confirm current inclusions on ACA’s e-commerce development page. Platform subscriptions, payment fees, paid apps, premium extensions, hosting, content and ongoing support may be separate.
The main cost driver is operational complexity, not the number of colours in the theme. A ten-product subscription store connected to fulfilment can require more work than a thousand-product catalogue imported from clean data.
Define the platform, catalogue, design, content, checkout, payment, shipping, tax, stock, integration, migration and support assumptions before comparing totals.
Shopify bundles hosted commerce infrastructure into its plan; WooCommerce runs on selected WordPress hosting. Each model creates different recurring costs and responsibilities. Include plan upgrades, hosting capacity, environments, backups, monitoring, CDN and specialist support where required.
Count products, variants, attributes, categories, bundles, subscriptions, digital items and custom options. Identify who supplies descriptions, images, dimensions, weights, tax classes, identifiers and stock. Data cleanup and mapping often require more effort than the import itself.
Price depends on whether an existing theme is configured, a theme is substantially adapted or a custom component system is built. Include mobile navigation, search, filtering, product templates, basket, checkout, account, error and empty states. Content work may include product photography, buying guides, policies and emails.
List card processors, wallets, local methods, subscriptions, deposits, gift cards, refunds, disputes and fraud controls. Confirm country availability, verification, settlement and fee structures directly with providers. Custom checkout logic needs careful testing because it sits on the revenue path.
Define destinations, locations, carriers, package sizes, product restrictions, flat or calculated rates, free-shipping thresholds, local delivery, collection and returns. Real-time carrier rates and label services may depend on the plan, carrier account or paid application.
Record where the business sells, how prices are displayed, customer types, currencies and required evidence. Technology can apply configured rules; it does not decide the business’s tax or legal obligations. Include appropriate professional advice in the project plan where needed.
Integrations with ERP, accounting, CRM, warehouse, point of sale, marketplace or supplier systems can become the largest part of the build. Define the system of record, field mapping, timing, retries, duplicate prevention, reconciliation, alerts and manual fallback.
A migration may include products, media, customers, orders, reviews, subscriptions, vouchers, URLs and search metadata. Customer passwords and recurring payment tokens may not be portable in the same way as catalogue data. Run test migrations, reconcile counts and plan redirects and rollback.
Include staff access, multifactor authentication, platform and extension updates, payment architecture, logging, backups, privacy controls, vulnerability handling and incident response. Using a payment provider can reduce the amount of card data handled directly, but merchant responsibilities remain. Confirm PCI DSS scope with the payment provider and a qualified adviser where appropriate.
Test devices, browsers, products, discounts, tax, shipping destinations, payment success and failure, refunds, emails, stock, fulfilment and analytics. Use controlled test orders and then closely monitor initial live transactions. Budget for fixing data and rule assumptions discovered during acceptance.
Model at least the first year and a normal operating year. A low launch price can become expensive if essential functions depend on several monthly applications.
Start with ACA’s website cost and scope estimator, then use the platform fit finder to clarify the operating model. Both are planning aids rather than quotes.
Possibly, using a tightly constrained self-service or template setup. Compare what is excluded: content, migration, integrations, testing, support and ongoing operation still need owners.
Data must be mapped, cleaned, tested and reconciled, while URLs, integrations, passwords, subscriptions and order history need explicit treatment.
Do not assume so. Ask for one-off delivery, recurring subscriptions, transaction charges and ongoing support to be shown separately.