WooCommerce vs custom ecommerce: which one should you build?

Short answer: WooCommerce vs custom ecommerce

Choose WooCommerce if your products, checkout and fulfilment look broadly like other stores in your sector, you have up to a few thousand SKUs, and your integrations are one-way or simple. Choose a custom ecommerce platform if you sell configurable products, need per-customer B2B pricing, sync large catalogues with an ERP in both directions, or your WooCommerce store already needs constant firefighting.

For most small and mid-sized retailers, a well-built WooCommerce store is the right answer. The rest of this article shows how to tell whether you are the exception.

Why does the WooCommerce or custom decision matter so much?

The platform sets three things that are expensive to change later: your data model, your maintenance cost and how fast you can add features.

Data model. WooCommerce stores a product as a post with metadata, and each variation as another post. That is fine for a T-shirt in five sizes. It becomes heavy for a sofa in 40 fabrics, 6 sizes and 3 leg finishes, because you either generate 720 variations or bolt on a configurator plugin that prices outside WooCommerce's own logic. Above 30 variations, WooCommerce already stops embedding every variation in the product page and looks combinations up by AJAX instead (the woocommerce_ajax_variation_threshold filter, default 30), a hint that the model was not designed for large matrices.

Maintenance cost. A WooCommerce store is WordPress core, WooCommerce, a theme and often dozens of plugins, each with its own release cycle. Every update is a small compatibility test. A custom platform has fewer moving parts, but every feature is yours to maintain.

Feature speed. On WooCommerce, a lot of features exist as plugins you can install in an hour. On a custom platform, nothing exists until it is built, but anything can be built exactly as needed without fighting a plugin's assumptions.

When is WooCommerce enough?

Be honest with yourself here: WooCommerce is enough far more often than agencies selling custom builds admit. It is the right choice when:

• Your catalogue is simple or lightly variable: up to a few variations per product, prices that do not depend on combinations.
• You have up to roughly 10,000–20,000 SKUs and stock updates a few times a day, not every minute.
• Your integrations are standard: a payment provider, one or two couriers, an invoicing or accounting tool, a Google Merchant feed, an email platform. All have mature plugins or straightforward REST API connections.
• Content matters to your marketing. WordPress is still one of the best editors for blog posts, guides and landing pages.
• You want ownership without platform fees. WooCommerce is open source with no revenue share, and you can move host or agency whenever you like.

Modern WooCommerce is also faster than its reputation. High-Performance Order Storage (HPOS), which stores orders in dedicated tables, has been the default for new stores since WooCommerce 8.2, and the block-based Cart and Checkout has been the default for new installs with block themes since 8.3. Combined with object caching (Redis), a CDN and a lean plugin list, a WooCommerce store can keep Core Web Vitals green.

When does a custom ecommerce platform pay off?

Custom pays off when the way you sell is the thing that makes you different, or when WooCommerce workarounds already cost more than code would. Typical triggers:

• Configurable products where the price comes from a matrix of options, dimensions or materials, and must be correct online.
• B2B pricing: per-customer price lists, volume tiers, credit limits, payment terms, quotes that become orders, several buyers under one company account.
• Deep two-way ERP sync: stock per warehouse, prices, customers, orders, invoices and shipments with Business Central, SAP or similar, every few minutes, with conflict handling.
• Many supplier feeds that change constantly and need mapping, deduplication and enrichment before they go live.
• Omnichannel selling: sales agents, showrooms, in-store assisted selling and online orders on one platform.
• Performance under load that no amount of caching fixes because the slow part is logged-in, personalised pages such as B2B catalogues.

Warning signs your WooCommerce store has outgrown plugins

If you recognise three or more of these, it is time to price an alternative:

