Shop systems at a glance: SaaS, open source, headless & enterprise platforms explained in an understandable way

TL;DR - Decision matrix

Before you work your way through thousands of words, I have worked out 2 options here - for the lazy readers among you 🙂 One is a clean and clear table with all the information and the 2nd option is an interactive „shop system finder“ - you enter your information and get a corresponding result, have fun.

Shop system finder with direct results

This table is no substitute for a detailed analysis. But it shows the direction in which you should think. The details follow below.

What is a shop system?

A shop system is software that enables the online sale of products or services. That sounds banal, but the distinction is important - because not everything that has anything to do with e-commerce 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:

A payment provider such as Stripe or PayPal is not a shop system - it processes payments. A marketplace such as Amazon or Etsy is also not a shop system, but a platform on which you sell your products within a third-party ecosystem. And a CMS such as WordPress is only a shop system through extensions (e.g. WooCommerce).

However, the boundaries are becoming increasingly blurred. Many modern platforms combine shop functionality with content management, marketplace features or API-first architectures. This is precisely why you need a clean taxonomy to understand the landscape.

Taxonomy: What types of shop systems are there?

The shop system market is fragmented. Hundreds of solutions exist worldwide, and the differences lie not only in the range of functions, but above all in the 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 are not rigid boxes. Shopware, for example, started out as an open source monolith and now offers SaaS hosting and headless options. WooCommerce is open source, but lives in the WordPress CMS ecosystem. The classification describes the primary architectural approach - not an exclusive affiliation.

SaaS Commerce

Software-as-a-Service shop systems are hosted complete solutions. The provider takes care of hosting, security, updates and infrastructure. You pay a monthly fee and can get started straight away.

The SaaS model dominates the entry-level market in e-commerce. The reason is simple: you don't need a technical team, your own server or a deployment pipeline. Register, add products and get started.

The trade-off is just as clear: you give up control. This applies to the source code, the hosting environment, partly the design and, above all, the dependency on the provider (vendor lock-in). If Shopify changes its prices or removes a function, you have little room for negotiation.

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 is for general information purposes only and does not replace legal advice. If you have specific legal questions, please consult a solicitor specialising in media or copyright law. We accept no liability for decisions made on the basis of this article.

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

When SaaS Commerce makes sense: If you want to get started quickly, don't have a development team and your business model fits into the standard framework of the platform. As soon as you need to customise heavily or want to retain control over infrastructure and data, you will reach your limits.

Open Source Commerce

Open source shop systems make the source code freely available. You host the software yourself (or via a service provider), have full access to the code and can customise the system as you wish.

Open source does not mean free. The software itself costs nothing, but hosting, development, maintenance, security updates and customisation cost time and money. The advantage: you have full control. No vendor lock-in in the traditional sense, no dependence on the pricing decisions of a SaaS provider.

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: If you have individual requirements, want to retain control over your infrastructure and data or already have a development team that can manage the shop.

CMS Commerce

CMS Commerce describes shop systems that have evolved from a content management system or are based on it as an extension. The origin is content, not commerce.

The approach has a clear advantage: If your business model is strongly content-driven - such as a blog with an integrated shop, a magazine with affiliate products or a portfolio with additional sales - then you don't need a separate system.

The boundary to open source commerce is blurred. WooCommerce is both open source and CMS Commerce. The difference lies in the architectural approach: with CMS Commerce, the shop is the extension, not the core.

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: If you already use a CMS and the shop is a supplement, not the business purpose. Or if content and commerce should be on an equal footing.

Headless Commerce

Headless commerce separates the front end (what your customers see) from the back end (product data, order logic, payment processing). Communication takes place via APIs. The front end can be a website, but also an app, a voice assistant or an IoT device.

The headless model is not a new invention, but its relevance has increased significantly in recent years. The driver: companies want to customise their frontends without being tied to the template logic of a monolithic shop system. And they want to use the same commerce backend for multiple channels.

How headless commerce works:

The classic monolith delivers everything from a single source - backend logic and frontend display are tightly coupled. With headless, the backend exists as an independent service that provides data via REST or GraphQL APIs. The frontend is developed separately, typically as a single-page application (React, Vue, Next.js) or as a native app.

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: If you need to serve multiple touchpoints (web, app, POS, social), if your front-end team wants to use its own technologies or if the standard templates of monolithic systems limit you. For a single standard shop with manageable traffic, headless is overkill in most cases.

Enterprise Commerce

Enterprise commerce platforms are designed for large companies with complex requirements - international markets, multiple brands, deep ERP integration, high transaction volumes and customised business logic.

The boundary between mid-market and enterprise is not clearly defined. As a rule of thumb: if you need an integration partner team to set up the system and the licence costs are in the six- to seven-figure range, you are in the enterprise segment.

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: When your business has reached a level of complexity that can no longer be mapped with mid-market solutions. International rollouts, complex B2B pricing logic, deep ERP integration or regulatory requirements in multiple markets are typical triggers.

Marketplace systems

Marketplace systems enable multi-vendor business models - i.e. platforms on which several independent sellers offer their products via a central platform. The operator provides the infrastructure, the retailers supply the product range.

