Our primary use cases for Spryker are within a B2C marketplace setting. It enhances digital commerce operations and provides a composable solution for activating or disabling features as needed.
Spryker Cloud Commerce OS
Spryker Systems Australia Pty Ltd.External reviews
External reviews are not included in the AWS star rating for the product.
Offers a huge coverage of features that are needed for marketplace businesses
What is our primary use case?
How has it helped my organization?
Spryker has helped us by offering a huge coverage of features that are needed for marketplace businesses. It also includes a framework feature called Stage Machine, which allows us to adapt the checkout process to our needs with a lot of flexibility.
What is most valuable?
The platform's composability is valuable as it provides a variety of extensions to interface with other solutions.
Additionally, its API-first approach facilitates everything through the API, allowing for externalization or the use of preferred solutions within the same stack. The integration capabilities are particularly beneficial.
What needs improvement?
Spryker, even with its native features, often requires some development and configuration into the code, which is not straightforward in the beginning. The framework approach assumes you might not need to develop. In reality, native features sometimes need development. An improvement could be in reducing the amount of initial development work required even when native features are used.
For how long have I used the solution?
I have been working with Spryker Systems for six months.
How are customer service and support?
The customer support has been responsive, although sometimes the documentation can be outdated, requiring us to seek additional support.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Prior to using Spryker, I worked with other technical solutions.
How was the initial setup?
The initial setup was moderately challenging. It is well-documented. However, there are some cases where the documentation can be outdated, necessitating support. I would rate the experience as eight out of ten for ease of setup.
What other advice do I have?
Overall, I would rate the solution an eight on a scale from one to ten.
A Robust and Versatile Platform for Developers
great product easy to use
A promising start
I m still learning
Pros and Cons of a Robust E-Commerce Solution
It has a modular and customizable setup that allows users to choose and integrate the features and third-party services they need.
It has a growing and innovative solution that is future-proof and offers a fast time-to-market.
It has a higher cost and maintenance effort that may not be suitable for small or budget-conscious businesses.
Modular and flexible Commerce Framework
- Provides lots of OOTB features
- State machine provides lots of flexibility when it comes to customizing the OMS part
- Motivated and skilled people behind the product
- Smooth GoLive experience
- Access to production system (logs etc.) needs improvement, but already on the roadmap
- Hiring people with relevant experience is quite hard since the product is relatively new
Digital Commerce PaaS service, supporting various e-commerce use-cases, in a comprehensive package
Enterprise-grade architecture, API-first
Scalable Cloud-based offering
Clear onboarding process
Lacks in certain key funcional areas, especially in Marketplace module
Complex Solution with potential to become the leader in E-Commerce
- 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
- 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