Hiring an e-commerce developer looks simple from the outside. You need someone who can build or fix a store, you find a portfolio with nice-looking sites, you agree a price. Six months later a surprising number of merchants are stuck with a theme nobody else can edit, a checkout that breaks every time an app updates, and a page speed score that quietly costs them conversions every day.
The problem is rarely skill in the abstract. Most developers can write code. The problem is that commerce work has a specific shape: it touches revenue directly, it lives on platforms with strict rules, and it has to keep working while marketing, merchandising and third-party apps change things around it. This guide covers how to hire for that shape: what an e-commerce developer actually does, which skills separate a store builder from a generic web developer, how to choose between a freelancer, an agency and an in-house hire, what the work should cost, and how to tell afterwards whether it paid for itself.
What an e-commerce developer actually does
The title covers a wide range of work, and being clear about which part you need is the first filter.
Storefront and theme development. Building or customising the customer-facing store: templates, product pages, collection filtering, cart and mini-cart behaviour, responsive layouts. On Shopify this means Liquid and Online Store 2.0 sections; on WooCommerce it means PHP templates and hooks; on headless builds it usually means React or Vue on a framework like Next.js or Hydrogen.
Platform configuration and apps. Setting up payments, shipping rules, taxes, markets and currencies, and choosing (or building) the apps that fill gaps. A good developer will tell you when an app is the wrong answer because it loads 300KB of script on every page.
Integrations. Connecting the store to the ERP, inventory system, 3PL, CRM, email platform, reviews and analytics. This is where a lot of real complexity lives, and where cheap work tends to fail silently, such as orders that never reach the warehouse or customers who never reach Klaviyo.
Migrations. Moving catalogues, customers, order history and URLs from one platform to another without losing rankings. If you are planning one, our guides to migrating from Magento to Shopify and moving from BigCommerce to Shopify walk through the redirect and data-mapping work in detail.
Performance, maintenance and CRO support. Keeping Core Web Vitals healthy, removing dead app code, fixing bugs after platform updates, and building the variants your conversion team wants to test.
Very few people are excellent at all five. When you write the brief, lead with the one that matters most to your business this year.
Skills that separate a good e-commerce developer from a web developer
A strong general web developer can pick up commerce work, but the gap shows in a few predictable places. These are the things to probe for.
Platform depth, not just platform familiarity
Ask which platform they have shipped the most stores on and what its limits are. Someone with genuine Shopify depth can explain checkout extensibility, the difference between metafields and metaobjects, Shopify Functions for discounts, and why certain customisations need Shopify Plus. A Magento or Adobe Commerce developer should be comfortable with modules, indexers and caching layers. Vague answers like "I can work with any platform" are a warning sign for anything beyond a basic theme install.
Checkout and revenue awareness
The checkout is the most valuable few hundred lines of your site. A good e-commerce developer treats it cautiously: they test payment methods, discount stacking, tax edge cases and subscription flows before shipping, and they know how to roll back. Ask them to describe a checkout bug they caused or fixed. Candidates who have never broken anything have usually not worked on anything important.
Performance discipline
Every theme section and app adds weight. Ask how they approach page speed on a store with 25 installed apps. You want to hear about auditing third-party scripts, lazy-loading below-the-fold media, image formats and dimensions, and measuring field data rather than only lab scores. Speed work also pays off in organic search; our Shopify SEO optimization guide covers where technical fixes intersect with rankings.
SEO-safe habits
Developers make SEO decisions constantly, often without knowing it: URL handles, canonical tags, faceted navigation, pagination, structured data, heading hierarchy, redirects. A careless theme rebuild can deindex collection pages or duplicate thousands of filter URLs. Ask how they handle filtered collection URLs and what they check before launching a redesign.
Analytics and tracking literacy
If your GA4 purchase events, Meta pixel or Google Ads conversion tags break during a rebuild, your ad platforms start optimising on bad data. The developer does not need to be an analyst, but they should know the difference between client-side and server-side tracking, how consent mode affects measurement, and how to verify a purchase event fires once, with the right value. The conversion tracking guide is a useful checklist to hand them.
Communication and documentation
Stores outlive developers. Ask to see a handover document or README from a past project. If a developer cannot explain what they built in plain language, you are buying future dependency.
Freelancer, agency or in-house?
There is no universally right answer, but the trade-offs are consistent.
Freelance e-commerce developer. Best for well-scoped projects: a theme customisation, a set of integrations, a performance sprint, ongoing small tasks. You get direct access to the person doing the work and usually lower rates. The risks are capacity (one person, one set of holidays), breadth (strong on code, maybe weak on design or strategy), and continuity if they take a full-time job.
E-commerce development agency. Best for full builds, replatforms and stores with complex integrations. You get a team with design, development, QA and project management, and some protection against any one person leaving. You also pay for that overhead, and junior staff may do more of the work than the pitch implied. Ask who specifically will be writing your code. If you are weighing agencies on a legacy platform, our breakdown of what to look for in a Magento development agency applies to most platforms.
In-house developer. Makes sense once you have a steady stream of work, typically a store doing high seven figures or more with frequent launches, testing and integrations. You get context and speed on small changes. You also take on salary, benefits, management, and the risk that one person becomes the only one who understands the stack. Many brands pair one in-house developer with an agency for large projects.
A useful rule: if you cannot write down at least three months of specific development tasks, you do not yet need a full-time hire.
What an e-commerce developer costs
Rates vary with location, platform and seniority, but US and UK ranges are reasonably stable.
- Freelancers: roughly $50–$150 per hour. Senior Shopify Plus or Adobe Commerce specialists can charge more, and offshore rates can be well under $50.
- Agencies: roughly $100–$250 per hour, often sold as fixed-price projects or monthly retainers.
- In-house: US salaries for mid-to-senior e-commerce developers commonly land in the $90,000–$150,000 range before benefits and overhead.
Typical project sizes:
- Theme customisation on an existing store: a few thousand dollars.
- Custom theme build on Shopify or WooCommerce: roughly $10,000–$40,000.
- Replatform with data migration and integrations: $30,000 to well over $150,000 depending on catalogue size, B2B requirements and ERP complexity.
- Headless build: usually six figures, plus higher ongoing maintenance.
Cheaper quotes are not automatically worse, but a quote that is half the others usually means something has been left out: QA, redirects, tracking, or post-launch support. Ask each bidder to list exclusions.
How to judge whether the work will pay back
Development spend is easiest to justify when you tie it to a number before the project starts. Three simple framings cover most cases.
Conversion rate lift. If a rebuild improves mobile checkout completion, estimate the impact on revenue. Plug your current sessions and orders into the conversion rate calculator, then model what a 0.2 or 0.5 point improvement would be worth over a year. For a store with 100,000 monthly sessions and a $90 average order value, moving from 2.0% to 2.3% is around $324,000 in additional annual revenue.
Margin, not revenue. Revenue gains only matter after cost of goods, fees and fulfilment. Run the lift through the profit margin calculator to see what actually reaches the bottom line, then compare it with the project cost.
Break-even timeline. For large builds, use the break-even calculator to work out how many months of incremental profit it takes to recover the investment. A $40,000 rebuild that adds $6,000 of monthly gross profit breaks even in under seven months. One that adds $1,000 takes more than three years, which is longer than many themes last.
Paid media also benefits from better stores. When landing pages convert better, the same ad spend returns more revenue, which shows up immediately in the ROAS calculator. That makes developer work one of the few costs that improves the efficiency of every channel at once.
Interview questions worth asking
Skip the generic "tell me about yourself" and use questions that expose how the candidate actually works.
- "Walk me through the last store you launched. What went wrong in the first week?" You are looking for honesty and a real debugging process.
- "We have 30 apps installed and mobile LCP is 4.5 seconds. Where do you start?" Good answers begin with measurement and script auditing, not a rebuild.
- "How do you handle URL changes during a redesign?" Listen for redirect mapping, crawling before and after, and checking Search Console.
- "How would you verify our purchase conversion is firing correctly after launch?" They should mention test orders, tag assistant or debug views, and matching platform order counts.
- "What would you refuse to build, and why?" Experienced developers push back on requests that hurt speed, maintainability or SEO.
- "Who owns the code and the accounts?" The answer should be you: your platform account, your GitHub repository, your app subscriptions.
A paid trial task, one to three days on a real but non-critical ticket, tells you more than any interview.
Red flags
- The developer wants the store, domain or app accounts registered in their name.
- No version control, or edits made directly on the live theme.
- No staging or preview environment for testing changes.
- Every problem is solved by installing another app.
- A portfolio of attractive homepages but nothing about results: speed, conversion rate, revenue, organic traffic.
- Fixed-price quotes with no written scope or list of exclusions.
- No mention of accessibility, which carries real legal exposure for US retailers.
Writing a brief that gets good proposals
Good developers are busy and prioritise briefs that are clear. Include:
- Your platform, plan and current theme, plus a list of installed apps.
- Your monthly sessions, conversion rate and average order value, so they can size the impact.
- The specific outcome you want, such as "cut mobile LCP below 2.5 seconds" or "launch B2B wholesale pricing for 400 accounts".
- Integrations that must keep working.
- Deadline drivers like a peak season or product launch.
- Budget range. Hiding it wastes everyone's time.
If user research is part of the project, run it before development starts rather than after launch. Our guide to usability testing services covers how to get that done quickly, and the findings make a far better brief than a list of competitor sites you like. For a wider view of where development fits into growth, see our overview of e-commerce conversion rate optimization.
Managing the engagement once it starts
Agree on a working rhythm from day one: a shared task board, a weekly check-in, and a clear definition of done that includes testing on real devices. Ask for changes to be reviewed on a preview theme or staging site before they go live, and keep a changelog so marketing knows what shipped and when. After launch, schedule a 30-day review comparing conversion rate, speed and organic traffic against the baseline. That review is where you find out whether you hired well, and it gives you the evidence for the next budget request.
FAQ
What does an e-commerce developer do?
An e-commerce developer builds and maintains online stores. That includes theme and storefront development, platform configuration, app and system integrations, data migrations between platforms, performance optimisation, and ongoing fixes as the platform and apps change.
How much does it cost to hire an e-commerce developer?
In the US and UK, freelancers typically charge $50–$150 per hour and agencies $100–$250 per hour. A custom Shopify or WooCommerce theme usually costs $10,000–$40,000, and a full replatform with integrations can range from $30,000 to well over $150,000.
Should I hire a Shopify specialist or a general web developer?
For anything beyond simple content changes, hire a specialist in your platform. Platform-specific knowledge of checkout rules, app architecture, metafields and performance constraints prevents expensive mistakes that a generalist may not see coming.
When does an in-house e-commerce developer make sense?
Usually once you have a steady, predictable backlog of development work, at least several months of defined tasks, and a store large enough that faster turnaround on small changes has measurable revenue value. Before that point, a freelancer or agency retainer is typically more cost-effective.