Shop systems explained: SaaS, open source, headless and enterprise platforms

TL;DR - Decision matrix

Want the short version? Start with the comparison table or use the interactive shop-system finder. Enter a few details and it will point you towards the options that best match your needs.

Shop system finder with instant results

The table is a starting point, not a substitute for a detailed evaluation. The sections below explain the trade-offs in more depth.

What is a shop system?

A shop system is software for selling products or services online. That definition matters because not every e-commerce tool is a shop system.

At its core, a shop system comprises:

• Product management (catalogue, variants, prices)
• Shopping basket function and checkout process
• Payment processing (via connected payment providers)
• Order management
• Customer management

Which is not a shop system:

Stripe and PayPal are payment providers, not shop systems. Amazon and Etsy are marketplaces where you sell within someone else’s ecosystem. WordPress only becomes a shop system when you add an extension such as WooCommerce.

The boundaries are increasingly blurred. Modern platforms often combine commerce, content management, marketplace features and API-first architecture. A clear classification makes the landscape easier to understand.

What types of shop systems are there?

The shop-system market is fragmented, with hundreds of products worldwide. The biggest differences lie not only in features, but in architecture and operating model.

Instead of an alphabetical list, a classification by system type helps. Each type has its own strengths, limitations and target groups.

These categories overlap. Shopware began as an open-source monolith and now also offers SaaS hosting and headless options. WooCommerce is open source but sits inside the WordPress ecosystem. The categories describe each product’s main architectural approach, not a rigid label.

SaaS Commerce

Software-as-a-service shop systems are fully hosted platforms. The provider handles infrastructure, security and updates; you pay a recurring fee and can launch quickly.

SaaS dominates the entry-level e-commerce market for a simple reason: you do not need your own servers, deployment pipeline or technical team. Create an account, add products and start selling.

The trade-off is control. You depend on the provider for source code, hosting, parts of the design and platform decisions. If prices rise or a feature disappears, your options may be limited.

Typical SaaS shop systems:

• Shopify - Global market leader in SaaS commerce. Huge app ecosystem, strong internationalisation. For SMEs to mid-market.
• BigCommerce - Positions itself as an alternative to Shopify, more focussed on B2B and mid-market. Offers a headless option.
• Squarespace - Primarily a website construction kit with integrated shop function. Strong in design, limited in complex e-commerce requirements.
• Wix eCommerce - Similar to Squarespace: Website-first, shop function as an add-on.
• Ecwid (Lightspeed) - Embed solution that integrates shops into existing websites.
• Jimdo - German provider, highly simplified, for micro-enterprises.
• ePages - European SaaS provider, often used as a white label solution by hosters and telcos.
• Volusion - US provider, rather niche position.

Strengths: This article provides general information and is not legal advice. If you have a specific question, consult a lawyer specialising in German media or copyright law. Do not rely on this article alone when making a legal decision.

Weaknesses: Limited customisation, vendor lock-in, ongoing costs even with low turnover, dependence on app ecosystems for extended functions.

When SaaS Commerce makes sense: Choose SaaS when you want to launch quickly, have no development team and can work within the platform’s standard model. Heavy customisation or strict control over infrastructure and data can expose its limits.

Open Source Commerce

Open-source shop systems give you access to the source code. You host the software yourself or through a service provider and can adapt it to your requirements.

Open source does not mean cost-free. Hosting, development, maintenance, security updates and customisation still require time and money. In return, you gain control and are less dependent on a SaaS provider’s pricing and product decisions.

The open source segment is enormously diverse. It ranges from WordPress extensions to complex enterprise platforms.

Typical open source shop systems:

