Standard theme or your own design for a web shop?
Later than theme sellers suggest, earlier than most owners notice.
Every shop platform ships with themes that look good enough to launch with, and launching with one is almost always the right first move. The interesting question is when that stops being true.
The honest answer: later than theme sellers suggest, and earlier than most owners notice.
Why a standard theme is the right start
A theme is a finished set of decisions made by people who have watched thousands of shops. It handles the product page, the cart, the checkout, the mobile layout and the edge cases you have not thought of yet — out of stock, one photo, a very long product name.
Starting here means your first months are spent on the things that actually determine whether the shop works: photographs, descriptions, prices, delivery and what happens after someone orders. None of those are design problems.
The four signals that you have outgrown it
You are fighting the theme. You keep wanting layouts it does not do, and the workarounds are accumulating. Each one is a small maintenance debt.
Your shop looks like your competitor's. Not a vanity problem once shoppers compare two tabs and cannot tell which is which.
The theme is slowing you down. Popular themes carry features you never use, and they load anyway. If a speed test blames scripts rather than images, the theme is a real candidate.
Something specific about how you sell does not fit. Configurations, bundles, made-to-order, a size guide that matters. This is the strongest signal, because it is about the business rather than about taste.
What "your own look" should actually mean
Not a bespoke rebuild of everything. In practice the valuable version is a small number of deliberate departures on the pages that matter:
- The product page, which is where the decision happens
- The first screen of the home page
- The checkout, left almost entirely alone
Everything else can stay standard, and should. Custom checkout flows are where small shops lose money and do not find out for months.
The cost people miss
A custom theme is not a one-off purchase; it is a thing you now own. Platform updates arrive, and a standard theme absorbs them while a custom one needs someone to check.
Budget for that before you commit. If nobody will own it, a good standard theme that stays current beats a custom one that quietly rots.
Shop is coming soon at ChatBuild. The same chat-first route as our websites, for web shops — describe the shop and it is built. There is no purchase flow yet; the waitlist is the way in. Join the shop waitlist.
A reasonable sequence
Launch on a standard theme. Spend the first months on photographs, copy and delivery. Keep a list of the moments you fight the theme.
When that list has a pattern in it — not five annoyances but one recurring shape — you have a brief, and a brief is what makes custom work worth buying. Until then, the theme is not what is holding the shop back.
Related: what makes any site recognisable applies here too, and most of it is not design. Once orders arrive, connecting the shop to your bookkeeping is the next thing worth automating.
Frequently asked
- Does a custom theme make a shop faster?
- Only if speed was the reason for building it. Popular themes carry features you never use and load them anyway, so a custom build can be leaner — but an unmaintained custom theme drifts, and a lean standard theme with resized images usually beats both.
- Should I customise the checkout?
- Almost never. The checkout is the most expensive page in a shop to get wrong, it is the most tested part of any platform, and small shops that rebuild it tend to lose orders in ways they do not discover for months.
Sjors Hooijen Builds ChatBuild and writes about getting a business online without turning it into a project. Questions about this article? Email hi@chatbuild.com.