WooCommerce makes sense when the store is part of a content site rather than the whole of it: a brand that publishes seriously, a catalogue with editorial around it, a team already fluent in WordPress.
Commerce
WooCommerce for content-led catalogues.
For stores where content and catalogue live together. Custom Woo builds, plugin discipline, and the performance work that most Woo sites are missing.
What this requires from you
-
The plugin question
Woo's strength and its weakness are the same thing — there is a plugin for everything. Every plugin is code you did not write running in your checkout. We keep the list short, check what each one loads on the front end, and write the small ones ourselves rather than installing a suite to get one feature.
-
Making it fast
Out of the box, a Woo store does a lot of work per request. Object caching, page caching with correct exclusions for cart and account, a sensible number of products per query, and images generated at the sizes actually used. Most Woo performance problems are a handful of uncached queries repeated on every page.
-
Custom where it counts
Pricing rules, shipping logic, subscription behaviour and B2B account handling are where a Woo build earns its money. Those become proper plugins with tests, not snippets in a theme file that the next update overwrites.
-
Payments, tax and reality
Gateways, tax rules and stock sync with whatever the warehouse actually uses. We test the failure paths — declined card, partial refund, oversell — because those are the journeys customers remember.
-
Updates as routine
Core, plugins and PHP versions are updated on a schedule against a staging copy, with a rollback path. A store left far behind on updates is a security incident waiting for a date.
Compare with Shopify or read e-commerce and retail.
Discuss the next step
Tell us what you want to build or improve. We reply with a plan, an indicative budget and a start date.