Ecommerce website cost: what an online store costs to build and run
Ecommerce website cost is set less by the design than by what the store has to do behind it: how many products and variants it carries, how many markets, languages and currencies it sells into, which payment and delivery options it offers, and which systems it must stay in sync with. On top of the build come costs that recur every month for as long as the store is open. This guide explains each cost driver, compares a hosted platform with a custom build over five years, lists the costs people forget and shows how to compare quotes on the same basis.
It does not quote our own prices. It explains how an online store budget is built, so any quote you receive, from us or from anyone else, makes sense. For what we build, see online store development; for websites in general, see our guide to the cost of website development.
The short version
- The build: platform set-up or development, design, product data import, payment and delivery set-up, integrations, testing and training.
- Platform and transaction costs: a monthly plan or hosting, payment fees on every order, and paid apps or plugins.
- Maintenance: updates, security, backups and fixes, every month the store is live.
- Running the store: product data, orders, returns and customer service. This is staff time, and it never stops.
The biggest cost of the build: people's time
A store is built from hours: setting up the platform, designing the pages that sell, importing and cleaning product data, testing the checkout and connecting the systems behind it. What an hour costs follows where the team works. Eurostat's release of 31 March 2026 puts average hourly labour costs across the whole economy in 2025 at €34.9 in the EU and €38.2 in the euro area, from €12.0 in Bulgaria to €56.8 in Luxembourg (read on 12 November 2026). These are whole-economy figures, not agency rates; compare totals for the same scope, not hourly rates.
The market is worth building for. Eurostat reports that in 2025, 95% of people aged 16 to 74 in the EU had used the internet in the previous 12 months, and 78% of them had bought or ordered goods or services online (E-commerce statistics for individuals, read on 12 November 2026).
What drives ecommerce website cost
| Driver | Why it adds work | How to keep it in check |
|---|---|---|
| Catalogue | Variants, bundles, configurable products and many attributes need a data model, filters and careful import | Clean the product data before the build, not during it |
| Markets and languages | Each market adds translations, currencies, tax rules, delivery zones and legal texts | Launch in the markets that sell today; add the next one as a project |
| Design | A fully custom theme takes far more design and testing than an adapted ready theme | Customise the product page and checkout path; keep the rest standard |
| Payment and delivery | Each payment method and carrier needs set-up, testing and clear terms | Offer the methods your customers actually use |
| Integrations | ERP, warehouse, accounting, inventory and marketing tools each have their own interface and limits | Integrate stock and orders first; export the rest at first |
| Customer accounts and B2B | Customer-specific prices, quotes and invoice payment change how the whole store works | Decide early whether trade customers order in the same store |
| Accessibility | Filters, variant pickers and the checkout are where accessibility usually fails | Test with a keyboard and a screen reader from the first design |
| Migration | Moving from an old store means products, customers, orders and every old URL | Map old addresses to new ones before launch |
Hosted platform or custom store: compare five years
For most stores that sell standard products to consumers, a hosted platform such as Shopify, or WooCommerce or Shopware with good hosting, is the sensible start, and a good supplier will say so. A custom build pays off when the way you sell does not fit a platform: configurable products, complex trade pricing, a marketplace model, or a store that is really part of a larger system.
Put both routes in one table for the same catalogue and integrations over five years:
- Hosted platform: the plan you actually need, times sixty months, plus transaction fees on your expected order volume, paid apps, theme licence, the set-up project and any custom app work.
- Custom store: the build, then hosting, maintenance, security updates and planned changes each year.
- Both: product data work, payment processing fees, integrations, training and the cost of moving later.
Payment fees belong in every comparison because they grow with sales, not with the website. Strong customer authentication for online card payments is required under the second Payment Services Directive (Directive (EU) 2015/2366, Article 97, read on 12 November 2026); your payment provider handles it, but it shapes the checkout and should be tested.
The hidden costs of an online store
- Product data. Photos, descriptions, sizes and variants for every product, in every language. It is usually the largest task nobody priced.
- App and plugin creep. Reviews, subscriptions, filters, translations and feeds each add a monthly fee, and together they slow the store.
- Returns and consumer rules. EU consumers have 14 days to withdraw from a distance contract (Directive 2011/83/EU, Article 9), so returns handling, refund flows and clear terms are part of the build.
- Integration upkeep. ERP, carrier and payment interfaces change, and each connection needs looking after.
- Accessibility fixes. Retrofitting an inaccessible theme costs more than choosing an accessible one at the start.
Pricing models and who carries the risk
| Model | How it works | Who carries the risk |
|---|---|---|
| Fixed price | An agreed price for a written scope | The supplier carries estimation risk; the buyer carries the risk of a wrong scope |
| Time and materials | Hours billed as worked, against an estimate | The buyer carries overrun risk; most flexible |
| Phased fixed price | The core store at a fixed price, later phases priced one at a time | Shared: each commitment is small and based on real sales data |
| Platform plan | A monthly fee, often with a share of each sale | The buyer carries the risk of fees growing with sales and of features moving to higher plans |
How to compare ecommerce quotes
- Which platform, which plan, and which paid apps or plugins are assumed?
- Is the design a ready theme, an adapted theme or fully custom?
- How many products are imported, and who cleans the product data?
- Which payment methods, carriers, markets and languages are included?
- Which integrations are included, and what is assumed about the other systems?
- Is accessibility tested, and against which standard?
- Are redirects from an old store included?
- What does maintenance cover each month, and what counts as new work?
- Are the store account, domain, code and data in your company's name?
Ways to spend less without cutting quality
- Start on a platform. Move to custom only when the platform clearly limits sales.
- One market first. Prove the store sells before translating it.
- Product data first. Clean data makes filters, feeds and search work without extra code.
- Own the account. A store in your company's name can change supplier without starting over.
Related reading: website redesign cost for moving an existing store, API integration cost for ERP and warehouse links, and the European Accessibility Act. Trade customers with their own prices are covered on B2B ecommerce solutions. All our services are on the services page, and every guide is in the guides library.
Questions people ask
How much does an ecommerce website cost?
It depends on the route and the scope: a store on a hosted platform with a ready theme and a few hundred products is a different project from a store with your own design, customer-specific prices, several languages and an ERP integration. The build is only part of it; platform plans, payment fees, apps and maintenance recur every month. Any figure given before the catalogue, markets and integrations are written down is a guess.
Is Shopify cheaper than a custom ecommerce website?
At the start, usually yes. A hosted platform such as Shopify removes hosting, security updates and much of the checkout work. Over several years the answer depends on the plan, the transaction fees, the paid apps you need and how far your processes fit the platform. Compare the total over five years for the same catalogue and integrations.
What are the monthly costs of an online store?
The platform plan or hosting, payment processing fees per order, paid apps or plugins, the domain and email, maintenance and updates, and the time someone spends on product data, orders and customer service. Marketing is usually the largest running cost of all, and it is often left out of the website budget.
Does an online store have to be accessible?
In the EU, the European Accessibility Act applies to e-commerce services sold to consumers from 28 June 2025 under Directive (EU) 2019/882, with an exemption for microenterprises providing services (fewer than 10 employees and a turnover or balance sheet of no more than EUR 2 million). Building accessibility in from the start costs far less than fixing a live store.
How long does it take to build an ecommerce website?
A store on a hosted platform with a ready theme and clean product data can go live in weeks. A custom design, several markets and integrations with ERP or warehouse systems take months. Product data is the usual delay: photos, descriptions and variants are seldom ready when the project starts.
Sources
- Eurostat: EU hourly labour costs ranged from €12 to €57 in 2025 (31 March 2026, read 12 November 2026)
- Eurostat Statistics Explained: E-commerce statistics for individuals (2025 data, read 12 November 2026)
- Directive (EU) 2019/882 (European Accessibility Act), Articles 4 and 31 (read 12 November 2026)
- Directive 2011/83/EU (Consumer Rights Directive), Article 9 (read 12 November 2026)
- Directive (EU) 2015/2366 (PSD2), Article 97 (read 12 November 2026)
Your online store scope checklist
Write one line for each before you request quotes. The answers make quotes comparable.
- The number of products and variants, and the state of the product data.
- The markets, languages and currencies at launch, and the next ones.
- Payment methods and carriers customers expect.
- Consumers only, or trade customers with their own prices too.
- The systems to connect: ERP, warehouse, accounting, marketing.
- Design: ready theme, adapted theme or custom.
- An old store to migrate: products, customers, orders and URLs.
- Accessibility standard to test against.
- Who runs the store day to day: products, orders, returns, service.
- Ownership: store account, domain, code and data in your company's name.