// Service · Specialist
Ecommerce websites with category structure from real search demand, product pages written one at a time, product markup and a checkout with less friction.
// The demand
The Companies House register lists 187,354 UK companies under SIC 47910, retail sale via mail order or over the internet, as of 2026. In our experience the ones that grow do it on two screens: a category page built out of the words people actually search, and a product page that answers the last question before somebody commits.
That is the difference between an online shop and every other kind of website. A brochure site gets a handful of pages and each one can be argued over. A store gets hundreds, most of them generated from a spreadsheet, and the quality of that spreadsheet does a lot to decide how the whole thing performs. So we start with what people type and build the categories out of it, rather than mirroring how your warehouse happens to be organised.
If you are in Glasgow and already know the build is WooCommerce, our WordPress ecommerce web design in Glasgow page covers that stack, that city and how those projects run. This page is the wider version of it. Anything about how we design and code in general belongs on the main web design page. The price-transparency argument in a service business, rather than a shop, sits on web design for salons.
// What we deliver
We map how your market words things before anyone draws a menu, then build the category tree and the on-site filters around that language. Warehouse logic and shopper logic often disagree, and the site has to follow the shopper.
Every product gets its own copy answering the things that stop a purchase: sizing, materials, what is in the box, delivery timing, returns. Variants share a page rather than spawning near-identical ones, so the catalogue stays readable to a shopper and to a crawler.
Price, availability, brand, SKU and review rating written into the page as structured data, so Google has a machine-readable version rather than an inference. That is what a rich result gets built from.
Guest checkout on by default, address lookup, the delivery cost shown before the final screen, and the payment methods your customers already hold. Every extra field between a full basket and a paid order is one more place to lose it.
Product photography is usually the heaviest thing a store carries. We serve each image at the size the device asks for, in a modern format, with dimensions set so nothing jumps as it loads, and we hold the whole page to a budget agreed at the start.
// The leaks
Thin product copy comes first, and it is usually copy that was written once and pasted across a range. Twelve colourways share the same two sentences from the supplier, so no page has anything of its own to be found for, and a shopper comparing two of them learns nothing that would settle the choice.
Missing product markup is next. Without it, the price, the stock position and the star rating exist only as words in a layout, and the search result stays a plain blue link beside competitors showing a figure and a rating. The information is already in the store, and nothing is passing it to the machine that reads it.
Then there is weight. Uncompressed photography at full camera resolution makes a product page crawl on mobile data, and our experience is that a shopper waiting on a spinner goes back to the results page rather than to the basket. Images are usually the first thing to fix and the cheapest.
// Stack
The usual answer for a UK retailer who wants to own the platform, run their own catalogue and keep the running cost predictable. We build the theme from scratch rather than buying one, so the store is not carrying features it never uses.
Where you would rather somebody else handled payments, PCI scope and platform updates, Shopify carries the commerce and we design and code the storefront on top of it. You give up some control over the plumbing and you maintain less of it.
For catalogues where speed is the whole argument, the pages are built ahead of time and the basket, stock and payment run through an API. The fastest of the three and the one with the most development in it, so it earns its place on larger stores.
// Selected work
A retailer of Scottish and Celtic designer pieces whose reputation sat in niche circles while terms like Celtic jewellery UK went to other shops. Six months that opened with discovery workshops, a competitor review and an audit of the whole site, then produced practical guides, a knowledge hub tied to the product categories, and optimised product pages underneath them.
A halal food importer in Japan, selling into a country-wide market with nothing online at all, where visibility beyond a few cities was the real constraint on growth. Over six months, development, design and marketing ran as three separate teams, and what launched was an SSL-protected WordPress store where a customer could browse a range and place an order.
// Pricing
£2,500 is the entry point, and stores reach it less often than brochure sites do. That floor covers a focused catalogue, a custom theme, the category structure, product markup, a payment gateway and the launch search work.
Catalogue size is the first thing that moves it, though not in the way people expect. A thousand products imported cleanly from a spreadsheet costs less to build than eighty products with inconsistent data, missing images and three ways of recording a size. Beyond that, the additions with real build time in them are a migration off an existing platform, multi-currency, a subscription or trade-account tier, and a connection into stock or accounting software.
Search on a store is a longer job than on a brochure site, because there are hundreds of pages to earn rather than a handful. Some retailers begin an ecommerce SEO retainer at launch and others wait a quarter to see what the new structure picks up unaided. Tell us your product count and current platform on a call and we will price it. The tiers are published if you want the shape first.
"Delivix transformed our online presence completely. Their SEO expertise helped us rank on the first page of Google within three months. The team is professional, responsive, and truly understands digital marketing."
"Working with Delivix was a game-changer for our business. They redesigned our website and implemented an SEO strategy that doubled our organic traffic. Highly recommended!"
"The team at Delivix delivered exceptional results. Our new website is fast, modern, and converts visitors into customers. Their ongoing support and expertise in SEO have been invaluable."
The other questions are answered on the brief. Fill it in or book a call.
It starts at £2,500, and the figure needs two facts from you before it means anything: how many products you sell, and how clean the data behind them is. A tidy export with images, variants and descriptions in order builds quickly at almost any size. A catalogue that has to be untangled first costs more than a much larger one that does not. We look at your export on the first call.
There is no ceiling that matters in practice. The work scales with the state of your data rather than the row count, so the first task is always an import test on your real export. That surfaces the duplicate SKUs, the missing images, the variants recorded three different ways and the prices sitting in the wrong column, which is far better found in week one than in launch week.
No, and separate pages per variant usually make things worse. Colour, size and finish belong on one product page as options a shopper switches between, which keeps the reviews, the ranking and the link equity together in one place. Genuinely different products get genuinely different pages. The rule we apply is whether somebody would search for it by itself.
They can, and product structured data is the mechanism. Each product template carries price, availability, brand, SKU and aggregate rating in a machine-readable block, and we validate the templates rather than spot-checking a handful of pages. Whether any of it appears on a given day is Google's call. What we control is that the data exists, matches the visible page, and updates when your stock does.
Usually a fix, and it is worth finding out before you spend on a rebuild. We run the store against real mobile conditions and separate the causes: oversized images, a theme loading scripts it never uses, unbounded plugins, or hosting that has been outgrown. Oversized photography is what we find most often, and it is the cause you can solve without touching the build. We tell you which bucket yours falls into and price both routes.
It comes down to who you want maintaining the plumbing. WooCommerce on WordPress gives you ownership of the platform and a predictable running cost, which suits most UK retailers we talk to, and our WordPress ecommerce page sets out how those builds run. A hosted platform takes payments, PCI scope and updates off your plate in exchange for less control. We recommend one and explain the trade.
Where they are sensible we keep them, because the safest migration is the one that changes least. Where they carry old category paths, session parameters or a platform's numbering scheme, they get replaced and every old address is mapped to its new home before launch. We crawl the current store first, record what earns traffic today, and check weekly for a month afterwards that it still does.
We can, and on a large catalogue we usually write the templates and the top sellers rather than all of it. Supplier copy goes into the same words as every other stockist, so the pages that matter get written from scratch around what a buyer asks before purchasing. For the long tail we set a structure and a field list your team can fill in consistently, which keeps the catalogue coherent as it grows.