What Custom Shopify Development Actually Costs and What Drives the Number

If you have asked three Shopify agencies for a quote on the same project and gotten back three numbers with almost nothing in common, you have already found the real problem. Nobody is lying to you. The phrase “custom Shopify development” simply covers more than one kind of work. A checkout tweak and a ground-up Plus replatform both fall under that phrase. The price difference between them is a different order of magnitude entirely.

The number you actually need is not “how much does custom Shopify development cost.” It is “what, specifically, in my project, is going to move that number.” This article covers the four factors that set the price, where projects typically go over budget, what a scope document should contain before you sign anything, and the questions to ask before you accept a quote.

Why Shopify Development Cost Isn’t a Price List

A flat price list does not exist because the phrase “custom development” covers wildly different work. It can mean a focused theme adjustment, or a full Shopify Plus build with custom apps and system integrations. A published number would be true for almost no one, because it depends entirely on what “custom” means for that specific store.

What we can give you is where our own projects land. Theme-based work, where a well-configured theme takes targeted customization, runs $3,000 to $5,000. A custom build, designed and developed rather than adapted, runs $6,000 to $10,000. Shopify Plus projects start at $10,000 and go up from there.

Those are SPLIT Development bands, not an industry survey. They tell you the shape of the work at each level. They do not tell you what your project costs, because that still depends on how many hours your specific scope needs, and scope is set by the four factors below.

None of this means pricing is arbitrary. It means the number is a function of scope, not of the word “custom” itself.

The Four Things That Move the Number

Every Shopify project quote, whether it comes in low or high, answers four underlying questions. Getting clear on these before you request a quote is the best way to keep the number you receive from moving later.

Catalog Complexity

A 40-SKU catalog with one sizing logic and a 4,000-SKU catalog spanning multiple categories are not the same build, even if both merchants ask for “a custom Shopify store.” Catalog complexity affects the data model, the collection architecture, the filtering logic, and often the product page template itself. A store selling footwear and outerwear needs different sizing structures for each. That is template work, not a settings toggle.

Integrations and App Replacement

Connecting Shopify to an ERP, a 3PL, a subscription engine, or a custom CRM is routinely one of the most expensive line items in a build. Cost per connection varies more than anything else on a quote, because it depends on the system API and on how much custom logic has to sit between the two platforms. A documented REST API with a stable data model is a different job from a legacy system that exports a CSV on a schedule.

Sometimes a third-party app gets replaced with custom code instead, because the app is too expensive at scale, too limited, or creates a checkout conflict. That replacement carries its own cost on top of the integration itself.

This is rarely a single connection. On One Clear Drop, a zero-waste subscription brand, SPLIT Development built on top of Sharpei Subscriptions as the subscription engine rather than writing billing logic from scratch. Custom Shopify Flow automation was layered on top for a free-third-order promotional mechanic.

The most complex piece was a separate integration: an automated handoff to an external debt-collections platform for subscribers who stopped paying. That required reconciling subscription state from Sharpei with the order history Shopify holds. A third, independently built flow handled quarterly consumable replenishment on top of all that. Two external system integrations plus a custom automation layer, on one store. It is a realistic picture of why “one integration” in a quote can hide very different amounts of work.

Design Scope vs Template Scope

There is a real difference between customizing a theme (new sections, a revamped homepage, new templates layered onto an existing foundation) and building a custom design from a Figma file with no theme underneath it. That difference is what moves a project from the $3,000 to $5,000 band into the $6,000 to $10,000 one. Advanced builds on Shopify Plus sit above both, and their cost scales with integration count, platform migrations and B2B logic rather than with the number of templates.

“Theme customization” at a serious level can still be a large build. For ISMYLOVA, a Miami luxury boutique carrying dozens of designers and thousands of SKUs, SPLIT Development used Dawn as the technical foundation but rebuilt most of what a shopper actually sees on top of it: custom product cards and page templates, a reworked mega-menu that blends categories and designer brands, a bespoke cart drawer, and full Shopify Markets configuration for international selling.

Nothing about that build was a default Dawn install, and it was not a from-scratch custom theme either. It sits deliberately in the middle of the spectrum, which is where most serious fashion and retail catalogs land.

Ongoing Support After Launch

A launch is not the end of the cost conversation. Most agencies price post-launch support as a separate retainer, and the structure matters more than the headline number: bug fixes only versus active feature development, response-time guarantees, and how often the store needs updates as Shopify ships platform changes. A quote that covers the build and says nothing about the week after launch is missing a real cost, not a minor one.

SPLIT Development supports One Clear Drop on exactly this basis after launch. The work is priced task by task rather than as a fixed monthly block: fixes and new functionality as the subscriber base grows and edge cases surface that a pre-launch scope could not have predicted. For a store built around subscription logic and multiple integrations, that ongoing relationship is where a meaningful share of real-world reliability gets maintained.

Theme Customization vs Custom Theme Build

