Shopify stores rarely fail at the storefront. The theme loads, the product pages look right, the cart works. What breaks is further in — at the seams, where the store meets a supplier’s stock feed, a courier’s API, an accounting system, or a promotion the platform has no native way to express.
The pattern repeats across the stores we get called into. A merchant runs a campaign built out of three stacked discount apps. The apps each work. Together they apply in an order nobody specified, and a fortnight later the margin report does not match the revenue report. Or inventory is synced by a nightly export that silently skipped forty SKUs because one supplier changed a column heading. Nothing shows an error. The store just quietly sells things it does not have.
That is the honest shape of Shopify development work. A small part of it is making a store look the way it should. Most of it is making the store behave correctly at the points where Shopify hands responsibility back to you.
What Shopify development services actually cover
The phrase covers four fairly different kinds of work, at very different costs. Knowing which one you need is most of the decision.
- Store setup and configuration. Installing a paid or free theme, loading products, configuring tax, shipping zones, payment providers, domains and email. Real work, but configuration rather than engineering.
- Theme customisation. Adapting an existing theme — new sections, custom product-page layouts, structured content through metafields, a redesigned collection experience. This is where most stores spend their budget, and where the most value usually sits.
- A custom theme build. Building a theme from a design, rather than bending someone else’s. Justified when the brand experience is the differentiator, or when an existing theme has been customised so heavily that maintaining it costs more than replacing it.
- Apps, integrations and business logic. Connecting Shopify to systems that were never designed to talk to it, and encoding rules the platform does not model natively. This is the part that quietly decides whether an operations team spends its week selling or reconciling.
Most requests that arrive as “we need a Shopify developer” turn out to be the second or the fourth. Very few are genuinely the third.
What Shopify handles for you — and where that stops
Shopify’s central trade is a good one: you give up some control and you stop being responsible for an entire category of problems. It is worth being precise about where that line falls, because the line is exactly where development work begins.
The parts you genuinely stop worrying about
Hosting, SSL, CDN delivery, uptime during a traffic spike, PCI compliance for card data, and the security patching of the platform itself are Shopify’s problem. For a self-hosted store, every one of those is a standing cost and a standing risk. That difference is real, and it is the strongest argument for the platform.
The checkout is the boundary
Shopify owns its checkout, and that ownership is the source of both its reliability and its constraints. You cannot rewrite it. What you can do is extend it through Shopify’s own extension points — interface extensions that add fields or content at defined positions, and server-side functions that change how discounts, shipping options and payment methods behave.
That covers a great deal in practice: a delivery-date picker, a gift message, a rule that hides express shipping for oversized items, a discount that stacks in a specific order. What it does not cover is a fundamentally different checkout flow. If your business genuinely requires one, Shopify is the wrong platform and no amount of development will change that. Being told this early is cheaper than discovering it in month three.
Apps solve a problem and create a cost
The App Store is the platform’s real advantage and its most common failure mode. Any individual app is cheap relative to building the same thing. Fifteen of them are not. They stack monthly fees, each adds scripts to the storefront, several will want to modify the same theme files, and two of them will eventually disagree about which discount wins.
The useful question is not “is there an app for this” — there usually is. It is whether this particular capability is close enough to your business’s core that owning it outright is worth the build cost.
The theme customisation trap
Themes receive updates from their authors. A theme whose Liquid files have been edited directly cannot take those updates without someone manually reconciling the changes, so in practice it never does — and two years later the store is running a version of a theme that has diverged from anything the author supports.
Modern Shopify themes are built to avoid this. Sections, blocks and app blocks let a great deal of customisation live in configuration and in additive files rather than in edits to the theme’s core templates. A developer who reaches for direct file edits as a first instinct is quietly handing you a maintenance bill that arrives later, under someone else’s name.
Shopify or WooCommerce? An honest comparison
We build on both, so we have no stake in the answer. The choice comes down to how much control you need and how much operational responsibility you want to carry.
| Shopify | WooCommerce | |
|---|---|---|
| Hosting & security | Included and handled for you | Yours to arrange, monitor and pay for |
| Checkout control | Extendable at defined points, not replaceable | Fully customisable, including its structure |
| Payment flexibility | Strong for card markets; third-party gateways may incur extra fees | Any gateway, including manual and regional methods |
| Running cost | Predictable plan fee, plus app subscriptions that accumulate | Hosting plus maintenance; no per-feature subscriptions |
| Time to launch | Faster — the infrastructure decisions are already made | Slower, with more decisions to get right |
| Data ownership | Your data, on their platform, via their APIs | Your database, on your server |
| Best suited to | Teams who want to sell rather than operate software | Stores with unusual workflows or regional payment needs |
The short version: Shopify is usually right for a store that wants to grow without acquiring a technical operations burden. WooCommerce is usually right when the business model itself is unusual — manual payment verification, region-specific courier workflows, or order processes that no hosted checkout will ever model. We have written elsewhere about replatforming between the two, which is a different project from either.
What Shopify development costs
Rates vary enormously by region and by what is actually being bought. The ranges below are for the development work itself and reflect what serious projects cost from an established agency — Shopify’s own plan fee and any app subscriptions are separate and ongoing.
| Scope | Typical range | What it involves |
|---|---|---|
| Store setup and launch | $1,500–$4,000 | A paid theme configured properly: products, collections, tax, shipping, payments, domain and email. Light visual adaptation. |
| Theme customisation | $4,000–$12,000 | Custom sections, product-page work, metafield-driven content, collection and navigation redesign, performance tuning. |
| Custom theme build | $12,000–$30,000+ | A theme built from a design system rather than adapted. Usually paired with a brand or UX project. |
| Custom app or integration | $3,000–$18,000+ | ERP, inventory or courier integration; Shopify Functions for discount, shipping or payment logic; internal admin tooling. |
| Ongoing support | $300–$1,500 / month | Changes, monitoring, app conflict resolution and the small work that otherwise waits months for a project. |
Two notes on reading that table. A quote far below these ranges is usually configuration being sold as development, which is fine if configuration is what you need and expensive if it is not. And a quote far above them should come with a scope document explaining why — complexity is a legitimate reason, and vagueness is not.
When you actually need a custom app
Most stores never need one, and an agency that proposes a custom app for every request is selling hours. There are three situations where building genuinely wins.
- The logic is your business. Pricing rules, allocation, made-to-order configuration — if the rule is the thing that makes you different, renting it from an app means your differentiator is on someone else’s roadmap.
- The integration does not exist. Regional couriers, local accounting systems and older ERPs often have no App Store listing at all. Someone has to write the connector, and the alternative is a person retyping orders between two screens.
- The app stack has become the problem. When six subscriptions cost more annually than a build, conflict with each other, and slow the storefront down, consolidating into one owned app is a cost reduction rather than an expense.
Outside those cases, an App Store subscription is the better answer, and we will say so. We build custom Shopify apps when they are warranted — which is less often than an agency with hours to fill would tell you.
How to choose a Shopify developer
Portfolios all look similar, because Shopify themes all reach a similar baseline. These questions separate the work from the presentation.
- “How do you customise a theme without blocking its updates?” A good answer talks about sections, app blocks and additive files. A vague one means you will inherit a theme nobody can update.
- “What will this add to page weight?” Anyone who has genuinely worked on conversion has a view on the storefront performance cost of what they are proposing.
- “Which of these features should be an app we buy instead?” A developer who never recommends buying is not advising you.
- “Who owns the code, and what happens if we leave?” The answer should be immediate, unambiguous, and in the contract.
- “What does support look like after launch?” Stores need changes. A developer with no support arrangement is planning to disappear.
Warning signs
- A fixed price quoted before anyone has asked what the store needs to do.
- No mention of staging. Changes going straight to a live store is not a workflow, it is a habit.
- Every requirement answered with “there is an app for that” — or none of them.
- Reluctance to name the theme, framework or approach they intend to use.
- Timelines that do not include your review time. Your feedback is part of the schedule, not an interruption to it.
How we approach Shopify work
We start by asking what the store has to do operationally, not what it should look like. Design matters — it is most of why people trust a brand — but a beautiful store that cannot express its own shipping rules will consume more of your week than an ordinary one that can.
Customisation goes into sections, blocks and metafields wherever the platform allows it, so the theme can still take updates. Integrations are built to report their failures rather than swallow them, because a sync that silently skips records is worse than one that stops and says so. And anything we build is documented well enough that another developer could pick it up, which is the only meaningful test of whether you own it.
The same principles apply to our Shopify theme development and app development work, and to the maintenance that keeps either of them working after launch.
Frequently asked questions
How long does a Shopify store take to build?
A configured store on an existing theme is typically two to four weeks. A substantial theme customisation is six to ten. A custom theme built from a design runs ten to sixteen weeks, and a custom app or integration is usually four to twelve depending on what it connects to. The largest variable is rarely the development — it is how quickly product data, photography and copy arrive.
Do I need Shopify Plus?
Most stores do not. Plus is worth its cost at high order volume, for multi-store or multi-region operations, or when you need the deepest level of checkout control and higher API limits. Below that threshold the money is almost always better spent on development and marketing than on the plan tier.
Can you customise the Shopify checkout?
Yes, within Shopify’s extension model. Fields, content and validation can be added at defined points in the checkout, and discount, shipping and payment logic can be changed with server-side functions. What is not possible on any plan is replacing the checkout with a flow of your own design — if that is a hard requirement, the platform is the wrong fit.
Is Shopify better than WooCommerce?
Neither is better in general. Shopify removes the operational burden of running store infrastructure and charges for that in plan and app fees. WooCommerce gives complete control over checkout, payments and data, and charges for that in hosting and maintenance. Choose Shopify to sell without operating software; choose WooCommerce when your business model needs behaviour a hosted checkout will not allow.
Will custom development slow my store down?
It can, and badly done it usually does. Every app and script added to a storefront costs page weight, and page weight costs conversions on mobile connections. Well-built custom work is frequently faster than the app stack it replaces, because one purpose-built feature loads less than three general-purpose ones.
Can you work on a store you did not build?
Yes, and it is most of what we do. The first step is an audit: what the theme is, how heavily it has been modified, which apps are installed and what they actually cost, and where the storefront is losing speed. That audit is worth having even if you then decide to do the work elsewhere.
Planning a Shopify build, a replatform, or trying to work out whether a custom app is justified? Let’s Talk — we will give you a straight assessment, including when the answer is that you do not need us.