Key Takeaways
- The storefront is perhaps a third of the work. The rest is stock accuracy, delivery and returns, payments and VAT, and the operational plumbing behind them.
- Platform choice comes second, not first: decide the operational requirements — stock, fulfilment, VAT, integrations — and the platform choice usually makes itself.
- UK specifics that are not optional: VAT at the right rate per product with MTD-ready records, credit-note trails for returns, and post-Brexit customs data if you import or export.
- The most common expensive mistake: launching a shop whose stock figure does not match the shelf. Overselling costs more than a slow website ever will.
Ecommerce website development is usually discussed as though it were a design project with a checkout attached. In practice the storefront is about a third of the work. The rest is whether the stock figure on the page matches the shelf, whether the delivery promise can be kept, whether payments and VAT produce records that survive a return and an audit, and whether any of it talks to the systems you already run. Get those right and a plain shop sells. Get them wrong and a beautiful one generates complaints.
What an Ecommerce Build Actually Contains
| Layer | What it covers | Rough share of the work |
|---|---|---|
| Storefront | Catalogue, search and filtering, product pages, basket, checkout | About a third |
| Stock & pricing | Live availability, price rules, variants, bundles, backorders | Often the largest single piece |
| Fulfilment | Picking, packing, labels, tracking, partial shipments, returns | Consistently underestimated |
| Payments & tax | Gateways, VAT per product, invoices, credit notes, refunds | Small to build, expensive to get wrong |
| Integrations | Accounting, ERP or stock system, couriers, marketplaces | Each one a small project of its own |
| Operations | Who processes an order, who handles a return, what happens at 5pm on Friday | Not development at all, and it decides whether the rest works |
The UK Parts That Are Not Optional
- VAT at the right rate, per product. Not everything is standard-rated: some goods are zero-rated or reduced, and getting it wrong is a liability that accrues quietly with every sale.
- Making Tax Digital records. Digital records from order through invoice, feeding the accounting package that files. The shop is a source of records, not the filer.
- Returns that produce a credit-note trail. Consumer rights mean returns are normal, not exceptional. A refund that does not generate a matching credit note is a reconciliation problem every month.
- Post-Brexit customs, if you cross a border. Commodity codes, country of origin, duty and import VAT captured on the purchase and carried into landed cost — otherwise your margin is a guess.
- Consumer information duties. Clear pricing including VAT, delivery costs before checkout, cancellation rights, and honest stock statements.
- UK GDPR and PECR. Lawful basis for marketing consent, a cookie approach that is actually compliant, and retention that ends in deletion.
Confirm current VAT rates and consumer-rights detail with HMRC or your accountant rather than with any article, including this one. What does not change is that these belong in the build rather than being bolted on afterwards.
Choosing the Platform — Second, Not First
Platform arguments are the most enjoyable part of an ecommerce project and the least useful place to start. Decide the operational requirements first and the choice usually narrows itself.
| Option | Where it wins | Where it strains |
|---|---|---|
| Hosted platform | Fast to launch, someone else handles security and PCI scope, large app ecosystem | Per-transaction and per-app costs compound; unusual logic means fighting the platform |
| WordPress with WooCommerce | Content-heavy shops, full control, no per-transaction cut | You own performance and security; large catalogues need real care |
| Custom build | Unusual pricing or fulfilment rules, deep ERP integration, performance as a differentiator | Slower to launch and you own everything, including PCI scope decisions |
| Headless | Multiple channels from one catalogue, editorial and shop as one experience | More moving parts, more to maintain, rarely justified below real scale |
For most UK SMEs the honest answer is a hosted platform or WooCommerce, with the effort going into stock accuracy and fulfilment rather than the storefront. Custom earns its place when the pricing or fulfilment logic is genuinely yours — trade pricing tiers, made-to-order items, split shipments from multiple locations.
Where the Money Actually Goes
We do not publish our own fees. What is worth knowing is which lines surprise people, because it is rarely the design.
- Product data. Getting a catalogue clean, consistent and complete — variants, dimensions, weights, images, tax codes — is frequently the largest single cost, and it is your data, so nobody else can do it alone.
- Integrations, per system. Accounting, stock, courier, marketplace. Each has its own quirks, rate limits and failure modes.
- Returns and edge cases. Partial refunds, exchanges, replacements, lost parcels. Easy to leave out of scope, and then handled by hand forever.
- Ongoing per-transaction costs. Payment fees, platform commission, app subscriptions. On a hosted platform these can exceed the build cost within a couple of years, which is worth modelling before you choose.
- The photography. Not development, and it does more for conversion than most development does.
The Long Tail Point, Since People Ask
Long-tail ecommerce means most of your revenue coming from many low-volume products rather than a few bestsellers. If that is your shape — spares, specialist components, wide catalogues — three things follow.
Product pages have to earn their own traffic, because nobody browses to a specific bracket; they search for it. That means genuinely useful product content: specifications, compatibility, dimensions, what it fits, what it replaces. Second, search and filtering inside your own site matters more than the homepage, because visitors arrive mid-catalogue and need to find the adjacent thing. Third, stock accuracy becomes critical rather than important: with thousands of lines, overselling is a systems problem, not a diligence problem.
This is also where ERP integration stops being optional — see MRP, ERP and WMS and custom ERP for UK businesses. For the build itself, UK web development.
Frequently Asked Questions
What is an ecommerce website?
A site that sells directly: a catalogue, product pages, a basket and a checkout, plus the operational layer behind them — stock, pricing, payments, tax records, fulfilment and returns. The storefront is roughly a third of the work; the rest decides whether the shop actually functions.
How much does an ecommerce website cost in the UK?
It depends far more on your catalogue and integrations than on the design. The lines that surprise people are cleaning and completing product data, one small project per integration, handling returns and edge cases properly, and ongoing per-transaction and per-app costs, which on a hosted platform can exceed the build cost within a couple of years.
How do I build an ecommerce website?
Decide the operational requirements first — how stock stays accurate, how orders are fulfilled, how VAT and returns are recorded, what it must integrate with — and the platform choice usually narrows itself. Then get the product data clean, because that is normally the biggest single piece of work and only you can supply it.
Which platform is best for a UK ecommerce site?
For most SMEs, a hosted platform or WooCommerce, with the effort spent on stock accuracy and fulfilment rather than the storefront. A custom build earns its place when the pricing or fulfilment logic is genuinely yours — trade tiers, made-to-order items, split shipments — or when it must integrate deeply with an ERP.
What is long-tail ecommerce?
When most revenue comes from many low-volume products rather than a few bestsellers — spares, specialist components, wide catalogues. It changes three things: product pages must earn their own search traffic with real specifications, on-site search and filtering matter more than the homepage, and stock accuracy becomes a systems requirement rather than a matter of diligence.
Want a straight answer on your own site?
Book a free strategy call. We look at what you have, tell you what is worth changing and what is not, and the audit is yours to keep either way — including the times the answer is that your site is fine.
Book a Free Strategy Call