Skip to main content
TrustRadius
SAP Commerce Cloud

SAP Commerce Cloud

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.

Read more
Recent Reviews

SAP Review

6 out of 10
October 31, 2023
Incentivized
We use SAP Commerce Cloud in our organization to help our people go out and market our product more efficiently and professionally than …
Continue reading

Feels quite outdated

6 out of 10
October 25, 2023
Incentivized
SAP Commerce Cloud is our commerce platform. It is a very extensive platform and comes with OMS, product management and much more. It does …
Continue reading
Read all 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

View all 20 features
  • Product management (65)
    8.9
    89%
  • Bulk product upload (63)
    8.5
    85%
  • Product catalog & listings (64)
    8.4
    84%
  • Website integration (64)
    8.3
    83%

Reviewer Pros & Cons

View all pros & cons

Video Reviews

1 video

SAP Commerce Cloud Review: Serves As A Customizable Solution For E-commerce Needs
03:13
Return to navigation

Pricing

View all 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?

42 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.

Return to navigation

Product Demos

Headless eCommerce with SAP Commerce Cloud

YouTube
Return to navigation

Features

Online Storefront

Features for creating an online storefront with a browse-able product catalog.

8.2
Avg 7.7

Online Shopping Cart

Features that facilitate the collection of items so that customers can purchase them as a group.

8.1
Avg 7.6

Online Payment System

Features related to processing online payment for eCommerce purchases.

8.2
Avg 8.3

eCommerce Marketing

Features related to marketing for eCommerce websites

7.7
Avg 7.5

eCommerce Business Management

Features related to business management and administration of eCommerce operations

8.9
Avg 7.8
Return to navigation

Product Details

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

Screenshot of Product Cockpit for managing catalogs, categories and product contentScreenshot of Order Management Capabilities including sourcing and allocation rulesScreenshot of Commerce sites on two different mobile devicesScreenshot of Landing page from an e-commerce siteScreenshot of Web page with product categories and search results from an e-commerce siteScreenshot of Screenshot displaying headless commerce storefronts

SAP Commerce Cloud Videos

SAP Commerce Cloud Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported CountriesGlobal
Supported Languages50+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 highest, with a score of 9.2.

The most common users of SAP Commerce Cloud are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(170)

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Erin Riggers | TrustRadius Reviewer
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.
Hybris is straightforward to implement and customize for teams well versed in the Java Stack. The learning curve for technical staff with no exposure to Java is quite steep. Official training courses targeted at front end implementation would be tremendously beneficial in jump-starting productivity for those who fall into this category.
  • 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.
I truly enjoy leading Hybris development projects and participating in new feature development for the platform. I see huge potential for growth and hope to be instrumental in bringing Hybris to the bleeding edge of presentation layer technology.
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.
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.
  • 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.
I give this an 8 instead of a 10 because in hindsight, while I am extremely happy with the platform and the things I've learned through my exposure to it, I also see so many areas for improvement in the outcome of my efforts.

My advice to front end developers working with Hybris and/or the Java stack for the first time, is to not be intimidated by it. Question everything. Trust your intuition. Do not be afraid to refactor or completely replace something that appears integral to the platform if you see a clear benefit to doing so. It's much less far reaching than you think and the core system will not come crumbling to its knees if you make broad sweeping alterations. In fact, the energy you will expend to retool your site with a new framework will grow in tandem with the amount of time you spend hesitating, and at some point may become critical enough to force your hand while simultaneously becoming risky enough to destabilize your entire project delivery. If you don't like JQuery UI, punt it. If you don't care for the Blueprint CSS framework, burn it down. Making the strategic decision to adopt the toolset that best fits your organization from the very beginning will pay off in spades.

  • 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.
Figuring out the CMS tools took some time. Supporting documentation is sparse.

I also found the tools to be slow at times, making simple template edits an arduous process.
Return to navigation