Bespoke vs template: do you actually need a custom online shop?

The case for templates is straightforward: lower upfront cost, faster to launch, and for straightforward product ranges they do the job. No one is arguing that every online shop needs a bespoke build.

The case against templates is more nuanced - not that they're bad, but that they come with constraints that aren't always obvious when you're choosing one. This guide is about understanding those constraints clearly enough to make a decision you won't regret in year two.

What a template actually gives you

A template is a pre-built design for a website or online shop. It establishes the visual structure: where the navigation goes, how product listings are displayed, what the product detail page looks like, how the checkout flows. You customise within those structures - colours, fonts, images, some layout options - but the structure itself is fixed.

This is fine when your business fits the template's assumptions. Most templates are designed for a generalised ecommerce scenario: a product grid, a detail page, a basket, a checkout. If your shop is a version of that scenario, a template serves it adequately.

It becomes a problem when your business has specific needs the template wasn't designed for - a particular way of presenting products, a checkout flow that reflects how your customers actually buy, a visual identity that's meaningfully different from a generic retail shop.

What templates genuinely can't do

There are things that look like template options but aren't. They're limits you discover after you've started using the template:

• Structural page layout changes - the template places your product images on the left, you want them centred with a specific aspect ratio. This often requires custom code, which costs as much as bespoke work.
• Custom URL structures - Shopify uses fixed paths like `/products/` and `/collections/`. WooCommerce uses `/product/`. If your SEO strategy requires a different structure, you're fighting the platform.
• Checkout customisation - on most Shopify plans, the checkout is Shopify's. You can change colours and logos but not the flow, the field layout, or the confirmation page behaviour.
• Non-standard product structures - if you sell products with complex variants, bundles, or options that don't fit a simple size/colour/material model, you'll hit the edges of what the template and platform support.
• Unique design decisions - if your brand genuinely has a distinctive visual identity, it will look compromised on a template designed for the average shop.

When a template is the right choice

Be honest with yourself about these criteria. If they apply to your situation, a template is a legitimate choice:

• You're selling commodity or semi-commodity products - price and availability are the primary buying factors, not the shopping experience itself
• You have a limited product range - 5-50 products with straightforward variants fits neatly into template structures
• You're testing a market - starting on a template to prove demand before investing in a bespoke build is a sensible sequence
• Budget is genuinely constrained - you cannot commit £1,000+ upfront, and you understand the trade-offs
• Your brand doesn't depend on distinctiveness - the shop is a transaction mechanism, not a brand experience

When bespoke is worth the investment

• Your brand is the product - art, ceramics, bespoke clothing, artisan food, anything where the look and feel of the shop directly affects how customers perceive what you're selling
• You have specific checkout or product requirements - anything that doesn't map to a standard variant/SKU model, or requires a checkout flow designed around your customer's actual journey
• You've already been constrained by a template - you're on Shopify or WooCommerce and you keep hitting limitations that require workarounds or expensive custom development
• SEO is important to you - bespoke shops can be built with clean, optimised URLs and page structures from the outset, rather than working around platform defaults
• You want to own it - not rent access to it on someone else's infrastructure indefinitely

The hidden cost of the wrong template

The most expensive scenario isn't choosing bespoke when you didn't need it. It's choosing a template, spending 18 months fighting its limitations, paying a developer £500-£2,000 to work around each one, and then deciding to rebuild properly anyway.

Bespoke from the start is almost always cheaper than template plus significant customisation work. The template saves money on paper until the customisation requirements catch up with the saving.

"We've never had a client who moved from bespoke to a template. We've had plenty who moved the other way."

A practical test

Before committing to either route, do this: pick two or three Shopify or WooCommerce themes that look plausible for your business. Try to imagine your actual product range in them. Can you see your specific products displayed the way they need to be displayed? Does the checkout flow match how your customers actually buy?

If the answer is yes, a template is probably fine. If you find yourself thinking "it would work if I could just change this one thing" - and that thing is structural - you've found your answer.