Hiring a Shopify development agency: the scope, the four phases, and how to judge the work

A Shopify development agency builds and extends Shopify stores: theme work in Liquid, custom sections and metafields, app configuration and custom apps, data migration, integrations with your ERP or warehouse, and the front end performance work that keeps a heavily extended store fast. Hire one when the store needs more than a theme and a few apps, when you are migrating from another platform, or when your catalogue has structure that off the shelf themes do not handle. The single most useful thing you can do before approaching anybody is to write down which of those four jobs you are actually buying, because agencies specialise and the pitch rarely tells you where their depth is.

This page covers choosing an agency for a standard Shopify build. For the enterprise plan and its specific partner requirements, see the four capability stacks of an ecommerce agency.

What the work consists of

Workstream	What it involves	Who should own it
Theme and front end	Liquid templates, sections, custom blocks, responsive build, speed	Agency developer with Shopify specific experience
Data model	Products, variants, collections, metafields, metaobjects, taxonomy	Agency with your merchandising lead in the room
Apps and custom code	Choosing apps, removing duplicates, writing a custom app where no app fits	Agency, with a named cap on app count
Migration	Products, customers, orders, URLs and redirects from the old platform	Agency, with your data owner signing off each pass
Integrations	ERP, 3PL, accounting, subscriptions, loyalty, CRM	Agency plus the vendor's own implementation team
Analytics and tagging	Consent, events, server side tagging, feed accuracy	Agency, with your measurement owner

A store that fails after launch usually fails on two of these: the data model was never designed, so collections and filters cannot be built properly, and the migration left the URL map incomplete. Both are cheap to specify and expensive to retrofit.

The brief that gets comparable quotes

1. Current state. Platform, catalogue size, number of variants, markets, currencies, languages and order volume.
2. What must be true at launch. The three things that will be checked on day one, written as pass or fail statements.
3. The integrations list, with the vendor name and the version or API for each one.
4. The merchandising requirement. How customers should filter and browse, in your words. This drives the data model and it is the requirement agencies most often receive too late.
5. Who does content. Product copy, photography, category text: yours, theirs or split.
6. Internal capability. Whether anybody on your side can edit Liquid after launch.
7. Budget range and launch window.

The technical questions that separate a partner from an installer

• How will you structure the data model for our catalogue? Listen for metafields and metaobjects used deliberately, and a view on variants versus separate products.
• How many apps do you expect to install, and which ones do you plan to replace with code? Every app adds scripts to the storefront. A partner who has an opinion here is worth talking to.
• How do you handle theme version control and staging? Expect Git, the Shopify CLI, a development theme per branch, and a documented release process. An agency editing the live theme in the admin is a risk you are paying for.
• What is your approach to checkout customisation? Shopify moved checkout customisation to its extensibility model, so a plan built on editing checkout markup directly is out of date.
• How do you manage the URL map on migration? Expect a full old to new mapping, redirects created in bulk, and a crawl to prove nothing resolves to a 404.
• What is your performance budget, and how will you prove it at handover? Expect a number, a test method and a retest after apps are installed.
• Who writes the documentation, and what does it contain?
• Are you listed in the Shopify Partner directory, and at what level? The partner programme is public and verifying the listing takes a minute.

The four phases, and what each one should deliver

1. Discovery. A data model diagram, a sitemap, the integration list with owners, and a scope document with explicit exclusions. Pay for this separately if you can: a paid discovery with one agency is cheaper than a fixed price build with the wrong one.
2. Design and build. Templates built as reusable sections so your team can create pages later without a developer. Insist on this; it is the difference between a store you can run and a store you must keep paying to change.
3. Migration and QA. Two dry runs before the real one. The QA list covers checkout on real cards, tax and shipping by market, discount codes, inventory sync, every email template, and the redirect map.
4. Launch and thirty days after. Someone on call, a daily error check, and a fix window included in the fee rather than billed as change requests.

Fee models

• Fixed price per project. Works when discovery is complete. Without discovery it produces change requests, which is how a fixed price becomes the most expensive option.
• Time and materials with a cap. Fair for both sides when the scope has genuine unknowns, such as an ERP integration.
• Monthly retainer for continuous improvement. The right model after launch: a budget of developer days per month against a prioritised backlog you own.
• Revenue share. Rare and worth examining closely. Ask what happens to the share if you change agency.

The handover that keeps the store yours

Put all of this in the contract before work starts:

• The Shopify account is in your company's name, with your billing, and you hold the owner role.
• The theme repository is in your organisation, with the agency added as a collaborator.
• Any custom app is registered to your account, with source code delivered and licensed to you.
• Documentation covers the data model, the integrations, the release process and the known issues.
• A thirty day offboarding obligation, so a change of agency is a transition rather than a rebuild.

After the build, the work that pays

A new store is the start of the job. The ordering of what to do next is covered in marketing a Shopify store, and the platform specific search constraints that a developer should design around, including collection pages, variant URLs and app bloat, are in Shopify SEO. Bring both into the build brief rather than raising them after launch, because the fixes are template level and templates are cheap to change before a store is live.

hiring a Shopify development agency: the questions that keep coming up

Do I need an agency, or will a freelancer do?

A freelancer is a good fit for theme customisation and ongoing small changes. Choose an agency when the project includes a migration, multiple integrations or a hard launch date, because those need more than one person and a cover plan.

How long does a Shopify build take?

A themed store with light customisation moves quickly. A custom build with a migration and two integrations takes substantially longer, and the integration partners usually set the critical path. Ask each agency for a dated plan with the dependencies named.

Should the agency choose a premium theme or build from scratch?

Start from a well maintained theme and extend it with custom sections in most cases. Build from scratch when your merchandising or configurator requirements have no equivalent in any theme.

How many apps is too many?

Count the scripts each app adds to the storefront rather than the apps themselves. Set a performance budget at the start, measure after every install, and replace the heaviest apps with code when they cost you more than they return.

Who owns the SEO during a migration?

Name one person, on your side, who signs off the redirect map and the template level markup before launch. This is the single highest risk item in any replatform.

What should I ask the agency's references?

Ask what went wrong, how it was handled, how long the agency took to answer during launch week, and whether they would hire them again for a second project.

A line for the post launch backlog: ask the assistant first

Once the store is live, shoppers will ask an assistant for "a good brand for this" before they type your name anywhere. The reply is built from product pages, reviews and mentions the assistant can read. That is not the theme you commissioned, and a handover document does not mention it.

Put one recurring task in the agency's retainer: ask five shopper questions in ChatGPT, Gemini and Perplexity and log which stores appear. AI Knows Us does this at scale, so the log is a report and not a screenshot.