What Questions Should I Ask a Shopify Developer Before Hiring Them?

One of the biggest mistakes Shopify store owners make is hiring developers based on technical skills alone. Many founders assume that 'can they build it?' is the most important question in a developer hiring conversation. In reality, the most important question is often 'do they understand why they are building it?'

A developer can be excellent at writing Liquid, configuring Shopify metafields, and building custom sections while being a genuinely poor fit for your business. They may build exactly what they were briefed to build, correctly and on time, while the underlying business problem that prompted the brief remains entirely unsolved. The best Shopify partners understand ecommerce, conversion, operations, and customer experience. The code is how they implement solutions to business problems. It is not the point.

134The Question Most Founders Never Ask First

Before the ten questions below, there is one framing question worth asking yourself before any developer conversation: what business problem am I trying to solve? Not what do I want to build, but what outcome do I need to produce. Low conversion rate, high abandoned cart rate, inability to run a specific checkout flow, need to connect Shopify to an ERP — these are business problems. A new hero section design is not a business problem. Having that clarity before engaging a developer separates founders who get good outcomes from those who spend money on development without measurable business impact.

135Question 1: Can You Show Me Stores You Have Worked On?

Portfolio evidence is the most reliable indicator of real capability. Any Shopify developer or agency should be able to provide live URLs of stores they have worked on, not just screenshots and case study descriptions. Live stores allow you to evaluate the actual product page experience, mobile layout, page speed (test with Google PageSpeed Insights), and checkout flow on a real device. A developer unwilling or unable to share live examples should be treated with significant scepticism. The exception is under NDA — but even then, they should be able to describe the specific work done and the business outcome it produced.

136Question 2: What Exactly Was Your Role on Those Projects?

Many developers showcase stores in their portfolio where they changed a banner, fixed a single bug, or built one custom section, while the presentation implies they delivered the entire build. Understanding the specific scope of what they owned versus what they contributed to is essential for evaluating whether their capability matches what you need. Ask specifically: did you build this from scratch or customise an existing theme? Did you work with a design team or create the designs yourself? Were you responsible for the full build or a specific component? The answers reveal whether the portfolio represents their work or the work of a team they contributed a small part to.

137Question 3: What Is Your Process for a Shopify Project?

Strong developers have a defined process. Weak developers wait for instructions and react to whatever the client asks for next. A good process for a Shopify project includes discovery (understanding the business requirements and current technical state before any development begins), specification or briefing (documenting what will be built before building it), a staging environment where work is reviewed before affecting the live store, a QA workflow that systematically tests functionality on both mobile and desktop before delivery, and a defined handover that includes documentation the client can use to make future changes. A developer who describes their process as 'you tell me what you want and I build it' is a developer who will produce exactly what was specified, regardless of whether what was specified solves the business problem.

138Question 4: What Happens If Something Breaks After Launch?

Post-launch support is where many developer relationships break down. Shopify updates, app updates, and theme updates can all affect custom code. A developer who provided no post-launch support terms leaves the client in a vulnerable position the first time something breaks after go-live. Ask specifically: do you offer a support period after launch, and what does it cover? What is your process for rolling back changes if something breaks? Do you maintain theme backups before making any changes to the live store? How quickly do you respond to post-launch issues, and what is that support's cost structure? Good developers have clear answers to all of these because they have had these situations arise before.

139Question 5: How Will This Decision Impact Conversion Rate?

This question separates developers who think about code from those who think about outcomes. When you ask a developer how a proposed change or feature will affect the store's conversion rate, a developer without ecommerce understanding will give you a blank look or talk about technical implementation. A developer with genuine ecommerce understanding will discuss customer experience considerations, how the change affects the mobile buying journey, whether there is a simpler implementation that achieves the same business outcome, and potentially whether the change is likely to help or hurt conversion based on what they have seen across other stores. This does not require the developer to be a CRO specialist. It requires them to understand that the purpose of the store is converting visitors into customers.

140Question 6: What Shopify Apps Would You Recommend for This?

App knowledge is a reliable indicator of platform experience depth. A developer who has worked across many Shopify stores knows which apps are the standard solutions for subscriptions, reviews, loyalty, search, upsells, and wholesale management. They also know which apps have known issues, which have poor Shopify compatibility, and where custom development is genuinely preferable to available app solutions. A developer who defaults to custom development for requirements that could be solved with well-chosen apps at a fraction of the cost is either inexperienced with the app ecosystem or incentivised to build rather than solve. A developer who recommends an app solution before custom development wherever it is appropriate is almost always the better long-term partner.

141Question 7: Can This Be Done With Existing Shopify Functionality?

Many requirements that founders believe require custom development can be solved with the Shopify theme customiser, a well-chosen premium theme, a page builder like Instant or Replo, or native Shopify functionality introduced in recent platform updates. A developer who examines a requirement and immediately quotes for custom development without investigating whether existing functionality covers it is either not familiar enough with the current platform capabilities or is optimising for billable hours rather than client outcome. Ask this question for every major feature or functionality request. The best developers will frequently surprise founders by showing how a requirement can be met without any custom code.

