WooCommerce developer UK: fix the store you have before you pay to replace it

What does a WooCommerce developer do for a UK online shop?

A WooCommerce developer maintains, repairs and extends an online shop built on the WooCommerce plugin for WordPress, working in PHP, the database, the theme and the hosting rather than only in the admin screens. For a UK shop that also means getting VAT, couriers, card payments and consent rules right.

The work usually falls into four buckets. Fixing: errors at checkout, emails that never arrive, stock that goes negative, a plugin update that broke the product page. Speeding up: slow category pages, a sluggish admin, timeouts during a sale. Extending: a product builder, trade prices, a subscription option, a connection to your accounting or stock software. Deciding: whether the store is worth keeping at all.

A designer who installs themes can handle the look. A WooCommerce developer is the person you need when the answer lives in code: a hook in a plugin, a slow database query, a tax rule that rounds wrongly, a payment callback that never reaches your site.

Because we work remotely from India, we do this through admin access, SFTP or SSH, a staging copy and a shared task list. You never need to post hardware or meet anyone. If you only need design work on a new site, our WordPress website design service is the better starting point.

Should you fix WooCommerce or move to Shopify?

Fix WooCommerce when the problems are specific and the store holds value you would lose in a move; move to Shopify when the real problem is that nobody wants to own hosting and updates. Most stores we look at fall into the first group.

Value you lose in a move is easy to underestimate. Years of order history, customer accounts, reviews, product URLs that rank on Google, blog content, custom fields that hold sizes or materials, and the exact way your checkout behaves all need mapping, redirecting or rebuilding. A migration is a project, not a switch.

On the other hand, WooCommerce has a cost that never appears on an invoice: attention. Someone has to update WordPress core, plugins and the theme, test that checkout still works, watch the hosting and respond when something breaks. If that someone is you at 11pm, a hosted platform may buy back your evenings.

• Fix if: the store makes money, problems are recent or specific, and you rely on custom product logic or content.
• Fix if: your organic traffic and product URLs are a real source of orders.
• Consider moving if: you have spent more on emergency repairs this year than a platform plan would cost, and the site is still unstable.
• Consider moving if: the catalogue is simple, you use few custom features, and you want zero server responsibility.

Already decided to switch? Read the Shopify website cost guide for UK sellers before you commit, so the monthly bill is not a surprise.

What a WooCommerce health check covers before any quote

A health check is a short, fixed-scope review of your store that tells you what is wrong, why, and what each fix would cost, before you commit to development. We ask for it first because guessing from a symptom leads to wasted work.

We start on a staging copy, never your live shop. Then we look at the PHP version and hosting resources, the list of active plugins and when each was last updated, the theme and any template overrides that are out of date, error logs, scheduled tasks, whether HPOS is on, how many database queries a category page makes, and how long checkout takes to respond.

We also check the UK-specific parts: tax settings and classes, how prices display in the basket and on invoices, which gateway extension handles cards and wallets, how orders move to your courier, and whether analytics tags fire before or after consent.

The output is a ranked list in plain English. Each item says what we found, what it affects (sales, speed, compliance or admin time) and a quoted fix. You pick what to do. Some owners take the list and hand it to their existing developer, which is fine.

UK VAT tax tables and VAT-inclusive prices in WooCommerce

For a UK store, the usual set-up is prices entered inclusive of VAT, displayed including VAT everywhere, with separate tax classes for standard, reduced and zero-rated products. Getting any one of those settings wrong can show customers the wrong total or put the wrong VAT on invoices.

GOV.UK lists the three UK VAT rates: 20% standard, 5% reduced and 0% zero rate. WooCommerce ships with matching default classes (Standard, Reduced rate and Zero rate) and lets you choose whether prices are entered with or without tax, how prices display in the shop and at checkout, and whether tax is calculated from the shipping address, billing address or shop base. Rates can be imported from a CSV file, which keeps tax tables tidy when you sell abroad as well.

The mistakes we see most often are small but costly: prices entered excluding VAT on some products and including it on others after a bulk import, a children’s clothing or food range left on the standard class, rounding set per line when your accountant expects per order, and invoices generated by a PDF plugin that ignores the tax class entirely.

We set the classes and display, test a basket with mixed-rate items, and check the order email and invoice. Which products belong in which class is a decision for you and your accountant; we implement it exactly and never give tax advice.

