This page reflects our views and assessments. All information is sourced from publicly available information and does not represent the vendor’s official position.
Name
URL
Architecture
Typical scenarios
i
Project Hosting
i
Code-access
i
Gartner Magic Q 23
Name
URL
Architecture
Typical scenarios
i
Project Hosting
i
Code-access
i
Gartner Magic Q 23
1
SAP Commerce
Modular, Java-based application
B2C
B2B
Marketplace
SaaS
Full Access
Leader
No results from filter
Evaluation
⭐ Highlights
SAP Commerce, especially when integrated with other SAP products like S/4HANA, is extremely powerful and capable of serving even the largest enterprises.
The underlying Java platform (Hybris) was released in 2001, making SAP Commerce a highly mature and battle-tested system.
👍 When to use
Companies with established Java teams that heavily use SAP ecosystem services may effectively leverage the full capabilities of this extensive system.
Companies with extreme requirements in with regard to scalability
👎 When to avoid
Companies seeking a more lightweight solution and lacking extensive in-house SAP expertise may find SAP Commerce overly complex for their needs.
Functionality
Summary
SAP Commerce is feature-complete for both B2C and B2B scenarios. However, it is limited in supporting Marketplace use cases, as it does not include a dedicated merchant portal. For this purpose, SAP officially recommends an additional vendor like Mirakl
Beside the relevant e-commerce related features, SAP Commerce also ships with advanced solutions for product management, order management and is pre-integrated with SAP S/4HANA and other SAP CX solutions.
There are multiple approaches to tailor SAP Commerce to specific needs:
Full Source Code Access: Licensed customers receive access to the complete source code of SAP Commerce (formerly Hybris). This allows for in-depth customization of the platform. SAP Commerce provides an extension architecture designed to ensure that customizations do not interfere with updates, enabling the platform to remain updatable even after modifications.
Side-by-Side Extensibility: This approach focuses on maintaining a clean core without making code-level changes. Instead, businesses can build web services that integrate with SAP Commerce using APIs and events. SAP’s Kyma Runtime
, running on an isolated Kubernetes cluster, supports this by enabling the development of custom microservices and serverless functions. This allows for extensions without altering the core platform, ensuring updates and system stability are maintained.
Storefront approach
SAP offers a template-based solution called Composable Storefront, built on Angular. It is available exclusively to licensed customers.
However, there is an open-source alternative called "Spartacus," which can be used by customers of SAP Hybris on-premise (now end-of-life, as noted below). You can find the repository here:
SAP offers a wide range of enterprise services. A typical SAP Commerce setup integrates with several of these services, like the SAP S/4HANA ERP system, via the Integration Extension Pack.
Hosting
While it was previously possible to self-host SAP Commerce, the on-premise version is now deprecated and will no longer be supported after mid-2026. Existing customers must transition to the cloud version or another shop system.
SAP Commerce is hosted on the SAP Commerce Cloud Version 2 (CCv2), managed through a cloud portal. The automation engine provisions and deploys the storefront, SAP Commerce, and the Solr search engine.
SAP Commerce Cloud is operated on MS Azure.
The Angular-based Composable Storefront can be hosted either in SAP Commerce Cloud or with any other provider.
Case Studies
All information is based on public sources and manually curated. Projects that are completely hidden from the public, are excluded. Contact us to contribute