Optimizely Customized Commerce is a headless PaaS commerce solution built to scale commerce results for enterprise brands.
N/A
Spryker Cloud Commerce OS
Score 6.0 out of 10
N/A
Spryker Cloud Commerce OS is a modular Commerce System that enables B2B, B2C, and Marketplace business models through any customer interface, touchpoint, and device. Boasting extensibility, best-in-class performance, and fast time-to-market, the vendor states Spryker is trusted by brands such as TOYOTA, HILTI, and TomTailor. The Spryker Cloud Commerce OS NOW version has been specifically developed for manufacturers and brands who want to reach customers directly online.
Our experience may be unique because we opted for an Epi core team to implement our website/console set-up and connection to our PIM and ERP. The experience may have been different with a 3rd party or it may not have. That said, we have been live with our primary website for almost 2 years and I still do not consider it was ever "done". We have been going back and forth on functionality issues and bugs since launch. I have low confidence that changes made the previous day will 100% be online the next - so my team rechecks the work they did the previous day to ensure everything is online. The addition of a second channel and enhancement requests have compounded the issues. I feel this product would work fine with singular or less complex market SKU offerings.
Spryker is very well suited (B2C and/or B2B) for big companies with complex and individual business models or also if your company needs a certain level of customization. Very good fit, if you need a scalable system. It is rather not the perfect fit for small companies or companies with very basic E-Commerce needs.
Episerver has a robust discount engine. This engine, combined with "visitor groups" allow our marketing department to categorize customers and offer a variety of discounts to targeted customers at specific times.
Episerver has a full-featured, storefront experience that can handle everything you might want for an e-commerce website.
Episerver offers A/B testing that can be helpful for trying out new content ideas and tracking the results.
Support. Episerver used to have direct support and access to the tech team to discuss and resolve issues. The new support portal is not enough for developer needs.
Quality Assurance. We find issues in the Episerver code that should have been resolved in QA before release.
Sales. Episervers sells the framework as a solution while showing Alloy. While it helps Episerver sell more, it puts the implementation partner into trouble as the client thinks they bought the solution. Episerver does not provide a solution. It provides a framework that you can build a solution on.
Content - content administration is not a strong part of Spryker, although it improved over the years. I still see room for improvement in the world of bigger CMS systems being able to also do "commerce".
Backoffice-usability - for non-technical users the first few days, weeks and month[s] can be full of surprises. An extended documentation, or more intuitive handling on the backoffice could serve every party on Spryker.
Off-the-shelf internationalization - Spryker right now comes with an initial data set in English and German, which is for a German based company already a pretty stable starting point. Extension on the base data for Europe-wide used countries would be very helpful - French, Italian, Polish, Russian, etc.
Really want to be able to spend more time and resources on rolling out new things with Episerver but at the moment we seem to be fixing alot of issues and pain points with the way our system was setup.
The administrative interface is largely intuitive and relatively easy to use. The complexity of business needs and ability to customize can affect this (i.e. you have to set up and develop with the user in mind), but the basic structure is largely solid. There are some areas of redundancy (such as Commerce Manager overlapping with other administrative areas) that can sometimes cause confusion or offer some functions in one place, whereas other related functions are managed on a completely different page.
Spryker's usability depends a lot on custom development. Therefore, I would like not to consider usability as something that comes with Spryker Cloud Commerce OS. Spryker Cloud Commerce OS; however, brings all the tools needed to design a solution with great usability.
We had an incredible team at Episerver Supporting us with the go live, reviewing our integration, and pushing our integration partner to deliver a quality product
Support suffered from Spryker Cloud Commerce OS's rapid growth. Contacts, department heads, and support systems changed frequently. Support processes as well as documentation are rather poor. One notices that they are putting more effort into the customers recently, but in the course of growth, there is still a lack of focus here. As a customer, I would like to see growth at a slower pace and a phase of stabilization.
Fully understand what is OOTB feature of the platform before proceeding to develop. Then implement a customization of key features once you can prove they are working as OOTB to make them more user friendly and productive for the business. Eg pre order and e gift card
Optimizely Commerce Cloud offers a very wide range of features for admin users. There is less a need for an IT specialist or programmer to be involved when changes need to be made.
If you compare Spryker with commerce solutions on the market, you will notice that the focus is not on the front end. Spryker assumes that the store is only one of many possible channels through which customers order today and in the future. To understand the differences, one must therefore take a look at Spryker's architecture. This is divided into the Spryker [Cloud] Commerce OS (the backend with all process-related components), the front-end modules for B2C and B2B, as well as the integration modules (middleware) and interfaces (Glue API).
Extending the reach and visibility of the brand through content and commerce.
Increased customer satisfaction through better accessibility (self-service) and easy access to important product information (CAD data, technical documentation, etc.).
Rapid deployment thanks to packaged business capabilities and clear development leads to fast ROI and low TCO.