Which payment gateways work with WooCommerce in the UK?

WooCommerce works with the main UK card processors and digital wallets through official or well-maintained gateway extensions, so the right choice is usually the processor you already hold a merchant account with, or the one whose fees suit your order size. We configure whichever you pick; we do not resell processing or take a share of it.

What matters technically is less the brand than how the extension behaves. Does it use a hosted payment page or an on-site card field? Does it support Apple Pay and Google Pay? Does it handle Strong Customer Authentication challenges on mobile without losing the order? Does it write refunds back to WooCommerce so stock and accounts stay right? Does it support subscriptions if you sell them?

The common failures are also technical: webhooks pointing at an old domain, so paid orders stay “pending payment”; a caching rule that caches the checkout page; two gateway plugins fighting over the same wallet button; and test mode left on after a migration.

We fix these by checking the webhook log on the processor side, excluding checkout and basket from caching, removing duplicate plugins, and then running a real low-value payment and refund on the live store. For a deeper look at card set-up across platforms, see payment gateway integration for UK sites.

Exporting WooCommerce orders to Royal Mail Click & Drop

Royal Mail’s Click & Drop can connect directly to a WooCommerce store and pull in eligible orders so you can print labels without retyping addresses. When the integration misbehaves, the cause is nearly always order status, shipping method names or missing weights on the WooCommerce side.

Royal Mail’s Click & Drop help centre explains that the WooCommerce integration imports orders in Processing status and does not pick up older orders beyond a short window, then updates the order in your store after despatch. That means any plugin that changes order statuses, such as a custom “awaiting stock” status or a pre-order extension, can quietly stop orders reaching your label queue.

Our checklist for a reliable export is short. Every product has a weight in kilograms. Shipping methods have clear names that map to Royal Mail services. Custom statuses are documented and either excluded on purpose or mapped. The REST API keys used by the integration belong to an admin account that will not be deleted when a staff member leaves.

If you use a different courier or a shipping aggregator, the same principles apply: clean weights, clear method names and predictable statuses. For larger operations we can write a small plugin that exports orders in exactly the format your warehouse or courier tool expects.

Why is my WooCommerce site slow, and how does a developer fix it?

A slow WooCommerce site is usually caused by too many plugins loading on every page, heavy images, cheap or distant hosting, an old PHP version, or orders still stored in the WordPress posts table. A developer measures first, then fixes the biggest cause rather than installing yet another speed plugin.

We measure three different kinds of slow separately. Storefront slow: product and category pages that take ages on a phone, which hurts Core Web Vitals and conversions. Checkout slow: the basket and payment step, which cannot be page-cached and so depends on server speed and plugin load. Admin slow: order screens that crawl, which usually points at the database.

Fixes are chosen by cause. Unused plugins are removed and scripts are stopped from loading on pages that do not need them. Images are resized and served in modern formats. Page caching covers the catalogue while basket, checkout and account pages are excluded. Object caching with Redis or Memcached takes load off the database. PHP moves to a supported version; WordPress.org currently recommends PHP 8.3 or greater.

Hosting matters too. A UK or nearby European data centre keeps response times short for British shoppers, and a plan with enough PHP workers stops checkout queuing when an email campaign lands. We give you a before-and-after measurement for every change, so you can see what the money bought.

HPOS: moving WooCommerce orders to their own database tables

High-Performance Order Storage (HPOS) moves WooCommerce orders out of the general WordPress posts tables into dedicated order tables, which makes order screens, reports and checkout writes faster on busy stores. It is worth doing on almost every established shop, carefully.

According to the WooCommerce developer documentation, HPOS became the default for new installations from WooCommerce 8.2 in October 2023 and stores orders across dedicated tables with their own indexes. Stores created earlier may still run on the old posts storage, or in compatibility mode that writes to both.

The risk is not HPOS itself but old plugins that read orders straight from the posts table. Those plugins break silently: an invoice plugin prints blank addresses, a reporting tool shows zero sales, a courier export skips orders. So we audit every active plugin for HPOS compatibility first, replace or patch the ones that fail, run the sync on staging with a copy of your real orders, compare totals, and only then switch the live store during a quiet hour.

After the switch we keep compatibility sync running for a short period so rolling back is possible, then turn it off once everything has been checked. You get a written note of what changed and which plugins were replaced.

