Optimizely Commerce Connect is a PaaS e-commerce backend solution coupled with Optimizely's PaaS CMS to help e-commerce organizations, of any type, create highly customized websites and buying experiences with a two-in-one content and commerce solution.
N/A
Spryker Cloud Commerce OS
Score 6.4 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.
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
More Pricing Information
Community Pulse
Optimizely Commerce Connect
Spryker Cloud Commerce OS
Considered Both Products
Optimizely Commerce Connect
Verified User
Anonymous
Chose Optimizely Commerce Connect
In my opinion, Sitecore is a developers and users' nightmare. Terrible UX. Way behind on the curve. Don't recommend.
Alderich Web Solutions worked great for us however when it came to diagnosing and fixing issues with the website we had to rely on the support with little ability for us to "get under the hood" and look at the issue for ourselves. After switching to Optimizely, having this …
Stibo STEP MDM was a powerhouse. It seems we could do anything we could dream up, but we also had an in-house IT dev team to support it. The cost was the reason we went with Optimizely Commerce Connect. We did not explore HubSpot for this project.
Optimizely Commerce Connect 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.
Optimizely is more flexible and more customizable, but also more efficient from a development standpoint. Salesforce Commerce Cloud has more capabilities but is more prone to become complex, and also generally more expensive. Magento is a comparable alternative but with less …
Just depends on the use case. Some clients are more heavily weighted towards a marketing CMS and don't need a ton of complex technical functions of their eCommerce platform. For these we recommend Episerver.
Episerver did not have a headless CMS offering when we implemented. They may offer one now, but they are very late to the game in offering an API-based CMS experience. If you use an Angular or React front end, and you want to communicate with this incredibly expensive product …
Episerver's plug and play architecture is the winning factor comparing to AspDotNetStorefront. We did not choose Magento because it was not built on .Net.
Coming from a Software Engineering background, Episerver was the preferred system as it was an attractive platform from a developer's point of view. Today, I consult solely on Episerver solutions and still prefer the platform for multiple reasons (some already covered earlier …
Episerver was by far the most user friendly content platform allowing our business to easily manage the content with ease resulting in an overall productivity increase and time for the team to spend less time doing content management and more time managing the personalization …
During the evaluation, Episerver was by far the most flexible as far as features and implementation go. Some of the more SaaS-based products don't allow for the level of customization needed for our clients, clientele. While the other platform boasted similar features, they …
Overall, Episerver seemed easier to use from a user perspective and easier setup. There was also preexisting resources with Episerver experience. Factoring in costs it became an easy solution.
I did evaluate other products in addition to Episerver. The other finalist was Magento, which has a very robust cart and a large market share. I have used that platform in the past and overall had been happy with it's performance. I ultimately selected Episerver because it was …
Spryker Cloud Commerce OS appealed to us because they have open code, the licensing model was better compared to most vendors, and you have a high degree of developer freedom. The approach of composable commerce is good to integrate it into existing infrastructure, which is …
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 …
Spryker as a PaaS solution allows individualization on code and project level. Developers enjoy working with Spryker due to its modular structure as it is easy to learn, code and customize.
It was mostly the fit for purpose for a proof of concept and the wide variety of out-of-the-box functionality that was convincing. As a platform itself, many aspects were very similar across the different platforms.
Spryker is a PHP and open-source stack-based solution, it's more a component framework, and not a traditional software product. You build your own custom solution based on best practices.
There is Hybris and salesforce which I was thinking to choose as an opportunity. The selection goes to Spryker Cloud Commerce OS, cause it brings in all the most value for us as an agency and much more for our customers. All in all, Spryker Cloud Commerce OS has everything that …
Spryker offers the customizability of Symfony but adds predeveloped features and an infrastructure that is more suited for e-commerce projects. Because of it's structure and used patterns the code can be understood between multiple developers and even different companies that …
Spryker is more advanced and allow more customization. The storefront is already fast in Spryker default implementation without any special settings. Spryker Commerce OS also fit better with complex business requirements and have a clearer approach to connect with third-party …
We worked with other Shop-Solution frameworks like shopify, shopware or woo-commerce, and similar. The way how Spryker Cloud Commerce OS was built - namely from the technical pov first - is probably the biggest argument why we are working with it for our enterprise level …
We integrating different ecommerce systems for our customers, but as I hear - Spryker has the most flexibility and most professional tech stack. They have a good focus on performance.
Very strong fit for mid-sized organizations that need more flexibility and customization as compared to canned or template-based offerings, but also want the efficiency and externalization that comes with a pre-existing, cloud-hosted platform (as compared to a full custom offering). Works well with a PIM and more mature catalog data in order to fully leverage the dynamic data capabilities.
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.
Web content management -- the interface is drag and drop and makes it very easy for business users to create product pages.
In site search with Episerver Find -- it is easy to promote attributes and make quick tweaks to fine-tune results.
Integrate with other systems -- we have integrated with our ERP, our product information management system, our digital asset management system and our marketing automation system to take advantage of investments we have already made in content and customer data.
Extendable - you can extend the core functionalities to every business need.
Scalable - the technical implementation supports a highly scalable system approach.
Adjustable - besides implementing new functionalities the core functionalities can be adjusted to the business needs.
Up-to-date - compared to other E-Business solutions, the technological foundation of Spryker is growing, with the technological development and implementations [which] are kept up-to-date with quarterly releases.
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.
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 job functionality is one of the strongest benefits Optimizely offers. It allows a savvy user to quickly go in to a given job, see the job history to find errors and then even take the steps of a job, copy the code and paste it back into your source to diagnose a potential issue.
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
Stibo STEP MDM was a powerhouse. It seems we could do anything we could dream up, but we also had an in-house IT dev team to support it. The cost was the reason we went with Optimizely Commerce Connect. We did not explore HubSpot for this project.
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).
Time-To-Market: With Spryker you can run MVPs in less time and you can test new functionality with certain groups of users.
Due to its speed it is very likely to have reoccurring customer because of a very good customer experience.
With Spryker our customers increased their revenue especially in times of Corona where orders doubled and Spryker was able to cope with the load with no substantial increase in server power.