Audit the stack
Every plugin, cache rule and theme customisation currently running, and what each one does.
Development
Woocommerce Development
WordPress gives you more control than Shopify and more ways to break something. We build and fix WooCommerce sites with the plugin conflicts and caching layer already accounted for.
0
Plugin conflicts left unresolved at handover
2–5wk
Typical build & QA timeline, depending on scope
1
Full stack audit before any code changes
The problem
WordPress makes it easy to add a plugin, not to remove one
A typical WooCommerce site accumulates a page builder, a caching plugin, two or three "marketing" plugins each injecting their own scripts, and a theme nobody fully understands anymore. Development work here means knowing what's actually running before you change anything.
We build and modify WooCommerce sites with that reality built in — caching rules that don't break dynamic pricing, plugin conflicts resolved rather than worked around, and changes tested against the stack you actually run, not a clean install.
The fix
What we build
- Custom theme and page-builder development, or targeted fixes to what exists
- Checkout customisation within WooCommerce's block-based checkout
- Caching and CDN rules that don't break tracking, personalisation or dynamic pricing
- Plugin conflict resolution, including the ones nobody remembers installing
- REST API and Zapier/Make integrations to your CRM or fulfilment stack
- Built alongside the WooCommerce tracking rebuild, not before it
Before & after
What changes once the stack is actually known
Same site, same plugins — the difference is knowing exactly what each one does before changing anything.
Nobody knows what half the installed plugins do
Years of quick fixes leave a plugin list nobody fully understands, each one a risk the next change might trip over.
Before
Unknown plugin stack
After
Fully audited stack
Caching quietly breaks dynamic pricing and tracking
A cache rule tuned for speed serves the same page to every visitor, including the tracking pixel and the price they were shown.
Before
Cache breaks tracking
After
Rules tested with tracking on
Changes tested on a clean install, not your real stack
A fix that works on a bare WooCommerce install can still fail once it meets your actual plugins, theme and caching layer.
Before
Tested on bare install
After
Tested on your real stack
Process
How a build runs
Scope and build on staging
Changes made and tested against a copy of your real stack, not a bare install.
QA against caching and edge cases
Checked with caching active, since that's where most WooCommerce bugs actually surface.
Deploy and document
Pushed to production with a written record of what changed and any new dependencies.
What clients say
Don't just take our word for it
We were told the ads were working while our accountant said otherwise. They were the first people to open the tracking and show us why both things were true at once. The reported number dropped after the fix, then grew for real.
I had no idea how much of my reporting was double counted. Now the number on the dashboard is a number I can actually plan against.
A tag manager migration from years ago had never been finished. Every signup had been counting twice, and nobody had noticed because it was consistent. Finding that paid for the whole engagement.
Questions
Common questions
Do you work with our existing page builder?
Yes — Elementor, Divi, Bricks and the block editor are all fine. We work within what you have unless there's a specific reason to move off it.
Can you audit which plugins are actually needed?
That's usually the first thing we do. Most sites we open are running plugins nobody has used in over a year, each one adding load time and risk.
Do you handle hosting as well?
We can recommend changes if hosting is the actual bottleneck, but we don't manage hosting directly — that stays with your existing provider or agency.
Do you handle plugin updates after the build ships?
The initial build isn't ongoing maintenance, but we document every dependency so updates can be tested safely, and we're available if you'd rather we handle it.
Start here
Find out what your account is actually reporting
Send us access and we will come back with a written audit: what is tracked, what is double-counted, what is missing, and what we would change first.
No pitch deck · No lock-in · Findings are yours either way