4 out of 5.0, Reviewed Dec 6, 2016
Implementing Hybris was not without its challenges, however it was refereshing to use a platform that was so open to using as much or as little of the platform. It was also refreshing to see a product that engaged the best the open source world had to offer rather than trying to re-invent it in a proprietery manner. We were able to cut down our time to market significantly over past experiences while delivering a modern cusomter experience that our whole company is excited about (and that doesn't usually happen in B2B!). Overall we found this platform has set us up for future growth and will allow us to continue to extend and grow our platform to other parts of our business and integrate with others as well.
Invest in growing your internal knowledge and employee bench. Each company has their own spin on eCommerce - and you must make it your own. Don't completely rely on external vendors as they do not know your business as well as you or your employees - this sounds obvious but often it isn't done at enough levels. Ensure you have your own developers, UX, etc and don't be afraid to fight your leadership for this investment... if you don't ask for headcount you will never get it.
Hybris is quite open and uses a lot of proven technologies and patterns within the Java/Spring realm. This allows you to grow your team faster because the skillsets are NOT proprietary; your developers and architects only need to learn the platform; not a new language or pattern. I have also enjoyed the use as much or as little of the platform outlook and the responsiveness of the Hybris organization itself - this is not your father's SAP company...
I struggle to answer this question; perhaps the data hub component. With Hybris now being an SAP company we expected the integration to the SAP ECC (ERP) to be much more robust and ready for a company of our scale... This component was not mature enough for us and we wound up using custom integration; the good news is this [the custom integration] met our needs and Hybris/SAP worked with us to solve the problem.
This is more of an SI comment and less so on the software - but ensure there is complete transparency from the beginning. Don't allow things to become a 'black box' - this is your implementation after all - no matter what the vendor may think. Remind them you are the customer.
We would take more time in vetting our partners. We chose an SI based on gut instinct, and while in the end we feel it is working out it didn't come without its struggles. We also would have liked to reduce the overall number of vendors within the project. It was great to have more than one point of view so I don't recommend using only one company but beyond 3 you wind up with more finger pointing than you have time to wade through. Also ensure you are not afraid to make tough decisions we lived too long with a key person who was just not a fit; we eventually replaced this person and now wish we would have done so sooner.
4 out of 5.0, Reviewed Nov 8, 2016
Hybris consulting team were great in support, but be sure to get advise on what you might needup front from others. Eg, Cache strategy is key within the application. We partnered with a good SI which was key to staying married during and after delviery of the project. This is more key than the software to some degree.
Consider the interation to other applications and use as many of the cartridges as possible. Less bespoke makes upgrades easier Ask the business what data they want too as the data model is fundamental to sucess.
Adoption is high, so there is a large pool of resource who want to be involved with Hybris.
Would like more integration into stores. Keen to get a EPOS front end that looks god ASAP.
Nothing to note here.
The presentation layer was the poorest part of the offering, CSS and UX. Whislt these are seperate to Hybris, they are inherent in most replatform projects. The application itself requires structured data, as you would expect, so ensure you have this before you begin. The Hybris application is only one of the moving parts of the project we implement, and was the easiest to slot into place. Adding the business logic added much more complexity. Simplifying as much of this as possible up front and adopting this before you start the project will help.
It does what it says it does for e comerce. I would like to see it become a wider front end in stores for us.
4 out of 5.0, Reviewed Nov 7, 2016
We had every major issue fix fast. but some things took to long.
get the management behind it
That is very very stable and has a lot of business processes build into it.
its imense expansive.
We would love to be more consultant on the business process side
we would be more focussed on the core requirements and see from there.
4 out of 5.0, Reviewed Jul 15, 2016
The implementation went well. There were some customization but Hybris allowed for much of the requested functionality.
Start with a much more thorough 3 month planning & scoping exercise.
3 out of 5.0, Reviewed Jun 7, 2016
SAP is mature in ERP domain. However, their venture into PLM was very new, and they had to rely heavily on third party service providers for implementation expertise, and we had to plan a phased approach rather than big-bang implementation.
Do your homework around implementation and roll out, trainings etc. from total cost of ownership. Don’t just look at the cost of procuring a license.
PLM being a part of the robust enterprise SAP platform.
PLM version in its infancy stage in terms of maturity for Retail domain.
Brought in more expertise around implementation and roll out rather than relying on third party service providers.
Prioritize service offerings into what would matter the most to the business/users (ROI, business functionality, etc.). In the initial roll out versus the rest; if possible, do a proof of concept pilot to mitigate risks early on in the process.
4 out of 5.0, Reviewed Jun 2, 2016
It’s good except performance tuning, integration with 3rd party applications also requires detailed design.
Test early the integration components.
Product cockpit, master data integrations.
Admin console, time for performance tuning.
With strong SAP integration and process driven.
Conduct PoC, assess security and integration challenges, and build internal and external forces in parallel to manage the cost.
Many features but requires knowledge to leverage.
Though challenges with integration but manageable.