What Is Ecommerce Web Design?
The difference between a shop and an ordinary website is not the shopping basket. It is that every page is a step in a transaction. The whole thing also has to keep working as the catalogue grows.
What Ecommerce Web Design Means
Ecommerce web design is the work of designing and building a website that sells products directly, taking orders and payment without anybody having to telephone you. It covers how the shop looks, how it is organised, how somebody moves from arriving to paying and what connects to the systems behind it.
The phrase misleads slightly, because design suggests appearance and appearance is the smaller part. A great deal of the work is decisions rather than drawings: how a catalogue is divided up, what a customer sees when they narrow a list of three hundred items down to four, what happens when something is out of stock, which page a search engine will treat as the important one.
Those decisions are invisible in a portfolio. Two shops can look equally good and be entirely different underneath. The difference will show up in the second year rather than the first.
What follows sets out how a shop differs from an ordinary website, what is actually in a build, why the work does not stop at launch and who does it. The full series sits in our ecommerce web design guides.
How It Differs From An Ordinary Website
A brochure website has perhaps twenty pages. Somebody wrote each one. They change once or twice a year. One person can hold the entire thing in their head.
A shop has thousands of pages and nobody wrote most of them. They are produced by templates filled from data, with stock levels, prices, variants and availability sitting behind each one. They change daily without anybody touching the design. That single difference produces every other one.
What it does to structure. You cannot hand build three thousand pages, so you build a handful of templates and a system for organising what flows into them. The consequence is that template and structural decisions carry far more weight than any individual page. Get a product template right and three thousand pages are right. Get the category structure wrong and three thousand pages sit in the wrong place.
What it does to maintenance. A brochure site can be left alone for two years and will still work. A shop cannot, because it depends on things that keep moving: payment providers, platform updates, delivery rules, tax treatment, stock feeds. Neglect shows up as breakage rather than as staleness.
What it does to cost. This is why quotes differ so widely. You are commissioning a system rather than a document. Systems are priced by what they have to do rather than by how many pages they contain.
What Is Actually In The Build
Six components, described by what they do rather than by how they are set up. Knowing they exist is what lets a buyer read a quote.
The catalogue and product data
Everything the shop knows about what it sells: names, descriptions, prices, images, categories, variants, weights and codes. This is the foundation and it is almost always underestimated, because a spreadsheet exported from an old system is rarely in a state a new shop can use.
The basket and checkout
The sequence between deciding to buy and having bought. It holds what somebody has chosen, applies delivery and any discount, collects an address and hands over to payment.
Payments
Taking money and confirming it arrived. Which provider, which methods, plus what a customer sees at the moment they hand over card details.
Delivery and tax rules
What it costs to send something, where you send it, how quickly, plus how tax is applied. Simple for one product to one country. Considerably less so across weight bands, regions and product types.
Customer accounts
Order history, saved addresses, returns and tracking. Optional. The decision to require an account has a measurable effect on completed orders.
Integrations
Connections to whatever else the business runs: stock systems, accounting, shipping labels, marketplaces. Each one is a project of its own and each is a source of ongoing dependency.
Why It Does Not End At Launch
A shop is not a thing you have made. It is a system somebody has to run. That distinction catches out almost every first time buyer.
What ongoing actually covers. Platform updates arriving whether you want them or not. Apps and plugins updating on their own schedules and occasionally conflicting. Security patching. Payment providers changing requirements. Prices and stock changing constantly. Products arriving and being discontinued. Seasonal changes to delivery. Tax and consumer rules changing. And things simply breaking, usually in the checkout, usually at the weekend.
The reason this surprises people is that they budgeted for a project and received an operation. A brochure site genuinely can be commissioned once and largely left. A shop generates work every week for as long as it trades. That work has to belong to somebody by name.
There is a second order effect worth understanding. A neglected shop does not merely become dated. It degrades, because it depends on external services that keep moving underneath it. A payment method stops being supported. An app is abandoned by its developer. A platform update changes how something behaves. None of that happens to a static website.
Which is why the useful question when commissioning is not only what it costs to build. It is who looks after it afterwards, what that costs and what happens at nine on a Saturday when checkout stops working.
Where Design And Search Overlap
A shop's ceiling in search is set during the build, by people who may not have been thinking about search at all.
The reason is that the decisions which determine how findable a shop can be are the same decisions a designer or developer makes for other reasons. How categories nest inside each other. What the web addresses look like. What happens when a shopper narrows a list by colour and size. Whether that combination becomes a page in its own right. How products connect to categories and categories to each other.
None of that is presented as a search decision. It is presented as structure, navigation and convenience. It gets settled early, because everything else depends on it.
The consequence is uncomfortable. Those decisions are the expensive ones to undo. Changing how a category tree is organised on a live shop with three thousand products means changing addresses, redirecting the old ones and accepting a period of disruption. It is a rebuild rather than an adjustment, which is not true of most things people ask us to change.
This is the central argument of the whole cluster and it is taken apart properly in how web design affects ecommerce SEO. The practical version, meaning how a build is sequenced so this does not happen, is in how to build an ecommerce website with SEO built in.
Who Builds It
Four kinds of supplier answer to the phrase ecommerce web design. They cover genuinely different ground. A buyer who knows which one is in front of them asks better questions.
A designer. Concerned with how it looks and how the layouts work. Many are excellent at it. Some do not build, some build within a theme's limits and structural questions may fall outside what they were engaged to consider.
A developer. Makes it function, connects it to other systems and solves the things a theme cannot do. Design and search structure may or may not be part of what they take on. The ones who say so plainly are the ones to trust.
A platform specialist. Knows one platform in depth and works within its conventions, which is efficient. The limitation is that the answer to any question tends to be whatever that platform does, since that is the tool in hand.
An agency. Covers the range, in principle. Quality varies more here than in the other three, because agency is a description of a business model rather than of a capability.
One question separates them faster than any portfolio. Ask what happens when the right answer is not the one the platform does by default. Somebody who has met that situation will describe it. Somebody who has not will say it does not arise. Judging a supplier properly is covered in how to choose an ecommerce web design agency.
What It Costs, Roughly
Ecommerce quotes vary more than any other kind of web work. The reasons are knowable rather than mysterious.
Five things move the number. How many products there are and how many variants each carries. What state the product data arrives in, which is the one buyers never expect. Whether the design is bespoke or a theme configured well. What has to connect to what, since every integration is a small project. And whether an existing shop is being replaced, which is a different job from building a new one.
There is a second bill that sits outside the build price and continues forever: platform subscription, transaction fees, apps and hosting. Comparing two proposals on the build figure alone can produce the wrong answer, because the cheaper build sometimes carries the more expensive running costs.
The drivers are taken apart properly, along with how to compare two quotes without guessing, in how much ecommerce web design costs in the UK. If you would rather discuss a specific project than read about ranges, our ecommerce web design page explains how we work.
Common Misunderstandings
Each of these is reasonable on the face of it. Each leads somewhere expensive.
That a template makes it cheap. A template settles how it looks, which was never the expensive part. It does not load your products, clean your data, decide your categories, set your delivery rules or connect anything to your accounts. All of that remains. It is the bulk of the work.
That the shop is finished at launch. Launch is the point at which the running begins. Budgeting as though it were the end produces a shop nobody is resourced to look after.
That any web designer can build one. Many can produce something that takes an order. The difference shows in what happens as the catalogue grows, when a structure that was fine at eighty products becomes unmanageable at eight hundred.
That search can be added afterwards. Some of it can. The parts covered in block five cannot be added cheaply, because they are structural. A shop that is easy to find is a shop whose structure was decided with that in mind. Deciding it afterwards means changing it.
The last one is why we treat design and search structure as a single piece of work rather than as two purchases.
Structure decided
before design starts.
We plan the category structure, addresses and filter handling before anybody opens a design tool, because those are the decisions that need a rebuild rather than a fix. Design, build and search structure as one piece of work rather than two purchases.
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 what the work is. The rest of the series covers what makes a shop good, what it costs, which platform suits which business, where conversion is lost and why the search ceiling is set during the build.
