I interact with WooCommerce all day everyday.
Developers call it bloated. Competitors call it legacy. New entrants (like FluentCart) arrive promising to strip away the complexity and deliver something clean, fast, modern. And every few years, someone tries to build a simplified version. (I am not excluding Woo itself.)
I pull my hairs out just thinking over some weird quirks I might have to work on that day. Yes, I stopped counting how many times I felt I was gaslit by WooCommerce just by how I missed a small setting that was so ‘obvious’ that I should know better.
Jokes on you. Settings don’t mean anything to me, so I just quit remembering them.
Complexity isn’t a bug. It’s being human.
WooCommerce succeeded because business and commerce are made of regulations and complexities. Every moving part is messy. Taxes vary by jurisdiction, product type, customer location. Shipping has zones, weight classes, carrier rules, dimensional pricing. Variable products have size, color, material, inventory per variant, backorder rules, sale pricing schedules.
And that’s just online side. Merchants have to think everything through as a whole operation outside of online stuff.
That’s the reality of real business. The WooCommerce looks complex because commerce is complex. Stripping that away doesn’t simplify the merchant’s life — it just makes the platform incapable of holding their actual business.
We are not going to solve the complexity of taxes or shipping because that’s just how they are. They’re human systems — regulatory, regional, historical, negotiated. The software that pretends otherwise isn’t simpler. It’s just incomplete.
Calling WooCommerce ‘flexible’ is an understatement. It has the capacity to hold the mess — and that’s exactly what real commerce needs.
Merchants are not clueless. Don’t assume they are.
Most business operators are literate in many aspects of their operation. A shop owner running a t-shirt business understands variants, inventory, wholesale pricing, tax exemptions… They didn’t learn these things from WordPress. They are bringing their knowledge to it, and judging if the tool simply works for them or not.
Sure, there are people who might wake up one day and say “Imma start selling my 3D printed keychains” and they might just need a simple setup. But they will eventually grow to learn these operational side of business to make their vision come true. Platform isn’t gonna give you everything they need. While these platforms pretend like they are the all-in-one solution.
And that savviness of users is hidden gem that no one notices.
It’s why the commerce ecosystem thrives, why extensions get built, why people documents to share with others, why workarounds get shared. The platform and the user base co-evolve.
This is what gets overlooked when simplified alternatives target “frustrated WooCommerce users.”
WordPress already solved the hardest problem.
WordPress already solved user roles, editing, media management, content ownership, plugin ecosystem, the developer-to-operator handoff, and 20 years of accumulated solutions to problems that felt mundane the moment they were solved.
Developers choose WordPress not because they love it, but because their clients can use it after they do the hand-off. It’s a people-centric, people-enabling platform. The deliverable isn’t a website—it’s a website plus the ability for a non-technical person to own and operate that website indefinitely without a developer on call.
The question doesn’t change. Only the technology does.
People are going to question and land on the same answer: “Why build a WordPress site when Claude Code can make static sites without needing WordPress?”
Because the end user needs to edit and operate. The issue that WordPress solved 20 years ago is still relevant — because the human world hasn’t changed. If anything, things will get further complex over time.
A developer or an AI agent can build anything. But when building is done, who operates it? The merchant. The blogger. The business owner who knows their inventory intimately but has never opened a terminal. That person needs to edit a product description at 11pm. Process a refund when a customer complains. Change store hours before a holiday. None of that is a development task. All of it is a business operation.
And here’s the quiet irony: AI-assisted development actually reinforces the WordPress case rather than threatening it. The build cost collapses. But the daily, ongoing operation by a non-technical human stays constant. So the ratio of time building to time operating shifts dramatically toward operating. Which makes the operator experience more important, not less.
Every generation of developers looks at WordPress and sees it as legacy blogging platform or even feel second-hand embarrassment for thinking about WordPress as framework.
Blogging or not, the 20-year-old problem is still the problem even to date.