Optimizely Configured Commerce vs. Spryker Cloud Commerce OS

The eCommerce catalog side has a lot of benefits to it and has been much easier to work with and customize than the CMS side. It is this integration and using both for a branded marketing website that has the user journey from browsing and leading into the eCommerce side that has been the bigger challenge, outside of the overall stability of the releases with the bugs we have encountered. I think the solution is well suited if you are mainly a catalog site. We, however, sell machinery and solutions that are not sold via the eCommerce site and we need to showcase them on the website. However, we have a core industrial catalog of consumable products that support the machine and solutions purchases which are very well suited for the eCommerce catalog. It is the CMS/Catalog integration that has caused a need for more customizations to the platform and as a result increased costs to maintain, lowering our overall ROI from the solution. We are also a bit hamstrung by having to rely on our development partner to make changes that our digital agency is better suited to do for us in the CMS. It is requiring extra cost and resources as a result. If more functionality could be surfaced, it would be much better.

Incentivized

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.

• Integration Jobs/Connections - Providing a good out-of-the-box solution to hook into ERPs and common endpoints.
• Design and Development Partner Network to work with - If you have customizations in mind, the Optimizely partner network will give you the chance to find a suitable partner to meet your needs.
• Good layout/flow/settings breakdown - There are a lot of "redundant" settings, but the more management access, the better.

Incentivized

• Data Importers - Spryker is able to cope with large chunks of data ingest e.g. from PIM or ERP. Its integrated Middleware of handling this data.
• Scaling - Modern architecture makes it possible to scale flexible.
• Internationalization - Role our your shop with different assortments, pricing and products with out of the box features.
• Pricing - Spryker supports custom pricing out of the box (volume prices, gross/net prices, customer specific pricing).
• Order Management.

Incentivized

• Need the ability to look at more of our user data
• Need the ability to refresh our sandbox environment with production data in quicker, more efficient ways
• Classic CMS is very limited in ways end users like myself can edit widget content

Incentivized

• 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.

Incentivized

Quite flexible and easy to use for daily marketing user tasks, like updating page listings, promotions, and copy. More in-depth tasks like managing product attributes, rearranging product taxonomy placement, and CMS editing are not user-friendly and require a careful and detailed process to follow.

Incentivized

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.

It's a mixed bag. The team has been very nice, but there has been an underlying feeling of condescension because we have complained or "caused trouble" over the inadequacy of the CMS component. Also, support for modifications or UI changes has been terribly slow. Understandably, COVID has made life hard for everyone, but there is an expectation that we complete our work immediately, but their team will "put it in queue" when we have a request or find a bug. Further, we certainly feel that we were sold a list of capabilities that we have not seen come to fruition. Finally, the change of ownership 3 times (Insite -> Epi -> Opti) over our implementation period has been both confusing and disruptive.

Incentivized

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.

Incentivized

I was not very involved with this process. It has been 3 years since we made a decision and I can't even remember the name of the other companies we were considering. I was in a different role then so I was less involved with the eCommerce department. I do remember really liking the people we were working with. That played a huge role in our selection since we would be working with them for years on the site.

Incentivized

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).

• Automation of updates and integration with ERP has saved time and provides reliable data for the website in sync with ERP
• Integration with external PIM has saved time and provides reliable sync with content data for the website. Changes and improvements have been slow and difficult.

Incentivized

• 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.

Incentivized