The claim, and the honest version of it
"WooCommerce doesn't scale" is forum folklore. "WooCommerce scales forever" is hosting-company marketing. Both are wrong in useful ways. WooCommerce runs genuinely large stores, serious order volumes are real, but it runs them on purpose-built foundations, and the stores that hurt are the ones that grew past their foundation without noticing. This page maps the actual ceilings, the symptoms of hitting each, and the honest decision point. The service framing lives at the WooCommerce page; the slow-store triage page covers the day it starts creaking.
The four real ceilings
- The hosting ceiling (hits first, hits everyone). Shared hosting runs a Woo store to roughly a few thousand orders a month before admin queries and cart traffic start queuing. The fix is graded: quality managed host → dedicated resources → object caching (Redis) → database on its own tier. Every ceiling below this one gets mistaken for this one, which is why "WooCommerce is slow" is usually "the store outgrew a $12 plan."
- The catalog ceiling. WooCommerce handles large catalogs, with the right data layer. Beyond tens of thousands of products with heavy attribute filtering, default lookups strain and search/filter queries crawl. Fixes: proper indexing, faceted-search infrastructure, disciplined variation design (variations are rows to the database, 500 products × 30 variations is 15,000 lookups waiting to hurt).
- The plugin ceiling. The ecosystem is Woo's superpower and its scale liability. Subscriptions, bookings, loyalty, marketplace, EU VAT, each plugin adds queries to every cart and checkout request. At scale, each integration must justify its queries. The honest pattern: fewer, better plugins; custom where the stack fights itself; and the marketplace team when multi-vendor enters.
- The operational ceiling. Volume creates weight: order tables bloating (Woo's high-performance order storage exists precisely for this), email queues, session tables, reporting queries over millions of rows. Fixes are data hygiene (archiving, table maintenance) and infrastructure, not a platform swap.
The graduation decision, made honestly
Move off WooCommerce when the cost of staying exceeds the cost of moving: when checkout performance needs infrastructure spending approaching a Shopify Plus fee, when the plugin stack needs more engineering than a purpose-built stack, or when operational load demands a platform whose job is operations. Stay when the catalog model is idiosyncratic, the team knows WordPress, and the ceiling in the way is the hosting tier, the most common case by far. The audit that decides this measures queries, cache hit rates and checkout latency, not vibes. Context: WordPress vs Shopify for the platform debate, the cost calculator for either build, and the brief when the audit says "fix the foundation" or "graduate."