SAP Hybris Commerce Reviews

I chose this out-of-box E-Commerce solution because it helps you start up your E-Commerce business in a very good amount of time since Hybris already provides you the end-to-end flow with minimum customization. You can quickly go live with the customer.

We can set up catalogs for our Hybris customers. One is an inventory catalog and another is a product catalog. Every catalog comprises two things, the daily version and the online version. These are figures that you can see for review purposes to determine that everything is fine. Once you approve the changes, it is clearer on the online version and readily available to the customer.

Furthermore, in the online catalog you can provide all your content pages, like your home pages, your product pages, your cart pages. What do they all look like? You can drop a component, and at the same time you can design a component. Let's suppose you want to create a subscription component from your homepage for the very first user. You can wrap, you can get the full component, do modeling in your code, just do a small reflection in the JSP. You configure the JSP, and create a particular component and drop into your home page at any place.

You have to create a slot across their few sets of slots, slowly providing you a better hybrid. For the slot, the main slot, the right and left slot, and center slot. But if you want a particular slot to be created for a particular component, you can create those slots by writing in a text file - just the configuration. Those slots are then available on your page. You just need to map them your JSP page, on the front-end file, and drop your components into the index. The index is another feature of Hybris. It basically allows you to import and export the data from the Hybris system.

When you drop a component there's an ingredient level on that site. So I can do everything. The back-end mapping is already there. Whenever they are forcing some data, it is back-end and needs to be written by the developer. It basically captures the front-end information from the form you entered and stores it in the DB.

So behind that layer are all Spring MVC models. We can look at the structure. You enter the data and Hybris builds the information and storage. It uses all MVC packets to handle this.

SAP Hybris Commerce has many valuable features. It will provide you the homepage, the search pages, the list pages, the product detail pages, the cart pages, and the checkouts. Furthermore you can use it to do a presentation for the business. With minimum customizing you can see the product, catalog, the prices with the payment gateway division and just go live. Overall, a request time of two to three months is a very efficient time for creating the E-Commerce session to go live. This is a very powerful product in that you can have single or multiple countries managed by a single Hybris solution.

Their promotion calculations capacity is powerful. They set out how they're going to calculate their set up, their loyalty factors, and their different promotions. They are even capable of doing customizations for different types of promotions, different set ups and more. You can customize your promotion. Normally out-of-box solutions have around 10 to 12 promotions. It crosses all the E-Commerce functionality, but it's specific and there's no functionality, although you customize the solution and implement in your application.

Hybris provides out-of-box features for promotions like percentages of sound, sound promotion, buy one get one, particular product bundle, and product partner promotion. These are out-of-box promotions where you just configure your products, and configure your categories and you're done.

For the checkout, they provide you the interface, and you have the capacity to provide your delivery address, the delivery method applicable for each country, and payment gateways. They do the summary pages. They provide you with pickup instruction functionality. Now you can add any product to the customer store. 

One of the major negative aspects of this is the back-end agent. They provide you a back-office portal which is meant for the agent where they can do a manual provisioning for order checks, they can confirm, they can do a one time product editing, and do a synchronization of the product from stage version to online version. Stage version is just a replica of the online one. So whenever you're doing some change, pushing to stage, it will synchronize to the online version with just a single button click and all the changes will go live in a short time.

It also provides you the built-in capacity for Solr. Solr helps you to search the indexing of the product. It is a different tool and it is already integrated here. You just need to index your products for the configuration which is very easy with the configuring they provide. Out-of-box they provide you the main conventions like searching over the brand category and size ranges. You can include promotions, as well. Then you can search over wide contractors. It provides everything. So with hardly any work it will do a Solr customization. 

Out-of-box you're quickly ready for business. The developer needs to do a small set up, changes in their code, test it, and you are done with the product.

They also provide the good feature of product classification. Let's say you are selling mobile phones, and you have features for a particular mobile that has a black power, black handset, and five inch display. Everything is on display about it in detail. Also they have different attributes on display, with descriptions of the product and what comes with the it. You can write a review and the back-end agent or back-office review manager will review your comment, whether it's a good comment or it's a really some rude words. They can approve or reject those comments and it will be live immediately.

Once an order is placed, the main thing is how you provision the order for the customer. For further fulfillment purposes, it can be triggered very easily from the codes once you place the order. It includes a set of actions that you will receive about whether it's already capable to be delivered or not.

It checks that the order is properly calculated, the pricing parameters are properly set, the delivery modes are set, delivery items are set, the payment incentives, billing and everything. Then you can take the payment capture from the payment gateway.

