What a custom Shopify theme buys over a Theme Store theme

Shopify’s Theme Store is the best argument against hiring a developer. Around two hundred themes, two dozen of them free and the paid ones between $150 and $500, all reviewed by Shopify, all built on Online Store 2.0 with sections you can rearrange yourself. For a catalog that fits the template, buying one is the right decision and we say so in quotes.

The question is what “fits the template” means, because a store finds out it does not fit about three months after launch.

TLDR

Buy a Theme Store theme when your products look like the demo and your brand can live inside its settings. Go custom when the design already exists, when the product page needs logic the theme does not have, when speed has run out of settings to change, or when the store is the brand. Custom themes land between $4,500 and $9,000 and usually start from Dawn.

What a Theme Store theme gives you

A lot. Shopify’s theme requirements make every listed theme pass a performance floor, a minimum average Lighthouse score of 60 across the home, collection and product pages, work across the checkout, support sections on every page and expose its design through settings. Support from the theme developer is included. Updates arrive as new versions you can move to.

For a store with standard products, product photos on white, a few collections and a brand that is a logo and two colors, that is the whole job. The setup is a week of work by the store owner or a day by a developer.

Where it stops

Four situations, in the order we see them.

The design exists already. A brand that paid for a design system, or a store moving from another platform with a look customers know, will spend more bending a theme toward the design than building it. Every theme has a personality, and a Figma file that fights it produces a store that looks like a compromise.

The product page needs logic. Configurable products, measurements that change the price, bundles with rules, made-to-order lead times, wholesale prices for logged-in accounts. A Theme Store theme has a variant picker and a quantity box. Anything beyond that is either an app injecting its own markup into the page, which is where speed goes to die, or custom Liquid and JavaScript in the theme. We build the second one.

Speed has run out of settings. A theme with eight apps injecting scripts, a hero video and a mega menu will not get faster by changing settings. A custom theme loads only what the page uses, and the apps that matter are rebuilt as theme sections rather than injected scripts. This is the most common reason existing stores come to us.

The store is the brand. Fashion, furniture, anything sold on how it looks. The layout, the type, the way the product page moves, are the product. A template is the wrong tool by definition.

What custom actually means

Not a theme from a blank file. Almost every custom theme we build starts from Dawn or Horizon, Shopify’s own open source themes. Both are fast, accessible, and maintained by Shopify. The custom work replaces the design layer and adds the sections and product logic the store needs, and keeps Dawn’s structure underneath so the theme stays compatible with checkout and app blocks.

You get a theme in your admin and a repository in your Partner account, with sections named for what they do so the store owner can build pages in the theme editor without calling anyone.

The updates row is the real cost of custom. A Theme Store theme gets new versions for free. A custom theme is yours, which means keeping it current with Shopify’s changes is also yours, or ours on a Care retainer.

What a custom theme removes

The speed argument for custom is usually stated as what a custom theme adds. It is more accurate as a list of what it removes, because a Theme Store theme is fast on the day it is installed and gets slow from what accumulates on it.

App embeds. Every app that adds something to the storefront does it with a script tag injected into every page, whether the page uses it or not. A store with a reviews app, a wishlist app, a size chart app, a countdown timer app and a popup app has five scripts on the checkout page, where none of them do anything. A custom theme rebuilds the two that matter as sections and drops the rest.

Unused sections and settings. A Theme Store theme carries every option any of its buyers might want: six header layouts, four product page styles, animation toggles. The CSS and JavaScript for all of them ship on every page. A custom theme has one header, one product page and the CSS for those.

Third-party fonts and icons. Two font families in four weights each is eight font files before the page paints. A custom theme picks one family, two weights, and loads them with the right hints.

The result is measurable in the theme inspector before launch, and it is the reason a custom theme built on Dawn will usually score higher than Dawn itself with the same apps installed: the apps are gone.

What the handover includes

A custom theme is code you own, and the handover has to make that true rather than nominal. Ours includes the theme in your Shopify admin and in a repository in your Partner account, a settings schema with every section and block named for what it does rather than what it is, a one-page guide to the theme editor for the person who will build pages, the Figma file if we made one, and the Lighthouse scores on the home, collection and product pages at launch so you have a baseline.

It does not include an app for every feature. Where a section replaces an app, the section is documented as such, so nobody reinstalls the app a year later because they did not know the theme did it.

Week by week

A custom theme build on the store build tier, three to six weeks, runs roughly like this:

1. Week one is design. Either an existing design is reviewed against Shopify’s templates and sections, or a design is made. The product page is designed first because it carries the logic.
2. Weeks two and three are the theme: theme.liquid, the JSON templates, the sections and blocks, on a development store with the real catalog loaded.
3. Week four is the product page logic and the app replacements: the configurator, the size chart, the reviews section, whatever the list is.
4. Week five is testing on real devices, the speed pass, and the theme editor guide.
5. Week six, when there is one, is the launch on the live store, usually as a theme published on a quiet morning with the old theme kept unpublished for a month.

A theme that starts from Dawn and replaces the design layer with no unusual product logic finishes at the short end. A theme with a configurator and three app replacements is the long end.

Buying a Theme Store theme well

If the afternoon test says buy, three habits keep the theme fast for longer than the demo.

Pick the theme for the product page, not the home page. Every theme has a good home page in the demo. The product page is where the store sells, and it is the one whose layout, gallery and variant picker have to fit your products. Judge the theme on how your worst product looks on it: the one with nine variants and one photo.

Add apps one at a time and measure after each. Install the theme, run the speed report, then add the reviews app and run it again. When a single app takes fifteen points off the score, you know which one, and you can ask whether a theme section would do the same job. Stores that install eight apps in a week never find out which one hurt.

Keep the theme updated from the Theme Store, and keep customizations in the theme editor rather than in the code. The moment someone edits the Liquid, updates stop being safe to apply, and the theme quietly becomes custom without any of the benefits. If the edits are unavoidable, that is the signal the store has outgrown the template.

How to decide in one afternoon

Install three Theme Store themes on a development store and load your real products into each one. Not the demo products, yours. Then try to build your home page and your product page the way you want them. If you finish and it looks right, buy the theme. If you spend the afternoon working around the theme, the afternoon told you the answer.

Questions