How Much Does a Shopify Store Cost?

Short answer: in the US market, a Shopify store built on a customized theme typically costs $8,000 – $30,000, and a custom store build with a bespoke front end, real integrations and a migration typically costs $30,000 – $150,000. Ongoing conversion and optimization work on an existing store typically runs $2,000 – $10,000 per month on top of that.

Those ranges are wide because "a Shopify store" covers everything from a small catalog on a lightly adjusted theme to a multi-market operation wired into an ERP, a warehouse and a subscription system. The shopify store cost you will actually pay depends far less on the platform than on your catalog, your integrations, the data you need to move and how much of the front end is designed from scratch. Platform subscription, app and transaction fees are separate running costs set by Shopify and app developers; this guide covers the build and the people, not those fees.

This guide is for founders, e-commerce managers and marketing leads who need a realistic budget before they talk to suppliers, and for anyone comparing quotes that differ several times over and wondering why. It sets out the pricing models, the market ranges next to our own published starting rates, what drives the cost, an illustrative budget, how to get an accurate quote, the red flags in cheap quotes, and how to budget beyond launch.

Pricing models for a Shopify build and what each includes

Suppliers price Shopify work in a handful of ways, and the model shapes what you are buying as much as the number does. Before comparing two quotes, work out which model each one uses, because a fixed price and an hourly estimate for the same scope carry very different risks.

Most real projects combine models: a fixed-price or phased build to launch, then a retainer afterward. The common mistake is to budget only for the first part. A store is not finished at launch; it is at the start of a period in which you learn what customers actually do on it, and that learning needs someone to act on it.

What a fixed price should include

A credible fixed-price proposal for a Shopify store names the templates to be designed and built (home, collection, product, cart, content pages, search, account, and any special templates such as a bundle builder), the apps to be installed and configured, the integrations and in which direction data flows, the data to be migrated and how it will be checked, the number of design revision rounds, the browsers and devices tested, and what support is included after launch. If a proposal describes the work only as "a Shopify store with custom theme", it is not really a fixed price; it is a number waiting for a disagreement.

What hourly and retained pricing should include

For time-and-materials work, ask for an estimate broken down by phase and task, the rate for each role, how often hours are reported, and what happens when a task runs over its estimate. For retained engineering, confirm how many hours are included each month, whether unused hours roll over, how quickly work starts, and who sets priorities. The value of a retainer comes from continuity: the same developer learning your store, so each change costs less than it would with someone new.

Market ranges next to our published starting rates

The table below puts the typical US market ranges for Shopify work beside our own published starting rates. Our rates are for project shapes rather than for Shopify specifically, so the closest match is shown for each line; they are starting prices, not guaranteed totals, and a store with heavy integrations or a large migration will be quoted above them.

Read the table as a map of where your project is likely to sit, not as a menu. A themed store for a small, simple catalog with standard payments and shipping will sit near the bottom of the themed range. The same store with a subscription app, a loyalty program, a connection to an inventory system and several thousand products migrated from another platform is already moving toward the custom band, even if the front end still starts from a theme. If you want the wider picture beyond Shopify, our guide to how much an e-commerce website costs covers other platforms and build types.

The landing page line is included because many store owners need one alongside the store: a launch page for a new product line, a pre-order page, a campaign microsite. It is often cheaper to build that separately than to bend a store theme into a campaign shape it was not designed for.

What drives Shopify store cost

Six factors account for almost all the difference between a quote at the bottom of the themed range and one well into the custom band. When two suppliers quote very different figures for what you think is the same store, the explanation is almost always that they have made different assumptions about one of these.

Catalog size and complexity

Two hundred simple products is not two hundred configurable ones with option-dependent pricing. A simple product has a title, description, images, a price and perhaps a size variant. A configurable product may have several option sets that change the price, the image, the lead time and the shipping rules, and may need a custom product page to present those options clearly. Shopify's native product and variant model handles a lot, but once options multiply beyond its limits, or pricing depends on combinations, the work moves to apps, metafields or custom code, and each of those needs design, build and testing. Metafields and metaobjects are also how structured content such as size guides, ingredient lists and care instructions gets onto product pages, and setting them up well takes time.

Integrations

ERP, inventory, fulfillment, tax, subscriptions, loyalty: each is another system with its own failure modes. An integration is not just "connecting" two systems; it is deciding which system is the source of truth for each piece of data, what happens when the connection fails, how errors are surfaced and who fixes them. An inventory sync that fails silently oversells stock. A tax integration configured wrongly under-collects. Well-built integrations also respect the platform's API limits, which matters once order volume grows; our guide to getting store API rate limits right explains why. Transactional email is a smaller but often forgotten integration point, and transactional email for online stores deserves its own line in the scope.

Migration

