What Makes a Good Shopify Store Design?
The Shopify answer is different from the general one. A good store here is one that works with the platform rather than against it. The most reliable test is how little it has to fight Shopify to do what it does.
The Test That Is Specific To Shopify
How much does this store have to fight Shopify in order to do what it does? The less it fights, the better it is designed. That is a different question from whether a shop is well designed in general. It is the one this page answers.
This test is narrower and it predicts something the general ones do not. Everything that becomes expensive about a Shopify store later comes from a decision to work around the platform rather than with it. The maintenance bill, the inability to update, the dependence on whoever built it and the eventual rebuild all trace back to the same root.
Which makes this a test about the future rather than the present. That is the useful part. Two stores can look identical on launch day, cost roughly the same and diverge completely over three years, entirely because of decisions nobody could see at the time.
Building With Sections Rather Than Fighting Them
Modern Shopify themes are assembled from reusable sections. There are two ways to build a store on one. They produce the same result on launch day.
Working with the system. Arranging the sections the theme provides, configuring each one, then where something genuinely does not exist, having it built as a proper section that then appears in the editor alongside the others.
Working around it. Fixing layouts directly into the templates so they look correct and cannot be adjusted afterwards. The page looks right. It also cannot be changed by anybody except the person who wrote it.
The commercial consequence is the whole point. A store built the first way can be rearranged by its owner in an afternoon. A store built the second way needs its developer for every change, permanently, including trivial ones.
There is an uncomfortable reason the second approach is common. It is faster. Fixing a layout into a template takes less time than building a configurable section that somebody else can use, so the quote that came in lower is frequently the one that creates the dependency. It is rarely deliberate. It is a corner cut under price pressure. The cost lands on you later.
The test takes one minute after handover. Open the theme editor and try to move something on a page you were shown. If you cannot, you have the second kind of store.
Collections Are The Structure
On Shopify a collection is doing four jobs at once, which is why collection decisions are structural rather than a matter of tidiness.
It is what navigation points at, the page somebody browses, the page answering a search for a type of product rather than a specific one, plus how merchandising happens, since collections can be assembled by hand or by rule.
Four things therefore have to be decided rather than allowed to happen. What the collections actually are, in the words customers use. How they nest. Which are maintained by hand and which by rule. And which products belong in more than one.
There is a specific reason Shopify stores drift here. It is worth naming, because it is a platform characteristic rather than carelessness. A product can sit in any number of collections at no cost, while creating a collection takes seconds. So collections get added whenever something does not fit, each addition entirely reasonable on its own.
Two years on, the result is a menu that matches how the business thinks rather than how anybody shops, plus a set of collection pages nobody arrives on. How those pages should then be designed is covered in how to design ecommerce category pages.
Restraint With Apps
Every app brings three things: code onto your pages, a charge every month and a dependency on somebody else's work. A well designed Shopify store uses few of them. Somebody can also say what each is for.
How app decisions show up later. As slowness, because each app loads its own code and frequently does so on every page rather than only where it is needed. As a monthly total nobody quoted, since apps are approved one at a time and never reviewed together. As fragility, when an app stops being maintained or stops agreeing with a theme update. And as residue, because removing an app does not always remove the code it added to the theme.
None of that makes apps a bad idea. It makes an unexamined collection of them an expensive one, invisible precisely because every individual addition was justified.
The question worth asking about each. What happens if we remove this tomorrow? If nobody in the business can answer, it is not earning its place and it has probably been running for a year.
One further check regularly finds something. Ask whether any app duplicates a capability the theme already offers, since it is the easiest monthly charge anybody will cancel.
Where Shopify's Defaults Are Already Good
Some parts of Shopify are handled well without anybody improving them. Knowing which lets you push back when an agency proposes to rebuild one.
The checkout. Built and tested at a scale no individual store could reproduce. It is also largely fixed on standard plans, so effort spent trying to work around it is effort spent against the platform rather than for your customers.
Cart, variant and payment handling. Sound for the great majority of catalogues, including the range of payment methods customers expect, which is a large amount of work you are not paying for.
Image handling. The platform does a considerable amount automatically regarding how images are served at different sizes, which is work that would otherwise sit with a developer.
The section system itself on a current theme, which is the subject of block two.
Store search for modest catalogues, where the standard behaviour is adequate and only becomes limiting at scale.
So one question answers any proposal to rebuild these. What specifically is wrong with the default for our store? Occasionally there is a real answer. Frequently rebuilding it was simply billable.
Where They Are Not
Five places where the standard behaviour leaves something for a designer to solve, with a note on which need a developer instead.
Collection page content. The default is a grid with limited room for anything explaining what the shopper is looking at. Solvable by a designer on a modern theme, since sections can be added to collection pages.
Product information beyond the standard fields. Anything your products need that Shopify does not hold by default has to be stored and then displayed. Storing it is admin. Displaying it well is usually a developer, since it needs the theme to know it exists.
Filtering on a large catalogue. Adequate at modest sizes and increasingly limiting as a catalogue grows. Frequently an app, sometimes a developer.
Store search at scale. The same pattern. Fine for hundreds of products, worth improving at thousands.
Anything conditional. Showing one thing to one kind of visitor and something else to another. Always a developer or an app, never a setting.
Which side of the line each falls on is the subject of Shopify web designer against Shopify web developer. It is worth establishing before anybody quotes.
Can The Owner Maintain It Afterwards
Almost nobody asks this before commissioning. It determines what the store costs to own thereafter.
A store that needs its designer for every change is a liability rather than an asset. Updates get delayed because each needs a request and an invoice, seasonal changes stop happening, then the business loses the ability to respond to its own trading.
What makes a build maintainable. Layout held in sections the editor exposes rather than fixed into templates. Text and images held as content rather than written into the theme. Anything unusual documented in writing rather than in somebody's memory. And at least one person in the business actually shown how to use it.
How to make it a requirement rather than a hope. Before the work starts, name five changes you expect to make yourself after launch. Adding a product to a collection. Changing a home page banner. Reordering sections on a page. Editing the text in a section. Publishing a new page. Get written agreement that those five will not require the supplier.
That list costs nothing to agree at the outset. Asking for it afterwards, once the build approach is settled, is asking for a rebuild.
Theme Updates
Theme developers release updates. Fixes, performance improvements and changes keeping the theme working as Shopify itself changes. What happens to those updates is the most expensive decision made during a Shopify build. It is almost never made deliberately.
The mechanism. Where a theme's existing files have been edited, an update overwrites or conflicts with that work. Taking the update means reapplying every customisation. Keeping the customisations means declining the update.
What stores actually do. They decline, without anybody framing it as a decision. Nobody says the store will stop receiving theme updates. The update simply never happens, then does not happen again.
Where that leads. Performance improvements are missed. Fixes for platform changes are missed. And the distance between your theme and its current version widens each year until updating is no longer an update but a rebuild, usually discovered at the moment something breaks.
What reduces it. Keeping customisation in sections added alongside the theme rather than in modifications to the theme's own files, wherever the requirement allows. It is not always possible. It is possible more often than it is done, because the alternative is quicker.
So there is one question worth putting to anybody quoting a Shopify build. How will this store take theme updates in two years? Somebody who has thought about it answers specifically. Somebody who has not will tell you updates rarely matter, which is the answer that costs money.
What The General Design Guidance Covers
Everything above is specific to Shopify. A large amount of what makes any shop good is not. Repeating it here would produce a worse version of guidance that already exists.
Where conversion is actually lost, plus why it goes at a small number of identifiable points rather than evenly, is in how website design affects ecommerce conversion rates.
What makes a first time visitor trust a shop enough to enter card details, along with the standard a shop should be judged against, is in what makes a good ecommerce website.
Why stores are slow, what can be fixed without rebuilding and what cannot, is in why ecommerce website speed affects sales and rankings.
Those three cover the general questions. This page stays on the ones that apply only because the store is on Shopify.
Built so you can
change it yourself.
We build in sections the theme editor exposes, so the layout stays yours to rearrange after we leave. Before starting we agree in writing which changes you will be able to make without us.
What Shopify work covers:
Ongoing management afterwards sits inside our fixed monthly fee. Build work is quoted per project.
Six guides.
One platform.
This page covers what good looks like on Shopify. The rest of the series covers the role, who does what, how themes work and when custom is justified, free themes against paid, plus what to ask before hiring.
