Likelihood to Recommend Well suited for our needs of multiple images for auto auctions from a variety of sellers. Pointing them to one platform is easier than attempting to use a variety of platforms as we were doing before (email, slack,
Dropbox and
Google Drive would randomly be used by a variety of employees )
Read full review 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.
Read full review Pros Flexible. This CMS can be easily extended and provide access to dynamic content Simple. The WYSWG is very easy to work with and identifying pages and content in the system is fairly easy Clean Interface. The interface is clean and uncluttered keeping focus on the content and not other factors. Read full review 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. Read full review Cons Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either. There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly. A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through. Read full review 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. Read full review Usability 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.
Read full review Support Rating 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.
Read full review Alternatives Considered In the past we've used
WordPress to manage documentation content.
WordPress was more flexible than Contentful but also prone to inconsistencies and we ended having a lot of hacks to accomplish various
WordPress tricks. With Contentful there's less ambiguity so content producers are less likely to go astray. We also have our own in-house programmatic template solution for managing content, but this was a previous pain point when we needed to get the dev team to do a deploy for every content change.
Read full review 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).
Read full review Return on Investment Positive - new hires are able to get onboarded quicker with us using Contentful Positive - we can customize the journey of what modules/material the user sees after a course/video/article Positive - it's been an overall game changer when hiring external candidates who need extensive training Read full review 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. Read full review ScreenShots Spryker Cloud Commerce OS Screenshots