• More than 40 active plugins, several of which modify the cart or checkout
• Updates are postponed because "the last one broke something"
• Imports fail with 504 Gateway Timeout or Allowed memory size of 268435456 bytes exhausted
• WooCommerce → Status → Scheduled Actions shows hundreds of failed or pending actions
• Staff keep a spreadsheet next to the store to correct stock, prices or orders
• Product edit screens take 10+ seconds to load or save
• Customers see stock that is not available, or prices that differ from the ERP
• You pay for several plugins that each do part of the same job

Not every symptom means "go custom". Some are fixed by better hosting, HPOS, cleaning wp_options autoload data or replacing two plugins with one integration. But if the problem is structural (data model, sync, pricing logic), plugins will not fix it.

What a typical integration actually moves

When people say "we need ERP integration", they usually mean several separate flows. Writing them out like this makes the WooCommerce or custom question much easier to answer:

Data	Source of truth	Direction	Typical frequency
Products and attributes	ERP or supplier feeds	To the store	Daily, or on change
Stock per warehouse	ERP	To the store and marketplaces	Every 5–15 minutes
Prices and B2B price lists	ERP	To the store	Hourly, or on change
Customers and trade accounts	Store and ERP	Both ways	On registration or change
Orders	Store and marketplaces	To the ERP	Within a minute
Invoices and credit notes	ERP or invoicing tool	To the customer and the store	On issue
Shipments and tracking	Courier	To the store and customer	On label creation and status change

If only the first and last rows apply and they run daily, WooCommerce with a plugin or a simple REST API job is enough. If most rows apply, at minute-level frequency, plan for custom code, either as a custom WooCommerce plugin or as part of a custom platform.

WooCommerce vs custom ecommerce: decision matrix

Score your store against each criterion. If most of your answers fall in the custom column, the extra budget is likely to pay back.

Criterion	WooCommerce fits	Custom fits
Catalogue size	Up to ~20,000 SKUs	20,000+ SKUs or many supplier feeds
Product type	Simple or few variations	Configurators, price matrices, bundles with rules
Pricing	One price list, coupons	Per-customer B2B lists, tiers, contracts
ERP integration	One-way export, daily stock	Two-way, near real-time, multi-warehouse
Marketplaces	One channel via plugin	Several marketplaces with shared stock
Checkout	Standard checkout	Quotes, approvals, credit terms, custom steps
Traffic profile	Mostly anonymous, cacheable	Many logged-in or personalised sessions
Content and blog	Strong (WordPress editor)	Possible, needs a CMS built in
Time to launch	4–12 weeks	3–6 months
Build budget (estimate)	€2,000–€20,000; €20,000–€60,000 with deep integrations	€40,000–€150,000+
In-house skills	Generalist WordPress support	Access to a development team
Lock-in	Low: open source, many agencies	Medium: depends on code quality and documentation

The middle ground: custom WooCommerce

There is a third option that many stores end up with: WooCommerce for products, orders and payments, with a bespoke theme and custom plugins for the parts that matter, such as an ERP connector, a pricing engine or a configurator. You keep the WooCommerce ecosystem and the admin your team knows, and you replace the fragile plugin stack with code written for your business.

It does not remove WooCommerce's data model, so it is not the answer for the heaviest configurators or B2B portals. For a store with complex integrations but standard products, it often delivers 80% of the benefit at half the cost.

Step by step: how to decide between WooCommerce and custom

1. Map your data flows. For stock, prices, products, customers, orders, invoices and shipments, write down where each one is created, where it must go, and how often. Two-way flows with minute-level frequency are the strongest custom signal.
2. Audit your current store, if you have one. Export the plugin list, check Scheduled Actions for failures, time the admin product edit screen, and run PageSpeed Insights on a category and a product page.
3. List the three features that sell for you. If all three exist as maintained WooCommerce plugins or simple integrations, WooCommerce wins. If none do, price custom.
4. Estimate the manual work. Count staff hours per week spent copying orders, correcting stock or updating prices. Multiply by 52 and by an hourly cost. That number is your annual budget for automation.
5. Price both options on the same scope. Ask for fixed quotes for WooCommerce (or custom WooCommerce) and for a custom platform, plus three years of hosting and maintenance.
6. Plan the exit. Whatever you choose, make sure you own the code, the server access and the data, and that URLs are planned so a later move only needs 301 redirects.