Not every project needs a from-scratch build. The first question in any scoping conversation is whether a well-configured theme, with targeted customization, solves the problem.

Signal	Theme customization usually fits	Custom theme build usually needed
Catalog structure	Single product category, stable sizing and variant logic	Multiple categories with genuinely different logic (footwear plus apparel, for example)
Design ambition	Brand fits within an existing theme’s layout patterns	Design starts as a Figma file with layouts no theme was built to hold
Integrations	One or two standard, app-based integrations	Custom API connections to ERP, 3PL, or proprietary systems
Interactive features	None, or handled by an off-the-shelf app	Configurators, booking systems, custom calculators, generative product tools
Update cadence	Manual seasonal or occasional updates are manageable	Collections, content, or pricing need to change on a schedule the theme can’t automate
Team capacity	In-house team can manage app settings and content	Nothing in-house can maintain custom Liquid, sections, or app logic

If most of your answers land in the left column, a configured theme is very likely the right and cheaper starting point. If two or more land in the right column, that is usually where a custom build starts paying for itself, because a theme workaround for a structural problem gets more expensive to maintain than building it correctly once. We went through that decision in more detail in our breakdown of standard Shopify development versus a custom build.

Where Projects Go Over Budget

Quotes rarely go over budget because the original number was wrong. They go over budget because the scope changed after the number was set, and the same handful of causes show up again and again.

Scope discovered mid-build, not before it. A catalog turns out to need two sizing systems instead of one. A “simple” integration turns out to require custom middleware because the two APIs do not talk to each other cleanly. This is the single most common driver of overruns, and it is almost always avoidable with a more thorough discovery phase.

Third-party app conflicts. Two apps that both modify checkout, or a theme and an app that both try to control the same section, can force custom development just to resolve the conflict. That work was never in the original quote, because nobody knew the conflict existed until both were installed together.

Design finalized after development starts. When Figma files are still changing once Liquid work has begun, every round of design revision becomes a development revision too, and those hours are rarely built into a fixed quote.

“While you’re in there” additions. Small, reasonable-sounding requests get added mid-project: one more page template, one more automation. They are individually cheap and collectively the most common reason a fixed-price project quietly becomes a time-and-materials one.

No defined post-launch boundary. Without a clear line between included in launch and billed separately after, bug fixes and small feature requests in the weeks after launch get treated as original scope by the client and as new work by the agency. That mismatch shows up as a dispute, not a line item.

What a Realistic Scope Document Contains

A scope document is the tool that prevents most of the list above. A document worth signing off on should include, at minimum:

• A page-by-page or template-by-template breakdown. Every unique template the store needs (product, collection, PDP variants, landing pages, checkout customization) should be listed, not folded into a single line item that says “custom theme.”

• A named list of every integration, including which system owns which data, and whether the connection runs through an existing app, a Shopify API, or custom middleware.

• Explicit out-of-scope items. What is not included is often more useful than what is. It is what prevents scope creep later.

• A design-freeze point, the stage at which design changes move from included revisions to billed change requests.

• A launch-to-support handoff, separating what counts as a launch bug fix from what counts as a new feature request and a separately scoped piece of work.

• A timeline broken into phases (discovery, design, development, QA) rather than a single end date, so a delay in one phase is visible immediately instead of showing up as a missed launch.

If a quote arrives without most of this, that is not automatically a red flag. But it usually means the real scoping conversation has not happened yet, and the number you were given is a placeholder rather than a commitment.

Questions to Ask Before You Accept a Quote

Before signing off on any Shopify development quote, a short conversation can surface most of the risk above.

• What exactly is the catalog and integration assumption behind this number? If the agency cannot name the specific sizing logic, apps, or systems the price assumes, the number is a rough estimate rather than a scope-based quote.

• What happens if the riskiest part turns out to be more complex than expected? Name it yourself (a legacy ERP, an unusual sizing system, a custom checkout flow) and ask directly how a surprise there gets handled and billed.

• What is explicitly out of scope? A vendor who answers this quickly has actually scoped the project. A vague answer usually means the number will move.

• What does support look like in the first 30 days after launch, and what does it cost after that?

• Can you show a build with a comparable scope? Not just “a Shopify store,” but a project with a similar catalog structure, integration count, or feature set.

• Is their “Shopify Plus Partner” claim current? Shopify sunset that standalone program in December 2024 and folded agency credentials into a single Partner Program with five tiers: Registered, Select, Plus, Premier, Platinum. A vendor still leaning on the old badge alone is not necessarily wrong, but it is fair to ask what tier they hold now. SPLIT Development is listed at Select tier in the Shopify Partner Directory.

A vendor who welcomes these questions and answers them with specifics is usually the one whose final invoice will look like their first quote.

Between the pricing bands, the four cost drivers, and the questions above, you should have a clearer picture of where your project sits — theme customization or a custom build. If your catalog, integrations, or design ambitions still don’t fit cleanly on one side, SPLIT Development can take a closer look at the specifics.