5 Things Your WooCommerce Agency Never Told You
- Most WooCommerce agencies optimise for project completion, not for long-term store health — and four common practices make stores progressively harder and more expensive to maintain.
- Plugin sprawl is the number one hidden cost: 40+ plugins means 40+ update cycles, 40+ potential conflict points, and performance degradation that accumulates invisibly over time.
- Hardcoded customisations in the child theme break on every WooCommerce major release — most agencies know this and charge for the fix each time rather than building update-safe solutions.
- Most agencies never discuss the hosting performance ceiling: a £10/month shared host will bottleneck a store at around 20 concurrent visitors, regardless of how well the site is built.
This is not an anti-agency post. Good WooCommerce agencies do excellent work. But the agency model has structural incentives that do not always align with your interests as a store owner — and understanding them helps you ask better questions and make better decisions when you hire.
Thing 1: Your Plugin Count is a Ticking Clock
Every plugin you add is a dependency. Each one has its own update schedule, its own potential conflicts with other plugins, and its own performance overhead. A store with 50 plugins is not twice as complex as a store with 25 — it is exponentially more fragile. When an update breaks something (and it will), diagnosing which plugin interaction caused it takes hours. Agencies bill for those hours. The incentive to reduce plugins does not always exist.
Thing 2: Child Theme Customisations Are Technical Debt by Design
When an agency adds custom functionality by modifying templates in a child theme, they are creating code that will break when the parent theme updates. This is known, it is a deliberate trade-off (it is faster than building a proper plugin), and it means every major WooCommerce or theme update is a potential breakage event that requires paid maintenance. A clean solution would be a properly namespaced plugin — but that takes longer to build and the client usually cannot tell the difference.
Thing 3: Page Speed Scores Are Vanity Metrics in the Wrong Context
A 90+ PageSpeed score in a staging environment with no products, no logged-in users, and no cart activity tells you almost nothing about how your store performs under real load. Many agencies deliver stunning PageSpeed scores on launch day. Six months later, with 5,000 products and real traffic, the store is slow and the agency is gone.
1. How do you handle WooCommerce major version updates — do you have a staging test process? 2. What is your policy on plugin selection — do you build custom or install plugins? 3. What happens to our site if we stop working with you? 4. Can you show me a current client whose store has been running for 3+ years without major rewrites?
References
- WooCommerce Extension Best PracticesWooCommerce Developers — the right way to build WooCommerce customisations (plugins vs child theme).
- Core Web VitalsGoogle Web.dev — the real performance metrics that affect search ranking and user experience.
- WooCommerce Release CycleWooCommerce.com — major, minor, and patch release schedule that determines customisation breakage risk.
Leave a Reply