Hire a Shopify developer: what to ask before you sign anything

When hiring a Shopify developer, it is crucial to consider three key decisions: whether a developer is necessary, the approach to take (Liquid or headless), and whether the developer is qualified for your specific version of Shopify. Relying solely on apps is often the best solution for most stores, as they are quick to install, well-maintained, and less expensive than custom code.

To determine if you need a developer, consider the following: if an app covers 80% of your needs but the remaining 20% is a hard business requirement, a developer may be necessary. Additionally, if your checkout logic exceeds what Shopify Plus functions can provide, or if custom pricing rules, B2B tiered discounts, or subscription logic cannot be found in existing apps, you should hire a developer.

Performance-related issues, such as poor Core Web Vitals scores due to a theme with multiple app-injected scripts, also warrant hiring a developer. If you require custom integrations with an ERP, WMS, or PIM lacking a Shopify app, you will need a developer to handle API work.

Before hiring a Shopify developer, ask these five questions:

1. Can you demonstrate a live storefront you have built that continues to perform well?

2. How do you handle app conflicts in Shopify?

3. How do you hand off the project, including the theme Git repository, documentation, and a staging-to-production deployment process?

4. Are you experienced with Shopify Plus or standard Shopify?

5. How do you scope work for tasks you have not completed before?

Shopify development pricing varies based on the complexity of the project. A budget under £3,000 typically covers theme customisation, while £5,000–£15,000 funds a custom liquid theme with performance work and basic integrations. A £15,000–£40,000 budget pays for complex liquid builds with custom app development, Shopify Functions, checkout UI extensions, or tight ERP integration. If a quote falls significantly below these ranges, ask what is not included, as scope gaps often result in change orders.

The right developer should provide a properly maintained repository, a README explaining custom sections and app dependencies, and a staging environment for local previews. Ensure that, upon handoff, you have access to commit history, a staging store, and a clear deployment process. If a developer promises headless solutions without understanding your app requirements, GMV, and team capacity, treat this as a yellow flag.