If you’re e-commerce business is growing, you may be thinking about replatforming. Where to start? Which platform is best and should you go for a bestpoke solution. Here are the pros and cons, using 200,000 products as a baseline.
The article is largely AI written but does contain salient information.
For a complex e-commerce operation with 200,000+ SKUs, the decision is less about “which platform is best” and more about where you want complexity to live:
- inside the platform,
- inside your integrations,
- or inside your own engineering team.
At that scale, the key constraints become:
- catalogue performance
- search/indexing
- ERP integration
- inventory synchronisation
- pricing rules
- multi-store/multi-region support
- operational workflows
- scalability under load
- long-term maintainability
Below is a practical comparison.
1. Bespoke / Custom-Built Commerce Platform
This can mean building your own commerce software, though at Datadial we have our a base e-commerce system, so you don’t need to worry about starting from scratch. The DD Ecomm is highly specified, flexible and extensible.
Pros
Complete flexibility
You own the data model, workflows, checkout logic, integrations and UI.
This matters when you have:
- unusual product structures
- advanced configurators
- marketplace logic
- highly customised B2B pricing
- multiple warehouses
- unusual fulfilment flows
- subscription + wholesale + retail combined
Off-the-shelf platforms eventually force compromises.
Better architecture for huge catalogues
200k+ products is no longer “normal ecommerce”.
A bespoke platform can be designed around:
- microservices
- event-driven architecture
- distributed indexing
- queue systems
- dedicated search infrastructure
- CDN-heavy delivery
- highly optimised product storage
You avoid the “plugin ecosystem bottleneck”.
No platform constraints
You are not constrained by:
- Shopify API limits
- WooCommerce WordPress overhead
- Magento architectural legacy
- SaaS checkout restrictions
You control:
- deployments
- infrastructure
- performance tuning
- caching strategy
- indexing strategy
Lower long-term licensing costs
At enterprise scale:
- Shopify Plus fees
- Adobe Commerce licensing
- transaction fees
- app ecosystem costs
can become substantial.
A bespoke platform may eventually become cheaper if:
- revenue is very large
- engineering team already exists
- complexity is high enough
Easier deep ERP integration
Large commerce businesses are often really:
- ERP-led businesses
with a storefront attached.
Custom platforms can integrate deeply with:
- SAP
- Microsoft Dynamics 365
- Oracle NetSuite
- warehouse systems
- PIMs
- procurement systems
- pricing engines
without fighting platform limitations.
Cons
Extremely expensive
True enterprise bespoke commerce builds commonly cost:
- £150k–£2m+
- sometimes far more
Especially if:
- search
- OMS
- PIM
- promotions
- customer accounts
- reporting
must all be custom.
Longer time to market
You are rebuilding:
- admin tooling
- order management
- promotions
- customer service tools
- CMS capability
- analytics hooks
- integrations
Platforms like Shopify already solved these.
You own everything forever
This is the biggest hidden issue.
You now maintain:
- security
- PCI compliance
- infrastructure
- bugs
- upgrades
- technical debt
- scaling
- developer onboarding
There is no vendor absorbing complexity for you.
Key-person risk
Many bespoke systems become dependent on:
- one agency
- one architect
- one internal engineering lead
That can become dangerous commercially.
2. Shopify / Shopify Plus
Shopify
Pros
Fastest operational path
Shopify removes:
- hosting
- infrastructure
- scaling concerns
- security patching
- PCI headaches
Teams can focus on:
- merchandising
- marketing
- conversion optimisation
Excellent operational stability
For standard commerce:
- uptime
- scaling
- CDN delivery
- checkout reliability
are world-class.
Lower operational burden
Smaller engineering teams can run large businesses.
That is why many brands choose Shopify Plus even when they could go bespoke.
Good ecosystem
Apps and integrations exist for almost everything.
Cons
500k+ products is pushing Shopify hard
It can be done, but:
- catalogue management becomes difficult
- complex filtering/search needs external systems
- indexing becomes complicated
- API rate limits become painful
- bulk operations become engineering-heavy
Very large catalogues typically require:
- headless architecture
- external PIM
- external search
- middleware layers
At that point Shopify becomes “checkout infrastructure”.
Limited backend flexibility
Shopify is excellent until:
- your business process differs from Shopify’s assumptions.
Then you start building workarounds.
App dependency
Large Shopify stores often become:
- dozens of paid apps
- middleware layers
- custom connectors
This creates hidden operational fragility.
Vendor lock-in
You do not truly control the platform.
3. Magento / Adobe Commerce
Adobe
Magento (Adobe Commerce) sits between:
- bespoke
and - SaaS simplicity.
It is often the “enterprise flexibility” choice.
Pros
Designed for complex commerce
Magento is very strong at:
- huge catalogues
- multi-store
- B2B
- pricing rules
- internationalisation
- complex attributes
- advanced promotions
It was built for complexity.
Better suited to 500k+ SKUs than WooCommerce or standard Shopify
With proper infrastructure:
- Magento can support massive catalogues
- sophisticated indexing
- complex search layers
Strong API/headless capability
Magento increasingly works best as:
- headless commerce backend
with a custom frontend.
Large ecosystem
Lots of:
- extensions
- developers
- agencies
- enterprise integrations
Cons
Operationally heavy
Magento is notorious for:
- complexity
- maintenance overhead
- upgrade pain
- performance tuning requirements
You generally need:
- dedicated developers
- DevOps
- infrastructure expertise
High total cost of ownership
Licensing, hosting and engineering costs become substantial.
Technical debt risk
Poor Magento implementations become:
- slow
- fragile
- difficult to upgrade
This is extremely common.
4. WooCommerce
WooCommerce
Pros
Excellent for content-led commerce
Strong if:
- SEO/content marketing is central
- WordPress already exists
- catalogue complexity is moderate
Cheap to start
Very low initial barriers.
Flexible ecosystem
Huge WordPress plugin ecosystem.
Cons
200k products is generally beyond WooCommerce’s comfort zone
Possible? Yes.
Advisable? Usually no.
WordPress/WooCommerce was not architected primarily for:
- enterprise catalogue management
- large-scale indexing
- extremely high concurrency
You will spend significant time:
- tuning databases
- fixing plugin conflicts
- managing cache layers
- optimising search
Plugin fragility
Large WooCommerce estates often become operationally messy.
Security and maintenance burden
You inherit:
- WordPress patching
- plugin updates
- hosting optimisation
