fabric vs. Spryker Cloud Commerce OS

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.

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

Incentivized

• The documentation and developer bootcamp is sometimes out-of-date.
• Open code, not open source, all bugs need to be submitted to an internal system without accepting patches from communities.
• Steep learning curve.
• The bridges at the core level sometimes cause difficulties in project-level implementation.

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.

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

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.

Incentivized