SAP Commerce Cloud Review
I use SAP Commerce Cloud for Business-to-consumer (B2C) and Business-to-business (B2B) websites.
Overview
What is SAP Commerce Cloud?
SAP Commerce Cloud (formerly Hybris) is designed to help businesses sell more goods, services, and digital content through every touchpoint, channel, and device through their multichannel ecommerce and order management solution, available as a SaaS or on-premise.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Product management (65)8.989%
- Bulk product upload (63)8.686%
- Product catalog & listings (64)8.484%
- Website integration (64)8.383%
Reviewer Pros & Cons
Video Reviews
1 video
SAP Commerce Cloud Review: Serves As A Customizable Solution For E-commerce Needs
03:13
Pricing
N/A
Unavailable
What is SAP Commerce Cloud?
SAP Commerce Cloud (formerly Hybris) is designed to help businesses sell more goods, services, and digital content through every touchpoint, channel, and device through their multichannel ecommerce and order management solution, available as a SaaS or on-premise.
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.sap.com/products/crm/e…
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
43 people also want pricing
Alternatives Pricing
What is Salesforce Commerce Cloud?
Salesforce Commerce Cloud (formerly Demandware) is a cloud-based eCommerce solution that touts flexibility and scalability for enterprises. It features merchandising tools, such as sorting, filtering, and image zooming.
What is Shopify?
Shopify is a commerce platform designed for both online stores and retail locations. Shopify offers a professional online storefront, a payment solution to accept credit cards, and the Shopify POS application to power retail sales.
Product Demos
Headless eCommerce with SAP Commerce Cloud
YouTube
Features
Return to navigation
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is SAP Commerce Cloud?
SAP Commerce Cloud is a commerce solution built mainly for large enterprises with advanced B2B, B2C, and B2B2C use cases. Users can customize the solution to meet specific needs and manage complex catalogs, products, and configurations in order to create hyper-personalized omnichannel experiences. The solution also includes comprehensive B2B commerce capabilities.
SAP Commerce Cloud Features
Online Storefront Features
- Supported: Product catalog & listings
- Supported: Product management
- Supported: Bulk product upload
- Supported: Branding
- Supported: Search & filter
- Supported: Mobile storefront
- Supported: Product variations
- Supported: Subscriptions & downloads
- Supported: Website integration
- Supported: Visual customization
- Supported: CMS
- Supported: Customer service tools
Online Shopping Cart Features
- Supported: Tax calculator
- Supported: Shipping calculator
- Supported: Checkout user experience
Online Payment System Features
- Supported: Returns & refunds
- Supported: Single-click checkout
- Supported: eCommerce security
- Supported: Credit card transaction fee
- Supported: B2B features
eCommerce Marketing Features
- Supported: Promotions & discounts
- Supported: Personalized recommendations
- Supported: SEO
- Supported: Product reviews
- Supported: Social commerce integration
- Supported: Customer registration
eCommerce Business Management Features
- Supported: Multi-site management
- Supported: Order processing
- Supported: Inventory management
- Supported: Accounting
- Supported: Shipping
- Supported: Custom functionality
Additional Features
- Supported: An API first approach, to setup and connect needed services to run an commerce shop, and microservices enabled architecture.
- Supported: Engages customers in the moment with contextually relevant shopping experiences anywhere across online and offline channels and devices
- Supported: Empowers sales and service reps to respond intelligently to customers’ needs with the holistic view of the customer journey.
SAP Commerce Cloud Screenshots
SAP Commerce Cloud Videos
SAP Commerce Cloud Integrations
- Dynamic Yield
- Coveo Qubit
- Sitecore Discover
- Algolia
- Visa Acceptance Solutions (CyberSource)
- Adyen
- Worldpay from FIS
- Stripe Payments
- Braintree, a PayPal service
- Avalara
- Vertex
- SAP S/4HANA Cloud
- SAP ERP, ECC
- SAP Marketing Cloud
- SAP Sales Cloud
- SAP Service Cloud
- SAP CPQ
- SAP Customer Data Solutions
- Bloomreach Commerce Experience Cloud
- Monetate
- Apache Solr
- OpenText Digital Asset Management for SAP Solutions
- CELUM ContentHub
- Mirakl Marketplace Platform
- Emarsys
- Tenovos
- Empathy.co
- Twiggle
- EasyAsk
- Paybright
- SAP Commerce Marketplace Management by Mirakl
- SAP Store Management solutions by GK
- SAP Paybacks and Chargebacks by Vistex
SAP Commerce Cloud Competitors
SAP Commerce Cloud Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
| Supported Countries | Global |
| Supported Languages | 50+Languages |
Frequently Asked Questions
SAP Commerce Cloud (formerly Hybris) is designed to help businesses sell more goods, services, and digital content through every touchpoint, channel, and device through their multichannel ecommerce and order management solution, available as a SaaS or on-premise.
Salesforce Commerce Cloud, Adobe Commerce (Magento Commerce), and Shopify are common alternatives for SAP Commerce Cloud.
Reviewers rate Order processing and Inventory management highest, with a score of 9.2.
The most common users of SAP Commerce Cloud are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(169)Attribute Ratings
Reviews
(1-2 of 2)Companies can't remove reviews or game the system. Here's why
March 26, 2023
Commerce Implementation for the enterprises
We moved all the client implementations from on-premise to cloud and have realized the ease of use of the software over the conventional one. Apart from ease in deployment and a cleaner structure of storefront, back office, and hac, this also gives Kibana based tracking of the logs and APM using Dynatrace.
- Deployment
- Debugging
- Setting up environment specific variables
- Isolating and monitoring server
- Cleaner separation between different servers
- build pipeline customization
- access related issues
- troubleshooting without SAP intervention
86.25%
8.6
100%
10.0
100%
10.0
76.66666666666667%
7.7
92%
9.2
- For my clients, it has streamlined the costs incurred in their IT infra as using SAP Commerce Cloud requires a lesser upfront setup
- Due to flexibility in SAP Commerce Cloud, another client was able to scale up their operations and ended up with 5x of orders in the pandemic
This is more customizable than its competitors and is much more customizable and possesses greater flexibility as well as a multi-channel environment for flexibility in its delivery. It comes with Out of The Box setup for B2B, B2C, Telecom, Utility, Marketplace, and Chinese-based accelerators that quickly enable us to have a fully grown eCommerce system at our disposal.
1000
Development and architecture of the application to modify as per client needs and also introduce new features. Apart from development, there is also the support and management of the existing applications and upgrading the underlying hybris commerce version as per industry rollout and to apply the latest security fixes.
100
Java development with full stack developers having proficiency in angularJS and having knowledge in SAP commerce cloud operations. In addition to this, the system maintainers also have functional knowledge of the commerce cloud tools like the HAC and Backoffice to support the day to day activities. In addition to this, the support team also have access to jira, kibana and performance monitoring tools.
- Ecommerce platform for wide variety of applications
- Supply chain operations for larger organizations
- Capable of having support for various integrations and change management of different systems
- Use of ASM functionality to address customer call center operations
- Utilize the application with IVR or sms based actions from users
- having a omni-channel or multitouch point for the commerce application
- Utilize its REST based OCC layer to further integrate more applications
- Integrate AI based suggestions for cross-sell or upsell to the users
Score 10 out of 10
Vetted Review
Verified User
Razorfish has formed a partnership with Hybris and have adopted the platform as our primary e-commerce offering going forward. My technology division, Razorfish West, led the charge in launching the organization's first implementation for West Marine in February of 2014. Several other Hybris initiatives are in active development throughout the company nation-wide.
- Solid architecture upon the Java Spring framework
- Clear, efficient separation of presentation and data layers
- Easy to setup and maintain local development environment
- UI layer easy to extend, or re-tool to fold in preferred frameworks and utilities.
- CMS Cockpit is slow and inefficient for performing certain kinds of content management and template manipulation tasks. I often defer to the HMC, but this is not a feasible option for our client's content management team.
- The OOTB UI code that ships with v5.0.1 is several years behind industry standard front end technology. v5.1 shows no promise of significant improvements in this arena. Some things I'd like to see: Dropping the Blueprint framework in favor of something Like Bootstrap, Less Framework or AngularJS. Jquery and key dependent plug-ins need to be upgraded and large, over-featured plugins like JQuery UI abandoned. SASS + Compass should replace static CSS. Granule should be dropped in favor of better tools for JS dependency management, code minification, and file concatenation.
- Maintaining independent codebases for Desktop and Mobile views increases UI development hours by a margin of 30-50%. Natively supporting the option to configure a responsive design with a framework such as AngularJS would offer flexibility to serve up content and site chrome targeted at a wider range of device classes than just desktop machines and mobile phones.
- With one solid Hybris implementation live, and another on it's heels in Q3, we've built significant in-house expertise in the platform. As we win more Hybris business, our ability to rapidly implement performant and unique e-commerce solutions for our clients can only improve.
sales, client engagement, technology leadership, new feature development and testing.
- Implemented in-house
- Professional services company
Implemented with a combination of in-house resources and experts contracted through Sceneric that worked both on-site in the Razorfish offices and remotely from Europe. I cannot say enough good things about Sceneric.
Yes
We organized the project into eight 3-week feature development sprints, a stabilization phase where we focused on critical defect resolution, and a UAT phase prior to launching the site.
Development of the sister site is underway and organized in a similar fashion.
Development of the sister site is underway and organized in a similar fashion.
Change management was a major issue with the implementation
With the scope of an initiative like this one being so large, there are always challenges in managing changing business needs of the client, scope creep, unforeseen technical hiccups, and all of the other things that contribute to churn. There was nothing unique to Hybris about the issues we faced.
The only thing I would say in regards to lessons learned specific to my own area of expertise, is that I would have put a great deal more effort prior to starting feature development, into scrutinizing the front end architecture that ships with Hybris to make certain it would scale to accommodate inevitable deviation from original specifications and allow adoption of new tech as it becomes relevant.
The only thing I would say in regards to lessons learned specific to my own area of expertise, is that I would have put a great deal more effort prior to starting feature development, into scrutinizing the front end architecture that ships with Hybris to make certain it would scale to accommodate inevitable deviation from original specifications and allow adoption of new tech as it becomes relevant.
- Steep learning curve for front end developers not already well versed in the Java stack
- Hybris documentation, at the point of project initiation a year ago, was too sparse to be helpful in the training of new members of my team.
- Impex files and the placement of significant portions of presentation layer code within them, was highly problematic for my UI team. One of the major functions of impex files is to store default CMS editable site content, and it was an arduous process to learn best how to troubleshoot and resolve defects for functionality that came from the markup stored within them.
- Via the HMC, bulk modifications to templates, modules, products, etc, were very easy to make
- Editing templates via the CMS cockpit was very intuitive and straightforward.
- The preview and live edit features in the CMS cockpit were incredibly helpful.
- Understanding how Endeca integrated with the product catalog and categorization took some time to wrap my brain around.
- Documentation around category restrictions and other vital configuration details is sparse, requiring a lot of trial and error to learn when and how to apply them.
Yes
The mobile interface should be dropped entirely in favor of responsive design support.
Because the mobile site is an entirely separate codebase, supporting it required my team to author a lot of duplicate functionality with only slight differences between the desktop and mobile implementations.
Because the mobile site is an entirely separate codebase, supporting it required my team to author a lot of duplicate functionality with only slight differences between the desktop and mobile implementations.