Once everything is done, you can trigger a shipping notification to the customer that your item is getting shipped, we accept the amount and it's done. All the major proponents are configured, like asking for customer inserts and certain websites, billing or placing the order. And if you want a few more, you will still do it after the transaction.

Provisioning the order. You place the order, you got notification that something got delayed or the order got confirmed, or your order is getting shipped. You can configure these kinds of lists very easily. They are pre-set templates that you can customize.

I was telling you about one aspect of Hybris which is its index. We can use the index to import and export. The import export index is basically used to carry the data to and from Hybris. You can import the data into Hybris' system, and you can export the data.

Hybris is agile. This is good because a business keeps changing their requirements. You may not ask for something because the sales team has surveys on how common sites look. They can see it in the requirements. So once a particular page is finalized, you can do a development.

The advantage of this product is that it can be deployed within two weeks, even with some custom requirements. It's not a complete solution but if you have out-of-box solutions, you can basically design an out-of-box site on your domain with no issue. But out-of-box you can't sell to the customer, right? You want some customer references, so you can put a time-stamped book on their title, and in a period of two weeks, three weeks, four weeks, five weeks, you can have a complete site development. If you don't have visit estimation you can go live within two months with sufficient data.

It's basically dual-based, so everything that gets managed you have to supply, just to connect your directory to the Commerce Cloud. You just go there and apply their build. Basically, they provision a starting environment, like the desk environment, queue environment, production environment, streaming environment. 

It is all cluster-based. Hybris' SAP Commerce Cloud out-of-box provides you one back-office server, connectivity server and depending on the level they'll provide the same nodes that are basically meant for the public requests. It will be  four-node or eight-node.

So you can connect to the SAP Commerce Team, cloud team, and provision those cloud portals, and your team can deploy the base filters.

Even getting a build to the cloud is very easy. It's a simple task. It hardly takes two to three minutes to push your build on the cloud environment. There is no need to write a simple command, nothing. You just mention your password and everything is done and you push it in.

In terms of improvement? They have set up modules for marketing, financial, everything. I can say everything is an improvement because they keep changing their versions every six months depending on the niche of the business.

They could include additional types of payment implementations. Right now they are just providing CyberSourse. 

They give you a framework and we customize it. The front and back-end are very tightly coupled in the framework right now.

So now they're going to another open-source framework. They're writing their front-end part in Angular. So just the back-end and front-end thing will be coupled. That will make a lighter version.

I have been using this solution for the last 8.5 to nine years.

We have been using this version for the last five years and it is a stable solution.

You can scale the solution. We integrated with other frameworks very easily. You can integrate your hardware with different platforms if you want. There is Tomcat servers you can integrate. They also offer some other DBs. They have everything.

You can scale it normally if you're going to deploy on a commerce cloud, SAP will post your review on their DB which they have configured.

They have other configurations which you just need to do before so that your definitions, your data types, and your tables, will be in compliance with their database service implementation.

The customer support is good. Normally they keep asking about the incident or support ticket. Their team will contact you about the problem, about your configuration, your log files, and if they're able to evaluate the information. They will provide a solution. After applying those configurations it will help and if it is still not working, you can set up a call and the supporting people will contact you and have an on-call solution.

The initial setup is straightforward. They have a set of SAP notes on their Hybris help site that you can follow. It's a very simple setup. In a single day you can set it up.

I'm still a developer, so I know that if you have to customize the solution, you will have to go digging down in their code, and to define which business class to customize for. It will work for you. Because they have a very complex code or a very abstract code.

On a scale of one to ten, I would rate SAP Hybris Commerce a nine.

I work for a consulting company and SAP Hybris Commerce is one of the products that I have experience with, in this capacity.

Our current use case involves an SAP commerce product called Spartacus, which is based on the cloud version. SAP handles the backend, which is deployed on the cloud, whereas the front-end is based on Angular technology. The clients I'm working with now are interested in migrating to Angular, so my current use case is migrating all of the front-end interfaces accordingly.

One of the clients that I'm working with is a post office, and they have a very large volume of traffic. In fact, they have nearly one million unique users per day. With this level of traffic, they wanted to use it for other things as well. To best take advantage of it, they decided to build a marketplace into their website.

SAP Hybris provides very good integration for a market place. There is a solution called Mirakl, which has a partnership with Hybris and they provide ready-to-use code for building a marketplace. The whole project took between six and eight months for the first version, and it was a huge success. In one year, we spent eight months developing and four months testing all of the processes, but we have a marketplace ready and currently, we are receiving a great benefit from it.

