MarketPulse hiring guide
WooCommerce Developer Near Me
A WooCommerce store is WordPress, a plugin, a theme, a stack of extensions and a server, and every layer needs updates. The developer you hire builds features and also decides how safely those layers move together. This guide shows which skills to check, which duties to assign and how to test a developer before you sign.
A WooCommerce hire covers code and upkeep, so test both.
Searching for a WooCommerce developer near me means hiring for two jobs at once. One is building: product pages, checkout changes, connections to your till or accounting software. The other is keeping a self-hosted store healthy, because WordPress, WooCommerce, your theme and each extension release updates on their own schedules, and the server underneath has version requirements of its own.
This page covers the skills a WooCommerce developer should be able to show, with links to the official WooCommerce and WordPress developer documentation, the duties to put in writing, a method for spotting plugin bloat, a paid test task and eight questions that separate WooCommerce specialists from general WordPress builders.
What does a WooCommerce developer actually work on?
WooCommerce describes itself in its developer documentation as an open-source ecommerce platform built on WordPress, and it points new developers to WordPress plugin development first. In a live store, the work spreads over five layers:
| Layer | What lives there | Typical job for a local shop |
|---|---|---|
| Server | PHP, the database, memory limits, caching | Moving to a host that meets WooCommerce’s requirements |
| WordPress | Users, pages, the plugin system, hooks | Staff accounts with the right roles, safe updates |
| WooCommerce plugin | Products, cart, checkout, orders, shipping zones, local pickup | Pickup locations, postcode delivery zones, order emails |
| Theme | Templates, block layouts, a child theme for changes | A product page that shows stock per shop |
| Extensions and custom plugins | Bookings, subscriptions, payment gateways, your own code | A workshop booking form for a bike shop |
A developer who only knows the theme layer can make the store look right and still leave it fragile. Ask every candidate which layers they work in and which they hand to someone else.
Which WooCommerce skills should a developer prove?
- PHP and WordPress hooks. WordPress code changes behaviour through hooks: actions run a task at a set point, filters take a value, change it and return it. Good WooCommerce work adds custom behaviour through hooks in a plugin, so updates to WooCommerce and the theme do not wipe it out.
- Order code that works with HPOS. Since WooCommerce 8.2, new stores keep orders in dedicated tables (more on this below). Custom code has to read and write orders through WooCommerce’s own order objects.
- The WooCommerce REST API. The REST API creates, reads, updates and deletes store data as JSON through the WordPress REST API, and WooCommerce recommends using it over HTTPS. Any sync with a till, a warehouse or accounting software runs through it or through a plugin that uses it.
- Block-based cart and checkout. WooCommerce’s newer Local Pickup with several locations works only when the checkout uses the Checkout block.
- Child themes and block themes. WooCommerce’s developer docs cover setting up a child theme for classic themes as well as block theme development. Keep changes out of the parent theme, so a theme update cannot overwrite them.
- WP-CLI. Command-line tools for WordPress, including WooCommerce commands, speed up updates, imports and fixes.
Why does HPOS matter when you hire?
WooCommerce used to store orders as WordPress posts with post meta. High-Performance Order Storage (HPOS) moves them into tables built for orders and order addresses, and it has been the default for new installations since WooCommerce 8.2 in October 2023.
This touches your hiring in three ways:
- Old habits break. Code that reads order data straight from the posts table works on old stores and fails quietly on HPOS stores.
- Plugins can block it. When a plugin is not compatible with HPOS, WooCommerce disables the HPOS option under WooCommerce, Settings, Advanced, Features and lets you view the incompatible plugins.
- Switching needs care. Compatibility mode syncs orders between the old and new tables, and WooCommerce does not allow switching the authoritative tables while orders are waiting to sync.
Before the first call, open that Features screen yourself and note whether HPOS is on and which plugins are listed as incompatible. Ask the developer what they would do about each one. Someone who has never heard of HPOS has not kept up with WooCommerce for three years.
Who runs the server, the updates and the security fixes?
WooCommerce publishes server requirements for version 10.8 and later: WordPress 6.9 or greater, PHP 8.3 or greater, MySQL 8.0 or MariaDB 10.6 or greater, and a WordPress memory limit of 256 MB. It also says older PHP and MySQL versions still run WooCommerce but have reached end of life and can expose the site to security problems. Somebody has to own that list. Put the split in writing:
| Duty | Host | Developer | Owner |
|---|---|---|---|
| PHP and database versions | Provides them | Checks before each upgrade | Approves the date |
| WordPress, WooCommerce and plugin updates | Tests on a staging copy, then updates live | Places a test order afterwards | |
| Daily backups | Runs them | Tests a restore every quarter | Knows where they are |
| Security alerts for plugins | Patches or replaces the plugin | Gets a short report | |
| Admin accounts | Removes unused accounts | Approves new ones |
A monthly update routine that works for a small shop: copy the live site to staging, run all updates there, place a test order with pickup and one with delivery, check the order emails, then repeat the updates on the live site at a quiet hour and place one more test order. Ask candidates to describe their own routine; it should sound close to this.
How do you spot plugin bloat?
Every plugin adds code to update, test and secure. Bloat sets in when plugins pile up without anyone remembering why. Run this audit with your developer, or ask candidates how they would run it:
- Export the plugin list from the Plugins screen into a sheet.
- Next to each plugin, write the one job it does in plain words. A plugin nobody can describe gets flagged.
- Mark overlaps: two plugins that both add caching, two SEO plugins, two form builders.
- Mark plugins listed as incompatible with HPOS.
- For each flagged plugin, decide: keep, replace with one that covers two jobs, or remove after testing on staging.
Example audit (illustrative numbers): a bike shop starts with 38 active plugins. Six have no job anyone can name, five overlap with another plugin, and two block HPOS. Removing the six, merging the five overlaps into two and replacing the two incompatible ones leaves 38 − 6 − 3 = 29 plugins, nine fewer to update every month. At 5 minutes of testing per plugin per update round, that saves 45 minutes a month.
WooCommerce sells extensions through its own marketplace and says listed products follow its compatibility standards, which makes that marketplace a sensible first place to look for a replacement.
Where do you find WooCommerce developers?
WooCommerce runs a directory of Woo Agency Partners for building, migrating and maintaining stores. WooCommerce says every partner passes its technical and design review before being listed, and you can filter the directory by industry. For a specific fix or a short piece of focused work, the same page points to vetted WooCommerce developers on Codeable.
Use the directory as a starting list, then check fit yourself:
- Does their work include stores with physical products and local pickup or delivery?
- Do they host sites themselves, or work with your host?
- Who does the monthly updates after launch, and at what cost?
A WordPress developer close by is handy for a launch day in the shop or for training staff on the order screen. The code itself works the same whoever writes it and wherever they sit. If you are still choosing between one person and a team, read agency vs freelancer. MarketPulse does not rank or vet developers.
What makes a good paid test task for a WooCommerce developer?
Give every shortlisted developer the same task, budgeted at about 3 to 5 hours of their time, and pay their rate. You learn how they handle WordPress conventions, which a portfolio screenshot never shows.
Sample task (for a florist, an example):
- Write a small plugin, kept out of the theme, that adds a card message field to checkout.
- Save the message through WooCommerce’s order objects so it works with HPOS switched on.
- Show the message on the admin order screen and in the new-order email to the shop.
- Deliver it as a zip with a short readme: what it does, how to switch it off, which WooCommerce version it was tested on.
How to judge it: install the zip on a staging copy with HPOS on and place two orders. Then check four things. Did the code stay in its own plugin? Did they ask whether your checkout uses the Checkout block or the older shortcode checkout, since the two are built differently? Does the message survive a WooCommerce update? Is the readme there? A developer who passes all four has shown more than a 40-page portfolio would.
Which questions reveal real WooCommerce skill?
| Ask this | Listen for |
|---|---|
| Where would you put custom code for our store? | A custom plugin or a child theme, never edits to WooCommerce or the parent theme |
| What is the difference between an action and a filter? | An action runs a task at a point; a filter changes a value and returns it |
| Is our store on HPOS, and does it matter for your work? | They know where to check, and they read and write orders through WooCommerce’s order objects |
| Our checkout uses the Checkout block. What changes for you? | They ask which extensions touch checkout and test each one with the block before promising anything |
| How would you sync stock with our till every 15 minutes? | The REST API over HTTPS, scheduled jobs, what happens when one sync fails, and how to avoid selling the same item twice |
| Which PHP version does our host run, and is that enough? | They check it against WooCommerce’s current requirement of PHP 8.3 or greater |
| How do you run updates? | Staging first, test orders, then live at a quiet hour |
| How many plugins is too many? | No magic number; every plugin needs a named job, a maintainer and HPOS compatibility |
FAQ
Is a WordPress developer the same as a WooCommerce developer?
Every WooCommerce developer is a WordPress developer, but plenty of WordPress developers have never built a checkout change, an order sync or an HPOS-safe plugin. Ask for live stores they maintain and run the test task.
What is HPOS in WooCommerce?
High-Performance Order Storage keeps orders in dedicated database tables instead of WordPress posts. WooCommerce made it the default for new installations from version 8.2 in October 2023, and plugins that are not compatible can block it.
Which PHP version does WooCommerce need?
WooCommerce’s server recommendations for version 10.8 and later ask for PHP 8.3 or greater, tested up to PHP 8.4, along with WordPress 6.9 or greater (checked November 2026). Ask your host which version your site runs today.
Should my WooCommerce developer also host the site?
It can work, as long as the hosting account, the domain and the backups are in your name or can be handed over in a day. Separating host and developer makes it easier to change one without losing the other.
Where can I find a vetted WooCommerce developer?
WooCommerce lists Woo Agency Partners that passed its technical and design review, and points to Codeable for smaller focused jobs. Treat both as a shortlist and run your own checks and test task.
When should a WooCommerce store get its updates?
Plan a monthly update round on a staging copy, plus an extra round whenever a plugin you use announces a security fix. Each round ends with a test order on the live store.
Is WooCommerce the right platform for my shop at all?
That depends on your till, pickup and delivery needs and who will handle upkeep. The Shopify vs WooCommerce comparison for local businesses works through it job by job.
What should you do next?
Open your store’s Plugins screen and the WooCommerce Features screen, and write down the plugin count, the PHP version your host reports and whether HPOS is on. Take that page to every first call; how each developer reacts to it tells you a lot. Then send the same paid test task to your best three.
Not sure whether you need a WooCommerce specialist or a different kind of developer? Our guide to ecommerce developer types sorts problems by the kind of developer they need. For help preparing the brief, write to MarketPulse through the contact form.
Keep the WooCommerce hire on track
Guides for the budget, the platform choice and the weeks after launch.