Consent-aware analytics for a UK WooCommerce store under PECR

Under PECR, a UK store must get consent before setting cookies that are not strictly necessary, so analytics, advertising pixels and most marketing tags should wait until the visitor agrees. Basket and checkout cookies that the shop needs to function can run without consent.

The ICO’s guidance on cookies and similar technologies says consent must involve an unambiguous positive action, and that cookies which are helpful or convenient but not essential still require it. A banner that loads every tag first and asks afterwards does not meet that bar.

On WooCommerce this is fiddly because tags arrive from many places: a theme setting, a marketing plugin, a reviews widget, a chat tool, a manually pasted snippet. We find every source, route them through one consent tool, and use Google Consent Mode so GA4 ecommerce events such as purchases are handled according to the visitor’s choice rather than dropped or sent regardless.

We then test in a private window: decline and confirm nothing fires, accept and confirm purchases record. Your privacy notice wording and legal sign-off belong to you and your adviser. The UK GDPR cookie banner service covers this for any platform.

Extending WooCommerce with custom plugins instead of more add-ons

When an off-the-shelf extension almost does what you need, a small custom plugin written by a WooCommerce developer is often cheaper over time than stacking two or three paid add-ons that half overlap. It also loads only what your shop uses.

Typical UK requests: a made-to-measure calculator for blinds or curtains; trade customers who see net prices and order by case; a gift-message field that prints on the packing slip; a local delivery zone by postcode with a cut-off time; a “collect from shop” option with slots; stock synced from a spreadsheet or an EPOS export each night.

We write these as a standalone plugin in your repository, not as edits inside the theme or someone else’s plugin, so updates never overwrite them. Each one uses WooCommerce hooks and settings rather than direct database writes, has a short readme, and is tested against HPOS.

Bigger ideas, like a full trade portal with account credit or a customer area pulling data from another system, move into custom web app territory from US$900. For wholesale specifically, see the B2B wholesale website page; for accounts integration, the Xero integration developer page.

How to choose a WooCommerce developer in the UK: seven checks

Choose a WooCommerce developer by how they work, not by how many plugins they know: staging first, version control, written quotes and a clear handover. These checks apply to anyone you consider, including us.

• They ask for a staging copy and refuse to test fixes on your live checkout.
• They can explain in plain English why your store is slow before they propose a fix.
• They write custom code as a separate plugin, not inside the theme or third-party plugins.
• They check plugins for HPOS compatibility before switching order storage.
• They understand UK VAT display, tax classes and invoice requirements without being told.
• They leave your hosting, domain and admin accounts in your name and use their own user login.
• They give an itemised quote, and small fixes are priced before work starts.

A useful test question: “What would you check first if paid orders were stuck on pending payment?” A good answer mentions webhooks, caching on checkout and the processor’s log. A vague answer about reinstalling plugins is a warning sign.

If you are comparing a freelancer with a larger outfit, our agency vs freelancer guide sets out the trade-offs without pretending either is always better.

Red flags when hiring someone to work on your WooCommerce store

The clearest red flag is a developer who wants to work directly on your live shop without a backup or staging site. The second is anyone who asks you to move your hosting or domain into their name.

Other warning signs are quieter. A quote that says only “speed optimisation” with no measurement or list of changes. A plan to install a page builder on a working store to “make it easier to edit”. Edits made inside the parent theme, which vanish at the next update. Nulled or unlicensed premium plugins, which often carry malware and never receive security patches. Promises of guaranteed Google rankings after a speed fix.

Watch the handover too. At the end of any job you should have a list of what changed, any new plugins and why, where custom code lives, and confirmation that temporary admin accounts have been removed or can be. If a developer is reluctant to give you that, they are building dependence rather than a store.

We work through our own user accounts, keep changes in version control where your hosting allows it, and send a short written summary after every job. You can remove our access whenever you like.

Working with a WooCommerce developer in India from the UK

Working with us from the UK means WhatsApp for quick questions, video calls when a decision needs talking through, and a shared task list for everything else. Our afternoon and evening overlap your late morning and afternoon, and messages are answered seven days a week on Indian time.

A useful side effect of the time difference is that routine work, such as plugin updates or a planned HPOS switch, can happen in our morning, which is early in the UK when your store is quiet. Anything urgent is agreed case by case; response commitments, if you want them, are written into your quote rather than assumed.

