Spryker Systems Reviews

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.

Spryker Systems' best feature is the publish and sync capability. When we are creating a Glue API, the front end, or the Yves side, this is a very good feature. All data is available in Redis and Elastic. You don't need to run, write, or execute a query for the database. All the data is present in Redis and Elastic, so the response time is very fast. This is the main significant feature in Spryker Systems.

Spryker Systems offers several best features, including that it is headless. All containers are running separately, such as Zed, Yves, Glue, the back office, and the backend gateway. All containers have separate PHP, and all features run separately. Because of that, the performance is very good. A single instance is not executing on the server side. By default, Spryker Systems provides us with the setup for the AWS environment. It is a PaaS system. You simply go and use this very quickly, and no DevOps person is required. They set up everything, such as CI/CD and everything you need.

Spryker Systems has positively impacted my organization because it is very trendy in Austria and Germany. The main scope is that every organization wants to increase its business. When we use Spryker Systems, we can say that we have increased our business.

For Spryker Systems, there is one major issue I see. There are no peer groups or developer channels where we can post our problems. If we go with Magento and other frameworks, there are many developers available there. You can search on Google, and there are multiple solutions available. You can see the solution, apply it, and then determine if you are able to solve your problem. This type of community resource is missing in Spryker Systems, so they need to do a lot of work on their side.

Some user-friendly features are missing in Spryker Systems. Right now, in the present release, they did some things, but they need to do much more from a normal user's point of view. Currently, Spryker Systems is only focused on developer points of view, such as how a developer can extend the functionality or inject functionality into the system. However, if we talk about default features, there are no features. For example, there is nothing for reporting, and if we go with the configuration, only basic configuration is available. No high-level or low-level configuration exists. For example, if we want to showcase something on the cart checkout page, you cannot simply go into the configuration and enable or disable things. These types of features are missing. If Spryker Systems works on these parts, then it is a very cool platform from a user's standpoint.

I have been using Spryker Systems for three and a half years.

Spryker Systems is stable in my experience.

From the scalability side, Spryker Systems is very scalable. There is the multi-feature capability, the modular approach, and multiple things are available from a scalability point of view.

The customer support for Spryker Systems is very prompt. If you raise something, there are multiple incident categories, which means you need a response very quickly if it is a production issue. This is very helpful.

Before Spryker Systems, I was working on Magento in a service-based company that introduced this system. At that time, Magento had some issues, such as slowness. One of our clients was saying that Magento is too slow. That is why we went to Spryker Systems, and Spryker Systems has better features and functionality.

I did not evaluate other options before choosing Spryker Systems. The client suggested we go with Spryker Systems, so we didn't explore other systems.

Day-to-day, I am working on multiple projects that I am handling, including B2B, B2C, and the marketplace. If someone goes to the website or the web app and wants to purchase something, we are creating multiple e-commerce platforms. For example, we worked with the pharmacy or medical domain. Additionally, we also have experience in the automobile domain, and I also have experience in the electronics domain.

The main difference that Spryker Systems has made in my work is that if we have something that we need to create from scratch, there is a chance of increasing bugs. However, with a built-in feature that has been tested multiple times, there is low risk. Spryker Systems by default gives many features. For example, it has a modular architecture. If you want to extend something or if you want to inject it into Spryker Systems, it is very easy. A pretty simple format is present in Spryker Systems. From an extensive point of view or for a large project point of view, Spryker Systems is the best platform right now.

My advice to others looking into using Spryker Systems is that if they have very big product data or they have multiple payment gateways or multiple ERP integrations, they need to think about Spryker Systems. Spryker Systems gives us very extensive support for that. There are multiple things available. You simply go and develop or create a custom module. This is the modular architecture. For that particular size, you can choose Spryker Systems. I have given this review a rating of 9 out of 10.

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.

In Spryker Systems, the most valuable features are that the front-end is a separate part from the back-end. If I am working on the back-end, it is totally different from the front-end. When I connect these, I have a third folder available. When connecting these, I have to use this third folder. The Docker system image container is perfect for load balancing. In Spryker Systems, there is an EAV structure, but creating attributes there is tricky. I can add a basket over the cart; for instance, if I want to purchase bundle items for one customer, then I can add multiple products. After that, I can create a second bundle item in the cart and proceed with that. I can negotiate price there, and this functionality is also provided by Spryker Systems itself.

The price features are good in Spryker Systems. I can manage price according to customer groups or bases, which I think is valuable functionality.

In Spryker Systems, the main issue is that connectivity is too difficult. If I want to make a small change, I have to pass code through three layers: Zed, Yves, and middleware. This takes a lot of time to change things, and creating attributes for customers and products takes a lot of time as well; this is a significant disadvantage of Spryker Systems.

I used Spryker Systems for around two years, during which I developed modules there and some other APIs to connect the front-end to the back-end. After that, I left Spryker Systems.

I contacted their training partners only, not customer support. I believe it was Florin.

To install Spryker Systems on a system, it is easy and not complicated, because Spryker Systems provides a Docker image. I can run two or three commands, and it will automatically install on the system; that part is not complicated at all.