We have another client in France that had an event running, and they wanted to present their e-commerce websites at the event. We didn't have much time, perhaps five or six months, and they wanted to have a first version ready. It was a really complicated project, but since SAP Hybris provides all of the core features and our team is experienced, we successfully created the first working version in the allotted time. In turn, they were able to present their first version at the yearly event. That was another success.

I have worked with nearly all of the features. For example, I have worked on Stock Management, Payment Provider, searching with SOLR and Elasticsearch, and the Promotion Engine. 

For e-commerce projects, it has all of the core features so you don't need to develop a lot of things from scratch. If you have a client and they want to have an e-commerce project that is based on solid principles, you don't need too much time to develop it. SAP provides all of the e-commerce features and it is secure.

Security-wise, SAP deals with large clients, and they feel comfortable with the security that SAP provides.

SAP Hybris does not employ the latest technologies. For example, they still use GSP, Tag Files, an older version of Java, no microservices, and no Amazon Web services.

They have just started to work with the cloud, but they only support Microsoft Azure. If a client wants to use Amazon Web Services then they will not be able to. This is an area of improvement that they can work on. Especially now, with the cloud trending, everyone is talking about the cloud but SAP Hybris is not on it.

Non-Hybris developers find it complicated to work with. To work on Hybris projects, you really need an example to work from, otherwise, it will be more difficult.

I have about five years of experience with SAP Hybris.

Currently, it's stable. There are some very big clients who use SAP Hybris, including well-known brand names, and they're happy with it. In my opinion, it is really stable and I expect that new clients will continue to come.

SAP Hybris is not really following the new technologies, and they have just begun working with the cloud. I think that they need to put some work in for it to be more scalable. The way SAP or their products were developed, does not allow the product to be scalable.

The project that I am working on at the moment has one million unique users per day.

There is a big community for this product.

For technical issues, you have the community and people who will spend time looking at the issues you have. There are people providing open-source solutions that help developers improve things such as their build times, or other work tools.

There is also support from the vendor. If you have a question and contact support, you always have the answers in a really short time.

Overall, for me, the technical support is good.

I have developed other e-commerce platforms, although they were in native Java and Spring, with no e-commerce framework. In Java, it is more painful because you need to develop everything from scratch. Not only is it not as powerful as Hybris, but Hybris already has many included features that are already tested and proven.

The installation is not very complex. The documentation is clear and it doesn't need experienced developers just to set it up. The length of time for deployment depends on the performance of the server. It might take perhaps 30 or 40 minutes. On a local server, it's between 15 and 20 minutes to deploy.

Our DevOps team is responsible for the deployment. We have pipelines, and a Jenkins job to take care of it. We have an automatic daily deployment on the test environments and the dev environments.

The current project is quite large so we have a huge DevOps team of perhaps 13 people. For simple projects or medium-sized projects, two or three people can take care of the whole thing.

We generally don't need to involve SAP or another integrator, but it depends on the requirements. If there are special needs, for example, then a DevOps person is required. For the most part, however, if you don't host your website with a third-party then you don't need anybody else.

One of the projects that I am working on has the product environment hosted with a third-party. In that case, some of the people from that platform have intervened to solve issues.

We have seen ROI. This e-commerce solution represents 70% of the company's income.

SAP Hybris is expensive, which is why only the large clients use it. At the same time, I think that the return on investment warrants it. For me, the majority of the clients I work with are happy and they see ROI. In my opinion, the product is worth the price.

We did not evaluate other options. For e-commerce, most of my experience is with SAP Hybris.

My advice for anybody who is looking into implementing this product depends on the company size and the project size. If it's not a very big project, I advise using other solutions, other frameworks, or develop the project from scratch with native Java and Spring. On the other hand, if it's a big project then I will highly recommend using SAP Hybris.

The biggest lesson that I learned from using this product is to test, test, and test again. Never put something into production, live, until you are 100% sure. So, if you want to develop something then test it, retest it, and retest it again. You have to be careful because surprises always come.

This is a great product and I have rarely experienced issues with SAP Hybris itself. The majority of issues stem from how people use it. Support is also great. It uses Java, as a few e-commerce solutions are. A project that is based on Java is good because it's the world's most used technology.

On the downside, this product is expensive, although it is worth it for big clients.

I would rate this solution an eight out of ten.

