Quick answer
"Custom Shopify theme" covers three different jobs: customising a bought theme, building purpose-made sections on a bought base, or writing a theme from nothing. They cost wildly different amounts, and most stores need the first or second.
Price is driven by how many templates genuinely differ, custom buying logic, markets and languages, integrations, and whether a non-developer can edit it afterwards. A cheap quote is usually honest about hours and quiet about mobile, speed, edge-case states and handover.
If you ask five studios what a custom theme costs, you will get five numbers that do not overlap. That is not a market failure. They are quoting different work, because nobody agreed what the word means. Here is the split we use, and how to work out which job you are actually buying.
01 · Definitions
Three jobs share one name.
Job one: customising a bought theme. You start from a Theme Store or third-party theme and change what needs changing. Most of our client work is this, and it is not a compromise. The Ouz Co runs on a customised Prestige with a full right-to-left Arabic layout; Poppy Lissiman runs four regional storefronts on a customised Dawn. Both look nothing like the theme they started from.
Job two: purpose-made sections on a bought base. The theme stays, but the parts that carry your business are built from scratch: a flavour switcher, a stockist map, a tabbed product picker, a sample-set builder. The rest of the store uses what the theme already does well.
Job three: a theme built from nothing. No Theme Store base, every template written for this store. Material Kitchen is this. It is the rarest of the three and the only one that genuinely costs what people imagine a custom theme costs.
02 · The variables
What actually moves the price.
Design is rarely the expensive part. These are:
- How many templates are genuinely different. One product template is cheap. Four product types with different buying logic is four jobs.
- Custom buying logic. Bundles, subscriptions, personalisation fields, made-to-order, pack tiers. Anything the platform does not do natively is real engineering.
- Markets and languages. One store selling in one currency is one thing. Regional storefronts with translated content, per-market pricing and right-to-left layouts is another.
- Catalogue size and shape. Two hundred products with clean data is easier than forty with inconsistent options.
- Integrations. ERP, 3PL, POS and subscription apps each need real work, and each needs testing that nobody quotes for.
- Who edits it afterwards. Building so a non-developer can ship a landing page costs more up front and less every month after.
03 · The trade
Why the cheap quote is cheap.
A very low quote is usually honest about the hours and quiet about the scope. What tends to be missing:
- Mobile designed on its own grid, rather than reflowed from desktop. We built ParanCrafts with a phone layout designed separately for exactly this reason.
- Speed work. It is invisible in a demo and expensive to retrofit.
- Structured data, accessibility and the states nobody demos: empty cart, out of stock, search with no results, 404.
- Editability. If every future change needs the agency, the quote was a subscription in disguise.
- Handover. Documentation and source access, so you own what you paid for.
The question is never "is this expensive". It is "what did they leave out, and will I have to buy it later at a worse price".
04 · The decision
Work out which job you need.
Start from what is actually wrong. If your complaints are about how the store looks, you are in job one. If they are about something the store cannot do, you are in job two, and only the missing capability needs building. Job three is for stores whose buying experience is the product: a configurator, a made-to-order flow, a catalogue no theme anticipated.
Most stores that ask for job three need job two. The fastest way to find out is to write down the five things that must be true after launch. If a bought theme already does three of them, you are buying two pieces, not a whole theme.
05 · Comparing quotes
Make the numbers comparable.
Quotes are incomparable when briefs are vague, and vague briefs are the norm. Ask every studio to price the same explicit list:
- Which templates are being designed, and which reuse the base theme.
- Which sections are purpose-made, named individually.
- Which apps are being integrated, and who tests them.
- What performance target the build is held to, and how it is measured.
- What you receive at handover: source access, documentation, training.
- What happens after launch, and what it costs.
We publish fixed-scope prices for narrow jobs, starting at $299, precisely because a bounded problem should not need a discovery call to price. Anything genuinely custom gets scoped first and priced before a line is written.
Quick check
Before you commit.
- You know which of the three jobs you are buying.
- The brief names templates and sections individually, not "a custom theme".
- Mobile is quoted as designed, not as reflowed.
- Performance has a target and a measurement method.
- Handover includes source access and documentation.
- You know what post-launch changes cost before you commit.
Price the job, not the word.
Custom is not a tier, it is a description of how much of the store had to be made rather than configured. Decide how much of that you actually need and the quotes stop being mysterious.
Questions
Questions people ask.
Is a custom Shopify theme worth it over a paid theme?
Only when the store needs something a theme cannot do, such as custom buying logic, an unusual catalogue structure, or a market setup no theme anticipates. If the complaints are about how the store looks, customising a bought theme reaches the same destination for less.
Why do Shopify theme quotes vary so much?
Because "custom theme" describes three different jobs, and because vague briefs let studios quote different scopes. Make quotes comparable by naming the templates, the purpose-made sections, the apps, the performance target and what you receive at handover.
What is usually missing from a very cheap Shopify build?
Mobile designed on its own grid rather than reflowed, performance work, structured data and accessibility, the states nobody demos such as empty cart and out of stock, editability for non-developers, and a real handover with source access and documentation.