Magento Open Source vs. Spryker Cloud Commerce OS

It's well suited for large eCommerce stores as it requires much effort to set up and the development cost for setting it up is high. It's less appropriate to use Magento where you are looking for quick development and launch of the store. Also, it is required to have a developer or sometimes the entire tech team to manage an e-commerce store, so you may need to hire a few PHP developers.

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.

• Magento is perfect if our web design client likes a specific pre-made template and wants a fast solution.
• Magento allows us to customize its open-source code to create additional features and functionality.
• Magento saves small businesses time and money if they only need a simple solution.

Incentivized

• 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

• Magento 2 community is full of known and new bugs with long-pending pull requests and the community is on the hook for changes. Submit an very obvious issue to the github repo, and you will likely be met with a "this is open source and you use at your own risk." I counter this poor attitude with the fact that open source community has standards, and we do not label a "release" until those standards are met. Otherwise it's just a alpha, beta or numbered build. We don't release obviously bad software until it's fully working.
• Magento is expensive to maintain. You will need a well-paid php developer with apache and hosting knowledge, or you will have to hire an external firm. Either option will turn your website into an additional $100k/yr cost center, so you'd better be ready to ramp up sales. Every feature update or bugfix in the past year has uncovered more bugs, which my devs fix, but at the cost of timelines and billed hours way outside of my budget and target dates.

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.

It's the dominant force in the SMB open source market. With the continued support of eBay/PayPal, Magento will continue to evolve and should be a market leader for some time.

Magento has a relly step learning curve. This means that you need to find experienced developers who can lead junior ones, otherwise the overall development process can be a disaster. However, once you are comfortable in developing on the platform, the customization capability are basically limitless and you can adapt the platform to any use case you can imagine. Also, there are many alredy developed marketplace modules that can solve, out of the box, many problems you may face.

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.

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

Shopify is a closed ecosystem; the moment a client has a complex, custom workflow or needs to integrate with a legacy ERP system, Shopify’s app-based model falls short. WooCommerce just does not scale like Magento, and its architecture is not made for enterprise-scale e-commerce. SAP Commerce Cloud is a very close competitor, but it comes with licensing costs and sometimes can be overkill. It's, however, perfect if the customer already has something SAP in their ecosystem.

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

• Better Total Cost of Ownership than bespoke e-commerce solutions due to being open source and the wide range of free/commercial extensions available to extend the platform.
• Often more extensive to set up and maintain than other open source alternatives, such as WooCommerce.

• 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