What this guide covers
This guide explains what drives the cost of an ecommerce website, the ongoing costs people forget, and how to compare proposals. It deliberately does not quote prices, because a number without a catalogue model and an integration list is misleading.
Assumed knowledge
- A rough product count
- A list of the other systems the shop must connect to
Ask five developers what an ecommerce website costs and you will get five very different numbers, because they are quietly quoting for five different jobs.
This guide explains what actually drives the figure, so you can tell which job each quote is for.
The visual design is rarely the expensive part
This surprises people. Templates and design systems have made the appearance of a shop the cheapest it has ever been.
The cost sits in three places:
- The catalogue model. How products, variants, bundles, pricing and stock are structured. Every unusual case here has a cost.
- The checkout rules. Tax, delivery, discounting and payment behaviour, including the exceptions nobody mentions until week six.
- The integrations. Stock, order management, fulfilment, accounting and email, plus defined behaviour for when those systems do not respond.
A shop with 50 simple products and no integrations is a fundamentally different job from a shop with 5,000 configurable products feeding an ERP, even though both are "an ecommerce website".
What makes a quote go up
In rough order of impact:
- Configurable or made to order products
- Pricing that varies by customer, contract or quantity
- Stock held across multiple locations
- Integration with an existing ERP or stock system
- Migration from an existing site with URL and data history
- Unusual delivery or tax rules
- Trade and retail on the same site
The costs people forget
The build is a one-off. These are not.
| Item | Why it exists |
|---|---|
| Hosting and infrastructure | Scales with traffic and catalogue size |
| Platform or licence fees | Fixed, or a share of transaction value |
| Payment processing | A percentage of everything you sell |
| Maintenance and updates | Dependencies and platform versions do not stand still |
| Monitoring and backups | Cheap, and the thing you regret not having |
| Support | Someone has to answer when it breaks on a Saturday |
A build quote that ignores all six of these is not cheaper. It is incomplete.
How to compare two quotes
Proposals are rarely structured the same way, which makes direct comparison hard. Normalise them by asking each supplier the same questions:
- What exactly is in scope, and what is explicitly excluded
- What happens to my existing URLs, and who produces the redirect map
- Which integrations are included, and what happens when one is unavailable
- What are the ongoing costs in year one and year two
- Who owns the domain, the hosting and the code
- What does support cover, and what is charged extra
If two quotes differ by a factor of three, they are almost always quoting for different scopes rather than offering different value for the same scope.
On the cheapest option
A very low quote usually means one of three things: the scope is narrower than you think, the integrations are not included, or the work after launch is not included. None of those is dishonest if it is stated. The problem is when it is not.
The expensive version of a cheap build is the rebuild eighteen months later.
What we do
We do not publish prices, for the reason this guide exists: a number without a catalogue model and an integration list would be wrong in both directions.
What we will do is tell you plainly, at the enquiry stage, whether the budget you have in mind is realistic for what you are describing. That conversation is free and it saves everybody time.
Key takeaways
- Cost is driven by catalogue structure, checkout rules and integrations
- Configurable products, customer-specific pricing and multi-location stock raise it most
- Hosting, licences, payment fees, maintenance, monitoring and support are ongoing
- Quotes differing by a factor of three are usually quoting different scopes
- Ask every supplier the same six questions to compare fairly
- The expensive version of a cheap build is the rebuild eighteen months later
Frequently asked
Questions readers ask most
How much does an ecommerce website cost in the UK?
It depends almost entirely on the catalogue model and the integration list, which is why a figure quoted before seeing those is usually wrong in both directions. A shop with fifty simple products and no integrations is a fundamentally different job from five thousand configurable products feeding an ERP.
Why do ecommerce quotes vary so much?
Because they are quietly quoting for different jobs. One may exclude integrations, another may exclude the URL migration, another may exclude everything after launch. Normalise them by asking each supplier the same questions about scope, exclusions, integrations and ongoing cost.
What ongoing costs should I budget for?
Hosting and infrastructure, platform or licence fees, payment processing as a percentage of sales, maintenance and dependency updates, monitoring and backups, and support. A build quote that ignores all six is not cheaper, it is incomplete.
Is a cheap ecommerce website a false economy?
Not necessarily, if the narrower scope is clearly stated. The problem is when it is not. A low quote usually means the scope is narrower than you think, the integrations are excluded, or the work after launch is excluded.