142Question 8: Do I Actually Need Custom Development for This?

This question is the most powerful one on this list and the one most founders are reluctant to ask because the question itself feels like it might offend. Ask it anyway. A developer who answers honestly by telling you that a premium theme at $380 would meet your requirements better than a $5,000 custom build is a developer who is thinking about your business outcome rather than their invoice. A developer who tells you that custom development is necessary for every requirement, regardless of what it is, is a developer who is optimising for their own revenue. The best developers say no to custom development regularly. It is how they build long-term client relationships rather than one-time projects.

143Question 9: What Would You Do If This Was Your Store?

This question reveals whether the person thinks like a developer or an operator. A developer-first answer will focus on technical implementation options and what they would build. An operator-first answer will discuss priorities, tradeoffs, budget allocation, and what they would focus on first given the business stage and the available resources. The best answers acknowledge that not everything on the founder's list is equally valuable, identify what would have the highest business impact relative to cost, and are honest about what should be deferred or not built at all. A developer who engages with this question seriously is a developer worth working with. One who deflects back to 'what would you like me to build?' is telling you something about how the engagement will go.

144Question 10: Where Should I Spend My Budget Instead?

This question is deliberately uncomfortable. It asks the developer to recommend against their own engagement if the business would benefit more from a different investment. The best Shopify consultants and developers genuinely engage with it because they understand that a founder who invests in the right things at the right stage builds a business that becomes a long-term client. They may recommend investing in professional product photography, UGC and creator seeding, a product sampling programme, email marketing infrastructure, or paid advertising testing over any specific development project. A developer who cannot or will not engage with this question is not operating as an advisor. They are operating as a contractor waiting for the next brief.

145The Biggest Mistake Founders Make When Hiring Developers

Many founders hire developers to solve business problems that are not development problems. Low sales on a new Shopify store is almost never a development problem. It is a marketing problem, an offer problem, a traffic problem, or a positioning problem. A better-looking store will not fix any of those things. A developer hired to rebuild the product page to improve conversion on a store with 200 monthly visitors will produce a better-looking product page that still converts few visitors, because the underlying constraint is traffic volume and offer quality rather than page design.

The diagnostic question: if the conversion rate on this specific page doubled, how many additional sales would that produce per month at current traffic? If the answer is fewer than five additional sales, the problem to solve is traffic and offer, not page design. A developer cannot fix a marketing problem regardless of how well they execute the brief.

146Developer vs Ecommerce Operator: The Distinction That Matters

147Red Flags to Watch For

Promises guaranteed revenue increases. No developer can guarantee business outcomes. A developer who claims their work will increase conversion rate by a specific percentage before seeing the store, the traffic, and the offer is making promises they cannot keep.

Cannot explain decisions in non-technical terms. If a developer cannot explain why they are recommending a specific approach in plain English that a non-technical founder can evaluate, that developer is either unsure of the reasoning themselves or is not invested in the client understanding the work.

No QA workflow. A developer who does not describe how they test before delivering work is a developer who will regularly deliver work that requires fixing after it reaches the live store.

Pushes custom development for everything. If custom development is recommended for every requirement regardless of whether premium themes, apps, or page builders could achieve the same outcome, the developer is either not current with the Shopify platform or is optimising for billable hours.

Cannot discuss ecommerce conversion. A Shopify developer who cannot discuss what makes a product page convert, how mobile experience affects checkout completion, or what trust signals matter to first-time buyers is a developer who is building inside a commercial context they do not understand.

148Use AI to Prepare Before Any Developer Conversation

Before engaging any developer, use an AI tool like Claude to understand the scope of what you are considering and to evaluate alternatives. A useful prompt:

"I run a Shopify store in the [NICHE]. I want to accomplish [GOAL]. Act as a senior Shopify consultant and provide possible solutions across native Shopify features, app-based solutions, page builder solutions, and custom development. Then rank them by cost, complexity, maintenance burden, and expected business impact."

The output gives you enough context to evaluate whether a developer's recommendation is reasonable, whether they are proposing custom development for something a $39-per-month app solves, and whether the project scope they are describing makes sense for the goal you are trying to achieve. It also helps identify requirements you had not considered, which improves the quality of any brief you provide.

149The Best Shopify Partners Make You Smarter

The best consultants, developers, and agencies do not simply execute tasks. They explain why certain approaches are better than others, what the tradeoffs of each option are, what alternatives exist and when each is appropriate, and what the expected business impact of each decision is. A founder who finishes a Shopify project without understanding more about their platform, their options, and how to make better decisions next time has worked with a contractor. A founder who finishes a project with better operational understanding of their Shopify store has worked with a partner. The goal is finding the latter, and the ten questions in this guide are designed to help you tell the difference.