Moving products, customers, orders and URLs from an old platform is often the largest single line. Products need cleaning and mapping to Shopify's structure; customer records need checking for duplicates and consent status; order history needs a decision about how much to bring across and in what form; and every old URL that has search rankings or inbound links needs a redirect to its new equivalent. Migration is also the phase most often underestimated, because the state of the old data is rarely known until someone opens it.

Custom checkout

Some platforms restrict checkout customization, and working around that is expensive. Worth knowing before you choose. Shopify controls its checkout for security and reliability, and the deeper customization options are tied to its higher plan tier. If your business depends on something unusual at checkout, such as complex delivery scheduling, custom fields that drive fulfillment or B2B payment terms, confirm how it would be done on your intended plan before signing anything. Our comparison of Shopify and Shopify Plus covers when the upgrade becomes worth it, and the current rules should be checked in Shopify's own documentation at the time you scope.

Internationalization

Currencies, taxes, languages, shipping rules and compliance per market all add work. Selling in a second country is not a translation job; it means deciding on pricing per market, duties and taxes, which products can ship where, return rules, legal pages and customer service coverage. Shopify has native tools for multiple markets, but each market still has to be configured, translated, tested and maintained.

Design scope

A themed build on a solid platform is a fraction of a fully custom front end. A good theme gives you tested templates, accessible components and a fast baseline. Customizing it (brand typography, color, section layouts, a few new sections) is modest work. Designing every template from scratch and building it as a custom theme, or as a headless front end on a separate framework, multiplies the design, build, testing and maintenance cost, and it moves future changes from "a merchant can do this in the theme editor" to "a developer has to do this".

How the project timeline affects the budget

Time and cost are tied together because most of the cost is people's time. The phases below are typical for a Shopify project with real integrations and a migration. They overlap in practice, and a small themed store may skip or compress several of them.

Notice that the build and integrations phase has by far the widest range, because it is where integrations and catalog logic land. Also notice that the phase ranges, taken at their longer ends, run well past the 8–12 week turnaround quoted for our marketing site shape. That is not a contradiction: a store with multiple integrations and a significant migration is a larger project than the standard shape, and it should be scheduled and quoted as one. Our guide to how long it takes to build an e-commerce store goes further into scheduling.

The link to cost is direct. Every week a phase runs over is a week of the team's time, so the cheapest way to control a Shopify budget is to shorten the phases you control: make decisions quickly, supply content and data on time, and keep the number of people who must approve each design small.

An illustrative Shopify budget, built step by step

The example below is illustrative. The business is hypothetical and the hour counts are assumptions chosen to show the arithmetic; the prices are our published starting rates and the published US market ranges, nothing else. Your own quote will depend on your scope.

Imagine a brand selling a few hundred simple products in one country, moving from another platform, with a subscription option on some products and an existing email platform. It wants a customized theme rather than a bespoke front end, and plans to keep improving the store after launch.

1. Where the build sits in the market. This is a themed store on a hosted platform with basic integrations, so the typical US market range is $8,000 – $30,000. The migration and the subscription integration push it toward the upper part of that range rather than the bottom.
2. Our starting point. The closest published shape is our marketing site, from $18,000 per project. That is the floor for the build, not the quote; a scoped estimate may come in above it once the migration and subscription work are sized.
3. Post-launch engineering. Assume, for illustration, 15 hours per month of retained engineering at our starting rate of $145 per hour. That is 15 × $145 = $2,175 per month, or $2,175 × 12 = $26,100 over the first year.
4. Illustrative first-year floor. $18,000 for the build plus $26,100 for twelve months of retained engineering gives $44,100 as an illustrative floor for the first year of build and development work, before any scope-driven increase and before platform, app and payment fees.
5. Optional optimization program. If the brand later adds a dedicated conversion and optimization program, the market range is $2,000 – $10,000 per month. Six months at those rates would be $12,000 – $60,000, which is why it is usually started once the store has enough traffic to test against.

The value of an exercise like this is not the final number; it is seeing which line moves the total. Here the first-year engineering is larger than the build itself, which surprises many owners. Cutting it to a handful of hours a month would save money on paper but would leave the store unchanged for a year while competitors improve theirs. Doubling it would make sense only if there is a backlog of changes worth doing.

How to get an accurate Shopify quote

Quotes are only as accurate as the information behind them. A supplier who is given a two-line description will either pad the price to cover the unknowns or quote low and recover the difference through change requests. The procedure below gets you a number you can rely on.

A paid discovery phase is often the best money spent in the whole project. For a store with several integrations, it produces the documentation a fixed-price quote needs and removes most of the risk that would otherwise be priced in. If you are still choosing a platform, do that during discovery rather than after: our comparisons of Shopify versus WooCommerce and WordPress versus Shopify set out the trade-offs.

When you brief suppliers, include the non-commerce pages too. Shipping, returns, privacy and terms pages are part of the build and part of customer trust, and they take longer to agree than most teams expect; see our guide to getting store policies and legal pages right.