• WooCommerce - The most widely used open source shop system in the world. Runs as a WordPress plugin and benefits from the huge WordPress ecosystem. Easy to get started with, but scaling becomes challenging with large catalogues and high traffic.
• Magento Open Source (Adobe Commerce Community) - Long the standard for medium-sized to large shops. Powerful, but resource-intensive. Since the takeover by Adobe, the focus has increasingly shifted to the commercial cloud version.
• PrestaShop - Widely used in France and Southern Europe. Solid basis for medium-sized shops, active community.
• OpenCart - Lightweight, easy to install. For smaller shops with limited requirements.
• Shopware (Community Edition) - German provider with a growing international presence. Strong base in the DACH market, modern architecture since version 6.
• Sylius - PHP-based (Symfony), modular structure, aimed at development teams with individual requirements.
• Bagisto - Laravel-based, relatively young, growing community.
• Gambio - German provider, specially tailored to the German market (legal security, German payment providers).
• JTL-Shop - Closely integrated with JTL merchandise management, strong position in German multichannel retail.

Strengths: Full code control, no ongoing licence costs, adaptability without limits, independence from the provider, data sovereignty.

Weaknesses: Requires technical expertise or a team of developers, responsibility for security and updates lies with you, higher initial outlay.

When open source makes sense: Choose open source when you have specific requirements, want control over infrastructure and data, or already have a development team that can maintain the shop.

CMS Commerce

CMS commerce refers to shops built on or added to a content management system. Content is the foundation; commerce is the extension.

This works particularly well for content-led businesses—for example, a blog with a shop, a magazine with affiliate products or a portfolio that also sells services or products.

The boundary with open-source commerce is blurred. WooCommerce belongs to both categories. The architectural distinction is that, in CMS commerce, the shop extends the CMS rather than forming the core platform.

Typical CMS commerce solutions:

• WooCommerce (WordPress) - By far the largest CMS commerce solution. WordPress provides the CMS, WooCommerce the shop. The combination covers an enormous part of the market, especially in the SME segment.
• Drupal Commerce - For Drupal users who want to integrate Commerce. Modular, flexible, but with a steep learning curve.
• Craft Commerce - Based on Craft CMS. Niche product for design and content-focussed projects.
• Saleor - Originally Django-based, now positioned as a headless commerce platform. The CMS origin is still recognisable.

Strengths: Content and commerce in one system, low entry costs (especially with WordPress), huge plugin and theme ecosystem, familiar administration interface for content teams, fast implementation with existing CMS installation.

Weaknesses: Shop functionality is an extension, not the core - as complexity grows, you reach the limits of the architecture. Performance optimisation for large catalogues requires effort. Security and updates are your responsibility (especially with WordPress due to plugin dependency). Fewer specialised e-commerce features than with dedicated shop systems.

When CMS Commerce makes sense: Choose this route when you already use a CMS and commerce is an addition rather than the whole business, or when content and commerce are equally important.

Headless Commerce

Headless commerce separates the customer-facing frontend from the backend that manages products, orders and payments. APIs connect the two, allowing the same backend to serve a website, app, voice assistant or other interface.

Headless is not new, but it has become more relevant as businesses seek greater freedom over the frontend and want one commerce backend to support several channels.

How headless commerce works:

A traditional monolith combines backend logic and frontend presentation. In a headless setup, the backend provides data through REST or GraphQL APIs while a separate frontend—such as a React, Vue or Next.js application—handles the customer experience.

Typical headless commerce platforms:

• commercetools - One of the pioneers in the headless/composable commerce sector. API-first, cloud-native, strong in the enterprise segment. Originally from Germany.
• Elastic Path - API-first platform for complex commerce scenarios. Positioned in the enterprise mid-market.
• Medusa - Open source headless commerce framework. JavaScript/Node.js-based, growing community, flexible to use.
• Saleor - Open source, GraphQL API, Python/Django-based. Strong with development teams who want full control.
• Shopware Frontends - Shopware has offered a headless option via its own API endpoints and a Vue.js-based frontend framework since version 6.
• BigCommerce (Headless) - BigCommerce is also increasingly positioning itself as a headless backend that can be combined with any front end.

