Spryker Cloud Commerce OS - A new player in the e-commerce market
Overall Satisfaction with Spryker Cloud Commerce OS
At TOWA we are using the Spryker Cloud Commerce OS for more complex and bigger scale e-commerce enterprise projects. Currently, it's our standard framework for that kind of software project to help our clients to go into the digital market. The projects normally involve the integration of 3rd party services like PIM, ERP or other systems. We do have 2 dedicated teams to work with Spryker Cloud Commerce OS at the moment and we are growing.
Pros
- Best Practices integrated into the framework like SOLID Principles, Enterprise Architecture Design Pattern, etc
- Clear structure of the system components (zed, yves, glue, middleware, ...)
- Migration Guidelines for the available modules
- Number of modules
- Documentation which is getting better
Cons
- Current Documentation
- Developer Bootcamp
- Eco-System for finding already existing custom modules
- 3+ Enterprise Level Clients
- 1Mio+ in more Income
- E-Commerce as a new market
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 software projects. In that area we didn't find another suitable solution for us.
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 software projects. In that area we didn't find another suitable solution for us.
Do you think Spryker Cloud Commerce OS delivers good value for the price?
Yes
Are you happy with Spryker Cloud Commerce OS's feature set?
Yes
Did Spryker Cloud Commerce OS live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Spryker Cloud Commerce OS go as expected?
Yes
Would you buy Spryker Cloud Commerce OS again?
Yes
Comments
Please log in to join the conversation