TrustRadius Insights for Spryker Cloud Commerce OS are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Reliability: Several users have praised the Spryker Cloud Commerce OS for its reliability. They have found that the software consistently performs well, without experiencing any major downtime or technical issues.
Scalability: Many reviewers have highlighted the scalability of Spryker Cloud Commerce OS. They appreciate that the software can handle high traffic volumes and accommodate their growing business needs without compromising performance or stability.
Flexibility: Users have expressed satisfaction with the flexibility offered by Spryker Cloud Commerce OS. They mention that the software allows them to customize and adapt their online store according to their specific requirements, providing them with a solution that is tailored to their unique business model.
With the help of Spryker, I am able to address the following challenges in our business: combining product information from different APIs/third-party systems (akaneo, navision), making products available on different platforms via glue API, and creating data feeds for third-party consumers.
Pros
Speed
Scalability
Structured complexity
Cons
Store relation on concrete products (incl. further product relations such as attributes etc).
Multi-store capabilities in ONE database.
Likelihood to Recommend
There is a flat product structure - complex product structure (see improvements).
[The business problems Spryker Cloud Commerce OS address include] modular shop system in b2c business scope, [and the] redesign of legacy system. With Spryker, we have a standard system [that] helps us to address problems with an idea of its solution: integrate complex third party systems, like ERP, CRM and PIM.
Pros
[A] lot of suitable standard modules
Strong, sens[ible] data structures
Scalability
Cons
Multistore functionality is not completely thought through
Multi-tenancy is not completely thought through
Products and attributes per store
Likelihood to Recommend
Spryker [Cloud Commerce OS] is easy to customize. [It] has very detailed documentation, with data models.
VU
Verified User
Director in Information Technology (501-1000 employees)
We are an agency and are looking for a modern and flexible solution for our clients that can meet the complex and individual requirements of our clients.
Pros
It's a very flexible framework.
It helps to realize different and complex E-Commerce scenarios.
It comes with a lot of different modules and functionalities.
Cons
It is complex to implement due to its modular approach.
It is price-intensive.
Likelihood to Recommend
Spryker is particularly suitable for complex and individual e-commerce scenarios, such as complex B2B scenarios or marketplace solutions. As a result, Spryker is not the right choice when it comes to standard scenarios with low complexity, as the system is not an out-of-the-box tool, but requires configuration effort.
We implemented Spryker Cloud Commerce OS for different scenarios and requirements. Whether for marketplaces that bring together many users in different roles, B2B procurement platforms that map large assortments and product data volumes, or service platforms that establish completely new usage models.
Pros
Spryker Cloud Commerce OS is performant, especially if you have millions of products and transactions.
The software architecture of Spryker Cloud Commerce OS is modular and adaptable.
Spryker Cloud Commerce OS offers many features out of the box.
Cons
Getting started with Spryker Cloud Commerce OS for new developers is not trivial.
Likelihood to Recommend
For quickly building a global marketplace with millions of products and millions of transactions, Spryker Cloud Commerce OS is just what you need. Especially individual processes and requirements can be implemented very well with Spryker Cloud Commerce OS. For a small store project, however, I would not use Spryker Cloud Commerce OS, as there are simpler solutions out there for that.
We were looking for a solution that would fit the many requirements that our previous platform could no longer cover. Therefore, we conducted an evaluation and Spryker emerged as the winner. It is being used by a department, after collecting experience, maybe rolled out in the whole company of the clients.
Pros
Flexible eCommerce framework.
Fast time to market possible.
Deep understanding of the market.
Good network for partners.
Cons
Initial high investment.
Complexity need expert skills.
Implementation partner qualification.
Likelihood to Recommend
I would recommend Spryker to anyone looking for an innovative solution with many capabilities. It is also important to keep in mind that it is a framework and nothing out of the box. It's well suited for B2B challenges with international approach.
Spryker is the most scalable and flexible PHP based commerce enterprise system on the market. We use it to solve complex challenges that other technologies couldn't manage.
Pros
Scalability.
Modularity.
Process design.
Cons
APIs could be improvred.
Updateability.
Likelihood to Recommend
Best PHP based commerce system for highly customized applications integrated in complex system landscapes. Not necessary the best/cost effective system for standard style commerce business model of the last decade.
The Spryker Commerce Cloud OS is used in order to address the requirements of our customers ranging from basic B2C to complex B2B e-commerce scenarios. By making use of the high modularity and flexibility of Spryker, we are able to integrate it into the infrastructure (ERP/SAP, CRM, CMS, ... ) of our customers and extend standard functionality by customized solutions. Furthermore, Spryker allows us to freely decide between the usage of Spryker PaaS for hosting or to realize highly customized solutions in Azure/AWS.
Pros
Flexibility
Extensibility
Cloud Ready
Support / Contact to Developers
Cons
Updates / Long Term Support
API / Interface Stability
Third Party Integrations
Likelihood to Recommend
Spryker is well suited in complex B2C and B2C scenarios in which customers want to realize rather sophisticated transactional processes and therefore want to make use of existing functionality that has to be adapted and extended in order to custom tailor it to their individual needs.
Spryker is a less good fit for use cases in which only very basic needs need to be fulfilled.
We implement solutions for customers based on individual requirements. Our customers facing different B2B problems which can be solved in different ways; we combine all required components individually.
Pros
Separate frontend and backend tasks (jobs).
Technical system abstraction (container components).
Technology separation between frontend and other backend components.
Cons
Update and maintenance over the customer product lifecycle.
Internal API improvements.
Likelihood to Recommend
It depends on the customer requirements which product (not Spryker) maybe is a better solution for a start of a project. Important here is also the project setup on the client-side (project team, budget, etc.).
We are using Spryker to develop an e-commerce website; we are working to migrate an in-house shop to a completely Spryker shop Since it is an e-commerce framework, it already has everything we need for an online shop that can run well: A frontend online shop for customers, using Elasticsearch for searching products and Redis for storage. A backend UI for a back-office employee can update products and other information.
Pros
Modular architecture: Very clear, scalable, and easy to maintain.
Elasticsearch for searching.
Clean code base, follow SOLID Principle.
Frontend with atomic Design, BEM methodology.
Support polyfill.
Cons
Documentation for implementing React is still sketchy.
Bridge is superfluous in my perspective.
Likelihood to Recommend
Spryker is a huge platform with many build-in modules, provides solutions for almost every trouble you will get when building an online shop. It is really well suited in case your shop aims for having millions of users, cross country. However, if you just want to build a small simple shop with fewer features, you don't need to use Spryker.
At NFQ Asia, we use Spryker to build e-commerce solutions for some clients. The Spryker Commerce OS solves different problems on both B2B and B2C shops. It establishes a standard of organising the codebase structure, designing our database, connecting to third-party applications, etc... Furthermore, Spryker Commerce OS is highly flexible, allowing us to customise the shop to the varying needs of our clients. There are also many pre-built packages that we can start using immediately with a minimum effort for configuration.
Pros
Well structured codebase architecture.
Flexible to extend.
A good built-in solution for search.
The state machine for business processes.
The default implementation is already scalable.
Support multi stores.
Cons
The documentation and developer bootcamp is sometimes out-of-date.
Open code, not open source, all bugs need to be submitted to an internal system without accepting patches from communities.
Steep learning curve.
The bridges at the core level sometimes cause difficulties in project-level implementation.
Likelihood to Recommend
It is well suited for medium to large shops that need to connect to different external systems (PIM, CMS, CRM, OMS, etc...). The Spryker architecture makes it plays nicely with varying models of deployment. However, both software engineers and DevOps engineers have a steep learning curve to develop the Spryker shop correctly. This solution may not be the answer for small businesses that want a lightweight e-commerce solution.