These are my skills and right now these are the skills which I am working on with these products. I am currently working on Adobe Commerce, specifically. I do not have experience with Adobe ColdFusion. I worked on Spryker Systems around one year ago. In the last year, I have left Spryker Systems. We were working on maintenance until December. After that, I completely moved on to the Adobe Commerce project. It is a company project. Our company is providing services to the Redington company, so it is a Redington project. It is only for web. I have not used the headless structure in Spryker Systems. For analytics features, I used a third-party tool like Google Analytics in Spryker Systems, not Spryker Systems itself, to analyze customer data and other user data. I will recommend Spryker Systems. If someone has a big product, then they can use Spryker Systems there. If they do not want to lose customers' sessions or lose their customers, then Spryker Systems is a viable option. My overall rating for this product is nine out of ten.

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.

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.

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.

I have been using Spryker Systems for six months.

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.

Spryker Systems can handle growth and increased demand easily as its scalability is correct.

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.

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.

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.

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.

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.

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.

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.

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.

I have been using Spryker Systems for five years.

Spryker Systems is a good company with good customer support. However, there are also problems and setbacks from time to time.

Negative

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.

My main use case for Spryker Systems is developing a store for ZF Group for car parts. During that store development using Spryker Systems, I had to create an anonymization for users or clients that were unavailable for more than 25 days. The system started anonymization, but it kept the customer ID. When the customer tried to log in again, all the data was restored.

In my opinion, there are no best features on Spryker Systems. It is a very complex system that uses hexagonal architecture and is very complicated. I do not think humanity needs the hexagonal paradigm. MVC is good enough. I do not appreciate Spryker Systems.

Spryker Systems is complicated mainly because of the architecture. You have to write too many classes to do just little things, which is not necessary at all.

I have not noticed any positive impacts from Spryker Systems in my organization. I advised ZF to not use Spryker anymore and use Laravel instead, something more accessible for every developer with better features out of the box and better documentation. It is well written. I do not think Spryker Systems is good for any company.

Spryker Systems creates extra work and delays the development.

Spryker Systems should change to MVC, improve the ORM system, and use more libraries that are known by everybody, such as migrations. I think Spryker Systems should be rewritten and reset.

I have been using Spryker Systems for about three to four months.

So far, as I could see, Spryker Systems is stable in my experience.

I cannot measure Spryker Systems' scalability. I think it would be very difficult.

I did not interact with the customer support for Spryker Systems at all.

I had used YII, CakePHP, pure PHP, and Laravel before Spryker Systems. I was very upset when using Spryker.

I think Spryker Systems is deployed on Amazon Web Services, but there were too many levels and too many pipelines to do the deployment. I think it is just because Spryker Systems is too complicated and too complex. If it was Laravel, it should be much faster.

The company gave us credentials for Spryker Systems. I did not have to do anything.

I have not seen a return on investment with Spryker Systems.

I do not know if my team evaluated other options before choosing Spryker Systems. When I joined the company, Spryker Systems was already purchased and decided.

The advice I would give to others looking into using Spryker Systems is to change their mind. I believe I have said everything about Spryker Systems. My review rating for Spryker Systems is 1.

Spryker Systems is our primary e-commerce platform, and we have developed multiple applications including subscription portals, leasing portals, and billing and checkout functionalities using Spryker.

For example, we designed and developed the entire user interface for Spryker subscription portal and integrated it with the Zuora application for a customer's subscription. On the Ricoh client, a customer logs into our Spryker subscription portal and subscribes for their product through the application.

Spryker Systems has positively impacted us by allowing us to combine multiple applications onto one platform, thus reducing the number of resources required to handle all the applications. It is easy to manage when everything is on a single platform.

Spryker Systems supports us in cost-saving terms due to the requirement of fewer resources, and it also supports our compatibility since Spryker Systems is open for integrations with other frameworks.

Spryker Systems is very useful as we can use it as a user interface and as an entire ERP or CRM system.

Elasticsearch, OpenSearch, Spryker Systems offers the Glue API, and Spryker Systems also offers the directory structure in a proper manner with Yves and Zed separately, in addition to multiple libraries including mailing and checkout functionalities.

I rely on the directory structure and Glue API the most because we have multiple integrations with Spryker Systems.

Additionally, we are using OpenSearch in our day-to-day practice. For instance, we designed a form where we use OpenSearch for a customer. When typing two or three letters, we are able to get a list of the customers and companies in the search box. The admin panel is a very useful feature of Spryker Systems, where we can access multiple options including products, CMS, pages, and blogs, making it easy to build a user interface as per our requirement in Spryker Systems.

Spryker Systems can improve with their setup functionalities, as it is totally based on the Symfony framework and vendor libraries. When we build a Spryker Systems application in our local environment, it is really painful as it takes a long time, and the build requires a high-configuration system to become executable in our local environment. This is an improvement point in Spryker Systems.

I have been using Spryker Systems for about four years.

Spryker Systems has been good in terms of stability.

Spryker Systems has been good in terms of scalability.

I advise them that if they are planning to get Spryker Systems in their local environment or in their day-to-day practice, they need to use high-configuration systems and have a good technical environment in terms of heavy network and heavy systems. I have given Spryker Systems an overall review rating of eight.

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 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.

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.

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.

I have been working with Spryker Systems for six months.

The customer support has been responsive, although sometimes the documentation can be outdated, requiring us to seek additional support.

Positive

Prior to using Spryker, I worked with other technical solutions.

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.

Overall, I would rate the solution an eight on a scale from one to ten.