A marketplace is architecturally different from a standard shop. The core challenges lie in vendor management, the commission model, separate order processing for each retailer and quality control.

Typical marketplace platforms:

• Miracle - 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.
• Arcadian - 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: If your business model is based on third parties selling on your platform. The model is attractive because you don't need your own inventory - but the complexity of operation, legal situation and vendor management is often underestimated.

Developer Frameworks & Starter Kits

Developer frameworks are not ready-made shop systems. They provide the building blocks - APIs, modules, data models - that development teams use to build a customised shop. There is no admin panel that works straight away and no theme that you simply activate.

This area is growing, driven by the headless trend and the increasing demand for individualised commerce solutions. The target group is exclusively developer teams or agencies.

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 boundaries are fluid. The difference: A headless commerce system such as commercetools is a ready-made platform with an admin interface that is accessed via APIs. A developer framework such as Medusa provides the basic structure on which you can build your own platform.

When developer frameworks make sense: If your team has the capacity and the will to design a commerce solution from scratch. If standard solutions cannot reflect your business model. And if you are prepared to bear the additional development and maintenance costs in the long term.

Ecosystem Map: The shop system landscape at a glance

The previous sections describe individual categories. But how is it all connected? The following categorisation shows the shop system landscape along two axes: complexity of the setup 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.

Most companies start at the bottom left and move up to the top right as their business grows. This is not a law of nature - many successful shops have been running on Shopify or WooCommerce for years. But as requirements increase, demand typically shifts as well.

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

The choice of architecture is not a purely technical decision. It determines what kind of team you need, how quickly you can react to market changes and what your total costs will look like over the next few years.

Decision framework: Finding the right shop system

Choosing a shop system is not a feature comparison list. It's about the fit between your business model, your resources and your 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

How fast do you need to be live? Shopify in a week, WooCommerce in a month, a headless setup in three to six months, an enterprise implementation in 12 to 24 months. These are rough guidelines, but the order of magnitude is right.

4. scaling perspective

Where do you see yourselves in three years? If you want to scale from 100 products to 50,000, the choice of architecture is relevant today. A system change during operation is possible, but costly 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. There is no single provider that dominates the market - even if Shopify gives this impression in the public perception.

Global perspective

Shopify is the largest SaaS commerce platform worldwide in terms of the number of active shops. WooCommerce has by far the most installations, but a significant proportion of these are inactive or very small. Magento (Adobe Commerce) has long been the standard choice in the mid-market and continues to hold a relevant share there, but is losing ground.

Market shares vary considerably depending on the data source. Surveys by BuiltWith, W3Techs and similar services measure different things - installations, active use, traffic-weighted distribution. Absolute figures should therefore be treated with caution.

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 special feature of the DACH market: Legal requirements (GDPR, Packaging Act, cancellation policy, Price Indication Ordinance) make local providers that natively map these requirements attractive. International systems often require additional extensions in order to be operated in a legally compliant manner.

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

Artificial intelligence is finding its way into e-commerce on several levels: product recommendations, search optimisation, dynamic pricing, automated product descriptions, customer service chatbots. Practically all major platforms are integrating AI features - Shopify with „Shopify Magic“, BigCommerce via partnerships, commercetools via extensible APIs. It is still difficult to estimate how far-reaching the impact will actually be. The hype phase is still active.

Composable commerce as an architectural trend

The composable approach is gaining attention, especially in the enterprise segment. The reality is that for the majority of shops, a monolithic or simple headless architecture remains the more pragmatic choice. Composable solves real problems for large, complex organisations - but it is not a concept that makes sense for a shop with 500 products.

Unified Commerce

The boundaries between online shops, bricks-and-mortar retail, social commerce and marketplaces are becoming blurred. Unified commerce describes the approach of controlling all channels via a central system - one product catalogue, one inventory management system, one customer database. Shopify POS, Shopware and the enterprise platforms are driving this trend.

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

The GDPR was just the beginning. New regulations - the Digital Markets Act, the Data Act, national implementations - influence how shops are allowed to collect, store and use data. This affects not only the shop system itself, but also tracking, personalisation and the analytics infrastructure.

Tracking and analysis across shop systems

Regardless of which shop system you choose - without proper tracking and reliable analyses, you are flying blind. This sounds obvious, but is surprisingly often neglected in practice.

The challenge

Each shop system has its own tracking mechanisms that work differently. Anyone who operates several systems or combines channels faces the problem of merging data. There is also the legal dimension: in Europe, the GDPR requires a conscious decision on how user data is collected.

Many of the major tracking solutions originate from the USA and operate in a legal grey area as far as European data protection legislation is concerned. Cookie-based tracking is becoming increasingly unreliable due to browser restrictions and consent requirements.

What matters

For a reliable database in e-commerce, you need three things: a tracking solution that works independently of the shop system, clean GDPR-compliant data collection and an analysis option that actually provides you with actionable insights - not just raw data.

Cookie-less tracking approaches such as Trackboxx are gaining relevance in this context because they avoid the consent problem and still deliver usable analytics. But this is just one of many possibilities - the crucial point is that you think about your tracking right from the start and don't treat it as an afterthought.

FAQ - Shop systems