SAP Hybris Commerce is basically an eCommerce solution. We are Bosch-Siemens Home appliances. We sell household appliance products, like refrigerators, washing machines, etc... We have our own eCommerce website. Something similar to Flipkart or Amazon. We sell all these products with our websites.

For all the products there will be a product list. As a customer, you will log into this website and then select the particular product, for example, either Bosch or Siemens refrigerators, then check out and pay the bill. Then key in the delivery address, something similar to how you're going to buy any particular product on Amazon or Flipkart.

We have around 300 plus websites across multiple countries. We host and manage all these web applications, basically eCommerce applications. Apart from that, we do have other web applications, which are built on PHP and Node.js. Most of them are hosted on AWS, some of them are hosted on premises. And apart from that, there are solutions like SAP SD module, SAP MM, FICO, CRM.

Generally, as a customer, you will visit the store, purchase the product and the store may deliver on the same day or on the next day or whenever. It is a physical visit and then you're going to get the delivery. You visit the store, you pay and then you come back and the particular product will be delivered to your home. In our case, the customer can be anywhere. He or she visits the particular website and selects the product online. They can see all the features, and then pay online. The website itself will suggest on so and so date it'll be delivered. Based on the date provided, that particular product will be delivered. Post delivery, you can call the customer care. They will come and install. It is all online. You need not go to a physical store. With the click of few buttons with your mobile device or with your notebook or laptop you can purchase the products at your home. Whatever household appliances, it can be refrigerators, microwave ovens, washing machines. We really have lot of products.

We have found the B2B, B2C and D2C very valuable.

In terms of what could be improved, I would say the product search. There will be multiple criteria to search products and there will be a number of products in different categories. The question is how soon can I find the product which I'm looking for. The search can be improved.

There will be security involved in your payment gateway while you are paying. Creating a purchase order. There are many areas that can be improved in the front end - the look and feel performance wise. The entire life cycle right from logging into the particular eCommerce website until you check out, how soon I can complete this entire process? Those are the three areas. There are many areas one can improve.

I think we have the latest Hybris version from 2000, Hybris nine, something like that. Whatever features SAP is releasing, we are evaluating how they will be beneficial to the customer. If it is beneficial, then we are implementing. Apart from that I don't see anything extra.

We have been using SAP Hybris Commerce for close to eight years.

SAP Hybris Commerce is stable.

In terms of scalability, we had certain issues. For example, let's say we have Big Billion Day or Christmas Eve - there were some scalability issues. Now I think, with the help of AWS auto scaling, scaling out or scaling in is pretty much covered.

It is a worldwide solution. We have some 70 countries using it. 

In India itself, we have three teams developing and maintaining it. Two development teams and one support team. Deployment is also happening in Germany. There is a dedicated team there. I think, maybe three to four consultants. But all deployment will happen in Germany. Development and support teams will be in Bangalore. Each development team comprises somewhere around nine to 10 members. Support is also around nine to 10 members.

We have our own in-house solution. So, based on the customer feedback, our business team will analyze the requirements and accordingly, the development team and the IT team will implement the solution.

It's all BSH related development. So, whatever the customer needs, there is a business team that will understand and analyze them. If there are any developments that are required, that will be informed via technical specification documents or business specification documents through the development team. The IT team will materialize the requirements. We follow Agile methodology.

In our case, we started with the older version of Hybris, so at that time, there were not too many improvements. To meet the business requirements, it has been customized heavily. Complex customizations and complex developments have been developed. Those features are now available with the latest versions. Changing that into the latest version will be a tricky task now.

It was a long journey. The implementation started somewhere in the year 2013 or 2014. Currently we are working on whatever enhancement, minor changes or modifications which the customer is looking for. That will take probably two weeks or one month time to develop. To deploy, as it is a cloud deployment, hardly takes two or three hours down time.

We implemented all on our own. We used AWS and there are some deployment tools, like CHOF, all those things.

Obviously we evaluated other solutions. Such as Magento, Demandware and three or four other vendors. Since Bosch is implementing heavily on SAP, Hybris being a SAP product, after a careful analysis, the team arrived at SAP Hybris.

The end user can use any device for this - mobile device, desktop, laptop, anything. I would say it its very convenient

On a scale of one to ten, I would give SAP Hybris Commerce a nine.

I am a freelance SAP Hybris Commerce technical expert. 

I have worked with many clients on Upwork and outside Upwork. I also have an agency that contains many developers for Hybris, iOS, Android, and many other technologies.