Strengths: Maximum frontend flexibility, multi-channel capability from one backend, independent scaling of frontend and backend, free choice of technology in the frontend.

Weaknesses: Higher complexity, requires a front-end development team, longer time-to-market, higher initial costs, no visual page builder out of the box.

When headless commerce makes sense: Headless can make sense when you serve several channels, your frontend team needs full technology freedom or standard templates hold you back. For a conventional single-channel shop, it is often unnecessary complexity.

Enterprise Commerce

Enterprise commerce platforms serve large organisations with complex requirements such as multiple markets and brands, deep ERP integrations, high transaction volumes and custom business logic.

There is no fixed line between mid-market and enterprise. A useful signal is the need for a dedicated integration partner and licence or implementation costs in the six- or seven-figure range.

Typical enterprise commerce platforms:

• SAP Commerce Cloud (formerly Hybris) - Deeply integrated into the SAP ecosystem. Often the obvious choice for companies already using SAP ERP. Extremely powerful, but complex and cost-intensive.
• Salesforce Commerce Cloud (formerly Demandware) - Strong in the B2C and D2C sector. Deep integration into the Salesforce CRM ecosystem.
• Adobe Commerce (Magento Enterprise) - The commercial version of Magento. Cloud-hosted, with extended features for B2B and personalisation.
• Oracle CX Commerce - Part of the Oracle Cloud. For companies in the Oracle ecosystem.
• HCL Commerce (formerly IBM WebSphere Commerce) - Traditional platform, strong in regulated industries.
• Intershop - German enterprise provider, particularly established in B2B commerce.
• Spryker - Berlin-based company, Composable Commerce Approach, is aimed at enterprise customers with complex business models.

Strengths: Scalability at group level, deep integration capability (ERP, CRM, PIM), multi-market and multi-brand capability, professional support and SLAs.

Weaknesses: High licence and implementation costs, long project durations (often 12-24 months), dependence on system integrators, complexity in operation and further development.

When Enterprise Commerce makes sense: Enterprise platforms become relevant when international rollouts, complex B2B pricing, deep ERP integration or multi-market regulation exceed what mid-market products can handle.

Marketplace systems

Marketplace systems support multi-vendor businesses in which independent sellers offer products through one central platform. The operator provides the infrastructure; the sellers provide the range.

A marketplace differs from a standard shop because it must handle seller onboarding, commissions, split order processing and quality control.

Typical marketplace platforms:

• Mirakl - Enterprise marketplace solution. Used by large retailers who want to set up their own marketplace (e.g. MediaMarkt, Decathlon).
• Sharetribe - SaaS solution for the rapid launch of a marketplace. Particularly suitable for service and peer-to-peer marketplaces.
• CS-Cart Multi-Vendor - Established solution for multi-vendor shops, self-hosted.
• Arcadier - SaaS marketplace construction kit with various templates (products, services, rental).
• Spryker - Provides marketplace functionality as part of its composable commerce platform.

There are also numerous extensions that add marketplace functionality to existing shop systems. Plugins such as Dokan or WCFM Marketplace exist for WooCommerce, while Webkul extensions are available for Magento.

When a marketplace system makes sense: Choose a marketplace platform when third-party sellers are central to your business model. Avoiding your own inventory is attractive, but operational, legal and seller-management complexity is easy to underestimate.

Developer Frameworks & Starter Kits

Developer frameworks are building blocks rather than ready-made shop systems. They provide APIs, modules and data models for a team to build on, but usually no complete storefront or instantly usable admin experience.

This category is growing alongside headless commerce and demand for bespoke platforms. It is intended for development teams and agencies, not non-technical operators.

Typical developer frameworks:

