WooCommerce, hiring guide
How to Hire a WooCommerce Developer in the UK, and What It Should Cost
Most guides to hiring a developer are written by people who want you to hire them. This one is too, so read it with that in mind. What follows is still the honest version: the four routes available, what each one actually costs in Britain right now, the ten questions that separate a good hire from an expensive mistake, and the situations where the answer is that you should not hire anybody yet.
There is a particular kind of conversation that happens about four months into a badly hired website project. The store half works. The person who built it has become slower to reply. Nobody can say confidently who owns the hosting account. And the honest question underneath all of it is not what went wrong technically, it is why nobody asked a few specific questions at the start.
Hiring somebody to build or fix a WooCommerce store is not difficult, but it is unusually easy to do badly, because the buyer is almost always less technical than the seller and the differences between good and bad only become visible months later. This guide is written to close that gap. It covers what the job actually involves, the four routes you can take and what each genuinely costs in the UK, how to write a brief that gets you comparable prices, the questions worth asking before you commit, and the warning signs that should end a conversation early.
We build and maintain WooCommerce stores for a living, so we are not a neutral party. What we can offer instead is the view from inside the work, including the parts that make us less money to admit.
What a WooCommerce developer actually does
The phrase covers at least four different jobs, and a great deal of confusion comes from buyers and sellers using it to mean different things. Before you approach anybody, work out which of these you actually need, because the right person for one is often the wrong person for another.
Store building
Setting up WordPress and WooCommerce, designing the shop, configuring products, payments, shipping and tax, and making the checkout work end to end. This is largely configuration and design judgement rather than programming, and it is what most small businesses mean when they say they need a developer. The skill that matters here is knowing which of WooCommerce's several hundred settings actually matter to your business, and which plugins you genuinely need rather than the ones everybody installs by reflex.
Custom development
Writing actual code: a bespoke shipping calculator, an integration with your accounting system, a product configurator, a change to how the checkout behaves. This is a genuinely different skill set involving PHP, WooCommerce's hooks and filters, and enough discipline to write something that survives the next core update. Many people who build excellent stores do not do this, and many who do it well are not the right choice for a straightforward shop.
Maintenance
Keeping a live store safe and working: applying updates without breaking anything, backups that would actually restore, monitoring, and fixing things when they go wrong. It is the least glamorous of the four and by some distance the most commonly neglected. It is also the one where the gap between a cheap provider and a good one is invisible until the day it matters.
Optimisation
Making an existing store faster, more findable and better at converting. Performance work, technical SEO, checkout improvements, and the kind of analysis that tells you where visitors are leaving. This is closer to diagnosis than construction, and the useful practitioners are the ones who can tell you which three things to fix rather than handing you a list of forty.
Write down which of those four you need, in one sentence. If the sentence contains two of them, you probably need two different conversations, or one supplier who genuinely does both and can show you examples of each. A brief that says "I need a WooCommerce developer" produces four wildly different quotes and no way to compare them.
The four routes, and what each one is actually good at
There are four realistic ways to get WooCommerce work done in the UK. None of them is correct in general. Each one is correct for a particular set of circumstances, and the mistake is choosing by price rather than by fit.
Route one: an independent freelancer
A single person, usually working with several clients at once, often specialising in one part of the job. The good ones are extremely good value, because you are paying for skill without paying for an office, an account manager or a sales team.
The risk is not competence, it is continuity. One person gets ill, takes on a bigger client, changes career, or simply stops replying. If your store's entire technical history lives in one freelancer's head, you are exposed in a way that has nothing to do with how good they are. Mitigate it by insisting on documentation and by making absolutely certain the accounts are in your name, not theirs.
Best for: a defined project with a clear end, when you have the confidence to specify what you want and someone internally who can take over afterwards.
Route two: an online marketplace
The global platforms where you post a job and receive dozens of proposals within hours. We will not name them, but you know the ones. They are genuinely useful for small, well defined, low risk tasks: change this template, fix this bug, load these fifty products.
They are a poor fit for anything requiring judgement, because the model optimises for the wrong thing. You are shown proposals in minutes, sorted largely by price, from people who have not seen your business and cannot have thought about it. The lowest bidder on a store build is usually somebody who has decided what to build before understanding what you sell. Communication is asynchronous and often across several time zones, which is workable for a discrete task and painful for a project with a hundred small decisions in it.
Best for: contained tasks with an unambiguous definition of done. Poor for anything where the right answer depends on understanding your business.
Route three: an agency
A company rather than an individual, with more than one person able to work on your store. You pay more, and what you are buying is continuity, accountability and usually a defined process.
The thing worth understanding about agencies is that they vary enormously in a way that is invisible from the outside. A two person studio and a forty person agency both call themselves agencies, and the experience is completely different. In a larger one your work is likely done by someone junior under supervision, coordinated by an account manager who is not technical. That is not automatically bad, and for a large complex build it is exactly what you want. But if you specifically want the person who understands your business to be the person doing the work, you need a small one, and you should ask directly.
Best for: projects where continuity matters, where you want somebody accountable when things break, or where the work spans several disciplines.
Route four: hiring in house
Employing somebody, part time or full time. Almost always the wrong answer for a business running one store, and almost always the right one past a certain scale.
The arithmetic is straightforward: a developer's total cost is considerably more than their salary once employer contributions, equipment, holiday and management time are counted, and unless there is genuinely a full week of work every week, most of that spend buys idle capacity. The tipping point is not revenue, it is the size of the backlog. When you consistently have more than a couple of days of development work waiting every week, and it is not being cleared, employing someone starts to make sense.
Best for: businesses where the store is the business, with a permanent queue of work and enough revenue that a bad month does not make the salary painful.
Doing nothing for another quarter is a legitimate option and it is sometimes the right one. If you are not sure what you need, spending a few hundred pounds on a diagnosis before spending several thousand on a build is nearly always better value than guessing. The most expensive projects we see are the ones that started before anybody knew what problem they were solving.
The money question
What WooCommerce work actually costs in the UK
Published figures are rare in this industry, which is precisely why buyers find it so hard to tell a fair price from a bad one. The ranges below are what we observe in the British market in 2026. They are market observations rather than our prices, and they will vary with complexity, location and how much of the thinking you have done yourself.
| Work | Typical UK range |
|---|---|
| Freelance day rate | Roughly £250 to £600 a day, with experienced specialists above that |
| Small agency day rate | Roughly £500 to £900 a day |
| Simple store build | Around £1,500 to £5,000 for a straightforward shop with a modest catalogue |
| Complex or bespoke build | £8,000 upwards once custom development or integrations are involved |
| Basic care plan | Roughly £30 to £150 a month, largely automated |
| Managed care with a person attached | Roughly £150 to £600 a month |
| Enterprise store management | £1,200 a month and upwards |
Two observations about that table matter more than the numbers in it.
The first is that the cheapest care plans and the most expensive ones are not the same product with different amounts of it. Below about a hundred pounds a month, essentially nothing involves a human looking at your store: updates are applied automatically, a backup is taken that nobody has ever restored, and you receive a monthly report generated by software. That can be perfectly adequate for a simple site. It is not the same thing as somebody testing your checkout after an update, and it is worth knowing which you are buying.
The second is that the enormous range on builds is not mostly about quality. It is about scope. A five page shop with twenty products and one payment method is a fundamentally different job from a four hundred product store with three integrations, and both get described as "a WooCommerce site" in the first email. Most of the variance you see in quotes is people making different assumptions about which one you meant.
How we price it, and why we publish
Since we sell this work, the fair thing is to show our own numbers rather than only describe the market. Every price on our site is published on the page, which is unusual in this industry and deliberate. A complete WooCommerce store build is £3,450, including the first 20 products, with each additional block of 10 products at £150. A written health check of an existing store is £445. Ongoing care starts at £245 a month.
We publish for a straightforward reason. When prices are hidden, the first conversation is a qualification exercise in which the seller is working out what you can afford, and that is a poor start to a working relationship. When they are on the page, the first conversation is about whether the thing is right for you. It also means we cannot quietly charge two clients differently for the same work, which is a discipline worth having.
You do not have to buy from us to use that as a test. Ask anybody quoting you whether their price for your project is the same one they would give another business with the same requirements. The answer, and how comfortably it arrives, tells you something.
Writing a brief that gets you comparable prices
The single biggest cause of wildly different quotes is not the suppliers, it is the brief. Send four people a vague description and you will get four prices for four different projects, and no way to compare them. A brief does not need to be technical. It needs to answer the questions that change the amount of work.
- What you sell, and how many of them
The number of products is the single biggest driver of effort in a store build. Say the real number, including variations, and say whether it will grow quickly.
- Whether the content exists
Do you have product descriptions and photographs ready, or does somebody need to create them? This is the most commonly omitted fact and it changes a project's timeline more than anything else.
- How it ships
One flat rate to the UK is a different build from weight based international shipping with three carriers. Say which you need on day one.
- What must integrate
Accounting software, an EPOS system, a warehouse, a subscription tool. Every integration is real work and every one discovered late is a variation to the price.
- Whether anything exists already
A new build, a rebuild, adding a shop to a site you are keeping, or a migration from another platform. These are four different jobs at four different prices.
- Your actual deadline, and why
"As soon as possible" is not a deadline. A trade show, a seasonal peak or a product launch is, and a real date changes how the work is sequenced.
- Your budget range
Withholding it feels like negotiating strength and usually is not. Without it, quotes get built on guesses, and you spend three weeks comparing proposals for projects you cannot afford.
They come back with questions before they come back with a price, and at least one of those questions should be about something you did not think mattered. A quote that arrives within an hour of a seven point brief, with no questions attached, was not calculated. It was estimated from a template, and the variations will arrive later.
Ten questions to ask before you hire anyone
These are ordered roughly by how much trouble they save. The first four are the ones we would insist on if we were buying rather than selling.
- Who will own the hosting, the domain and the accounts?
The answer must be you, on all three, from the start. An arrangement where the supplier owns your domain or hosting is not a service, it is a hostage situation, and it becomes visible only when you try to leave. Ask specifically whose name the accounts will be created in.
- Who is actually doing the work?
In a larger agency the person selling to you is rarely the person building. That can be fine, but you should know. Ask who will write the code, who you contact when something breaks, and whether that changes after launch.
- What happens in the first month if something is wrong?
Every build has snags. What matters is whether fixing them is included and for how long. Get a specific period rather than a reassuring noise, and get it in writing before you pay a deposit.
- Is ongoing maintenance included, and if not, what does it cost?
Many quotes quietly exclude it, which is legitimate, and many buyers assume it is included, which is where the argument comes from. Ask for the monthly figure at the same time as the build figure so you are comparing total cost of ownership rather than headline price.
- Can I see a store you built, and its actual performance scores?
Anybody can show you a screenshot. Ask for the live URL and then run it through PageSpeed Insights yourself while you are on the call. Reluctance here is informative. Speed is not everything, but an agency that has never measured it is telling you something about how it works.
- How do you handle updates on a live store?
The correct answer involves the word staging. Applying WordPress and plugin updates directly to a live shop is the single most common cause of unplanned downtime in WooCommerce, and a supplier who does not test them somewhere else first will eventually break your checkout on a Friday.
- What is the plugin philosophy?
Ask how many plugins a store like yours typically ends up with, and what happens when one is abandoned by its author. You are listening for someone who treats every plugin as a liability to be justified rather than a feature to be added.
- What is not included?
Ask it directly and let the silence sit. A supplier who can list their own exclusions fluently has thought about scope. One who says "everything you need" has not, and the gap will be discovered by both of you at the worst moment.
- What happens if I want to leave?
Notice period, what gets handed over, and whether anything technically prevents a move. The answer should be boring. If it is not boring, that is the finding.
- What would you tell me not to buy?
The most revealing question on the list. Everybody selling has something in their range that is wrong for you, and a supplier who can say so has judgement worth paying for. One who thinks everything they sell suits everybody is either inexperienced or not listening.
Seven warning signs worth walking away from
None of these is proof of bad faith on its own. Two or more together is a pattern, and patterns are what you are looking for at this stage.
A price arriving before any questions
A fixed price given without understanding the catalogue size, the shipping rules or whether content exists is not a price, it is an opening position. It will be revised, and the revision will arrive when you are committed.
Vagueness about who owns what
If the answer to "whose name is the hosting in" involves any hesitation, stop and resolve it before anything else. This is the single most common way small businesses end up trapped, and it is entirely avoidable at the start and expensive to fix later.
Guaranteed rankings
Nobody can promise a position in Google's results, and Google's own documentation says so plainly. A supplier guaranteeing first place is either misunderstanding their own service or relying on you not checking. Related, and equally worth avoiding: anybody offering to generate reviews for you.
Maintenance folded silently into the build
If a proposal says "and we'll look after it" without a monthly figure attached, ask what happens in month four. Either it is free forever, which nobody can afford, or it is not included, which is fine but should be priced.
An unwillingness to show live work
Portfolio screenshots without URLs usually mean the work is old, was largely somebody else's, or has since been rebuilt by another supplier. Ask for two live stores you can visit and use.
Everything is bespoke
Custom code is sometimes necessary and often not. A supplier who wants to build from scratch what a well maintained plugin already does is either enjoying themselves at your expense or increasing the hours. Ask why the standard approach will not work, and expect a specific answer.
Communication that is already slow
How somebody communicates while trying to win your business is the best version of how they will communicate once they have it. A three day gap now is a two week gap in month six.
Somebody telling you that you do not need the thing you asked for is the strongest positive indicator in this whole guide. It costs them money in the moment and it is the clearest evidence that their advice can be trusted when the stakes are higher.
The ownership checklist
This is the part worth being pedantic about, because everything else can be fixed and this genuinely cannot without pain. Before work starts, confirm in writing that every one of these is in your name and that you hold the login.
| Asset | Why it matters |
|---|---|
| Domain name | The one thing that is genuinely irreplaceable. If a supplier registered it on your behalf under their own account, moving away means asking permission from somebody you are leaving. |
| Hosting account | Your site lives here. An agency reselling hosting under its own account controls your access to your own store, and stops your site the day the relationship ends. |
| Administrator login | You should hold a genuine administrator account throughout, not a limited one created for you. |
| Payment gateway | Always in your business name, connected to your bank account. No exceptions, ever. |
| Google Business Profile | Frequently created under an agency account and then effectively lost. The reviews on it are yours and are painful to recover. |
| Search Console and analytics | The historical data cannot be recreated. Losing access means losing years of it. |
| Plugin licences | Premium plugins bought on an agency licence often stop updating when you leave, which turns into a security problem quietly. |
| Backups | Know where they are, how far back they go, and whether a restore has ever been tested. |
None of this requires distrust. Good suppliers set it up this way as a matter of course, and ours are handed over in full at launch. The point is that you should not have to ask twice.
What happens after the build, which nobody budgets for
The most predictable failure in small e-commerce is not a bad build. It is a good build with nothing behind it. Three costs arrive after launch and almost never appear in the original plan.
Maintenance
WordPress, WooCommerce, the theme and every plugin release updates continuously, and each one is a small chance of something breaking. Unpatched stores are also the ones that get compromised. This is an ongoing cost whether you pay somebody or spend your own evenings on it.
Content
A new store has no reviews, no social proof and nothing to post. Product photography and video are not optional extras once you are competing for attention. We film this ourselves, which is why our e-commerce UGC portfolio exists alongside the build work, but the point stands whoever makes it: budget for content or expect a quiet launch.
Being found
Search Console only collects data from the day it is verified. A Google Business Profile compounds with age. Both take very little time to set up and neither can be backdated, which is why leaving them until month six is a genuine loss rather than a delay. If you are also planning to post consistently, social media management UK is a separate discipline again, and worth costing before launch rather than after.
Whatever the build costs, assume something in the region of a fifth of that again across the first year on maintenance, content and search foundations combined. Businesses that plan for it launch calmly. Businesses that do not tend to spend the same money anyway, more expensively, in a hurry, after something has gone wrong.
Choosing between the routes
A decision table, if you want the short version
Match your situation to the row rather than to the price. The most expensive mistakes in this market come from buying the right service for somebody else's circumstances.
| Your situation | What usually fits |
|---|---|
| One small fix on a working store | A freelancer, or a marketplace if the task is genuinely unambiguous |
| New store, modest catalogue, content ready | A fixed price build from a small agency or an experienced freelancer |
| Existing WordPress site that needs a shop | A retrofit rather than a rebuild, from somebody who checks theme compatibility first |
| Something is wrong and nobody knows what | A paid diagnosis before any build work is commissioned |
| Moving from another platform | Scoped individually. Anyone quoting a flat price without seeing the data is guessing |
| Large catalogue, integrations, bespoke logic | An agency with named developers and a written process |
| The store is the whole business and the backlog never clears | Hiring in house, with an agency retained for the parts you cannot cover |
If your situation is not in that table, the honest answer is that you probably need somebody to look at it before quoting, and you should be suspicious of anybody who does not want to.
Frequently asked questions
How much should a WooCommerce store cost to build in the UK?
For a straightforward shop with a modest catalogue, most credible UK suppliers land somewhere between about £1,500 and £5,000, and the variance inside that range is mostly scope rather than quality. Below roughly a thousand pounds you are usually buying a template installation with your logo on it, which can be entirely adequate if that is what you want and is worth knowing you are buying. Above about eight thousand you should expect custom development, integrations or a very large catalogue to be in the specification. Our own build is £3,450 with the first 20 products included.
Should I hire a freelancer or an agency?
A freelancer is usually better value for a defined project with a clear end, provided you are comfortable specifying what you want and there is somebody at your end who can take it over afterwards. An agency is worth the premium when continuity matters, when you need somebody accountable at three in the afternoon on a bad day, or when the work spans design, development and search. The question that actually decides it is what happens in month eight, not what happens in week one.
How do I know if a developer is any good before I hire them?
Ask for two live store URLs, visit them, buy something small if you can, and run them through a public performance test while you are still talking. Then ask what they would tell you not to buy. Technical assessment is difficult for a non-technical buyer, but judgement is legible to anybody: somebody who talks you out of the expensive option when it is wrong for you is demonstrating exactly the thing you are trying to assess.
Do I need a developer at all, or can I build it myself?
You can genuinely build a small WooCommerce store yourself, and for a handful of products with simple shipping, plenty of people should. What you are buying with a developer is not the ability to click the buttons, it is knowing which of several hundred settings matter, which plugins are liabilities, and how to make a checkout that does not lose people. If your catalogue is small, your shipping is one flat rate and your time is cheaper than the fee, doing it yourself is a reasonable decision.
What is the difference between WooCommerce and Shopify for hiring?
With WooCommerce you own everything: the code, the database, the customer list, the hosting. There is no platform fee on every sale and no version of events where the platform changes its rules and your business changes with it. The trade is that ownership comes with responsibility, so somebody has to apply updates and take backups. Hosted platforms move that responsibility to the provider and charge for it continuously. Neither is correct in general. If you want control and lower running costs and you are prepared to arrange maintenance, WooCommerce wins. If you want somebody else to own the problem, it does not.
How long does a WooCommerce build take?
For a store of the size most small businesses need, the build itself is a few weeks. In practice the timeline is set almost entirely by how quickly product content arrives, which is why the projects that overrun are nearly always the ones where nobody agreed who was writing the descriptions. If you have your content ready before you commission, you will be surprised how quickly it moves.
What questions should I ask a WooCommerce developer before hiring?
The four that matter most are who owns the hosting and domain, who is actually doing the work, what happens in the first month if something is wrong, and whether ongoing maintenance is included and at what price. The full list of ten is above, but if you only ask four, ask those. They are the ones whose absence causes the expensive conversations.
Is it worth paying for a store audit before hiring someone to fix things?
If you do not already know precisely what is wrong, almost always. A few hundred pounds spent establishing what the actual problems are, in what order, is nearly always better value than several thousand spent fixing whichever one was most visible. It also gives you a document you can send to several suppliers, which is the only reliable way to get comparable quotes. Ours is a written store audit at £445, and it is yours to act on however you like, including by hiring somebody else.
Monthly plans
Social media management, done for you
Small Business Social Pack
£149 per month
12 static posts, 1 platform, content creation done for you
View Small Business Social Pack- Most chosen
Rolling monthly, 2 months notice, no setup fees. All plans on the social media management page.
Our channels
Watch the work
Velena and Dragos
Travel, food and influencer content from the two of us, and the channel where the long form work lives.
Open the channelVelena Lifestyle
The agency channel. UGC examples, client work and finished campaign videos.
Open the channel
Dragos Nistor
Co-Founder and Business Strategist, Velena Lifestyle
Dragos handles strategy, briefs and delivery at Velena Lifestyle, the WooCommerce and content agency he co-founded with Velena Nikolova in High Wycombe. He was named a LinkedIn Top Entrepreneurship Voice in 2024. The agency builds and maintains WooCommerce stores and publishes every price on the page, including the ones most agencies keep behind a form.
Hiring for a WooCommerce store?
Every price we charge is on the page, including the ones you would normally have to ask for. If you are not sure which service you need, tell us what you are selling and we will say plainly, including when the answer is the cheaper option or nobody at all.