A bad Shopify developer doesn't just fail to deliver. They deliver something that requires a second developer to fix, they take weeks longer than quoted, and they leave you with code you can't maintain. Spotting the warning signs early is much cheaper than learning them mid-project.
Red flags before you hire
1. They can't show you live stores they've built.
Every experienced Shopify developer has a portfolio of live work. If someone presents screenshots in a PDF rather than live URLs, asks you not to visit a store because "the client requested privacy", or only shows you work they "contributed to" on a team, they're hiding something. It's usually a thin portfolio or work that isn't truly theirs.
Live URLs are non-negotiable. View the stores on mobile. Check page load time. Interact with the product pages and checkout. The work should hold up to scrutiny.
2. The quote arrives in under an hour with no clarifying questions.
Accurate project quotes require understanding the scope. What platform are you migrating from? How many product templates do you need? Does the checkout require customisation? What integrations are required? A developer who sends a price within an hour of receiving a brief, without asking any of these questions, is either guessing or quoting an artificially low number to win the work and adjust later.
Legitimate scoping takes time. A serious developer either asks questions before quoting or schedules a call to understand the requirements.
3. They're significantly cheaper than everyone else.
Sometimes cheap is cheap for a legitimate reason — location, earlier stage of career, simpler methodology. But when a developer is quoting 50% less than the next lowest quote for the same scope, something is different about what they're actually going to deliver. Ask specifically what they're including that others aren't, and what they're excluding that others are.
4. All their reviews are from the last six months.
A developer with fifty five-star reviews, all from the last six months, in a pattern that doesn't match organic Upwork growth is worth scrutinising. Reviews can be purchased. Experience can't. Ask for longer-term client references you can contact directly.
Red flags during the project
5. They're hard to reach and slow to respond.
A developer who goes quiet for three days without warning, misses agreed check-in calls, or takes a week to respond to a simple question is managing too many projects simultaneously or doesn't consider yours a priority. Communication patterns set in the first week of a project don't usually improve.
Set a communication expectation upfront — agreed response time, preferred channel, scheduled check-ins — and notice whether it's honoured.
6. The scope keeps expanding without a change order.
If a developer adds work to your project without pausing to scope and quote it, one of two things is happening: they're absorbing the cost (and resenting it), or they're planning to invoice for it at the end without your pre-approval. Neither is good.
Any work outside the original scope should generate a brief written description of what's being added, the cost, and your explicit approval before it begins. This protects both sides.
7. They can't explain what they built.
At any point during the project, you should be able to ask "what did you build this week?" and receive a clear answer. A developer who can't explain their work in terms a non-developer can follow either isn't doing what they said they were doing, or doesn't understand it well enough themselves. Neither is reassuring.
Red flags at handover
8. There's no documentation and no training offer.
A developer who hands over a Shopify store with "here are your login details" and disappears is leaving you dependent on them for every future change. A professional handover includes a walkthrough of the theme editor, documentation of any custom sections or features, and at minimum an offer to answer questions for a defined period after launch.
If the handover feels rushed or incomplete, it's worth addressing before the final payment is made.
What good looks like
For comparison: a developer worth hiring asks good questions before quoting, provides a fixed-price proposal with explicit scope, communicates consistently throughout the project, flags problems before they become crises, delivers work that matches the spec, and provides a complete handover.
None of these things are exceptional — they're the baseline for professional project delivery. If any of them are missing, that's the signal worth acting on.
For a full hiring guide including what credentials to look for, see how to choose a Shopify developer.