• Medusa - Open source, JavaScript/TypeScript, modular structure. Positions itself as an open source alternative to Shopify for developers.
• Vendure - TypeScript-based, GraphQL API, focus on extensibility and developer experience.
• Saleor - Python/Django, GraphQL-first. Can be used both as a headless platform and as a framework.
• Reaction Commerce (Mailchimp Open Commerce) - Node.js-based, was taken over by Mailchimp and continued as Open Commerce. Development recently less active.

Differentiation from headless commerce: The distinction is practical: a headless platform such as commercetools is a finished product with an admin interface and APIs. A framework such as Medusa provides the foundation on which your team builds its own platform.

When developer frameworks make sense: Choose a framework when your team has the capacity to build and maintain a commerce platform, and standard products cannot support the business model. The extra development and maintenance commitment is long term.

Ecosystem Map: The shop system landscape at a glance

The categories above describe individual product types. The next overview maps them along two axes: implementation complexity and degree of control.

Lower left area: Low complexity, low control. SaaS solutions such as Shopify or Jimdo. Quick start, little room for manoeuvre.

Left centre: Moderate complexity, increasing control. CMS Commerce and simpler open source systems. You need basic knowledge, but gain design freedom.

Upper left area: High control, moderate complexity. Open source systems and developer frameworks. Full code sovereignty, but you bear the responsibility.

Right side: Increasing complexity through integration, multi-channel or multi-vendor. Headless, enterprise and marketplace systems solve complex requirements, but require corresponding resources.

Many businesses begin with a simple, low-control setup and move towards greater control as requirements grow. This is not inevitable—successful shops can remain on Shopify or WooCommerce for years—but complexity often increases with scale.

Architecture comparison: Monolith vs. headless vs. composable

There are different architecture models behind the various shop system types. Understanding these is crucial for a well-founded system decision.

Monolithic architecture

A monolith provides the front end and back end as a coherent unit. Everything is integrated - product management, checkout, display, search function.

Most classic shop systems have a monolithic structure: Shopify, WooCommerce, Magento (in the standard configuration), PrestaShop, Gambio, JTL-Shop. The advantage: everything works together, out of the box. The disadvantage: changes to the front end potentially affect the back end and vice versa.

Headless architecture

With headless, the frontend is completely separated from the backend. The backend provides data and logic via APIs, while the frontend is developed independently.

The benefit: You can choose the frontend freely and develop it independently of the backend. The effort: You need a frontend team, and the overall complexity increases because two systems have to be coordinated.

Composable Commerce

Composable commerce goes one step further than headless. Here, not only is the front end decoupled, but each commerce function is operated as an independent service - search, checkout, PIM, CMS, payment - and plugged together via APIs.

The composable model promises maximum flexibility: best-of-breed for every function, interchangeable components, independent scaling. The downside: orchestrating dozens of services is demanding, the overall costs can be considerable and the system landscape becomes complex.

Comparison

Architecture is a business decision as much as a technical one. It affects the team you need, how quickly you can respond to change and the total cost over several years.

Decision framework: Finding the right shop system

Choosing a shop system is not a feature checklist. The right fit depends on your business model, available resources and growth plans.

The six decisive criteria

1. budget (initial + ongoing)

SaaS systems have low entry costs, but ongoing fees that increase with turnover. Open source systems cost more to develop, but the running costs are easier to control. Enterprise solutions require significant investment in licences and implementation.

2. technical team

Do you have developers in your team? If not, this limits the choice to SaaS and simple CMS commerce solutions. If yes, open source, headless and developer frameworks open up as options.

3. time-to-market

Consider how quickly you need to launch. A simple Shopify shop may take a week, WooCommerce around a month, headless several months and an enterprise implementation a year or more. These are rough ranges, but they show the difference in scale.

4. scaling perspective

Think three years ahead. If the catalogue could grow from 100 to 50,000 products, architecture matters now. Migrating a live shop later is possible, but expensive and risky.

5. integration requirements

Which systems need to be connected - ERP, CRM, PIM, marketing automation, payment providers? The more integrations are required, the more important open APIs and an established partner ecosystem become.

