What do you like best about Spryker Cloud Commerce OS?
- The willingness to support and help their clients is second to none
- Spryker cares for their client's success and invests massive effort into projects
- Platform offers extreme flexibility to build whatever is needed in a relatively short time
- Architecture and modularity are future-proofed when compared with other E-Commerce platforms
- Developers like using concepts and technologies Spryker is based on
- Spryker is regularly evolving, i.e., the academy is regularly adding new courses/trainings, Spryker App Composition Platform, etc.
- If you have an experienced internal dev team composed of med/sen FTEs with detailed project plans in terms of scope/timeline/budget, then Spryker is the way to go Review collected by and hosted on G2.com.
What do you dislike about Spryker Cloud Commerce OS?
- Almost non-existing developer community, documentation for developers often not up to date
- Onboarding for developers proved to be extremely long and hard (juniors up to one year, mediors 6 months and more, seniors from 3-6 months)
- Everything can be done; however you must follow the Spryker way (which sometimes is not easy to comprehend) and more than often increasing effort and prolonging the time for delivery
- Best suitable for building MVPs with basic needs in terms of features/functionalities/integrations and then increasing the complexity gradually over the time; in cases when re-platforming is needed, tremendous effort has to be invested in building custom features and functionalities increasing time-to-market
- Not covering complex grocery use cases (catchweight products, timeslots, logistics, integrations), a lot of OOTB features and functionalities provide basics, so they either must be developed from scratch or heavily reworked
- Even though it is PaaS, internal DevOps resources are a must-have, for the majority of AWS settings read-only privileges are granted, increasing the time and effort to make changes (everything has to be done via tickets on Spryker Support Portal)
- Frontend Yves is based on pure js. twig for templates and SCSS making it hard to find/hire frontend devs willing to work with that stack
- Hard to upgrade to newer versions since there is a lot of modules and inter-dependencies to take care of Review collected by and hosted on G2.com.