Signs Your Shopify Store Has Outgrown Its Current Developer

If you’re reading this, something has probably already gone wrong. Maybe a simple product page change took three weeks to ship. Maybe a new app broke your checkout the day before a sale. Maybe you asked your developer a straightforward question about Shopify Plus and got a vague answer back.

None of these things, on their own, mean you need to switch. Every Shopify store hits friction with its developer at some point, a busy week, a tricky bug, a miscommunication. The question worth asking isn’t “did something go wrong once,” it’s whether there’s a pattern, and whether that pattern is a sign your store has genuinely outgrown the person maintaining it.

This post walks through the real, concrete signs that indicate your Shopify build has moved past what your current developer can support, plus, just as importantly, the signs that don’t warrant a switch. By the end you’ll have a practical way to tell which situation you’re actually in.

The real question: has your store outgrown them, or is this a normal rough patch?

A lot of Shopify stores start with a freelancer or a small shop doing theme customisation, a handful of apps, and basic support. That’s completely appropriate for a store doing a few hundred orders a month on a standard Shopify plan with an off-the-shelf theme.

The problem shows up when the store’s complexity grows faster than the developer’s capability or capacity. Common growth triggers include:

Moving from Shopify to Shopify Plus
Adding B2B/wholesale functionality alongside DTC
Running 15+ apps that all need to play nicely together
Expanding into multiple markets, currencies, or a headless front end
Needing checkout customisation, custom shipping logic, or ERP/inventory integrations
Scaling paid traffic to the point where page speed and conversion rate genuinely move revenue

If any of these apply to you, it’s worth reading the signs below with a critical eye, not to justify a switch you’ve already decided on, but to check whether the diagnosis is accurate.

Sign 1: Turnaround times keep blowing out

Every developer has busy periods. The warning sign isn’t a slow week, it’s a consistent pattern where simple requests (a copy change, a metafield tweak, a new collection template) take far longer than the work itself should require.

In our experience running Shopify support and consulting engagements, a competent developer working inside an Online Store 2.0 theme can usually turn around a scoped, well-briefed change, a new section, a template variant, a metafield-driven module, within a few business days, not weeks. If small changes routinely queue for a fortnight or more with no clear reason (holiday periods and genuinely complex requests aside), that’s often a capacity or prioritisation problem, not a “this is just how Shopify works” problem.

Sign 2: They’re out of their depth on Shopify Plus or Liquid

Shopify and Shopify Plus are not the same platform to build on. Plus unlocks things like Shopify Functions for custom discount, shipping, and payment logic, Checkout Extensibility for customising the checkout experience, multiple checkout extension points, and higher API rate limits. A developer who has only ever worked on standard Shopify stores often doesn’t know these exist, let alone how to use them properly.

Practical signs of this gap:

They suggest injecting custom JavaScript into checkout instead of building a proper Shopify Function or checkout UI extension
They’re unfamiliar with checkout.liquid being retired for Plus stores (Shopify enforced Checkout Extensibility migration for Plus merchants by August 2024) and haven’t migrated legacy customisations across
They don’t understand the difference between Online Store 2.0 JSON templates and older, hard-coded Liquid templates
They default to “that’s not possible in Shopify” for things that are genuinely possible with the right approach

If you’re on Plus (or heading there) and your developer’s answers keep circling back to workarounds rather than native Plus features, that’s a real capability gap, not just a personality clash. If you’re not sure whether the jump to Plus even makes sense for you yet, it’s worth checking is Shopify Plus worth it before assuming the platform is the issue.

Sign 3: Every app install feels like a gamble

Shopify stores accumulate apps quickly, reviews, subscriptions, upsells, loyalty, shipping rules, personalisation. Each one injects its own scripts, app blocks, or webhooks into your store. A developer who understands Shopify properly should be able to tell you, before you install something, roughly what it will touch (theme app extensions vs. legacy script tags, whether it needs checkout access, what it’ll do to page speed).

Signs your developer isn’t managing this well:

New app installs regularly break something unrelated (cart drawer, product page JS, checkout)
Nobody can tell you which of your 20+ installed apps are actually still active in the theme
App conflicts get “fixed” with hacky !important CSS overrides or timeout-based JavaScript patches instead of a proper root-cause fix
There’s no process for auditing or removing unused apps, so app-related script bloat just accumulates

This is one of the most common patterns we see when we run a Shopify audit on a store that’s been through a few years of ad hoc development, a theme quietly carrying five or six apps nobody remembers installing, each adding its own load weight and risk of conflict.

Sign 4: No proactive performance or CRO input, ever

A developer who only ever does what you explicitly ask for is fine at small scale. Once you’re spending real money on paid traffic, or your store is core to the business, you need someone who occasionally comes back to you unprompted with things like:

“Your product page Largest Contentful Paint has crept up since the last theme update, here’s why”
“This app is loading a 400KB script on every page even though it’s only used on the cart page”
“Your mobile add-to-cart flow has an extra step that’s probably costing you conversions”

