Does your store actually need a custom theme, or does it need a good theme set up properly? Most founders who ask for a custom build are reacting to something real: the store looks like every other store, a key page cannot do what the brand needs, or the last developer left behind a tangle of edits nobody understands. But a from-scratch theme is the most expensive answer to those problems, and often not the right one.
This guide lays out the three realistic paths, what each costs in money and time, and a simple way to decide.
The three paths, not two
The question is usually framed as customize versus build, but in practice there is a middle option that fits a lot of brands.
Path A: Configure and customize a premium theme
You buy a well-built theme from the Shopify Theme Store and shape it using the theme editor: colors, typography, section order, imagery, and the settings the theme exposes. A developer may make light code edits, such as adjusting spacing or adding a small snippet. Because Online Store 2.0 themes let you add sections to almost any template, you can get a surprising amount of variety without touching code.
Path B: Premium theme plus custom sections
You start from a strong base theme and add purpose-built sections for the things the theme cannot do: an ingredient breakdown, a product comparison block, a shade finder, a lookbook layout. The core theme stays close to its original code, which keeps updates manageable, while the brand-defining pieces are custom.
Path C: A fully custom theme
A developer builds the theme from the ground up, sometimes starting from Shopify's open-source reference theme, with every template, section and style written for your brand. You get complete control over structure and code. You also own every line of it, including the upkeep.
How the paths compare
These ranges are illustrative and vary widely by region, agency and scope, but the relative differences hold.
| Factor | A: Customize a theme | B: Theme plus custom sections | C: Custom theme |
|---|---|---|---|
| Typical timeline | 1 to 3 weeks | 3 to 6 weeks | 8 to 16 weeks or more |
| Upfront cost | Lowest: theme license plus setup | Moderate: setup plus per-section build | Highest: full design and development |
| Design control | Within the theme's settings | High on key pages | Total |
| Theme updates | Easy if code is untouched | Manageable with care | Your developer's job, forever |
| Performance | Depends on the theme and apps | Good if sections are built lean | Can be excellent, or not |
| Who can edit | Anyone on the team | Anyone, if sections expose settings | Depends on how it was built |
| Best for | New or early-stage brands | Growing brands with a clear story | Complex catalogs or unusual UX |
The real cost is maintenance, not the build
Founders tend to compare launch prices. The bigger difference shows up over the next two or three years.
Shopify keeps adding platform features, and theme developers ship updates to support them. If you are on a Theme Store theme with minimal code changes, updating is fairly routine. The more you edit core theme files, the harder each update becomes, because someone has to carry your changes forward by hand. Stores that were heavily edited without documentation often end up stuck on an old version because updating would break something nobody remembers building.
A custom theme has no upstream updates at all. That is freedom, but it also means that when Shopify introduces something new, nobody builds support for it unless you pay for it. Budget for ongoing development time, not just the launch.
Custom sections sit in a useful middle ground. They are self-contained files, so a well-built section can often be carried across theme updates, or even moved to a new theme, with little rework.
Five questions that make the decision for you
- Can you name the specific pages or features the current theme cannot do? If you can list them, and it is three to six things, you likely need custom sections, not a custom theme. If the answer is vague, such as wanting it to feel more premium, start with better design, photography and copy inside a good theme.
- Is your shopping journey unusual? Build-your-own kits, heavy product configuration, subscription-first flows, wholesale and retail on one storefront, or very large catalogs with complex filtering can justify a custom build. A standard browse, choose and buy journey rarely does.
- Who edits the site day to day? If your marketing team builds landing pages themselves, whatever you choose must expose settings in the theme editor. A custom theme built without that in mind turns every banner change into a developer ticket.
- Do you have ongoing development budget? If not, a custom theme is risky. Pick a path you can maintain with the team you actually have.
- Is the brand settled? If a rebrand is coming within a year, do not commission a custom theme around the old identity. Customize a theme now and revisit after the brand work.
A worked example
Picture a skincare brand with around 40 products, a founder-led story, and a marketing lead who ships a new campaign page every month. Their complaints: product pages do not explain ingredients well, there is no way to compare the three moisturizers, and the homepage looks generic.
A custom theme would solve all of this, in maybe three to four months. But look at the list. It is an ingredient section, a comparison block and a homepage redesign. A premium theme with three or four custom sections, new photography and a tighter layout covers every complaint, launches in about a month, and leaves the marketing lead able to build campaign pages on her own using the same sections. That is Path B, and it is where many brands at this stage land.
Here is roughly how that month might run:
- Week 1: Discovery and theme choice. Audit the current store, list the pages that matter most, and shortlist two or three Theme Store themes that already handle the basics well. Check each one's demo on a phone, not just a laptop.
- Week 2: Design. Design the homepage, product template and the three custom sections in the chosen theme's style, so the new pieces look native rather than bolted on.
- Week 3: Build. Configure the theme on a duplicate, build the sections with settings the marketing lead can change, and connect ingredient and comparison data to product metafields so it updates in one place.
- Week 4: Content, QA and launch. Load real copy and photography, test every template on mobile and desktop, walk the team through editing, then publish.
The important detail is the metafields. Because the ingredient and comparison content lives in structured product data rather than hardcoded text, adding a fourth moisturizer next year is a data entry task, not a development project.
Now picture a furniture brand selling made-to-order pieces with fabric, size and finish options that change price and lead time, plus a trade program with separate pricing. That brand is fighting its theme on every page. Path C, or at least a heavily custom product template, is justified.
Red flags when someone quotes you
- A custom theme quote with no discovery phase. If nobody asked about your catalog, your team or your roadmap, the scope is a guess.
- Heavy edits to core theme files for simple changes. Colors, spacing and section order should be settings, not code edits.
- No mention of the theme editor. Ask how your team will edit content after launch. The answer should be specific.
- No plan for apps. Custom work that duplicates what an app does, or installs five apps where one section would do, both create long-term cost.
- No handover documentation. Whoever builds it, insist on a list of what was customized and where.
Where we usually start
For most small to mid-size brands, we recommend starting from a strong theme and adding purpose-built pieces where the brand needs them. Our Shopify sections service covers exactly that: lean, editable sections your team can reuse across pages without a developer. When a brand genuinely needs a custom build, our web and store development team scopes it properly first, so you know what you are paying for, how long it takes and what it will cost to maintain.