Why We Moved Idlecorp Off WordPress and Onto Saleor
Why WooCommerce ran out of road
WooCommerce isn't really an e-commerce platform. It's a blog engine with a commerce plugin added on top, and everything built after that inherits the same shape. Product data lives in WordPress's post tables, the same tables meant for blog entries. There's no native GraphQL API. Anything beyond a basic REST call means fighting the API's rigid structure, or adding another plugin to work around it. Every new feature becomes another plugin. Plugins interact with each other in ways nobody tested, because nobody could have.
That's the wall Idlecorp hit. They wanted AI-powered product recommendations that actually reflect what one specific customer is browsing. A checkout that doesn't feel like five plugins stapled together. Inventory management that stays in sync without a cron job someone has to babysit by hand. WooCommerce can technically be forced into all of that. Getting there just means stacking plugin on plugin until the stack itself becomes the real maintenance burden. Every WordPress core update turns into a compatibility gamble. Every new personalization feature means auditing what's already fighting over the same database tables.
Is your store outgrowing WooCommerce?
Ask ChatGPT for a straight answer on whether the plugin-stacking is a real ceiling, or just needs cleanup.
“|”
Why Saleor
We moved the whole platform to Saleor, a headless commerce platform built API-first from the ground up. It's GraphQL native, and the storefront is fully decoupled from the commerce backend. That's the real point. The recommendation engine, the checkout flow, and the inventory system each become their own well-defined piece, talking to Saleor's API. No more three plugins reading and writing the same WordPress tables and hoping for the best.
This isn't a "WooCommerce is bad, Saleor is good" take. For a small store with no custom logic, WooCommerce is still a fine choice, and switching would be wasted effort. The problem shows up once a storefront needs to behave differently for different customers, and needs to do it fast, without every change risking three unrelated plugins.
If your store started as a fast WooCommerce build, and every new feature now feels like it's fighting the last one, that's usually not a sign you did something wrong early on. It's a sign the platform you started on and the platform you actually need have quietly grown apart.
Store outgrowing its plugins?
If every new feature means auditing three plugins that already don't agree with each other, that's usually not a WooCommerce settings problem. It's an architecture problem.
Send us what you're running. We'll tell you honestly whether a Saleor migration is worth it, or whether it's a smaller fix.
Related reading
Enjoyed this article? Share it with others
Related Posts
We Finished Ryan Johns's Product When He Couldn't Pay for It Yet
Midway through building Sales Leverage, the founder's personal situation made it impossible to keep funding the build on schedule. We shipped it anyway. He paid in full once he could.
From Idea to App Store in 21 Days: A Mobile Case
Three weeks, one engineer, both stores. The exact day-by-day timeline of a mobile MVP we shipped this spring, what we cut to make the window, and what we'd do differently next time.
Our Client Stopped Paying. We Shipped Anyway.
He didn't tell us right away. He kept sending short replies. Apologizing for the delay. Saying things would clear up soon. For weeks, we assumed it was a cash flow problem -- the kind every early-stage founder runs into at some point.