Hybris is used for e-commerce needs. Hybris offers e-commerce features like checkout, payment options, and others for different phases of e-commerce.

We don't try to convince our clients to use Hybris. Our clients have already made the decision to use Hybris, then they come to us.

Storefront is the most valuable feature for our clients. It allows them to start their projects quickly.

Hybris offers a platform designed for speed. In one week, we can build a complete e-commerce solution. The checkout, the payment, and delivery options are all dedicated to B2C and B2B clients. That's the value for our clients.

Hybris is not currently using microservices. Technically, we can introduce microservices to deploy some aspects separately. 

Personally, I find that the Hybris code is not really clean, but that could be due to the fact that we don't always use 100% oriented objects.

Hybris is constantly adding new features that are aligned with market needs. For this reason, feature-wise, I don't see anything that needs to be improved, currently.

I have been using SAP Hybris Commerce for seven years.

SAP Hybris Commerce is stable. Currently, we get our support from the SAP side. If we experience any bugs, we can just contact them and they'll fix it right away. Overall, I think it's stable. It doesn't contain many bugs, and it doesn't crash. From my experience, it's good.

They need to use microservices to make it more scalable, but it's acceptable for now. At the moment, It's not really scalable but I can accept that as it offers many other advantages. 

SAP hybrid technical support is good. When we have an issue, we simply communicate with them and they provide us with online support.

I would give their hybrid support a rating of six out of ten.

From my experience, when we ask them for help, they provide us with the solution to implement; however, sometimes we need to wait for a long time for the answer, so we just take care of it ourselves. Sometimes they don't provide us with a clean, technical solution, so we have to implement our own solution. Then, when they have implemented the solution in the next version, we have to adapt our solution or remove it and adapt their solution. 

For SAP Cloud support, they are reactive and they provide an immediate solution to our problems. I would give their cloud support a rating of eight or nine out of ten. 

I have not used any other e-commerce solutions, only Hybris.

Regarding both private servers and the SAP Cloud, deployment is quick and easy. 