Red flags in cheap Shopify quotes

A low quote is not automatically a bad one. A small, simple store on a good theme genuinely can be built at the bottom of the market range. The problem is a low quote for a project that is not small or simple, because the missing money reappears later as change requests, delays or a store that has to be partly rebuilt.

Ownership deserves a specific check. The store, the theme files, the app accounts, the domain and the analytics should be in your name, with the supplier given access, not the other way round. Suppliers who build in their own accounts and transfer later create a dependency that is awkward to unwind if the relationship ends.

Also ask what the quote assumes you will do yourself. Many low quotes assume the client supplies all product copy, all photography, all data in a clean format and all content for policy pages. That can be a reasonable split, but it has to be visible, because that work takes weeks and is often the reason a launch date slips.

Where to spend and where to save on a Shopify build

Every budget involves trade-offs, and some savings are genuine while others simply move the cost to later. The distinction is whether the saving reduces work that does not matter to customers or defers work that will have to be done anyway, usually at a higher price once the store is live and changes are riskier.

Worth spending on

• Product page and collection page design. These are where most buying decisions happen. Clear option selection, good imagery, visible delivery and returns information and fast loading on phones repay their cost more reliably than a striking home page.
• Integration reliability. Error handling, monitoring and a documented plan for when a connection fails are unglamorous, but a silent failure in inventory or order sync costs real orders and customer goodwill.
• Migration quality and redirects. Losing the search rankings of old product and category URLs is one of the most expensive mistakes in a replatforming, and one of the easiest to prevent with a complete redirect map checked before and after launch.
• Accessibility and performance. Building to WCAG guidance and keeping page weight under control is far cheaper during the build than as a retrofit, and both affect how many visitors can actually complete a purchase.
• Testing of money paths. Payments, discounts, taxes, shipping rates and refunds should be tested with real scenarios for every market and every product type before launch.

Reasonable places to save

• Start from a strong theme. Customizing a well-built theme instead of designing every template from scratch is the single biggest legitimate saving for most stores.
• Launch with fewer templates. Special landing templates, lookbooks and editorial layouts can often follow in the months after launch, built by the retained developer once real traffic shows which ones are worth it.
• Limit the apps. Each app adds a subscription, scripts on the page, another vendor and another thing to break. Choosing a few apps carefully, and building small features in the theme where that is simple, keeps both cost and page weight down.
• Bring across only the order history you need. Migrating years of old orders in full detail is expensive; many businesses keep an archive export and migrate only recent history and customer accounts.
• Prepare your own data. If your team can clean product data and write copy on schedule, the supplier's hours go into work only they can do. Be realistic about capacity, though, because late content is the most common cause of a slipped launch.

The false economies are the mirror image: skipping discovery on a complex store, cutting the redirect work, dropping post-launch support, or choosing the lowest quote without checking what it assumes. Each saves money on the proposal and costs more within the first year.

Budgeting for a Shopify store over time

The most useful way to think about Shopify store cost is as a first-year and ongoing budget rather than a single build figure. The build gets you to launch; the running costs and the improvement work determine whether the store earns its keep.

The first year

Plan for four groups of cost: the build itself; platform, app, payment and domain fees, which vary by plan and provider; content and imagery, if not already in hand; and development after launch. The first weeks after launch always surface issues no test caught, so the post-launch allowance matters most early on. A retainer that starts the week after launch, with the developer who built the store, is usually the cheapest way to handle them.

Years two and three

Once the store is stable, the budget shifts toward improvement: conversion work, new features, seasonal campaigns, theme updates and app replacements as the business changes. This is where the conversion and optimization range of $2,000 – $10,000 per month becomes relevant, scaled to traffic and ambition. A store with modest traffic will not have enough visitors to test many changes, so its budget is better spent on research and obvious fixes than on a testing program.

Replatforming and major rebuilds

Stores rarely need a full rebuild every few years if they are maintained, but businesses do outgrow their setup. Signs include integrations that break regularly, a theme so patched that simple changes take days, or checkout and market requirements the current plan cannot meet. Setting aside a modest reserve each year for a larger change means that when it comes, it is a planned project rather than an emergency. If you are weighing platforms for that future move, our e-commerce development page explains how we scope a replatforming.

Reviewing the budget each year

Once a year, set the store's costs against what it produced. List every recurring cost (platform plan, each app, retained hours, optimization work) and ask of each one whether it still earns its place. Apps installed for a single campaign are often still being paid for long after the campaign ended, and retained hours may be better spent on a different priority than the one set at launch. Review the backlog of requested changes too: if it keeps growing faster than the retained hours can clear it, that is a signal to increase the allowance or to cut the list, not to let requests pile up unaddressed. A short annual review like this keeps the store's running cost tied to what the business actually needs from it.