Common mistakes when making the decision

• Choosing custom for the design. A unique look does not need a custom platform. A bespoke WooCommerce theme gives you full design freedom for a fraction of the price.
• Choosing WooCommerce because "it's free". The software is free; the hosting, maintenance and integration work are not. Price the full three years.
• Ignoring the people who use the admin. Your team spends more hours in the back office than customers spend on the storefront. Ask them what slows them down before you decide.
• Rebuilding everything at once. If only the configurator or the ERP sync hurts, replace that part first. A phased approach reduces risk and spreads the cost.

Questions to ask any agency before you sign

• Which parts will be off-the-shelf plugins, and which will be custom code?
• Who maintains each plugin, and what happens if one is abandoned?
• How are integrations monitored, and who is alerted when a sync fails?
• Will we get the full source code, server access and documentation?
• What does a typical feature request cost after launch, and how fast is it delivered?
• How are updates tested before they reach the live store?

An agency that answers these clearly, in writing, is usually one that has run stores for years rather than only built them.

What do WooCommerce and custom ecommerce cost over three years?

These are estimates for a mid-sized store (about 3,000 SKUs, ERP export, two couriers, one marketplace), excluding VAT and payment fees.

Cost item	Custom WooCommerce	Fully custom platform
Design and build	€8,000–€20,000	€40,000–€80,000
Integrations (ERP, couriers, marketplace)	€4,000–€15,000	Included or €5,000–€15,000
Plugin licences, 3 years	€600–€2,500	€0–€500
Hosting and maintenance, 3 years	€3,200–€9,000	€5,000–€15,000
Feature development, 3 years	€3,000–€12,000	€6,000–€20,000
Three-year total (estimate)	€18,800–€58,500	€51,000–€130,500

The gap is real, so custom has to earn it. It does when it removes a full-time job's worth of manual data entry, sells products a competitor cannot price online, or keeps a B2B channel that would otherwise run on email and spreadsheets. For a fuller view of build costs, see ecommerce website cost.

Where Raao's packages fit

Our Starter (from €1,900) and Launch (from €3,900) packages are custom-designed stores for up to 500 and 2,000 products. Enterprise is a custom quote for a fully custom build (PHP, React, Node.js) or advanced WooCommerce, with two-way ERP sync, marketplace sync, B2B, configurators and an SLA. Hosting and maintenance start from €89 a month, with no licence fees or revenue share. Prices are in EUR, excluding VAT; see pricing and ecommerce.

We recommend WooCommerce or custom after the discovery call, not before. If you want us to look at your current store and data flows, book a free 30-minute call.

How we did it for Kuiba

Kuiba is a store where custom was the right call, and the reasons map directly to the matrix above:

• Configurable products. Premium furniture comes in hundreds of finishes and sizes. Off-the-shelf platforms could not price these products correctly, so we built a configurator with price matrices, finishes, dimensions and accessories.
• Constantly changing supplier data. Automated imports for brands such as Bonaldo, Calligaris, Nardi and Miele, with AI-assisted category mapping, keep 10,000+ products from 25+ European brands current without manual entry.
• ERP as the source of truth. Every order is pushed automatically to Microsoft Business Central through the client's CRM layer.
• More than one sales channel. The same platform runs online sales, showroom visit bookings, quote requests with branded PDF brochures, sales-agent tools and a designer partner programme.
• Search and tracking built in. Instant faceted search with synonyms and an AI fallback, server-side GA4 and the Meta Conversions API, and feeds for Google Merchant, Meta, TikTok and Pinterest.

A store selling a few hundred standard products would not need any of this, and should not pay for it.