Web development

Custom WordPress and WooCommerce plugins, themes and integrations, and headless React or Next.js front ends

01 / The problem

What it looks like from your side

Your store needs something no off-the-shelf plugin does well, or three plugins half-do it and slow everything down.

Most stores reach a point where the plugin directory runs out. The checkout needs a hold-then-charge payment, the reviews need to come from a custom form, or marketing needs to know which flyer produced which order. That's where custom work pays for itself, as long as it's built to be maintained.

What I build:

Custom plugins. Self-contained WordPress and WooCommerce plugins with their own settings, hooks and data, so they survive theme changes and updates.
Themes. Block or classic themes built for speed, without a page builder's weight.
Checkout and payment flows. Pre-authorization, subscriptions, deposits, custom fields and order rules.
Integrations. REST and webhook connections between your store and the CRM, the courier, the ERP or your own systems.
Headless front ends. React or Next.js storefronts on top of WooCommerce or a custom API, when the theme layer is the bottleneck.

Every build follows the same rules: a written spec first, a staging copy, small tested steps, a line-by-line review, and code that lives in your repository, not mine.

02 / Signs

Signs you need this

Tick what sounds like your business

A stack of plugins that overlap or conflict
A checkout or payment flow your business needs but your theme can't handle
Manual copy-paste between your store and another system
A theme so customized that nobody dares update it
A front end that feels slow even after caching

Tick the ones you recognise.

03 / Method

What I do, step by step

Read the current setup: theme, plugins, custom code, hosting
Write a short spec: what it does, what it doesn't, how we test it
Build in small steps on a staging copy, with tests where they matter
Review every line, then deploy with a rollback plan
Hand over the code, the notes and a short walkthrough

04 / Deliverables

What you get

Working code in your repository
A written spec and hand-over notes
Staging and production deploys

The number I report at the end

The number the feature was built to change: orders through the new flow, hours saved, errors removed

Typical timeline: Days for a focused feature; weeks for a plugin or a headless front end

05 / Proof

Related work

US subscription supplement store

Building

QR attribution plugin

Problem: Street marketing had no way to prove which flyers produced orders.
What I built: QR codes with post-scan tracking and first/last-touch order attribution, built to grow with more features.
Outcome: In build for a live store; each order will carry the first and last QR scan that led to it.
Stack: WordPress
WooCommerce
PHP
React

Have a project like this?

Four short steps, about 90 seconds, with this service already selected. Then we book a discovery call.

Start a project