If you run an established Shopify store, the honest answer is: it depends on what you are actually fixing.
A theme tidy-up, a conversion-led rebuild, and a messy migration all get described as the same Shopify website project. They are not the same job. They do not carry the same risk. They should not carry the same price either.
That is where a lot of store owners get caught. They ask what a new Shopify website costs before they have worked out whether they even need a new website.
If sales are flat, I would not jump straight to a rebuild. I would look at the data underneath it first.
Sometimes the store really does need a new foundation. Sometimes the expensive move is just the wrong move wearing a more impressive label.
This guide will help you separate the cost question properly, compare quotes with a bit more clarity, and decide whether you need a rebuild at all.
The cost question most stores ask too early
The usual version of the question is:
How much does a Shopify website cost?
The more useful version is:
What exactly needs to change in the store, what is stopping that from happening now, and how much work is involved in fixing it properly?
That is the difference between buying a website and scoping a commercial project.
If the real issue is a weak product page, poor message handoff, soft repeat purchase, or a checkout friction point, a full rebuild can be the expensive version of avoiding the diagnosis.
If the real issue is that the theme is brittle, the catalogue structure is fighting the business, the integrations are messy, and every change breaks something else, then yes, the store may need a bigger reset.
The price changes because the scope changes.
Separate the three cost buckets before you compare quotes
The easiest way to get confused by Shopify pricing is to let three different costs blur into one number.
1. Recurring platform and software costs
Your Shopify plan is only part of the ongoing cost.
You may also be paying for:
- premium themes
- subscription apps
- reviews or UGC tools
- bundling or upsell tools
- Klaviyo or another lifecycle platform
- search, filtering, translation, or market tools
- shipping and fulfilment integrations
- analytics or attribution software
- custom app hosting or support
A project can look affordable up front while quietly loading the store with a heavy monthly software bill.
That is why every quote should show:
- which tools are required
- which tools are optional
- which existing apps can probably be removed
- who owns the accounts and licences
2. One-off project costs
This is the work most people think of first, but even here the number is made up of different jobs:
- discovery and commercial diagnosis
- information architecture and UX
- visual design
- theme development or custom functionality
- content entry or content migration
- data cleanup and migration
- redirects and SEO preservation
- QA, device testing, order testing, and launch support
Two agencies can give you the same headline price while including very different depth in those stages.
That is why the total matters less than the shape of the work behind it.
3. Ongoing support and optimisation costs
Launch is not the end of the spend. It is just the point where the store starts getting judged by real behaviour.
You still need to know:
- what happens if defects show up after launch
- what counts as a defect versus a new request
- whether the team gets training
- whether theme updates are included
- who maintains any custom functionality
- whether post-launch conversion work exists or the project just ends
A rebuild and an optimisation programme are different services. You do not want to assume you bought both when the proposal only priced one of them.
What pushes Shopify website cost up fast
Some decisions change the price far more than others.
Migration and data cleanup
Migration is where a simple move turns into a proper project.
The cost climbs when you need to preserve or improve:
- product data
- collections and category logic
- customer records
- historical orders
- articles and pages
- redirects
- metafields
- media
It climbs again when that data is inconsistent, spread across multiple systems, or being cleaned up as part of the move.
Integrations and custom business logic
This is where two stores that look similar on the front end can have completely different project cost underneath.
If the store depends on subscription logic, ERP or inventory syncs, fulfilment rules, custom tagging, customer-specific pricing, or operational workarounds the team uses every day, the project is not really about making the site look nicer. It is about rebuilding a working system without breaking the business.
That takes more discovery, more testing, and usually more risk management.
Markets, wholesale, and unusual buying flows
Multiple markets, wholesale logic, restricted catalogues, unusual selection steps, or technical product ranges all push the work up because they change the architecture, not just the templates.
Add those things late and you usually pay twice, once for the original design direction and again for the rework.
Custom design versus a strong theme
Custom is not automatically better.
A strong theme can carry a lot of stores a long way if the customer journey is straightforward and the merchandising needs are sensible.
Custom work earns its keep when the existing theme cannot support an important customer journey, operational requirement, or merchandising need cleanly.
If the custom work is there mostly because the team is bored of the current site, that is usually shiny-object syndrome, not a commercial reason.
The most expensive mistake is paying rebuild money for a diagnosis problem
This is the part most pricing guides skip.
Sometimes the store does need a rebuild.
But plenty of stores ask for rebuild quotes when the real issue sits somewhere narrower:
- the landing page is answering the wrong questions
- the product page is too vague
- the offer is weak
- the cart or checkout has avoidable friction
- returning-customer behaviour is soft
- the store keeps relying on discounting to force demand
In those cases, a full rebuild can feel like progress because it is a bigger move. It is still the wrong move if it does not fix the bottleneck.
If the real leak is conversion structure, start there. The published guide to Shopify conversion optimisation is a better place to look than a speculative rebuild budget.
The expensive mistake is pairing the wrong bottleneck with a big expensive fix.
What a good Shopify quote should make obvious
A decent quote should remove ambiguity, not hide it.
You should be able to see:
- what problem the project is trying to solve
- which templates and journeys are being redesigned
- which custom features are included
- which integrations are in scope
- who is handling migration and redirects
- how QA will be done
- who manages launch
- what is excluded
- how change requests are priced
- who owns the code, accounts, and assets after payment
If a proposal uses broad words like design, development, and migration without enough detail underneath them, it is hard to compare properly.
That is where cheaper quotes can get expensive later.
How to judge whether the investment can make sense
You do not need a fake ROI spreadsheet to think about this properly.
You do need a clear commercial problem.
Write the problem in measurable terms, for example:
- mobile traffic reaches product pages but add-to-cart is weak
- the theme makes campaign landing pages slow to launch
- the current setup cannot support required markets cleanly
- fragile integrations are wasting internal time every week
- the store relies on a patchwork of apps that keep conflicting
Then work backwards from the improvement needed.
What extra contribution would the project need to create over the payback period you care about?
How would that happen?
Would it come from more orders, a better conversion rate, fewer support issues, fewer manual workarounds, better retention, or lower software spend?
The point is not to promise a number. The point is to stop treating the project like a design purchase when it is really an operating decision.
When a rebuild is justified, and when a focused upgrade is smarter
Signs the current store may need a bigger rebuild
- the theme is brittle or risky to update
- key templates depend on messy custom code
- the store relies on too many overlapping apps
- navigation and catalogue structure no longer fit the business
- important integrations are unreliable
- international or wholesale requirements no longer fit the setup
- changes in one area keep breaking another
Those are foundation problems.
Signs a focused upgrade may be the better investment
- most of the store works reasonably well
- the main leak sits in a specific stage of the journey
- the offer is unclear
- the product page is doing a weak job
- checkout friction is obvious
- retention is soft after the first order
- the team has not proved that the whole site is the real issue
That is where a narrower project can outperform a rebuild because it puts the budget closer to the real problem.
If you are not sure which one you are looking at, take the Revenue Bottleneck Quiz before you start asking for proposal numbers. It is a much better way to narrow the layer than guessing from the surface symptom.
What to prepare before asking for a Shopify proposal
The better your inputs, the better the proposal.
Come with:
- the commercial reason for the project
- current store performance data
- the main customer problems you have observed
- your app list and recurring software costs
- required integrations
- migration requirements
- operational workflows that cannot break
- known theme or platform issues
- the markets or customer groups that matter most
- a realistic investment range
- the outcome the project needs to create
You do not need to arrive with a full technical specification.
You do need enough clarity that an agency can tell whether you need a rebuild, a migration, or a narrower improvement project.
The short version
A Shopify website does not have one price because it is not one job.
The price changes with the diagnosis, the systems complexity, the migration risk, and the amount of commercial and technical work needed to fix the right thing properly.
If you already know the store has structural limits and you want help scoping the work, book a call.
If you are still unsure whether this is really a rebuild problem, start with the Revenue Bottleneck Quiz. That usually saves people from buying the wrong project first.