If every performance or conversion issue on your store has been found by you, your marketing agency, or a customer complaint, rather than flagged by the person who actually maintains the code, that’s a sign your developer is operating in pure ticket-taker mode rather than as a technical partner.

Sign 5: Communication has become the bottleneck

This one’s less technical but just as real. Watch for:

Estimates that are consistently wrong in one direction (always longer, always more expensive)
Technical explanations that don’t actually answer the business question you asked
Changes going live without being communicated, or being communicated after the fact
No clear process for urgent fixes when the store is genuinely broken

Good communication doesn’t mean constant hand-holding, it means you’re not left guessing about the state of your own store.

Sign 6: The theme is held together with fragile custom code

Pull up your theme code (Online Store > Themes > Edit code) and look for:

Large blocks of inline JavaScript pasted directly into theme.liquid rather than organised into proper assets
Duplicated logic across multiple section files that should be a single reusable snippet
Hard-coded product IDs, collection handles, or prices sitting in Liquid instead of using metafields or settings
Comments like // temporary fix, remove later that have clearly been there for over a year

None of this is unusual for a store that’s grown organically, most stores have some technical debt. The concern is when nobody has a plan to address it, and every new feature gets bolted on top of the mess rather than cleaned up as part of the work.

Sign 7: They don’t understand Shopify’s platform limits

Shopify has hard rules that a genuinely experienced developer should know cold: API rate limits, the constraints around what can and can’t be customised in checkout without Plus, theme file size and asset limits, and how metafields, metaobjects, and the Storefront API fit together. A developer regularly surprised by these limits, discovering them mid-project instead of planning around them, will cost you time and, sometimes, a failed launch.

When switching isn’t actually warranted

To be fair to developers everywhere: not every rough patch means it’s time to move on. Some things that look like red flags usually aren’t:

A single missed deadline during a genuinely complex build (Plus migrations, custom app development, ERP integrations all take longer than expected sometimes)
Pushback on a request that’s actually a bad idea for your store (e.g. wanting to hack around Shopify’s checkout instead of using supported extension points)
Slower turnaround during Black Friday/Cyber Monday season, when every good Shopify developer in the country is at capacity
Being honest that something isn’t possible, Shopify does have real platform limits, and a developer telling you “no” isn’t automatically wrong

If it’s an isolated incident with a clear explanation, that’s not the same as a pattern.

A quick self-audit checklist

Before you make a call either way, run through this:

Turnaround, Have simple requests taken materially longer over the last 3-6 months, with no clear reason?
Plus/Liquid fluency, Can they explain, in plain terms, how Shopify Functions, Checkout Extensibility, or Online Store 2.0 templates work?
App governance, Do they know exactly what every installed app does to your theme and page speed?
Proactive input, Have they flagged a performance, SEO, or conversion issue without being asked in the last quarter?
Communication, Do you generally know the state of your store, or are you finding out about problems from customers?
Code quality, When you look at the theme code, does it look maintained, or does it look patched?
Platform knowledge, Do they understand Shopify’s real limits, or do they discover them mid-project?

If you’re answering “no” to four or more of these, that’s a genuine signal, not just a bad week.

When to bring in a specialist

If the checklist above is ringing true, the next step isn’t necessarily to fire your current developer immediately, it’s to get an independent, technical read on the actual state of your store before you make a decision. This is exactly the kind of gap a Shopify consulting engagement is designed to catch: a second opinion on your theme architecture, app stack, and Plus (or Plus-readiness) setup, done by someone with no stake in defending past decisions.

That review typically gives you one of two outcomes, a clear list of fixes your current developer can action, or confirmation that it’s genuinely time to bring in different help. Either way, you’re making the call with actual information rather than frustration.

FAQ

How do I know if my Shopify developer is actually experienced with Shopify Plus, not just standard Shopify?
Ask them directly about Shopify Functions, Checkout Extensibility, and B2B on Shopify if relevant to you. A developer with genuine Plus experience will talk about these specifically and know their current limitations, not just describe them in marketing terms.

Is it normal for a Shopify store to have technical debt?
Yes, almost all stores that have been live for more than a year or two carry some technical debt from apps, promotions, and past redesigns. The issue isn’t the debt itself, it’s whether anyone has a plan to manage it.

Should I switch developers or agencies right before a big sale period?
Generally no. Unless your current setup is actively broken, it’s safer to stabilise through peak trading (Black Friday/Cyber Monday, EOFY sales) and transition afterwards, when there’s less risk and more time to do a proper handover.

What should I ask a new developer or agency before switching?
Ask them to review your current theme and app stack first, rather than quoting blind. A specialist worth hiring will want to see the store before committing to timelines or pricing.

Will switching developers mean rebuilding my store from scratch?
Not usually. A competent incoming developer can typically work within your existing theme and Shopify setup, migrating or refactoring problem areas rather than starting over, unless the underlying theme architecture is genuinely beyond repair.

Next step

If you’re still not sure whether this is a developer problem or a “normal growing pains” problem, the fastest way to find out is to get a second set of eyes on the store itself. Book a call with our team and we’ll give you a straight answer on what we see.