Intelivita
11 min•

What Is eCommerce Web Development? Types, Features and Process

Oliver-Author

eCommerce web development is the process of designing, building and connecting a website that sells products or services online. It covers the shop front customers use, the checkout and payments, and the systems behind them: stock, orders, delivery and accounting.

This guide explains what an online shop needs, the ways to build one, how a build runs from first brief to launch, and the UK rules every shop must follow.

Key facts

Topic Details
Online share of retail 28.3% of retail sales in Great Britain were made online in December 2025 (ONS)
Main ways to build Hosted platform (for example Shopify), open-source platform (for example WooCommerce), custom build, headless
Typical stages Discovery, design, build, integrations, product data, testing, launch
UK rules to plan for UK GDPR, cookie consent (PECR), 14-day cancellation rights, VAT, PCI DSS for card payments

What Is eCommerce Web Development?

eCommerce web development is the process of building an online shop that lists products, takes payments and manages orders. It includes front-end design, back-end logic, the basket and checkout, and integrations with payment, stock and delivery systems.

Every build has a front end, a back end and integrations.

  • Front end: the pages customers see, such as product listings, product pages, the basket and checkout. It must work on phones, tablets and desktops.
  • Back end: the logic that calculates prices, discounts, delivery charges and tax, and records each order.
  • Integrations: connections to outside systems, such as a payment gateway, a courier, an accounting package or a CRM.

"eCommerce web development" and "eCommerce website development" mean the same thing. "eCommerce app development" is different: it means building a native app for iOS or Android, covered in eCommerce app development.

What Is an eCommerce Website?

An eCommerce website is a website where customers browse products, add them to a basket and pay online. Amazon sells a wide range of products, Etsy focuses on handmade and vintage items, and ASOS sells fashion: each is an eCommerce website built for a different kind of shopper.

For a business, an online shop takes orders at any hour and reaches customers outside its local area. Whether those benefits of an eCommerce website justify the cost depends on the products, the margins and the market.

How Is an eCommerce Website Different From a Normal Website?

An eCommerce website handles transactions: it stores products, prices and stock, takes payments and records orders. A normal website publishes information and collects enquiries but does not sell.

Feature Normal website eCommerce website
Main job Inform and generate enquiries Sell and take payment
Core features Pages, blog, contact form Product catalogue, basket, checkout, customer accounts, order management
Integrations Email, analytics, CRM Payment gateway, couriers, stock, accounting, CRM
Security and compliance HTTPS, UK GDPR HTTPS, UK GDPR, PCI DSS for card payments, consumer protection rules
Ongoing work Content updates Product updates, order handling, stock, platform and plugin updates
Build effort Lower Higher, because each transaction must be tested end to end

What Features Does an eCommerce Website Need?

Every eCommerce website needs a product catalogue, search and filters, a basket, a secure checkout, payment processing, order management and customer accounts. Most shops also need delivery options, discount codes and reports.

Group Feature What it does
Customer-facing Product catalogue Lists products with photos, prices, sizes, colours and stock levels
Search and filters Lets customers find products by name, category, price or attribute
Basket Holds chosen products and shows the running total
Checkout Collects delivery details, delivery choice and payment in as few steps as possible
Customer accounts Stores addresses and order history; guest checkout should stay available
Reviews Shows ratings and comments from previous buyers
Admin Product management Adds and edits products, prices and stock
Order management Tracks each order from payment to dispatch, refund or return
Promotions Creates discount codes, sales prices and free-delivery rules
Reports Shows sales, best-selling products and abandoned baskets
Integrations Payment gateway Takes card, wallet and other payments securely
Delivery and couriers Calculates delivery charges and creates labels and tracking
Accounting and stock Sends orders and stock changes to systems such as Xero or an ERP
Email and CRM Sends order confirmations and marketing to customers who opted in

What Are the Types of eCommerce Business Models?

The 5 main eCommerce business models are B2B, B2C, D2C, C2C and C2B. The model decides which features a site needs: a B2B site needs account pricing and bulk ordering, while a B2C shop needs a fast checkout for one-off buyers.

Model Who sells to whom Features it usually needs Example
B2C (business to consumer) A business sells to the public Fast checkout, guest checkout, promotions, reviews ASOS
B2B (business to business) A business sells to other businesses Customer-specific prices, bulk and repeat orders, quotes, invoices on account A wholesaler's trade portal
D2C (direct to consumer) A manufacturer sells direct, without retailers Brand-led design, subscriptions, customer data A brand selling its own products online
C2C (consumer to consumer) Individuals sell to each other through a platform Seller accounts, listings, ratings, payments held until delivery eBay
C2B (consumer to business) Individuals sell work or products to businesses Profiles, proposals, contracts, payouts Freelance platforms such as Upwork

