Composable commerce has supported complex ecommerce builds but documentation still needs work
What is our primary use case?
My main use case for Spryker Systems is primarily for e-commerce. I use it to build new cases in the system as my client requires, exploring the features and conducting proof-of-concept projects over the last six months on how clients work and their requirements.
I do not have anything else to add about my main use case or any other interesting projects I have worked on with Spryker Systems.
What is most valuable?
The best features Spryker Systems offers, in my opinion, is that it is known as composable commerce. It contains numerous features and all the capabilities Spryker has. If you want to use it as a multiple system in a single place, that is the reason Spryker has much capability to achieve in the new AI era. If we want to use anything such as RabbitMQ or Docker, these are the capabilities Spryker has. I recommend Spryker for future clients as well.
Over the last six months, I have found that Spryker Systems' composable commerce and integration capabilities have helped me because Spryker also has the capability with Docker. Using Docker, I can easily install Spryker on my system and utilize Spryker's multiple services such as queue services with a single click. I really appreciate that capability.
Spryker Systems has positively impacted my organization as it is completely new to me. Right now, I am still expanding their features and exploring their capabilities. At an organizational level, I have found that multiple clients want a system that they can easily handle. Spryker is capable of doing it. At the organizational level, I have found many things that Spryker can easily achieve, and that is why Cognizant is ready to extend Spryker Systems' capabilities around their clients.
What needs improvement?
Spryker Systems could be improved if we can reduce the complexity level. The documentation needs to be explored more, and we need to reduce the complexity because Spryker works between multiple systems. That is the reason we need to reduce the integrability. Otherwise, it will be a more expandable format available to developers. It would be better if we provide better documentation.
For how long have I used the solution?
I have been using Spryker Systems for six months.
What do I think about the stability of the solution?
Spryker Systems is stable for me, but there are still many things we need to improve in Spryker to make it truly easy for clients as well.
What do I think about the scalability of the solution?
Spryker Systems can handle growth and increased demand easily as its scalability is correct.
Which solution did I use previously and why did I switch?
I previously used Adobe Commerce solution for the e-commerce system before exploring Spryker Systems. I have not switched to Spryker; I am just exploring the next option for the e-commerce system. I am still using Adobe Commerce and exploring Spryker because sometimes clients want a system where they can easily integrate data. I see that Spryker also has much capability, which is why I think this is the right time to explore their capabilities as well.
What was our ROI?
I have not seen specific outcomes or metrics, but Spryker has many capabilities that reduce a lot of integration. I do not have any specific metrics to share regarding return on investment right now.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Spryker Systems is that the pricing or setup cost is acceptable for me, but we need to provide a version which is publicly available for developers, so it would be helpful.
Which other solutions did I evaluate?
Before choosing Spryker Systems, I explored Shopify and found it to be completely a SaaS-based system. BigCommerce and Shopify provide many capabilities, which is truly easy for clients who want a website that can open up quickly in a day. Most of the time, they go with Shopify and BigCommerce because of the capabilities they have in their SaaS system. In another way, Spryker Systems and Adobe Commerce do not have such capabilities. Adobe Commerce has a SaaS-based system, but it really works and it has much cost, so low-cost clients are unable to purchase those versions.
What other advice do I have?
My advice for others looking into using Spryker Systems is that it depends on their requirements. If clients want to create a system that is large in scope and they want to expand their system, then Spryker is the best option for that type of client. However, it depends on the type of requirements they have. If they want to explore a system at the microservices level, then Spryker is the best option. I would rate this review a six out of ten.
Modular platform has boosted global B2B spare parts revenue but still needs stronger B2B focus
What is our primary use case?
My main use case for Spryker Systems is that we have an e-commerce solution in the company that focuses mainly on spare parts sales, but is not limited to that; we also have other options. A concrete example of how I use Spryker Systems in the spare parts sales area is that it serves as our e-commerce backend system.
What is most valuable?
The best features that Spryker Systems offers, in my opinion, are the modular system, the headless system, and the back office functionalities.
Spryker Systems has had a positive impact on my company because we were able to generate a significant revenue increase in our e-commerce area. That is not only due to Spryker Systems, but also because we placed a strong focus on e-commerce and developed a stable, global platform. Spryker Systems enabled us here.
What needs improvement?
I think Spryker Systems could be improved if Spryker pays more attention to their customers and focuses more on promoting B2B business with new features and use cases that are specifically tailored to B2B sales. There are no other improvements I would like to see for Spryker Systems.
For how long have I used the solution?
I have been using Spryker Systems for five years.
How are customer service and support?
Spryker Systems is a good company with good customer support. However, there are also problems and setbacks from time to time.
How would you rate customer service and support?
What other advice do I have?
I would recommend to others who are considering Spryker Systems that it is not for small companies. The focus should be on B2B sales. Someone who only sells T-shirts does not need the complexity of Spryker Systems.
Decoupled Flexibility with a Learning Curve Challenge
What do you like best about the product?
I really like Spryker Cloud Commerce OS's headless, decoupled frontend-backend architecture. It's the 'North Star' feature for our global operations since it decouples the customer experience layer from the core commerce logic layer. This setup allows us to solve the 'global vs. local' tradeoff, giving us 100% flexibility to build custom frontends for the U.S. and APAC without needing to alter the unified global backend. Additionally, the core cloud-native backend and global commerce foundation are streamlined, thanks to the managed cloud infrastructure and pre-built enterprise modules.
What do you dislike about the product?
I find Spryker's admin interface and backend configuration overly complex, which is built for large enterprise teams. This enterprise-level complexity creates a steep learning curve and daily operational friction for our small team, which manages tasks like regional frontend tweaks and compliance configuration with no dedicated Spryker specialist. Additionally, while the core cloud-native backend is streamlined, the regional customization and admin UI configuration introduced significant hands-on development work and a steep learning curve, especially for a team without dedicated Spryker specialists.
What problems is the product solving and how is that benefiting you?
Spryker Cloud Commerce OS eliminates the 'global unification vs. regional localization' tradeoff and automates U.S./APAC regional compliance. Its headless architecture allows custom, localized frontends without affecting global backend, reducing manual work and maintaining unified commerce data.
B2B-Oriented with Seamless Hybrid Commerce Integration
What do you like best about the product?
I really like that Spryker Cloud Commerce OS has a B2B-first composable architecture. It's specifically built to support the complex, customizable workflows that enterprise B2B commerce demands, like quote-to-cash, CPQ, client-specific catalogs, and approval chains. It provides the scalability, flexibility, and omnichannel unification we need for hybrid B2B/B2C and marketplace models. This makes it stand out compared to other platforms that often treat B2B as an afterthought, whereas Spryker Cloud Commerce OS centers B2B in its design. The platform unifies B2B, B2C, and marketplace models on one cloud-native platform with a single source of truth for all data. I find the centralized order and inventory management feature extremely helpful as it allows us to manage global orders and inventory levels from a single dashboard. It eliminates oversells and stockouts with real-time inventory sync. The native marketplace-B2B integration allows merchants to offer B2B workflows like negotiated pricing and PO payment options, creating a new revenue stream. The setup was structured and manageable for our team, which is an added bonus.
What do you dislike about the product?
The CPQ/quote-to-cash module has a convoluted UI for creating custom quotes, which takes our sales reps 15–20 minutes per quote instead of the 5–10 minutes it could with a more streamlined UI. They often need IT support to troubleshoot simple quote rule logic. The quote approval dashboard lacks visibility features like color-coded statuses and regional filters, causing reps to waste time looking for updates.
What problems is the product solving and how is that benefiting you?
Spryker Cloud Commerce OS eliminates system silos between B2B, B2C, and marketplace operations, unifying data and workflows. It provides a single source of truth, automates real-time inventory sync, and supports complex B2B needs with native integrations, improving customer experience and order management.
Offers a huge coverage of features that are needed for marketplace businesses
What is our primary use case?
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.
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?
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.
Newcomer's Perspective
What do you like best about the product?
The flexibility and modular design, making it easy to build custom, scalable e-commerce solutions tailored to any business need
What do you dislike about the product?
A steep learning curve, especially for developers new to the platform, which can slow down initial development.
What problems is the product solving and how is that benefiting you?
Typical e-commerce issues.
Fast and Secure
What do you like best about the product?
Fast implementation and easy to use for the frontend users
What do you dislike about the product?
Hard to understand how to overwrite the functionalities at beginning
What problems is the product solving and how is that benefiting you?
Spryker Cloud Commerce OS is highly modular and API-first, enabling businesses to scale horizontally and vertically with ease. Its composable architecture allows companies to add or remove components as needed, adapting quickly to changing business needs.
A Robust and Versatile Platform for Developers
What do you like best about the product?
Modular Architecture , Performance, Customizability, Decoupled Front-End and Back-End , good integrated Apis. Overall, Spryker Cloud Commerce OS provides a powerful, flexible, and developer-centric environment that enables the creation of highly customized, scalable, and efficient eCommerce solutions. The platform's modularity, customizability, and robust performance capabilities make it an excellent choice for developers looking to build modern eCommerce systems.
What do you dislike about the product?
Spryker Cloud Commerce OS offers great flexibility, scalability, and customization, but it comes with a steep learning curve, resource-intensive setup, and complexity in maintenance. The platform's powerful modularity can be challenging for new developers, and the cost and ecosystem size may not suit smaller projects.
What problems is the product solving and how is that benefiting you?
Spryker addresses the need for scalable, flexible, and highly customizable eCommerce solutions. It benefits me by providing a powerful framework that accelerates development and supports complex integrations and business-specific customizations efficiently
A promising start
What do you like best about the product?
Spryker has an easy user interface and it's quite simple to step in
What do you dislike about the product?
Difficult to get what are the 'out of the box' features.
What problems is the product solving and how is that benefiting you?
Purchase service digitalization
I m still learning
What do you like best about the product?
The simplicity to manage products, as tecnical datas and other specificities.
What do you dislike about the product?
I feel it is very "product friendly", for other type of contents, its harder to understand what you can do pr not.
What problems is the product solving and how is that benefiting you?
Our clients are able to buy from different dellers in one platform.
