Most store owners post a job for "a Shopify person" and then get confused when the applicants look nothing alike. One replies with a portfolio of clean, high-converting theme customizations. Another replies with GitHub links, API documentation and a note about Liquid performance. Both are legitimately good at Shopify. They are good at different halves of it, and hiring the wrong half for your problem is the single most common way store owners waste a Shopify budget.
A Shopify web designer builds how the store looks: layout, brand, product page design and theme editor work. A Shopify web developer builds how it works: Liquid code, custom sections, app and API integrations, checkout logic and speed. Most stores need a designer first and only need a developer once the theme can't do what the business requires.
What does a Shopify web designer actually do?
A Shopify web designer works primarily inside the theme editor and the visual layer of the store: choosing and configuring a theme, setting up the brand palette and typography, laying out the homepage, collection and product pages, sourcing or directing photography, and making sure the storefront reads as a coherent brand rather than a stock template with a logo dropped in. Good Shopify designers also think about conversion, not just aesthetics: where trust signals sit on a product page, how the cart drawer behaves, what the mobile experience does with thumb reach and tap targets.
The boundary of the role is the theme's settings and section options. A skilled designer can push a stock theme a long way using Shopify's native customizer and section-based blocks, especially on Online Store 2.0 themes, which expose far more layout control without touching code than earlier Shopify theme generations did. What a designer typically cannot do, or shouldn't be doing without a developer alongside them, is edit Liquid templates directly, build a custom app, or wire the store into an ERP.
What does a Shopify web developer actually do?
A Shopify web developer works below the theme editor: Liquid templating, custom Shopify sections and blocks, theme architecture, the Storefront and Admin APIs, checkout extensibility (Shopify's framework for customizing checkout on Plus and, increasingly, non-Plus stores), third-party integrations with ERPs, PIMs and subscription platforms, and performance work tied to Core Web Vitals. If a request starts with "can we make the theme do something it wasn't built to do," that is a developer request, not a design request.
Developers are also who you need for anything touching data: custom metafields for complex product attributes, inventory sync with a warehouse system, or a build that has to survive a high-traffic launch without the theme falling over. None of that is visual work, and a designer without development skills genuinely cannot deliver it, no matter how good their eye is.
| Task | Designer | Developer |
|---|---|---|
| Theme selection and setup | Yes | Not their focus |
| Homepage and collection page layout | Yes | Only if custom code is required |
| Product photography direction | Yes | No |
| Custom sections beyond theme options | No | Yes |
| App and API integrations | No | Yes |
| Checkout extensibility, custom checkout logic | No | Yes |
| Page speed and Core Web Vitals fixes | Rarely | Yes |
| ERP, PIM or subscription platform sync | No | Yes |
| Brand consistency across pages | Yes | Not their focus |
Which one does your store actually need?
Work backwards from the request, not the job title. Three quick checks settle most cases.
- If the fix is "this doesn't look right," it's a design problem. Layout, spacing, imagery, color and typography issues almost never need code.
- If the fix is "this doesn't work," it's a development problem. Broken integrations, checkout errors, slow load times and anything involving an API sit with a developer.
- If the fix is "we need a feature the theme has never had," it's development, even if the outcome is visual. A custom product configurator or a bespoke bundle builder looks like design but is built like software.
A brand-new store on a paid theme, selling a straightforward catalog, usually needs a designer first and a developer only for setup tasks like domain, apps and basic tracking. A store that needs subscription logic, a loyalty program tied to a CRM, or a checkout flow that differs from Shopify's defaults needs a developer from day one, and probably needs one before it needs a designer.
Before posting a job, write down whether the last three requests you made were "make it look better" or "make it do something new." That single question routes most stores to the right hire faster than any interview process, and it stops you paying developer rates for a font change or designer rates for a broken webhook.
What does each one cost in 2026?
US market rates vary by seniority and engagement type, and the two roles command similar bands at comparable experience levels, though development work tends to consume more billable hours per project because of the testing and integration overhead.
| Engagement | Typical US range | Notes |
|---|---|---|
| Freelance designer, mid-level | $40 to $75 / hour | Theme setup, page layout, product page design |
| Freelance developer, mid-level | $45 to $70 / hour | Rises to $100 to $165 for senior or Plus specialists |
| Agency team, blended rate | $120 to $200 / hour | Usually includes both design and development capacity |
| Simple design-only project | $500 to $2,500 | Theme setup, brand configuration, product pages |
| Custom development project | $5,000 to $30,000+ | Custom sections, integrations, checkout work |
These are the ranges we see quoted across the US Shopify market in 2026 for legitimate freelance and small agency work, not the high end of enterprise Plus builds, which can run well past $100,000 on complex integrations. Offshore development talent prices meaningfully lower, often in the $25 to $40 an hour band, and can be a reasonable option for well-scoped, well-documented work, though communication overhead and time zone gaps add real project risk on anything ambiguous.
Can one person do both jobs well?
Sometimes, and plenty of freelancers market themselves as full-stack Shopify experts. For a small store on a stock theme with modest customization needs, a generalist is a perfectly reasonable hire and avoids the coordination overhead of managing two people. The risk shows up as the store grows: a generalist strong on the development side often produces mediocre visual design, and a generalist strong on design often writes Liquid that works but is slow or brittle under real traffic. If your store already has real design ambition and real technical requirements, at the same time, two specialists working together, or an agency team that carries both disciplines, consistently outperforms a single generalist stretched across both.
How do you vet either one before hiring?
For a designer, ask to see live stores they built, not just a portfolio of static mockups, and check the storefront on mobile yourself. For a developer, ask what happens to the theme's speed score after their typical build, and ask them to walk through a recent Liquid or API problem they solved, not just list technologies. For either, a short paid trial task, scoped to a few hours, tells you more than a resume. Our own guide to hiring a Shopify developer goes deeper on vetting questions, timelines and the red flags worth walking away from. If you would rather skip the hiring process altogether, our Shopify development team covers both roles under one project scope.
On projects where a store needs both, we run design and development in parallel rather than sequentially: the developer builds custom sections as skeletons while the designer finalizes brand and layout decisions, then the two get wired together in the same sprint. Sequential handoffs, design fully done and then thrown over to a developer, are where most timeline slippage happens on Shopify builds. It is the same coordination problem we cover in general terms in our guide to website design and development services, and it applies just as much to Shopify as to any other platform.
Frequently asked questions
What is the difference between a Shopify web developer and a Shopify web designer?
A Shopify web designer works on the visual layer: layout, typography, imagery, brand consistency and how the storefront looks and feels inside the theme editor. A Shopify web developer works on Liquid code, custom sections, app and API integrations, checkout logic and performance. Designers decide how the store looks. Developers decide how it works.
Do I need a Shopify developer or a designer for a new store?
A new store on a paid theme usually needs a designer first, to configure layout, brand and product pages. You only need a developer up front if you require custom functionality a theme cannot do out of the box, such as subscription logic, a custom configurator, or a non-standard checkout flow.
How much does a Shopify developer cost in 2026?
US-based Shopify developers typically bill $45 to $70 an hour at the mid level and $100 to $165 an hour for senior or Shopify Plus specialists, with agencies often at $120 to $200 an hour. Simple project work runs from a few hundred dollars, while custom builds with app and API integration commonly land between $5,000 and $30,000 or more.
Can one person be both a Shopify designer and developer?
Yes, and many freelancers market themselves this way, but few are equally strong at both. A generalist is a reasonable fit for a small store on a stock theme. A store with real design ambition and real technical requirements usually gets a better result from two specialists or an agency team that includes both.
What does a Shopify developer actually touch that a designer cannot?
Liquid template code, theme architecture, custom sections and blocks, checkout extensibility, third-party API and ERP integrations, page speed and Core Web Vitals work, and app development. Most theme editors block direct code access, so anything past drag-and-drop customization needs a developer.
Is Shopify design cheaper than Shopify development?
Usually, yes, for comparable seniority. Design-only engagements on an existing theme often run lower than custom development because there is no code architecture, testing or integration work involved. Once a project needs both, most of the budget still goes to development hours rather than design hours.
The takeaway
Stop hiring by job title and start hiring by the problem in front of you. If the store looks wrong, hire a designer. If it doesn't do something it needs to do, hire a developer. If it's both, budget for both, and expect development hours to carry more of the total than design hours once real integrations enter the picture. Getting this sequencing right, before you post the job, is worth more than any single interview question.