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.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
SAP Commerce Cloud is well-suited for large enterprises requiring robust personalization, seamless multi-channel integration, and the ability to handle high-volume transactions, especially during peak periods like Black Friday. Its scalability and advanced features make it ideal for businesses needing to manage complex product catalogs and global operations.Enough development capacities are needed to have a best in class shop
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Centralized Data Management: SAP Commerce Cloud excels in centralizing data from various operational sectors, which is pivotal in the chemicals industry. This feature allows for better oversight and management of complex supply chains, regulatory compliance, and customer interactions. Having a single source of truth for crucial business data minimizes discrepancies and promotes informed decision-making.
Real-Time Data Processing: The real-time data processing capability of SAP Commerce Cloud is invaluable. It aids in timely adherence to regulatory changes and helps in meeting customer demands promptly. In a sector where regulations and market conditions are ever-evolving, real-time data processing is fundamental for maintaining compliance and ensuring customer satisfaction.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It's a little pricey; further cost reductions will expand product selection; also, trained operators are required.
HAC occasionally functions extremely slowly and does not provide any problem messages; it simply gets stuck. Logging into the Backoffice for testing purposes causes a lot of trouble; it does not enable us to log in in one attempt, and the page refreshes every time we enter in the credentials.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
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.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
More true headless and a more rationale pricing. Since moving from the Hzbris Monolyth towards SAP Commerce Cloud a lot of progress has been made, but dissecting the monolyth into composable components where you just pay for what you use is still a longer journey and here pricing should be more realistic. Things become so expensive once they have the SAP stamp on them (example the SAP CIAM)
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
We have the right to open a ticket or submit request to SAP support teams for all the problems we have experienced. They also provide solutions for critical issues within 48 hours. In addition, the product has support documents such as a user guide and admin guide. In addition, there is a strong community of users. In this way, we can access solution of some specific problems that we have fallen on from there.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Scalability of the product was good Seamless integrations were helped in reducing the implementation for the development team to integrate with the SAP ERP Product framework helped customer to customize and adapt the new features which were developed basis business processes and ease of customer experience. Deployment and creation of the build becomes very easy with the CCv2 setup.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
SAP Cloud is much better than GoDaddy. it was a smooth transition and every aspect of the program is easier. My scalability increased greatly from GoDaddy to SAp Commerce Cloud and sales are now tracked easier and inventory is at the touch of a button, making sales much easier than previous software.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
The business users/admins were able to quickly segment products by brand, allowing for unique branding and header-less page design. As new products are added to the SAP backend, all characteristics and pricing automatically migrate to Commerce Cloud. We also segment our user sign-on (domains) by brand and allow targeting displays.
It has a positive impact on my client's business and ROI is higher than expected. As orders count is increasing due to smooth and better experience.
My current client's customers have given very positive experience about new website built on SAP Commerce Cloud.
Due to SAP Commerce Cloud website rollout is very easy and due to it, my current client has introduced around 25 websites. As SAP Commerce Cloud logic needs to develop once and can be reused for multiple websites easily with minimal effort.
Branding is also very easy as promotions, events can be implemented on the website easily and with minimum time.
SAP Commerce has helped our client to integrate the Recommendation tool ISS which is easy to configure after this tool product sale is increased. The best thing was that integration was very easy and quick.
One option of Blue/Green deployment helping us to check the production release in advance on production environment. Prev we don't have this option and many times face P1 issue in prod which had ruined client reputation. But now this feature is helping lot
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
