How Much Does Ecommerce Web Design Cost in the UK?
Ecommerce quotes vary more than any other kind of web work. The reasons are knowable rather than mysterious. This guide sets them out so you can read a quote properly instead of comparing two numbers that were never measuring the same job.
What It Costs
We price ecommerce builds per project rather than publishing a single figure. We will give you one after a conversation about what the shop actually has to do. That conversation is short and it is free.
It is worth saying why, because per project can be a way of avoiding the question. The reason here is specific. A twenty product shop with one delivery rule and a three thousand product shop with variants, trade pricing and a live stock connection are different pieces of work that happen to share a name. A single figure covering both would mislead everybody it reached.
What we will not do is quote a market average. The figures circulating for this are almost entirely unsourced, recycled between articles until they acquire an authority nobody can trace back to a measurement. Repeating one here would make this page feel more useful while making it less true.
So the rest of this guide does something more valuable than a number. It sets out exactly what moves the price, what sits outside the build price and continues forever, what gets quietly dropped at the cheap end and how to hold two proposals against each other. Read it and you will be able to place your own project within a range before anybody quotes you.
Why Two Quotes Can Differ By A Factor Of Ten
Five things account for nearly all of it. Naming them before discussing any of them is useful, because a buyer who knows the list can ask which ones apply to them.
Scope. What is actually being bought, which is where most of the difference hides.
Catalogue size and complexity. How many products, how many variants and how complicated the relationships between them are.
Bespoke against configured. Whether the design is drawn from nothing or a well chosen theme adapted properly.
Integrations. What has to talk to what.
New build against replacement. Whether there is an existing shop with orders, customers and search visibility to preserve.
The reason those five produce such a spread is that the phrase ecommerce website covers jobs that share almost nothing beyond the ability to take a payment. Asking what an ecommerce site costs is close to asking what a vehicle costs. The answer depends entirely on whether you mean something to get to the shops or something to move forty tonnes. Both are vehicles.
Which means a quote is only comparable to another quote if both were priced against the same understanding of those five. Most of the time they were not, which is what block eight is for.
What Drives The Number
Five drivers, in roughly the order they surprise people.
Products and variants
Variants multiply rather than add. Two hundred products in four sizes and three colours is not two hundred things to set up. Each combination may carry its own stock level, price, weight and code. A catalogue described as small can therefore be substantial once opened.
How the product data arrives
The largest hidden driver and the one almost nobody anticipates. A clean structured file with consistent naming, complete attributes and images matched to codes is a different project from a spreadsheet with merged cells, a folder of photographs named by camera and specifications sitting inside supplier PDFs. Same number of products, entirely different amount of work.
Bespoke design against a configured theme
A theme adapted properly is a legitimate choice rather than a compromise. It also moves the cost considerably. A bespoke design earns its money when the shop has a genuine requirement no theme accommodates, which is less often than agencies suggest.
Integrations
Every connection to stock control, accounting, shipping or a marketplace is a small project with its own testing, its own edge cases and its own ways of failing quietly at three in the morning. They are priced individually because they behave individually.
Content and photography
Somebody has to write the category and product descriptions and somebody has to photograph the products. If it is not you, it is in the quote. If it is you, it is in your calendar, which is covered in how long it takes to build an ecommerce website.
Platform Costs Against Build Costs
The build price is what you pay to have the shop made. The platform bill is what you pay to keep it running, it starts the day you launch and it never stops. Buyers routinely compare the first and ignore the second.
What sits in the running bill. Platform subscription. Transaction fees on every order, which scale with success. Apps and plugins, most of which charge monthly. Hosting, where the platform does not include it. Domain, certificates and business email.
How to compare properly. Take three years, since that is roughly how long a shop runs before it needs serious attention. Multiply every monthly charge by thirty six. Estimate transaction fees at the order volume you expect rather than the volume you have. Add the build price to that total. Compare those totals rather than the build figures.
Doing that exposes something buyers find counterintuitive. The cheaper build frequently carries the more expensive running costs. The reason is mechanical rather than sinister: when a build budget is small, functionality that would have been built gets supplied by apps instead. Each app is a monthly charge that continues for as long as the shop exists. You have moved cost from a one off into a subscription. Over three years the subscription usually wins.
Platform choice drives much of this, which is why it belongs earlier in a project than most people put it. That decision is covered in which platform is best for ecommerce web design.
The Costs People Forget
These are real costs whether or not they appear on a proposal. When they are absent from the quote, they have not been removed from the project. They have been moved to you.
Photography. Consistent product images across a whole catalogue, shot to the same standard on the same background. A day of a photographer's time covers fewer products than people expect.
Written content. Category descriptions and product copy that does more than repeat the manufacturer. For a large catalogue this is the single biggest content cost in the project.
Product data preparation. Cleaning, structuring and completing the information about what you sell. Covered above as a price driver and worth naming separately, because it is frequently excluded from a quote without being flagged.
Migrating what already exists. Existing orders, customer accounts, reviews and stored addresses do not move themselves. Reviews in particular are often lost, because nobody asked about them until afterwards.
Training. Somebody in your business has to be able to add a product, change a price and process a refund without telephoning anybody.
The first year of support. Sometimes included, frequently not, occasionally included for a period so short it expires before the shop has settled. Ask which.
What Gets Dropped At The Cheap End
A cheap quote is not evidence of anybody behaving badly. It is arithmetic. At a low price something has to give. What gives is predictable.
Discovery and structure planning. The work of deciding how the catalogue is organised before anybody designs anything. First to go, because it produces no artefact a buyer can look at.
Search groundwork. Category naming, address structure and filter handling settled deliberately rather than left at platform defaults.
Testing. Particularly on real devices and particularly placing a genuine order all the way through, including a refund.
Product data work. Handed back to the client, usually described as you supply the products.
Everything after launch. The project ends at the moment the shop becomes your problem.
The pattern in that list is the useful part. Every item on it is invisible in a portfolio. Nobody looking at a finished shop can see whether its structure was planned or whether it was tested on a real phone. The visible work survives a budget cut because the visible work is what gets judged. The invisible work is what determines whether the shop still makes sense in three years.
Project Fee, Retainer Or Both
Four arrangements are common. Each one pays a supplier to behave in a particular way. Knowing which behaviour you are funding is more useful than comparing headline figures.
Fixed project fee. You know the number in advance, which is why buyers like it. It also pays the supplier to define scope tightly and to resist changes, since every addition erodes the margin. That is not bad faith, it is the model working as designed. It suits well defined projects and it produces friction where requirements are still moving.
Phased. The project split into stages, each priced and approved before the next begins. It reduces risk on both sides and it is the sensible answer when scope genuinely cannot be pinned down at the start.
Retainer. A monthly amount for continuing work. It suits the running of a shop rather than the building of one. The risk is scope quietly thinning while the fee stays the same, which is why the work needs defining rather than describing.
Build plus ongoing. A project fee to make it, then a monthly arrangement to run it. This matches how a shop actually behaves, since the shop does not stop needing attention on launch day.
We work on the last of those. Build work is quoted per project. Everything afterwards sits inside our fixed monthly fee rather than being billed by the hour.
How To Compare Two Quotes
Eight questions, put to both suppliers in writing. The answers make two unlike proposals comparable, which is the only way the cheaper one can be recognised as cheaper.
Who owns the finished site, the code and the design files? The answer should be you. It is not always.
Who holds the domain, the hosting and the platform account? These should be in your name from the start rather than transferred later as a favour.
What happens if we part company? What you leave with, plus whether the shop continues to work.
What is included after launch, for how long? Stated in weeks or months rather than as a reassurance.
Is search structure in scope or excluded? Category structure, address patterns and filter handling specifically. This is the item most commonly absent. It is the one covered in how web design affects ecommerce SEO.
Who prepares the product data? Answered precisely rather than with client to supply products.
What will the running costs be? Subscription, apps and transaction fees, listed.
What is explicitly excluded, plus how are changes priced? The exclusions list is more informative than the inclusions list, because it is where the two proposals actually differ.
Common Mistakes
Four. They compound, because each one makes the next more likely.
Buying on price. Choosing the lowest number without establishing what each proposal contains. The cheapest quote is frequently the one that excluded the most, which means the difference will be paid later at a worse moment.
Paying for a design with no plan behind it. Commissioning how it looks before deciding how it is organised. The design then dictates the structure, which is the wrong way round and expensive to reverse.
Forgetting the running costs. Budgeting for the build and being surprised by the subscriptions, apps and transaction fees arriving every month afterwards.
Treating launch as the end of the spend. The commonest of the four. A shop needs attention every week it trades. A business that has spent everything getting it live has nothing left to run it with.
The connection between them is a mental model rather than carelessness. Buyers treat a shop as a purchase, like a van. It behaves like a member of staff: a cost to acquire and a cost to keep, where the second one is larger over time and the first one is the only one anybody budgets for.
A figure after
one conversation.
We price per project because the drivers on this page vary so widely. We will tell you which of them apply to your shop before quoting. Structure and search architecture are inside the build rather than sold separately.
What a build covers:
Ongoing management afterwards sits inside our fixed monthly fee. Build work is quoted per project.
Twenty guides.
One subject.
This page covers cost. The rest of the series covers how long a build takes, which platform suits which business, what to expect during a project and how to choose between agencies.
