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.
Loading Reviews List....
Spryker Cloud Commerce OS Reviews
12 Reviews
Engineering
Search is temporarily unavailable. Filters are still applied.
We use it for our own brands, as for our retail business. We can easily develop both streams in one platform and share features between the different markets around the world.
Pros
Flexibility to configure each store individually in every detail.
Modularity. Features can be easily be extended or adjusted.
Middleware component connects different ERP systems to our backend.
Cons
Upgradeability. Each ne release must be covered with with a migration document, but its missing most of the times.
Best practices and developer education is lacking of documentation and support.
The vendor platform lacks of test and documentation.
Likelihood to Recommend
Spryker is lacking a lot of standard features or backend views that might be used from other systems. So if you rely on them, you have to develop the most things on your own, which needs time and is most intense. The backend is basically not made for daily shop administration work out of the box. However, if you need a flexible system, which can easily interoperate with different systems, Spryker is a good fit. We can easily connect and integrate with other systems, that are part of the eCommerce system (ERP, PIM, CMS, CRM, etc)
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).
TOWA is an agency that focuses on digital business projects and uses Spryker OS for complex e-Commerce Projects for Enterprise and German Mittelstand (especially in Industry and B2B).
Pros
Supports the business case of our clients by providing out-of-the-box solutions as well as the necessary framework for growth and scalability.
Offers first class service during the projects and is a strong partner for customer success.
Is a strong partner for our company by providing excellent sales support as well as training for our development unit.
Cons
Deployment pipelines (PAAS) service.
More Content Management Features.
Likelihood to Recommend
Spryker offers the best architecture for complex business cases and makes individualization possible without the hassles of update issues or limitations. Plus, Spryker offers excellent onboarding, fast implementation and can be integrated very well with third-party systems like ERP, PIM, etc.
I am a programmer, I am involved in the development of an e-commerce site using Spryker.
Spryker is used as a sales website, as well as a product management page, and a delivery system. These are the main problems of an e-commerce site
Spryker is used by almost every department in the company.
Pros
Good scalability
Provide a complete solution for e-commerce site
Easy to customize and upgrade
Cons
Not suitable for small sites
Likelihood to Recommend
Suitable for large websites need a scalable system, a comprehensive solution in many aspects. Have an experienced development team, develop the project for a long time. There is a server system strong enough to meet the operation of Spryker. Not recommended for small sites, weak infrastructure, few users. Not good for small companies.
It's used to cover business ecommerce requirements of our customers. An additional use case is to add new custom customer features that might be missing in Spryker OS or adjust existing features to customer needs i.e. write an importer module to import them frequently to Spryker product-reviews feature. The main use case currently is to connect external systems with Spryker and provide them in a functional way to a user interface.
Pros
Very good code quality
Heavily usage of PHP feature scope
Always looking for new initiatives and to support latest platform versions
Good Support Desk - Very experienced contacts and professional tech experts
Good focus on technical solvings compared to provide marketing focused solutions
Cons
Part Confusion in Layer structure i.e. GLUE has less features than YVES and ZED is also a frontend but as well a backend API. Frontends could be leaved as frontends and backend frontends are seperate frontends
Lack of back-office / admin API i.e. to import customers, products via API
The company going in the direction to bind customers more and more with SaaS, PaaS, FaaS solutions - but leave no option for on-premise
No example integrations that clarify third partner modules provided in Spryker eco-namespace. This leaves a lot of space for issues and unexpected behaviors (additional work that needs to be done). Would be much better if a third-party integration is covered with a demo integration that can be booted to have more comprehensible estimations for the customer. Currently only ~3 demo applications with mock data. It's not a real-world scenario.
Likelihood to Recommend
It forces you to build code in a maintainable and structured way. One of the key features is that it has less magic and easy-to-follow code. They started to provide a docker setup that works on all OS by abstracting their platform issues. When you start a project, there is always the possibility the customer informs itself about a specific feature i.e. Akeneo integration support or factfinder integration out of the box - but the real world always shows it's not working that way in Spryker. The integrations always have to be adjusted on the project level and are not matching all of the Spryker features they provide - this is a big issue at the moment. The good part is, the existing boilerplate applications with mocked data are very good covered with solved development issues i.e. test execution (e2e, integration, unit), development toolsets, and good example workflow pipeline (phpstan, phpcs, phpmd...), working project level and well-tested feature integrations, automated dependency updates and support for different version combinations like php7.4 + MySQL, php8+psql, etc.
We use Spryker Cloud Commerce OS as a tool for building our clients' e-shop solutions. I supervise engineering teams, 30+ engineers in total working on Spryker. Spryker Cloud Commerce OS itself, helps us in dealing with complex business logic requirements and enables effective scalability for our clients.
First of all, it reduces ambiguities that may occur when the same problem is being solved by multiple engineers. Spryker-imposed code standards help us in keeping our overall project quality high.
Secondly, it helps to achieve faster time to market delivery of our projects. The system itself, allows to parallelize work between engineers efficiently and it takes only a few months to launch even the most complex projects.
Pros
Fast time to market
Well maintainable code
Reduce of the need to have inhouse engineers
Cons
Spryker Cloud Commerce OS requires a lot of boiler plate code. It may be repetitive or overly formal.
Likelihood to Recommend
Spryker Could Commerce OS is very well suited for companies which plans to have a high load/availability systems with large volume of orders or plans to implement an omni-channel business model. To sum up: the more complex your business model is - the more value you van extract from Spryker Commerce OS.
Less appropriate would be to use Spryker for smaller, more standard retail business models.
We implement Spryker Cloud Commerce OS for our customers. They are using it as their main commerce system. Integrating commerce, PIM, and ERP systems is a part of most projects. Increasing revenue and sales conversion by improving the performance and user experience of their commerce system is a major task. Spryker Cloud Commerce OS enables our customers to extend their commerce operations to create a marketplace.
Pros
Front-end performance
Consistent architecture makes it easier to implement new features
GLUE API as headless front-end
Offers a variety of sales channels
Cons
Maintaining (billions of) merchant prices
Usability of the Zed front-end
Out-of-the-box SEO capabilities
Likelihood to Recommend
Well suited for
B2C companies with revenue greater than €50 million
Marketplace approaches
Complex infrastructures where a lot of data integration is required
B2B businesses with a lot of customer prices
Less appropriate for
Small businesses with relatively low revenue and standard requirements for their online shop
Customers with needs for pop-up shops
Customers with no need for high availability infrastructure for their online shop
We are an implementation partner for Spryker Cloud Commerce OS. We implement custom solutions for our customers with Spryker Cloud Commerce OS, which builds the backbone of the online IT infrastructure of our customers and is connected to a lot of other systems and services like ERP, PIM, and others. Together with our customers, we create awesome online shopping experiences with the Spryker Cloud Commerce OS.
Pros
A lot of features out of the box
Possibilities of customizations is huge
Software architecture of Spryker Cloud Commerce OS is great and builds the base for a super flexible and robust software solution
Innovative and fast approach to building modern software
Cons
Development environment could be improved performance-wise
Experienced developers and architects are needed for customizations
Likelihood to Recommend
Well suited: If a customer has special requirements and wants to customize nearly everything, Spryker Cloud Commerce OS is the way to go. Spryker Cloud Commerce OS offers a lot of functionality out of the box--these features can be easily extended and modified for the customers needs--without a big hassle. Having a well tested and structured feature-set in place that can be easily customized is simple awesome--for the customers and also for the developers.
Less appropriate: If there is a small business with only a handful products that doesn't have the intention to grow and add a lot of customizations are also not necessary, maybe Spryker Cloud Commerce OS is a bit to much (also because it has license costs and is not an open-source product).
We are an integrator for Spryker Cloud Commerce OS, and work with the system for more than 2 years now, to provide our clients a solid, stable and extendable platform for their E-Business. My personal involvement is focused on transforming complex B2B-sales models into an online platform, to connect our clients with their clients.
Pros
Extendable - you can extend the core functionalities to every business need.
Scalable - the technical implementation supports a highly scalable system approach.
Adjustable - besides implementing new functionalities the core functionalities can be adjusted to the business needs.
Up-to-date - compared to other E-Business solutions, the technological foundation of Spryker is growing, with the technological development and implementations [which] are kept up-to-date with quarterly releases.
Cons
Content - content administration is not a strong part of Spryker, although it improved over the years. I still see room for improvement in the world of bigger CMS systems being able to also do "commerce".
Backoffice-usability - for non-technical users the first few days, weeks and month[s] can be full of surprises. An extended documentation, or more intuitive handling on the backoffice could serve every party on Spryker.
Off-the-shelf internationalization - Spryker right now comes with an initial data set in English and German, which is for a German based company already a pretty stable starting point. Extension on the base data for Europe-wide used countries would be very helpful - French, Italian, Polish, Russian, etc.
Likelihood to Recommend
From my experience, I categorise client businesses right now in two groups, Spryker-ready and "just not suitable". These two categories are based on the technical background which come with the clients business. If the business seems to be very simple on the outside, but has a lot of technical dependencies, connections and input resources, I would instantly go for Spryker as the architecture and way to implement "data driven" projects - is just supporting the way of consuming "endless endpoints," and present them in a simple way for the clients' customer to pursue the E-business.
On the other hand, projects which have no big technical background but a more complex, or "fancier" presentation, I would recommend a simpler and easier to adjust framework as the overhead are not worth it and the capabilities of Spryker won't be used fully.