We don't need one week to deploy it, but we need one week to start it and to customize some basic features like the checkout, payment methods, and some other features; then it's ready for deployment. I could deploy the basic solution (including the client's products and catalog) in one day, but it takes a week to deploy the complete package. 

Deployment is taken care of by Hybris. I don't configure it or manage it directly.

Regarding deployment in the server, we have some deployment steps that we follow, but it's simple. It's not complicated at all.

Because we are not direct clients of Hybris, we don't manage the pricing or licensing. We are technical experts, so the clients have already made the decision to use Hybris and to buy it. We don't have enough information about pricing or licensing as the clients that are using Hybris have already made this decision.

For someone who needs or wants to use Hybris — try to use the native features. Hybris consists of many great features by default. There is no need to try and customize them.

For example, if a client asks me to customize the checkout, then I need to check if Hybris allows this type of customization or not. If it already has this feature, then don't try to customize it and use your own implementation. If you do use your own implementation, when Hybris improves that native feature, you will need to be aligned with Hybris. In short, my advice is to try and use the Hybris features and coding, instead of adding your own code. 

The price is too high, but overall, Its code is clean and it's scalable. On a scale from one to ten, I would give SAP Hybris Commerce a rating of nine.

We are now using it as a customer front. We will be using it as a catalog base, and all of the other engines will be independent of Hybris Commerce. Hybris Commerce will be used as a catalog to reach our customers, but the backend will be completely different, mainly in the retail sector.

The simple steps for configuring your checkout processes, as well as the promotional engine, are the most valuable features of this solution. They are both excellent, and you can easily customize them.

The integration side of it with Hybris OCC to integrate with other systems is also effective. That's also a useful feature. It primarily has a lot of features that provide a significant advantage, and it's very good.

It's out of the box, it's a new spectrum.

It's good, but it depends on how you are customizing it to your benefit. It depends on your business objective and your angle, and how you want to go about it.

It's flexible, you can do anything with it.

I don't have any issues with the interface.

The price could be improved. It is very expensive to implement, which is why many companies who can't afford would normally move to Salesforce or Magento. 

It can be tricky to support other features that are inside customization.

I have been using SAP Hybris Commerce since 2017.

I used to work with versions 6.4, 6.5, 1811, and now 2011.

It's stable, especially when you're running it on AWS.

We have the auto-scaling packages. 

The entire framework of AWS's private network makes it simple for us. It's quite good. It's all about where you're hosting it.

I don't know how many users we have, but it's a lot.

Technical support is adequate, particularly on the paid version. Having a consultant to help us is a good thing. To be honest, it depends on the user's question or issue when calling in for normal support. It is determined by the complexity of the issues.

From my perspective, it's going to be extremely complicated for a new person who doesn't know, but it depends on how you build it, and how you run your own build in order to set it up. 

I wouldn't call it complicated. It's quite simple when you have the knowledge.

When you've been doing something for a long time, it becomes easier over time.

The deployment time depends on the size. The first initial deployment, is about three hours, depending on the data size, but after that, it's quite quick, mainly one hour.

The implementation was done in-house. We do everything ourselves.

I don't know the cost, but it can be expensive.

It's a good product in terms of scalability, functionality, and flexibility. The market should shift toward SAP Commerce. Without a doubt.

I would rate SAP Hybris Commerce a seven out of ten.

There are multiple use cases. I work with multiple clients, and each client has multiple use cases. My clients are mostly B2B and B2C clients and they are all involved in different areas of business. For example, I work with luxury clients, clients in construction, and clients in the medical field, too. They are all different in terms of project size. Some of my clients have just discovered SAP Hybris and want to integrate it; they just want to test it out and see if it works for them. 

SAP Hybris provides us with all of the e-commerce features that a client could need. For example, when we want to build an e-commerce project, we literally have everything we need to get started. The checkout process, order management, email management — everything comes integrated and ready-to-use. This is the strength of SAP Hybris.

The stack needs to be improved; they need to start using more new technologies. Technically we're still using GSP tags and GSL which are old technologies. Now, SAP Hybris has a new project called Spartacus. So, it's getting better, but there is still room for improvement. 

Currently, they don't offer support for mobile applications. Most of the projects I work on are web projects. I have never worked on a project using SAP Hybris that had mobile applications.

I have been using SAP Hybris Commerce for four years. 

It's rare that you'll find a bug in this solution. It has a strong code — well tested. This is one of the many strengths of SAP Hybris. 

We've never experienced any problems when it comes to scaling. It's really open to modification. Scalability-wise, I don't think there's an issue. 

They have a team for support. We had some cases where we needed some answers from technical support; they were happy to help. Sometimes, when we begin a new project, experts from the SAP Hybris team will actually review our code and tell us if there are any patches that we need to fill. They really care about providing for their clients.

If you haven't worked with SAP Hybris before, then the initial setup will not be easy. If you have no previous experience with Hybris, then it will be difficult to start. Still, the documentation is well designed and very detailed. 

This is an expensive solution. All of our clients are big. If you're a small business, then there's no need to use SAP Hybris; it's really only for big projects. Although it's expensive, it's worth it.

Overall, on a scale from one to ten, I would give this solution a rating of eight. 

We use it to monitor customer experience with regard to e-commerce.

It's the best tool on the market and is a complete e-commerce system for product management. For instance, if the customer has a log enterprise level product, they can manage it here.

It's connected to the whole SAP tool, and you now can connect any of the SAP tools to this customer experience tool. They have built a whole web so that any application can be connected to this particular software.

The WCS management or content management is not that great.

Every one and a half to two years, Hybris stops updating or supporting previous versions. This means that the end-customer has to update their version every time.

SAP Hybris can work on the virtual commerce (VR) feature, which is new to the market.

I've been working with this solution for the past eight years.

Stability wise, SAP Hybris Commerce is fine.

The scalability is good.

Technical support from the SAP team has been good, and I would rate it at four on a scale from one to five.

The initial setup was very complex earlier, but now it seems to be a bit easier.

We had a team of eight to ten people for the deployment, and four to five people for the maintenance of the solution.

On a scale from one to ten, I would rate SAP Hybris Commerce at eight.

Its dashboards, business features, and user-friendliness of a lot of business interfaces are valuable.

We work on B2B projects, and it is the most efficient software solution for B2B. The B2B accelerator is very much appreciated by our customers because it has some use cases that are ready for production. For some projects, we proposed the SAP Hybris solution because it was sufficient for use cases related to product management and data quality. With other e-commerce platforms, we would have needed integration with another product information management software.

Like every other SAP solution, it is very heavy. Also, the transition to the cloud is not very smooth because it is not really a SaaS solution. The upgrades are also not as smooth as you would expect from a complete cloud solution.

It should have a product recommendation feature as well as a promotional feature. It should also have more personalizations.

I have been using this solution for three or four years.

As a B2C solution, I would rate SAP Hybris Commerce a seven out of ten. As a B2B solution, I would rate it an eight out of ten.