6 Vendor lock-in vs. flexibility

How important is independence from the provider to you? SaaS platforms bind you more than open source solutions. Composable approaches minimise lock-in, but increase complexity.

This table is simplified. But it shows the direction of thought.

Market overview: Fragmentation and regional differences

The global shop-system market is highly fragmented. No single platform dominates every segment, even if Shopify’s public profile sometimes suggests otherwise.

Global perspective

Shopify is the largest SaaS commerce platform by active-shop count, while WooCommerce has the most installations overall, including many small or inactive sites. Magento, now Adobe Commerce, remains established in the mid-market but has lost ground.

Market-share estimates vary because services such as BuiltWith and W3Techs measure different things—installations, active use or traffic-weighted reach. Treat absolute figures as indicators rather than exact totals.

DACH market

The German-speaking market has its own ecosystem, which differs from the global distribution:

• Shopware has a strong position in the German SME sector and is growing internationally.
• JTL-Shop is deeply rooted in German multichannel retailing, particularly through its integration with JTL merchandise management.
• Gambio serves small to medium-sized German merchants with a focus on legal security and local payment providers.
• OXID eSales has an established base in B2B commerce in the DACH region.
• Shopify is also gaining share in the DACH market, particularly with D2C brands and start-ups.

The DACH market has specific legal requirements, including the GDPR, packaging rules, cancellation information and price-display rules. Local platforms may support these needs out of the box, while international products often require extra extensions. Legal compliance still depends on the complete setup.

European market

There are also regional focuses within Europe:

• PrestaShop dominates in France, Spain and parts of southern Europe.
• Shopware is growing beyond the DACH region into the Benelux market and Eastern Europe.
• WooCommerce is everywhere, especially in smaller shops.
• Magento/Adobe Commerce holds positions in the mid-market and enterprise segment.

Trends in e-commerce (as at the beginning of 2025)

The shop system market is changing. Some trends are clearly emerging, others are still at an early stage.

AI-supported commerce

AI is entering e-commerce through recommendations, search, pricing, product copy and customer-service chatbots. Most major platforms now offer AI features, but the long-term impact is still difficult to judge and the market remains hype-driven.

Composable commerce as an architectural trend

Composable commerce is attracting attention, especially among enterprises. For most shops, however, a monolith or straightforward headless setup remains more practical. Composable architecture solves real problems at scale, but adds needless complexity to a small catalogue.

Unified Commerce

The lines between online shops, physical retail, social commerce and marketplaces are fading. Unified commerce aims to manage every channel through shared product, inventory and customer data.

Social Commerce

Sales via social media platforms (TikTok Shop, Instagram Shopping, Pinterest) are growing, especially in Asia. The trend is recognisable in Europe, but is not yet dominating the market. Shop systems are responding with native integrations.

Regulation and data protection

Privacy regulation continues to evolve beyond the GDPR. New EU and national rules affect how shops collect, store and use data across tracking, personalisation and analytics.

Tracking and analysis across shop systems

Whichever platform you choose, unreliable tracking leaves you making decisions in the dark. It sounds obvious, yet analytics is still frequently treated as an afterthought.

The challenge

Every shop platform handles tracking differently. Combining platforms or sales channels makes the data harder to reconcile, while European privacy rules add another layer of implementation decisions.

Many major analytics products originate in the United States, so European businesses must assess transfers, consent and configuration carefully. Browser restrictions and consent requirements also make cookie-based tracking less complete.

What matters

Useful e-commerce analytics needs three things: tracking that is not tied to one shop platform, data collection that meets the applicable privacy requirements and reports that support decisions rather than merely displaying raw data.

Cookieless tools such as Trackboxx can reduce reliance on consent-dependent data and still provide useful analytics. They are one option, not a universal answer. The important point is to design tracking from the start.

FAQ - Shop systems