Hire a Shopify Theme Developer: 12 Questions to Ask

Hiring a Shopify theme developer looks simple until you compare three quotes. One is for ₹8,000 and one is for ₹60,000, and both describe the work as "customise your theme". A month later the cheap job has left a broken mobile layout, nobody can say where the code lives, and your store is slower than before.

This guide shows you how to hire a Shopify theme developer without guessing. It explains what the role covers, gives you twelve questions to ask, shows how to share store access safely and lists red flags that usually predict a bad project.

What does a Shopify theme developer actually do?

A Shopify theme developer writes and edits the code that controls how your storefront looks and behaves, mainly in Liquid, CSS and JavaScript. Liquid is Shopify's template language, and it decides what appears on product, collection, cart and home pages.

That is different from store setup, which means adding products, installing a theme and configuring settings in the admin. It is also different from app development, which needs back-end code and the Shopify APIs. When people say "Shopify developer", they may mean any of the three, so write down which one you need. Our Shopify Liquid development guide explains where theme code ends and app work begins.

Do you need a theme developer, an app or a page builder?

You need a theme developer when the change is about presentation and merchandising, and an app when it needs server-side logic. A page builder can help with one-off layouts, but it often adds scripts to every page.

If your question is whether to build a section or buy an app, our post on custom Shopify sections goes through the trade-offs.

Freelancer, studio or agency: which should you hire?

Choose by the size and risk of the work. A freelancer suits a defined change, a studio suits a series of modules, and an agency suits a rebuild with design, testing and support. The indicative figures below come from project experience in India and are not fixed prices.

Shopify's Partner Directory lets you browse by service, including theme customisation, and filter by location, language and price range, according to Shopify's hiring help page. Treat a listing as a starting point, not proof of quality.

What are the 12 questions to ask before you hire?

Ask questions that force specific answers, because good developers can describe past work in detail and weak ones fall back on generalities. Use this list in your first call:

1. Which live stores did you build, and what exactly was your part? Open them on your phone and complete a test checkout.
2. What did you build beyond theme setup? Look for custom sections, snippets or metafield-driven layouts.
3. Are you comfortable with Online Store 2.0? Sections, JSON templates and blocks should be familiar.
4. How will my team edit what you build? The answer should mention schema settings and presets, not hard-coded text.
5. Where will you work: live theme or a copy? The right answer is a duplicate or development theme.
6. Where does the code live? Expect version control and Shopify CLI.
7. Do you run Theme Check? Shopify's Theme Check flags errors and performance issues before launch.
8. How do you protect speed? Ask for before-and-after Core Web Vitals on past projects.
9. How do you test? Product, collection, cart and home templates, real phones and a full checkout.
10. How will you access my store? Collaborator access with limited permissions is the only good answer.
11. Who owns the code at the end? You should, with a full handover.
12. What happens if something breaks after launch? A stated bug-fix window and response time.

How do you check a portfolio properly?

Check a portfolio by testing live stores, not by admiring screenshots. Ten minutes per store tells you more than any case study.

• Open the store on a mid-range Android phone and use the cart and menu.
• Run Google's PageSpeed Insights on the mobile view. web.dev's Core Web Vitals guide lists the targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less.
• Count third-party app scripts in the page source; a dozen suggests features were installed rather than built.
• Ask what the developer personally built, and whether the client will take a reference call.

Remember that a fast store may have a simple catalogue and a slow one may suffer from apps the developer did not install. Judge decisions, not just scores. If your own theme is already sluggish, our guide to fixing a slow Shopify theme shows what an audit should find.

How do you give a developer access safely?

Give access through Shopify collaborator accounts and grant only the permissions the job needs. Shopify's help page on collaborator accounts explains that collaborators are Shopify Partners you have allowed to access your store, that they must have two-step authentication enabled, and that you manage or remove their access from your admin.

A few details from that page are worth remembering:

• The developer needs your four-digit collaborator request code before they can send a request, and you can generate a new code at any time.
• You review the permissions they request and can edit them before you accept.
• Collaborator access expires automatically if they have not logged in for 90 days.
• You cannot transfer store ownership to a collaborator, which protects you from the most damaging mistake.

Never share your owner email and password. When the project ends, remove the collaborator account.

How should the project run from quote to launch?

A safe project follows a fixed order, so the live store never becomes the test environment.

1. Write a one-page brief with the pages affected, mobile designs and who edits what.
2. Get a written scope that lists templates, settings, browsers and testing.
3. Agree access: collaborator request, limited permissions, named contact.
4. Build on a duplicate or development theme with version control.
5. Review a preview link on real phones, and have your marketing team fill in real content.
6. Run Theme Check and a speed check and compare with the starting numbers.
7. Publish at a quiet time with rollback notes, then monitor orders and errors for a week.
8. Receive the handover: code, documentation of settings and a list of files touched.

Also ask which theme the store is built on and how future theme updates will be handled. A heavily modified theme cannot simply take an update, so the developer should document every change. If your theme is old, our guide to moving to Online Store 2.0 explains why migrating first can make later work cheaper.

What red flags should make you walk away?

Walk away when a developer cannot show verifiable work, avoids process questions or asks for risky access. The most common warning signs are:

• No live links, or links to stores they cannot explain.
• A request for your owner login or staff account password.
• Editing the live theme directly, with no backup or preview.
• A very low fixed price with no testing, handover or support included.
• No answer on who owns the code.
• Promises of sales or rankings; no developer can guarantee those.
• Pressure to install many apps for features a section could handle.

How Arham Technology approaches Shopify theme work

Our Shopify Liquid development service is built for stores that have outgrown theme settings. We follow a change-control routine so your live store stays stable:

• Theme audit: we inspect the active theme's section map, app injections and performance hotspots before proposing work.
• Section spec: settings, blocks and the content model are defined so marketing can self-serve afterwards.
• Development theme build: code lands on a development theme with Theme Check and regression passes across templates.
• Merchant preview: your editors configure the new modules with real campaign content.
• Publish and guardrails: we document settings, leave rollback notes and monitor storefront health after launch.

Typical deliverables include Online Store 2.0 sections with merchant-friendly schema settings, reusable snippets, metafield-driven content and theme code clean-up. If you are starting a new store rather than extending one, see our Shopify development service, and read our Shopify store development cost guide for wider budgeting.

Next step

If you have a merchandising idea your theme cannot handle, or a theme that needs rescue, send us a short brief through the contact page. We will tell you whether a Liquid section, an app or a rebuild fits, and give you a delivery estimate. You can also read about the full Shopify Liquid development service first.