WooCommerce vs Custom E-commerce — Real Trade-Offs and When to Switch
WooCommerce vs custom ecommerce is a question of catalog size, daily orders and integration depth — not taste. WooCommerce is a reasonable choice up to about 3,000 SKUs, 200 orders a day and standard payments. Beyond that threshold the plugin stack becomes brittle, updates break checkout and wp-cron starves the database. A custom online store on Next.js + Postgres removes the 20-plugin dependency, gives a predictable 2-year TCO and integrates directly with ERP, warehouse and couriers.
When WooCommerce works and when it stops working
WooCommerce is a free WordPress extension with 5M+ active installs — there is a plugin for everything. That is also the weakness: every plugin is third-party code that can break your cart at the next release. Below is the practical line where WooCommerce starts costing more than it saves.
- ✓Up to 3,000 SKUs, 200 orders/day, 1-2 warehouses — WooCommerce handles this on a decent VPS with 15-20 plugins. Ideal for the first 12-18 months.
- ✓Standard checkout, one courier, one warehouse — Stripe and the courier plugin work, stock syncs via wp-cron, orders land in email. The classic SMB scenario.
- ✗5,000+ variants and B2B pricing tiers break it — wp_postmeta stores each attribute as a separate row. At 50,000+ variants product queries cross the 3-second mark even with object cache.
- ✗20+ plugins = update roulette — WooCommerce, WordPress core, the theme and paid plugins (WPML, cache, gateway, courier) all update on different cadences. One of them will break checkout on a Friday night.
- ✗Real ERP/warehouse integration needs middleware — the WooCommerce REST API is slow and writes to wp_postmeta. Two-way sync with a real ERP development stack needs an extra node service or a plugin like ATUM — more points of failure.
- ✗PageSpeed below 50 on mobile — WordPress + WooCommerce + cache plugin rarely beats 60 on Core Web Vitals without heavy manual script trimming. A custom Next.js store starts at 90+ out of the box.
- ✗Hidden TCO — €600-€1,200/year in plugin licenses — WPML, WooCommerce Subscriptions, courier modules, Bookings, Memberships, Multistore. Adds up to a year of custom software maintenance.
Who each option is for
Starter stores with up to 500 SKUs, 30 orders/day, one warehouse, one courier, no B2B. Budget €1,500-€4,000 to build and €40-€80/month for hosting plus plugin licenses. You can migrate to a custom online store later, when revenue justifies the spend.
3,000-8,000 SKUs, 100-300 orders/day, 2-3 warehouses, one or two couriers. Either heavy custom WooCommerce or a switch to custom ecommerce can work. The tie-breaker: B2B tiers, partner portal or real-time ERP sync — if yes, go custom now.
10,000+ SKUs, 500+ orders/day, B2B and B2C on one stack, multistore with shared stock, marketplace with external sellers, or warehouse plus manufacturing. Every month on WooCommerce here costs more in downtime than the budget for a custom build.
How we move you from WooCommerce to custom
We do not start from a blank rewrite — we start with an audit of what already works. About 70% of the logic in a mature WooCommerce store is standard (catalog, cart, checkout) and we replicate it directly. The other 30% — the custom business rules plugins do not cover — is exactly why you are switching.
1. Audit of the current WooCommerce store
We review every active plugin, integration and theme override. We mark which become native modules, which are dropped and which silently hold up revenue. Real numbers come from logs — traffic peaks, page load, conversion rate and where checkout drops.
2. Architecture — Next.js + Postgres + headless
Next.js 15 frontend with App Router and React Server Components for sub-1.5s LCP. Node/PostgreSQL backend with a normalized schema — products, variants, prices, stock and orders in real tables, not JSON metafields. Stripe/Mollie for payments, Algolia or Postgres FTS for search.
3. Catalog, customer and order migration
We write a one-off migration script that reads wp_posts / wp_postmeta directly and ports products, variants, images, customers, orders and coupons. All WooCommerce URLs are preserved with 301 redirects so SEO equity transfers without traffic loss.
4. Integrations — warehouse, couriers, ERP, accounting
We connect the new store directly to your couriers, payment gateways, bank feeds and existing ERP — no middleware plugins, just native API clients with heartbeats and alerts. See how to connect online store with warehouse and couriers for the concrete pattern.
5. Soft-launch, parallel run and cut-over
The new store runs in parallel with WooCommerce for 2-3 weeks on a subdomain. We process 50-100 real orders, measure conversion and LCP, then flip DNS during a low-traffic night. The old WooCommerce stays read-only for 90 days as a safety net.
Why Saitami
Pricing is fixed in EUR — no GMV-based fees or per-order taxes. Before deciding WooCommerce vs custom ecommerce, also see Shopify vs custom online store and custom software as a reference for similar trade-offs.
Frequently asked questions
When does WooCommerce actually stop being enough?
When you cross 5,000+ variants, 200+ orders a day, B2B clients with individual price lists or a multistore with shared stock. At that point wp_postmeta becomes the bottleneck, the cache invalidates on every order, and the number of plugins writing to the database makes every update risky.
What is the real 2-year TCO — WooCommerce vs custom?
Mature WooCommerce: €3,000 build + €1,000/yr plugin licenses + €600/yr hosting + €2,500/yr maintenance = ~€10,200 over two years. Custom: €12,000-€18,000 build + €0 licenses + €400/yr hosting + €2,000/yr support = ~€16,800 over two years. The €6,000 delta is recovered by the first 5-10% lift in conversion on a clean, fast checkout.
Will I lose SEO rankings when migrating from WooCommerce?
No, if the migration is planned. We keep every URL one-to-one, copy meta descriptions, category structure and schema markup. We add server-side rendering and Core Web Vitals under 1.5s, which Google ranks higher. Most of our clients see a 15-30% lift in organic traffic in the first three months after migration.
How long does the WooCommerce-to-custom move take?
Standard mid-size store (3,000-10,000 SKUs, 5-10 integrations, single language) — 10-14 weeks from kick-off to cut-over. Complex scenarios with multistore, B2B and production planning — 16-22 weeks. The first 3 weeks are audit and architecture, the next 6-10 are build and migration, the last 2-3 are parallel run and testing.
Ready for a defensible choice between WooCommerce and custom?
Send us your WooCommerce URL and a short note on your pain points (slow checkout, B2B needs, ERP sync). Within 5 business days you get an audit with a concrete recommendation — stay, optimize or migrate — and a hard EUR price for each path.
Request an audit and quote →Related services: Shopify vs custom online store · connect store with warehouse and couriers · e-commerce development