WooCommerce builds for stores that have outgrown the starter theme — senior-dev architecture from day one. If your store does real revenue, holds real customer data, and the next problem is “we cannot keep duct-taping this together,” the right answer is a developer who has been inside WooCommerce since the WooThemes era.
Recent commerce-relevant WordPress work: Sherwin-Williams · M.L. Campbell Training Centre · Sayerlack · national news network, 2011–2012 platform migration
Book a 20-minute discovery call Ask a question first
The problem you’re sitting in
Most WooCommerce stores are built by stacking plugins until the cart works, then patching whatever breaks. That is a fine way to launch. It is a brutal way to scale. By the time the store is doing $50K a month in revenue, the checkout is loading 14 third-party scripts, the order metadata is split across five plugin tables, and nobody is sure which extension is responsible for the tax calculation that has been quietly wrong for nine months.
The reset is not “rebuild everything.” It is “bring in someone who can architect the next stage without throwing away what works.”
What I build for WooCommerce clients
- Storefronts that respect the brand. Theme work that uses WooCommerce’s templating properly instead of fighting it, with checkout flows tuned for conversion rather than for plugin defaults.
- B2B portals. Customer-specific pricing, account-tier visibility, gated catalogues, purchase orders, net-30 terms, and the order-volume features WooCommerce can do well when configured by someone who has done it before.
- Subscriptions. WooCommerce Subscriptions configured properly, including the failed-payment dunning logic and the customer-facing self-management portal that most stores skip.
- Payment-gateway integration. Stripe, Square, Moneris, PayPal, Apple Pay, Google Pay. Including the parts that actually take work — webhook reliability, idempotency, refund flow, and the half-failure cases.
- ERP and accounting integration. Order sync to QuickBooks, Xero, NetSuite, or your in-house ERP. Real bidirectional sync with conflict handling, not a flaky middleware layer that fails silently on the third sync of the day.
- Performance work. WooCommerce stores have a specific performance shape: cart and checkout pages are uncached, the product catalogue is heavy, the database grows fast. The work is different from generic WordPress speed work.
What this is not
- Not dropshipping ops. I do not source products, manage suppliers, or run your fulfilment.
- Not store management. I build the platform; your team runs the store.
- Not ad spend or paid acquisition. Your marketing team owns that channel.
- Not “Shopify is wrong, switch to Woo.” Sometimes Shopify is the right answer. The discovery call will say so honestly if your situation calls for it.
Who this is for
- ✅ Operating WooCommerce stores doing real revenue whose codebase has accumulated five years of “we’ll fix it later.”
- ✅ Brands launching a new store that needs to be right from day one because there is no margin for a re-launch in 18 months.
- ✅ B2B operations that need WordPress as the public surface and Woo as the commerce engine, with serious account-level customisation.
- ✅ Subscription businesses where billing reliability is a customer-trust problem, not a technical convenience.
- ❌ Stores doing under $20K a year. The architecture overhead does not pay back at that scale; you are better served by a hosted platform.
- ❌ Buyers who want a “$1,500 WooCommerce site.” That price exists; the people who deliver it produce the kind of store this page describes the cleanup of.
How an engagement starts
The 20-minute discovery call is free. We talk through your store today, what is actually breaking versus what is annoying, and what success looks like in six months. By the end of the call I will tell you whether the next step is a paid scoping engagement, a fixed-fee build, an audit, or a referral elsewhere.
For stores in the “we have grown into a mess and need a senior pair of eyes” zone, the WordPress Site Audit ($2,200 fixed-scope) is sometimes the right first move before any build work. The audit produces the document that tells you what to fix in priority order; the build work follows from there.
Why work with me on this specifically
- WordPress development since 2007. WooCommerce work since the WooThemes era.
- Comfortable with the parts most agencies avoid: payment-gateway webhook reliability, subscription dunning, ERP sync conflict resolution, multi-currency stores, B2B price tier modelling.
- Prior portfolio work for one of Canada’s largest news networks during the 2011–2012 platform migration, where checkout-class performance and reliability work was a daily discipline.
- Senior-developer rate, $275 CAD/hr. WooCommerce engagements are quoted fixed-fee or retainer after scoping; the rate informs the quote.
- Independent client work, off the day-job hours at Sherwin-Williams.
Common questions
Should I be on Shopify instead?
Sometimes. Shopify is the right answer for stores that want to outsource the entire infrastructure problem and do not need deep customisation. WooCommerce is the right answer when you need control over the data model, your checkout, your customer accounts, or the integration surface to systems Shopify does not natively reach. The discovery call will give you the honest answer for your situation, not the answer that points to my invoice.
Can you migrate us off Shopify or another platform?
Yes. Order history migration is the part that takes the most care. Customer accounts, product catalogues, and content move more cleanly. The discovery call will scope it.
Will you build with WooCommerce Blocks (the new checkout)?
Yes when it fits. The block-based checkout is now mature enough for most stores. The classic checkout still has the edge in some integration-heavy scenarios. The build will use whichever serves your store, not whichever is newer.
Do you support WooCommerce Subscriptions specifically?
Yes. Subscriptions is one of the more reliable WooCommerce extensions, but the failed-payment retry logic and customer-facing self-management portal are where most implementations fall short. That is where I focus the work.
How long does a WooCommerce build take?
Smallest fixed-scope builds I take on are around 8 weeks. Larger B2B builds with ERP integration run 4 to 6 months. Quoted fixed-fee after the scoping work so you know the number before you commit.
When you are ready
If your WooCommerce store is doing real revenue and the architecture is starting to fight you, the 20-minute call is the lowest-friction way to figure out the next move.