Quotes and invoices come from India in USD. You pay from a GBP account through Wise, a bank wire or PayPal, normally per job or per milestone. We do not advise on how that is treated for your tax; your accountant does.

How much does a WooCommerce developer cost in the UK?

WooCommerce developer rates in the UK vary widely, and a direct comparison of hourly figures misleads more than it helps, because the real cost is hours multiplied by how accurately the problem is diagnosed. A cheaper hour spent guessing costs more than a dearer hour spent fixing.

With us, ongoing care starts at US$120/mo a month, which covers tested updates, backups and checkout checks. Individual fixes and extensions are quoted per job after the health check. A full rebuild or new WooCommerce store starts at US$750, and a larger custom plugin or portal starts at US$900.

Four things move a quote. First, the state of the store: years of abandoned plugins and theme edits take longer to untangle. Second, access: a host with staging and SSH is quicker to work with than one with only a file manager. Third, testing needs: subscriptions and multi-currency add test cases. Fourth, the amount of custom logic you want written rather than configured.

What we will not do is bundle hosting, plugin licences or card fees into our price. You buy those directly so you always see what they cost. For a sense of monthly upkeep across all website types, see the website maintenance cost guide.

WooCommerce SEO, product schema and AI search visibility

Keeping your WooCommerce store rather than migrating protects existing search visibility, and a developer can then improve it with faster pages, cleaner product data and correct structured data. Nobody can guarantee rankings, but broken foundations reliably hold a shop back.

The technical side we handle includes product structured data with price, availability and reviews where genuine, category pages that are not blocked or duplicated by filter parameters, a clean XML sitemap, canonical tags on variant URLs, and redirects when products are retired. We also check Google Search Console in your name for crawl and indexing errors.

Product feeds are part of this too. Google Merchant Center uses your product titles, prices, GTINs and availability to show products in Shopping results, and a feed full of mismatched prices gets products disapproved. We make sure prices in the feed match VAT-inclusive prices on the page.

AI assistants and AI Overviews tend to quote pages that state facts clearly: materials, dimensions, delivery times, returns. Good product descriptions and a delivery page that answers real questions help people and those systems alike. For ongoing growth work, monthly SEO starts at US$150/mo; see our ecommerce SEO service for UK shops.

Worked example: a hypothetical Sheffield kitchenware shop with a slow checkout

This scenario is invented to show the process; it is not a client. Say a Sheffield kitchenware retailer has run WooCommerce for six years, sells around 1,200 products, and is thinking about Shopify because checkout feels slow and paid orders sometimes stay on “pending payment”.

Health check findings: 48 active plugins, 11 of them unused; orders still in the posts table; PHP two versions behind; basket pages cached by mistake; the card gateway webhook still pointing at the old domain from a rebrand; a PDF invoice plugin that is not HPOS-compatible; analytics and a social pixel firing before consent.

What we would propose: fix the webhook and cache exclusions first, because they lose orders. Then remove unused plugins, replace the invoice plugin, move PHP to a supported version, and migrate to HPOS on staging before the live switch. Finally, wire all tags through one consent tool.

Why not migrate? The shop’s product URLs bring steady search traffic, it has trade pricing written as a custom plugin, and the problems are specific rather than structural. Moving would cost a full rebuild from US$750 plus redirect and data work, and would not fix a habit of adding plugins without review.

After: a monthly care plan from US$120/mo with quarterly plugin reviews, so the store does not drift back to where it started.

UK WooCommerce developer checklist before you hand over access

Before giving any WooCommerce developer access, prepare these items. They speed up the work, protect your data and make sure you stay in control of your own store.

• A full, recent backup of files and database that you have downloaded yourself.
• A staging site from your host, or permission for the developer to create one.
• A separate admin user for the developer, never your own login.
• A list of plugins you know you use, and any you are unsure about.
• Your accountant’s instructions on tax classes and invoice format.
• Access to your card processor dashboard (read-only is enough) for webhook checks.
• Your Click & Drop or courier account details, if order export is in scope.
• A quiet time window for live deployments, such as early morning UK time.
• Agreement in writing on scope, price and what the handover note will contain.

Ready to start? Send the plugin list and your main problem through our contact page or on WhatsApp, and we will tell you what the health check should focus on.