I worked on Spryker Systems during my last project for Redington. They were selling B2B products on their site, which contained the custom checkout, custom cart page, and quote page that we generated. In Spryker Systems, we have Yves and Zed folders for the back-end, so creating modules requires knowledge of core PHP. The business logic works in layers; there are four layers in its architecture: business, business logic, front-end layer, and application layer where I had to work. Additionally, there is middleware through which I had to pass business logic to the front-end or vice versa to the back-end. I can confirm that Spryker Systems can be used as a multi-channel platform. In my projects, I used Spryker Systems as an e-commerce site. It contains B2B and B2C, and it is language-based. I was able to change the language in multi-stores and utilize it according to my requirements for Spryker Systems. If Spryker Systems could improve their code to reduce the layers, that would be beneficial. They are using the facade design pattern in coding; if they could use the factory or repository directly in the front-end or back-end, wherever the developer wants, that would be advantageous. This feature is what I would like to see added.
My main use case for Spryker Systems is very broad. We are creating a store and developing the API for headless purposes. We custom-created over 70 APIs here. Additionally, this system has over 120 stores, and we provide the product data feed to that system. It is a Fortune 500 company, and the daily hits on the system are around eight to nine million, which we are processing. The best part is that we optimized the system to have an API response time within 500 milliseconds, where the structure of the response of the Glue API is approximately a thousand lines.
Associate Staff Engineer at a tech vendor with 10,001+ employees
Real User
Top 10
Mar 7, 2026
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.
Head of IT at a tech vendor with 10,001+ employees
Real User
Top 20
Mar 7, 2026
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.
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 Systems offers a flexible and scalable commerce platform designed for businesses seeking tailored digital solutions. Its modular architecture and API-driven functionality support customized applications across complex business landscapes.Spryker Systems empowers enterprises by providing a robust platform with features that cater to the dynamic demands of modern commerce. Engaging both B2B and B2C segments, it allows businesses to leverage its modular system for creating personalized...
I worked on Spryker Systems during my last project for Redington. They were selling B2B products on their site, which contained the custom checkout, custom cart page, and quote page that we generated. In Spryker Systems, we have Yves and Zed folders for the back-end, so creating modules requires knowledge of core PHP. The business logic works in layers; there are four layers in its architecture: business, business logic, front-end layer, and application layer where I had to work. Additionally, there is middleware through which I had to pass business logic to the front-end or vice versa to the back-end. I can confirm that Spryker Systems can be used as a multi-channel platform. In my projects, I used Spryker Systems as an e-commerce site. It contains B2B and B2C, and it is language-based. I was able to change the language in multi-stores and utilize it according to my requirements for Spryker Systems. If Spryker Systems could improve their code to reduce the layers, that would be beneficial. They are using the facade design pattern in coding; if they could use the factory or repository directly in the front-end or back-end, wherever the developer wants, that would be advantageous. This feature is what I would like to see added.
My main use case for Spryker Systems is very broad. We are creating a store and developing the API for headless purposes. We custom-created over 70 APIs here. Additionally, this system has over 120 stores, and we provide the product data feed to that system. It is a Fortune 500 company, and the daily hits on the system are around eight to nine million, which we are processing. The best part is that we optimized the system to have an API response time within 500 milliseconds, where the structure of the response of the Glue API is approximately a thousand lines.
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.
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.
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.