In the custom ecommerce vs Shopify vs WooCommerce choice, Shopify suits most standard stores that want to launch fast with little maintenance, WooCommerce suits teams that already live in WordPress and want ownership with moderate flexibility, and custom suits unusual business rules or deep integrations. Decide on your requirements first, not on the platform's popularity.
Platform features and fees change often, so verify current details on each vendor's own pages. This article deliberately contains no price figures; it explains how costs are structured so you can compare real quotes.
Custom ecommerce vs Shopify vs WooCommerce: the decision criteria
Before comparing platforms, write down what the store has to do. These criteria decide most cases:
- Catalogue and pricing complexity: simple products, many variants, made-to-order items, customer-specific prices, subscriptions, bundles.
- Integrations: accounting, ERP, warehouse, shipping, marketplaces, CRM.
- Team skills: who will administer the store day to day, and who can fix technical problems.
- Time to launch: a campaign date can outweigh perfect flexibility.
- Markets and tax: multiple currencies, languages and tax rules.
- Data ownership and portability: how easy it is to export customers, orders and content.
- Expected change: a store that will be reshaped constantly needs different foundations from a stable one.
Score each option from low to high against these. A simple weighted sheet reveals which trade-offs you are really making.
Shopify: strengths and limits
Shopify is a hosted platform: the vendor runs servers, security patches, checkout and uptime. You configure a store, choose a theme and extend it with apps.
Strengths: quick launch, a mature checkout, built-in payments and shipping integrations, less technical upkeep, and a large app and theme ecosystem. For a typical retailer with standard products, it removes a lot of operational work.
Limits: you work within the platform's data model and checkout rules. Heavy customisation of checkout or unusual business logic may require workarounds, higher-tier plans or custom apps. Costs are recurring and layered, and can grow as apps accumulate. Your storefront code runs in a hosted environment you do not control, and some features depend on the vendor's roadmap.
WooCommerce: strengths and limits
WooCommerce is an open-source plugin that turns a WordPress site into a store. You host it yourself or with a specialist host.
Strengths: ownership of code and data, strong content and SEO tooling through WordPress, a very large plugin ecosystem, and flexibility to customise with developers. It fits well when the store is part of a content-led site.
Limits: you are responsible for hosting, updates, security and performance. Plugin quality varies and conflicts happen. A store with many plugins needs regular maintenance, and scaling to heavy traffic or large catalogues takes deliberate tuning. Our WooCommerce performance guide and WordPress hardening checklist describe that ongoing work.
Custom: strengths and limits
A custom store is built to your requirements on a framework such as Laravel or ASP.NET Core, often using payment providers and shipping services through APIs.
Strengths: the checkout, pricing rules, workflows and integrations match your business exactly. You avoid paying for platform features you do not use, and you can design the data model around your operations, for example product configuration, B2B pricing or inventory that must synchronise with a warehouse system.
Limits: higher upfront effort, and you own everything: security, compliance work around payments, tax logic, accessibility, search, admin tooling and maintenance. Features that are free checkboxes on a platform, such as discount engines, abandoned-cart emails or returns, must be built or bought. A custom build without documentation can also create dependence on one developer, so insist on clean handover.
Fees and total cost
Compare structures, not headline numbers. Ask each option to be costed over a multi-year view:
| Cost area | Shopify | WooCommerce | Custom |
|---|---|---|---|
| Software | Subscription, by plan | Core is free; paid extensions common | Framework free; build effort |
| Hosting | Included | You pay a host | You pay infrastructure |
| Payments | Processor fees; possible extra fees if using an outside gateway | Processor fees | Processor fees |
| Extensions | Monthly app fees add up | Annual licences | Built as features |
| Maintenance | Low, vendor-run | Ongoing updates and security | Ongoing development and DevOps |
| Customisation | Theme and app work | Plugin and developer work | Core of the project |
Do not forget internal time: product data entry, content, support and the people who manage the system. For payment-related choices see adding Stripe or PayPal to a web application.
Migration and lock-in
Every route has lock-in, just of different kinds. On a hosted platform, your theme, apps and some data structures are tied to that vendor, though customers, products and orders can usually be exported. On WooCommerce, data is yours in a standard database, but plugin-specific data may be awkward to move. On custom software, the risk is dependence on the people who built it.
Migration between platforms is possible and common, but it is a project: products and variants, customers, order history, redirects for URLs, reviews, discount codes and integrations all need mapping, and passwords generally cannot be transferred in readable form, so plan customer communication. To reduce lock-in on any platform, keep regular exports, own your domain and accounts, document integrations and keep URLs stable.
Recommendation by situation
- Small catalogue, quick launch, limited technical staff: Shopify is usually the lowest-friction choice.
- Content-heavy brand, existing WordPress site, willing to maintain: WooCommerce.
- B2B pricing, configurators, unusual fulfilment, deep ERP or inventory integration: evaluate custom, or a platform plus a custom integration layer.
- Uncertain demand: start on a platform, validate sales, and revisit custom when real constraints appear. A phased approach often costs less than building too early.
- Existing platform working but slow or limiting: diagnose first; the fix may be tuning rather than replacement.
Custom beats both when the platform's rules actively fight your operations: when workarounds pile up, when several paid apps exist only to emulate one workflow, or when integration needs make the store a front end for your own systems.
Putting it together
Write the requirement list, score the three options, cost them over several years and test your hardest workflow in each. If you want a second opinion, see WooCommerce or a custom store for retailers or where to begin with eCommerce development, and our US software development page explains how a remote build is handled.
Frequently asked questions
What are Shopify's ongoing costs?
Typically a plan subscription, payment processing fees, fees for paid apps and themes, and possibly extra charges if you use an outside payment gateway. Fees and tiers change, so check Shopify's current pricing pages and add up the apps you actually need. Also count internal time spent managing the store.
When does custom beat both?
Custom wins when your business rules do not fit a platform: customer-specific pricing, configurable products, complex fulfilment, or deep ERP and inventory integration. It also makes sense when workarounds and stacked paid apps cost more than building the workflow properly. Expect higher upfront effort and ongoing maintenance responsibility.
Can I migrate between them?
Yes. Products, customers and order history can usually be exported and imported, but you must map variants, redirect old URLs, move reviews and discounts, and rebuild integrations. Customer passwords generally cannot be transferred readably, so plan communication. Treat migration as a project with testing, not a button.