A site where many sellers trade, as in C2C and many B2B models, is a marketplace rather than a single shop. Seller onboarding, commission and payouts make B2B marketplace development a different project from building one business's online shop.

Which Build Approach Should You Choose?

There are 3 main ways to build an eCommerce website: a hosted platform such as Shopify, a self-hosted open-source platform such as WooCommerce, or a custom build. Headless is a fourth option that separates the shop front from the platform behind it.

Feature Hosted platform (SaaS) Open-source platform Custom build Headless
Examples Shopify, BigCommerce WooCommerce, Magento Open Source Built on a framework such as Laravel or Node.js A Next.js or Shopify Hydrogen front end on top of a commerce platform
Hosting and security updates Handled by the platform Your responsibility (or your host's) Your responsibility Split between the platform and your front end
Ongoing fees Monthly plan; transaction fees on some payment set-ups Hosting, paid extensions Hosting, maintenance Platform plan plus front-end hosting
Control over features Limited to what the platform and its apps allow High Complete High on the front end
Time to launch Shortest Medium Longest Long
Best for Most small and medium shops Shops that want full ownership or already run WordPress Business rules no platform supports Large catalogues, several channels or strict speed targets

Platform prices, transaction fees and features change often; a side-by-side comparison of eCommerce platforms for UK small businesses shows which suits each kind of shop.

Hosted Platforms (SaaS)

A hosted platform runs the shop on the provider's servers for a monthly fee, so security patches, hosting and checkout updates are handled for you. You customise the design with a theme and add features with apps. Shopify suits shops that want this hands-off model, and Shopify development adds custom themes, apps and integrations where the standard features stop.

Open-Source Platforms

An open-source platform is free to download and install on hosting you choose, which gives full control over code and data. You take on hosting, updates and security. WooCommerce adds a shop to a WordPress site, and WooCommerce development covers custom extensions, performance work and connections to stock or accounting systems.

Custom eCommerce Development

Custom eCommerce development builds the shop's logic from code on a framework, rather than configuring a platform. Choose it when the business depends on rules a platform cannot support, such as complex trade pricing, product configurators or unusual fulfilment. It costs the most to build and maintain, so most businesses start with a platform and extend it.

Headless eCommerce

Headless eCommerce separates the front end customers see from the commerce platform that handles products, baskets and orders; the two exchange data through APIs. It gives full control over design and speed and lets one platform feed a website, an app and other channels. It also means 2 systems to build and maintain. The content side of a headless build often runs on a separate content management system, explained in headless CMS development.

Progressive Web Apps (PWAs)

A progressive web app is a website that behaves like an app: it can be added to a phone's home screen and can show cached pages without a connection, though checkout still needs one. A PWA is a front-end choice, not a platform. A native shopping app for the App Store and Google Play is a separate build.

What Technology Is Used to Build an eCommerce Website?

An eCommerce website has 4 technical layers: the front end customers see, the back end that runs business logic, the database that stores products and orders, and integrations that connect payments, delivery and other systems. On a hosted platform, the platform provides most of these layers; on a custom build, the development team chooses each one.

Layer What it does Common choices
Front end Displays pages and handles what customers click and type HTML, CSS, JavaScript; React, Vue.js or Next.js; platform themes (Shopify Liquid, WordPress themes)
Back end Calculates prices, tax and delivery; records orders; serves data to the front end PHP (Laravel, WooCommerce, Magento), Node.js, Python (Django)
Database Stores products, customers, orders and stock MySQL, PostgreSQL, MongoDB
Integrations Connect the shop to payments, couriers, accounting and marketing tools Payment gateways such as Stripe and PayPal; courier and accounting APIs
Hosting Runs the site and keeps it available The platform itself (hosted), or cloud hosting such as AWS, Google Cloud or Microsoft Azure

What Are eCommerce APIs?

eCommerce APIs are interfaces that let the shop exchange data with other systems, such as a payment gateway, a courier or an accounting package. A checkout uses a payment API to take the payment; an order then goes through a courier API to create a label. APIs usually follow REST or GraphQL standards; examples include the Shopify Admin API, the WooCommerce REST API and the Stripe API.

Each payment gateway charges different fees and supports different payment methods, so compare online payment gateways for UK businesses before choosing one.

How Is an eCommerce Website Developed?

An eCommerce website is developed in 7 stages: discovery, user experience and design, platform set-up or build, integrations, product data and content, testing, and launch with support. A typical project takes 8 to 20 weeks, depending on the platform, the number of products and the integrations.

  1. Discovery
  2. User experience and design
  3. Platform set-up or build
  4. Integrations
  5. Product data and content
  6. Testing
  7. Launch and support

1. Discovery

Discovery sets the scope: who the customers are, what they buy, which business model applies, and which systems the shop must connect to. The output is a written scope, a recommended platform and a cost estimate.

2. User Experience and Design

Designers map how customers move from a product to payment, then design the key page templates: home, category, product, basket, checkout and account. Designs are checked on mobile first, because the checkout must work on a small screen.

3. Platform Set-Up or Build

Developers set up the chosen platform or write the custom code, build the theme from the approved designs and configure tax, delivery zones, currencies and payment methods.

4. Integrations

The shop is connected to the payment gateway, couriers, accounting or stock systems, email marketing and analytics. Each integration is tested with real order data before launch.

5. Product Data and Content

Products, descriptions, images, categories and prices are imported, usually from a spreadsheet or an existing shop. When the shop replaces an old one, every old product and category URL needs a 301 redirect to its new address so search rankings carry over.

6. Testing

Testing covers every path to payment: guest and account checkout, discount codes, refunds, failed payments, delivery rules and tax. It also covers speed, accessibility and layout on phones, tablets and desktops.

7. Launch and Support

The shop goes live on its domain with HTTPS, analytics and search tracking in place. After launch, the platform, plugins and integrations need regular updates and security checks; plan website maintenance and support before go-live rather than after a problem.

What Does an eCommerce Developer Do?

An eCommerce developer builds and maintains online shops: they set up or code the platform, build the checkout, connect payment and delivery systems, and keep the shop fast and secure. On a small project one developer may do all of this; on a larger one the work is shared between a designer, front-end and back-end developers, a tester and a project manager.

An eCommerce developer works across 5 skill areas.

  • Platform knowledge: Shopify (Liquid themes, apps), WooCommerce (PHP, WordPress) or Magento.
  • Front-end code: HTML, CSS and JavaScript, often with a framework such as React.
  • Back-end code: PHP, Node.js or Python for business logic and custom features.
  • APIs and integrations: payment gateways, couriers, accounting and stock systems.
  • Security and performance: HTTPS, secure payment handling, caching and image optimisation.

A freelancer suits a straightforward shop on a standard platform. A team suits shops that need custom features, several integrations or a migration from another platform; in that case an eCommerce development agency can scope and build the full project.

What UK Rules Apply to an eCommerce Website?

A UK online shop must protect customer data under UK GDPR, ask for cookie consent under PECR, give customers a 14-day cancellation right under the Consumer Contracts Regulations, charge VAT correctly once registered, and take card payments in a PCI DSS-compliant way. The website has to be built to support each of these.

Rule What it means for the website
UK GDPR and Data Protection Act 2018 A privacy notice, secure storage of customer data, and a way to handle requests to see or delete data
PECR (cookies and marketing) Consent before setting non-essential cookies; opt-in before sending most marketing emails
Consumer Contracts Regulations 2013 Clear pre-order information on price, delivery and the seller; a 14-day cancellation period for most goods bought online, and refunds within 14 days of cancellation
Consumer Rights Act 2015 Goods must match their description and be of satisfactory quality; product pages and returns flows must reflect this
VAT Registration once taxable turnover passes £90,000 in a rolling 12 months; prices shown to consumers include VAT
PCI DSS The card industry security standard. Using a payment gateway's hosted payment page keeps card details off your servers and reduces what you must comply with
Strong customer authentication Many online card payments need a second check, such as a banking app approval; the payment gateway handles this through 3-D Secure
Accessibility The Equality Act 2010 requires reasonable adjustments for disabled users; WCAG 2.2 is the standard used to test a site

This is general information, not legal or tax advice; confirm your obligations with the ICO, HMRC or a qualified adviser.

How Much Does eCommerce Web Development Cost in the UK?

eCommerce web development in the UK costs £3,000 to £100,000, excluding VAT, depending on the platform, the number of products and integrations, and how much is custom-built. Running costs follow every year.

  • Platform: a hosted platform has a monthly fee; an open-source platform has hosting and extension costs; a custom build has the highest build cost.
  • Design: a ready-made theme costs less than a custom design.
  • Integrations: each connection to stock, accounting, couriers or a CRM adds build and testing time.
  • Product data: importing and cleaning hundreds or thousands of products, or moving them from an old shop, takes time and many quotes leave out.

Platform fees, design, integrations and product data together set the price; the full cost of an eCommerce website in the UK breaks this down by shop size and platform.

What Are the Best Practices for eCommerce Development?

The best practices for eCommerce development are to plan around clear goals, choose a platform that fits the business, and build a shop that is fast, secure, accessible and easy to buy from.

  • Set clear goals. Agree what the shop must achieve before choosing features and a platform.
  • Choose the right platform. Match Shopify, WooCommerce, Magento or a custom build to your budget, product range and in-house skills.
  • Design for mobile first. Build every page and the checkout to work on small screens.
  • Keep pages fast. Compress images, use caching and remove unused code and apps.
  • Use a trusted payment gateway. Take payments through the gateway's secure payment fields so card details never touch your server.
  • Make the checkout short. Offer guest checkout and show delivery costs before the final step.
  • Build in SEO. Use clean URLs, unique titles, product structured data and redirects from any old URLs.
  • Meet accessibility standards. Test against WCAG 2.2 so disabled customers can browse and buy.
  • Test before launch. Check every payment path, device and browser.
  • Plan maintenance. Schedule updates, backups and security checks from day one.

What Are the Common eCommerce Development Mistakes?

The most common eCommerce development mistakes are a poor mobile experience, slow pages, a long checkout and weak security. Each one costs sales.

  • Skipping mobile testing. Many shoppers buy on phones, so a checkout that fails on a small screen loses orders.
  • Ignoring page speed. Slow product and category pages make customers leave before they reach the basket.
  • A complicated checkout. Forced account creation and late delivery charges are common reasons for abandoned baskets.
  • Weak security. No HTTPS, outdated plugins or card data handled on your own server put customers at risk.
  • Thin product information. Missing sizes, materials or delivery times reduce trust and increase returns.
  • No SEO plan. Duplicate product descriptions and missing redirects make products hard to find.
  • No clear next step. Every page needs an obvious way to buy or continue shopping.
  • No post-launch support. Without updates and monitoring, performance and security get worse over time.

What Are the Current Trends in eCommerce Development?

The main trends in eCommerce development are headless and composable builds, AI-driven search and recommendations, faster wallet payments, and progressive web apps.

  • Headless and composable commerce: larger shops separate the front end and pick specialist services for search, content and payments instead of one all-in-one platform.
  • AI search and recommendations: product search and "customers also bought" suggestions based on browsing and order data.
  • Wallet and one-click payments: Apple Pay, Google Pay and saved payment details shorten checkout on mobile.
  • Progressive web apps: app-like speed and home-screen access without building a native app.

eCommerce Web Development FAQs

How long does it take to build an eCommerce website?

A typical eCommerce website takes 8 to 20 weeks. A shop on a hosted platform with a ready-made theme is quickest; custom design, many integrations or a migration from another platform add weeks. Discovery confirms the timeline before the build starts.

Do I need PCI DSS compliance for my online shop?

Yes, every business that takes card payments must follow PCI DSS. Using a payment gateway's hosted payment page or secure payment fields keeps card details off your servers, which greatly reduces the checks you must complete.

Which payment methods should a UK online shop accept?

Accept debit and credit cards, plus Apple Pay and Google Pay for mobile buyers. Add PayPal and buy now, pay later options if your customers expect them. Your payment gateway decides which methods are available.

Should I choose Shopify or WooCommerce?

Choose Shopify if you want hosting, security and updates handled for a monthly fee. Choose WooCommerce if you already run WordPress or want full control of your code and data, and can manage hosting and updates.

Can I move my online shop to another platform later?

Yes. Products, customers and orders can usually be exported and imported, though customer passwords often cannot be moved. Plan 301 redirects from every old URL so the new shop keeps its search rankings.

Do I need a developer to build an online shop?

Not always. A simple shop on a hosted platform can be set up without code. A developer is needed for custom design, integrations with stock or accounting systems, custom features or a migration.

Turn your product idea into a clear plan

Tell us about your idea, existing product or next phase. We'll review your goals, users and essential features, then outline a practical scope, delivery approach, timeline and expected cost with no obligation to proceed.