How much does an ecommerce website cost? Comparing quotes

The cost of an ecommerce website depends primarily on the sales model, custom functions, integrations and the work required to prepare products and content. Knowing that a store will contain one hundred products is not enough for a reliable quote. The same catalogue could run on a hosted platform, WooCommerce or a system tailored to the company's processes. Each option creates a different mix of initial, recurring and development costs.

A useful answer to “how much does an ecommerce website cost?” should therefore describe scope rather than present one universal figure. A good proposal explains what will be delivered, which fees continue after launch, what the client must provide and how work outside the agreed scope will be charged.

What makes up the cost of an ecommerce website?

The implementation price is only one part of the budget. Before signing a contract, separate the costs into four groups:

1. preparing and launching the store,
2. licences, hosting and third-party services,
3. maintenance and development after launch,
4. customer acquisition and sales operations.

Leaving out any group makes proposals difficult to compare. A cheap implementation may rely on several paid extensions. A more expensive quote may already include design, migration, analytics configuration and post-launch support that another supplier prices separately.

Functional scope matters more than product count

A straightforward store selling finished physical goods normally needs a catalogue, product variants, a basket, payments, shipping, transactional messages and order management. The price increases when the sales process introduces additional rules.

Typical cost drivers include:

• a product configurator or order personalisation,
• pricing based on customer, role or quantity,
• bundles, subscriptions or digital products,
• multiple warehouses and inventory sources,
• ERP, CRM, accounting or supplier integration,
• automated documents and a custom returns process,
• multilingual and multi-currency sales,
• specific permissions for B2B customers,
• migration of accounts, orders, products and SEO history.

Product count still matters, but the supplier needs to know who will prepare images, descriptions, variants, attributes and import data. An automated import from a well-structured file may require less work than manually completing a few dozen inconsistent product records.

Hosted platform, WooCommerce or a custom store?

Technology changes the cost structure, but it does not solve the offer, product data or fulfilment process for the business.

Hosted ecommerce platform

A SaaS platform combines software, hosting and part of the maintenance in a recurring fee. It can launch a standard sales model quickly, but available functions depend on the plan and app ecosystem. Shopify explains in its pricing and billing documentation that the subscription is a recurring charge and that local pricing and payment options can vary by business location.

The cost assessment should include:

• the platform subscription,
• paid apps and the theme,
• configuration and visual customisation,
• any transaction-related fees,
• limitations affecting exports, integrations and future development.

WooCommerce

WooCommerce provides extensive control over the store and lets the owner choose hosting, design and extensions. The core software alone does not reveal the total launch cost. The official WooCommerce pricing guide separates areas such as hosting, design, security, extensions and development, reflecting the owner's ability to assemble a suitable setup.

The proposal should identify paid extensions, who owns their licences and what happens to them when the supplier relationship ends. Responsibility for updates, backups and post-update testing should also be clear.

Custom ecommerce solution

A tailored store can be appropriate when a standard platform forces expensive workarounds or restricts a critical process. The higher initial investment may cover architecture, a bespoke interface, integrations and automation for the operational team.

There is little value in paying for a custom system merely to reproduce a standard catalogue and checkout. Technology should follow requirements. Our comparison of WooCommerce and Shopify explains two common approaches in more detail.

Design and the purchasing experience

An existing theme reduces design work, but navigation, categories, product pages and checkout still need to fit the offer. Bespoke design costs more because it considers the full purchase journey, mobile behaviour, error states and a consistent component system.

Check whether the design scope covers:

• homepage, product listing and product page,
• search, filtering and empty results,
• basket, shipping, payment and confirmation,
• customer account, orders and returns,
• mobile layouts, messages and form errors,
• accessibility and keyboard operation.

A homepage design alone does not demonstrate the complete ecommerce experience. Product options, filters and checkout often contain the more complex decisions.

Integrations need their own scope

“Integration with shipping and payments” is too vague. A proposal should name providers, describe the data flow, assign responsibility for accounts and cover failure scenarios.

A payment integration may only redirect the customer to a provider, or it may synchronise statuses, refunds and reporting. A warehouse connection may refresh inventory once a day or close to real time. These are materially different pieces of work.

Clarify:

1. Which data moves between systems?
2. Which system is the source of truth?
3. How often does synchronisation occur?
4. What happens when the connection fails?
5. Who pays for the API, connector and ongoing maintenance?

Costs after the store launches

The operating budget may include hosting or platform subscription, domain, licences, payments, transactional email, monitoring, backups and technical support. Marketing, product preparation, customer service and logistics are separate business costs.

Not every charge goes to the website supplier. Payment providers, platforms, app vendors and logistics services use their own billing models. The proposal should therefore distinguish:

• the one-off project price,
• fixed monthly or annual charges,
• fees linked to sales volume,
• work charged separately,
• expected development costs.

Before selecting a supplier, also review what an ongoing website maintenance plan should include.

How do you compare two ecommerce proposals?

First, bring the proposals to a common scope. If one includes migration, technical SEO and analytics while the other covers platform installation only, their headline prices are not directly comparable.

Use this checklist:

1. Views and functions included in the price.
2. Product count and the method of entering them.
3. Integrations with exact data scope.
4. Mobile design, accessibility and testing.
5. Paid licences, subscriptions and transaction fees.
6. Analytics, consent, technical SEO and redirects.
7. Training, documentation and access handover.
8. Warranty, maintenance and rates for further work.
9. Timeline and the client's responsibilities.
10. Ownership of code, accounts and data after the engagement.

If the project replaces an existing platform, use the ecommerce migration checklist as well. It highlights data, redirects and sales continuity that may otherwise be missing from the initial price.

What should you prepare for a specific quote?

Instead of asking only for the price of “a store with one hundred products”, describe the sales process. Prepare:

• product types, variants and configuration rules,
• countries, currencies, taxes, payments and delivery methods,
• systems that require integration,
• the source of product data,
• required customer and staff roles,
• the current store and migration scope,
• launch deadline and development plans.

This information allows a supplier to separate the launch scope, optional work and recurring costs. Explore AMCompany ecommerce development and selected projects. If you want to compare options for a specific sales model, tell us about the project. We will identify the decisions required before a reliable quote can be prepared.