- Look for experience relevant to your store’s catalogue, integrations and business model, not an arbitrary number of years.
- Ask candidates to explain their exact contribution to portfolio projects.Confirm when they would use theme settings, apps, custom Liquid or a custom Shopify app.
- Expect current GraphQL Admin API knowledge because Shopify’s REST Admin API is now legacy.
- Ask how performance, mobile usability, accessibility, SEO and analytics will be protected.
- Give developers collaborator access with only the permissions required for their work.Require a documented testing, launch and rollback process.
- Clarify ownership of themes, code, design files, app accounts and technical documentation.
- Put scope, milestones, support, exclusions, pricing and change-request terms in writing.Compare proposals based on relevant capability and total value, not the lowest quote.
Hiring a Shopify developer involves more than checking a portfolio or comparing hourly rates. The developer may influence theme architecture, app selection, tracking, storefront performance, customer data and the store’s long-term maintenance requirements.
The right candidate depends on the project. A theme adjustment requires a different skill set from a platform migration, custom app, ERP integration or Shopify Plus checkout implementation. Before approaching developers, document the required outcomes, current problems, budget constraints and systems the store must support.
The following 12 questions can help you evaluate a Shopify developer’s relevant experience, technical approach, working process and post-launch responsibilities.
Question 1: Have You Completed Shopify Projects With Similar Requirements?
Why it matters: Years of experience and total project count provide context, but they do not demonstrate whether the developer has solved a problem similar to yours. Relevant complexity matters more than an arbitrary requirement such as three years or ten projects.
What to ask:
“Which Shopify projects have you completed that are most similar to my requirements, and what was your role in each?”
What a strong answer should cover:
- Store type, catalogue size and business model
- Theme, app or integration work completed
- The developer’s individual contribution
- Constraints or complications encountered
- How the implementation was tested
- Whether they can provide a reference or verifiable example
Warning sign: The candidate presents complete stores without explaining which parts they personally designed, developed or maintained.
Question 2: How Would You Translate My Requirements Into a Shopify Solution?
Why it matters: A reliable developer should understand the business problem before recommending a theme, app or custom implementation. Starting with a preferred technology can create unnecessary cost and maintenance.
What to ask:
“Based on my requirements, what would you configure, buy, customise or build, and why?”
What a strong answer should cover:
- Requirements that Shopify supports natively
- Changes possible through the theme editor
- Capabilities requiring an app
- Work requiring Liquid or custom code
- Functionality requiring a custom app or Shopify Plus
- Ongoing app, hosting or maintenance costs
- Features that should be postponed or removed from scope
Warning sign: The developer recommends a complete custom build before investigating whether Shopify’s native features or an existing supported app can meet the requirement.
Question 3: How Do You Approach Themes and Custom Code?
Why it matters: Extensive theme modification can affect performance, accessibility and future updates. The developer should be able to distinguish between theme settings, app blocks, Liquid customisation and changes that create long-term maintenance obligations.
What to ask:
“How will you structure theme customisations so that the store remains maintainable?”
What a strong answer should cover:
- Working from an unpublished theme
- Reusable sections and blocks
- Use of Liquid, JSON templates, CSS and JavaScript
- Compatibility with theme updates
- Naming and documentation standards
- Avoidance of duplicated or unnecessary code
- Browser and device testing
Warning sign: The developer plans to make undocumented changes directly to the live theme without a backup, testing process or rollback plan.
Question 4: Which Shopify APIs and Integration Methods Do You Use?
Why it matters: Integrations may connect Shopify with fulfilment providers, ERPs, CRMs, accounting platforms, subscription systems or internal applications. The implementation must account for authentication, data mapping, API limits, failures and platform updates.
What to ask:
“Which Shopify APIs have you used, and how would you design and maintain the integrations required for this project?”
What a strong answer should cover:
- GraphQL Admin API
- Storefront or Customer Account APIs when relevant
- Webhooks and event handling
- Authentication and access scopes
- API versioning and deprecations
- Retry and failure handling
- Monitoring and data reconciliation
Warning sign: The developer proposes building a new integration primarily with Shopify’s REST Admin API. REST became legacy in October 2024, and new public apps have required GraphQL since April 2025.
Need Help With Shopify Development?
We build fast, custom Shopify stores designed to drive more sales.
Question 5: How Will You Protect Mobile Usability, Performance and Accessibility?
Why it matters: A responsive layout alone does not guarantee that a store is fast, accessible or easy to use. The developer should test important customer tasks across representative devices and interaction methods.
What to ask:
“How will you test mobile usability, storefront performance and accessibility before launch?”
What a strong answer should cover:
- Shopify’s Web Performance reports
- Current Core Web Vitals: LCP, INP and CLS
- PageSpeed Insights for diagnostics
- Navigation, search, filters and product variants
- Keyboard operation and visible focus states
- Text contrast, labels and alternative text
- Representative mobile browsers and screen sizes
Warning sign: The candidate promises a specific PageSpeed score without reviewing the theme, apps, content, tracking scripts and third-party services.
Question 6: How Will You Preserve SEO and Analytics?
Why it matters: Development can unintentionally change URLs, metadata, structured data, internal links, canonical tags and analytics tracking. A developer does not need to lead the SEO strategy, but should understand how implementation choices affect it.
What to ask:
“How will you protect existing SEO signals and ensure analytics remain accurate during the project?”
What a strong answer should cover:
- Preservation of important URLs
- Redirect mapping for changed URLs
- Indexability, canonical and robots directives
- Metadata and structured-data templates
- GA4 and advertising-pixel validation
- Consent configuration
- Search Console checks
- Pre-launch and post-launch crawling
Warning sign: The developer guarantees rankings or claims that adding schema and improving Core Web Vitals will automatically move the store higher in search results.
Question 7: What Project Management Tools Do You Use?
Why it matters: Apps can add useful functionality, but they also introduce subscription costs, data permissions, scripts, and external dependencies. Developers should not install an app merely because they have used it before.
What to ask:
“How will you evaluate whether we need an app, and how will you select one?”
What a strong answer should cover:
- Native Shopify alternatives
- Theme and plan compatibility
- Data access and privacy policy
- Storefront performance impact
- Pricing and usage limits
- Support and update history
- Overlap with existing apps
- Removal and data-export process
Warning sign: The developer recommends several apps without explaining their permissions, recurring costs, overlapping functionality or effect on the storefront.
Question 8: How Will You Access and Protect My Store?
Why it matters: A developer may need access to themes, apps, products, analytics or checkout settings. Access should be limited to the permissions required for the agreed work.
What to ask:
“What store access will you require, and how will you protect credentials and customer data?”
What a strong answer should cover:
- Shopify collaborator access
- Least-privilege permissions
- Two-step authentication
- No sharing of the store owner’s password
- Secure management of API credentials and secrets
- Restrictions on customer-data exports
- Removal of access after handover
- Disclosure of subcontractor access
Warning sign: The developer asks for the store owner’s login credentials or requests unrestricted access without explaining why it is required.
Question 9: Have You Worked on Stores Like Mine?
Why it matters: A change can work on one template while breaking another product type, market, browser, or app integration. Testing should be defined before development begins.
What to ask:
“What will you test before launch, and how will you reverse the release if something fails?”
What a strong answer should cover:
- Unpublished or development environment
- Acceptance criteria for each requirement
- Theme and app regression testing
- Product, variant, cart and checkout testing
- Mobile and browser coverage
- Analytics and marketing-pixel validation
- Test orders and payment scenarios
- Backup and rollback procedures
Warning sign: The developer considers the work complete once it appears correct on the homepage or plans to test major changes directly on the live store.
Question 10: How Would You Handle a Shopify Migration?
Why it matters: A migration can affect products, customers, historical orders, reviews, subscriptions, URLs, analytics, and integrations. Not every type of data can be transferred in the same way.
What to ask:
“What data, content and functionality can be migrated, and how will you validate the result?”
What a strong answer should cover:
- Migration inventory and field mapping
- Products, variants, customers and historical orders
- Reviews, gift cards, subscriptions and customer accounts
- URL and redirect mapping
- Tax, shipping and payment configuration
- Data reconciliation
- Test orders and launch sequencing
- Downtime and rollback planning
Warning sign: The developer describes the migration as a direct copy without auditing the source platform’s data structure, URLs and third-party functionality.
Question 11: What Will I Own, and What Support Will I Receive?
Why it matters: The merchant should understand what is being transferred at handover and which services remain dependent on the developer. Post-launch support should distinguish defects from new requests.
Need Help With Shopify Development?
We build fast, custom Shopify stores designed to drive more sales.
What to ask:
“What will be transferred to me, and what does your post-launch support include?”
What a strong answer should cover:
- Store and domain ownership
- Theme licence and source code
- Design and content files
- App and integration accounts
- Repository and deployment access
- Technical and administrative documentation
- Defect warranty period
- Response times and support hours
- Maintenance pricing after handover
Warning sign: The developer retains ownership of essential accounts or code without disclosing it, or describes all post-launch problems as separately chargeable work.
Question 12: What Are the Scope, Timeline, Cost and Change Terms?
Why it matters: A quote is difficult to evaluate without knowing what is included, excluded and assumed. Changes during development should follow an agreed process rather than being added informally.
What to ask:
“Can you provide a written scope with milestones, deliverables, assumptions, exclusions, costs and change-request terms?”
What a strong answer should cover:
- Deliverables and acceptance criteria
- Project stages and dependencies
- Client responsibilities
- Fixed-price or time-based billing
- App, theme and third-party costs
- Payment milestones
- Revision limits
- Change-request approval
- Launch and support dates
Warning sign: The proposal provides only a total price and launch date without defining deliverables, dependencies, exclusions or how additional work will be priced.
Shopify Developer Evaluation Checklist
| Area | Strong evidence | Warning sign |
Relevant experience | Verifiable, comparable work with a clear explanation of their role | Portfolio links without contribution details |
Technical approach | Explains native, app and custom options | Recommends custom development immediately |
APIs | GraphQL, webhooks, versioning and failure handling | Relies mainly on the legacy REST Admin API |
Performance | Uses real-user data and template-level testing | Guarantees a PageSpeed score |
Access | Collaborator account and limited permissions | Requests the owner’s password |
Testing | Written acceptance, regression and rollback plan | Tests only after publishing |
Ownership | Code, accounts and documentation transferred clearly | Developer retains essential assets |
Pricing | Defined scope, exclusions and change process | One unexplained total price |
Conclusion
A Shopify developer should be evaluated on relevant experience, technical judgement, communication, testing and long-term maintainability—not years of experience or portfolio appearance alone.
Begin with a written description of the required outcomes and ask every shortlisted candidate the same core questions. Compare how clearly they explain trade-offs, risks, dependencies and ongoing costs. Ask for important commitments to be included in the proposal or contract.
If you need implementation support after defining the project requirements, you can hire Shopify experts for theme, integration, migration, or custom development work.
Frequently Asked Questions
1. How do I evaluate a Shopify developer’s portfolio?
Ask which parts they personally completed, what constraints they encountered and how the result was tested. A relevant, verifiable project with a clear contribution is more useful than numerous unexplained store links.
2. Should a Shopify developer use a staff or collaborator account?
External Shopify Partners should generally request collaborator access with only the permissions required for the project. Do not share the store owner’s password, and remove unnecessary access after the work is completed.
3. Should I hire the cheapest Shopify developer?
Price should be evaluated alongside scope, relevant experience, testing, documentation and support. A lower quote may exclude migration, app costs, analytics, content entry or post-launch work included in another proposal.
4. What should a Shopify development contract include?
Include deliverables, acceptance criteria, milestones, dependencies, payment terms, ownership, confidentiality, third-party costs, change requests, launch responsibilities, warranty coverage and ongoing support. Obtain appropriate legal advice for the final agreement.
