Reviews (1-25 of 31)
Solving the digital challenge it is key to be fast and agile to address the business needs. The fast implementation of Spryker and integration in our system landscape allowed us to deliver an early digital market experience with limit time and cost effort.
- Separation between front-end and back-end
- Headless approach and very flexible [when] used by front-end
- Packaged business capabilities.
- Ready integration with third-party systems.
- Global footprint, especially in China.
- Improvements by the PaaS model.
- Packaged business capabilities.
- Headless approach.
- Separation between front-end and back-end.
- High flexibility and modularity.
- Integration with third-party systems.
- Global footprint.
- Improvements in PaaS.
It is oversized for off-the-shelf e-commerce.
Moreover we have a deep integration of SAP ERP.
- 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.
- 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.
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.
- a fully headless Spryker implementation, which communicates to n-other implementations on the in-house REST-API. This way the "face" of the shop could be adopted to a brand new Frontend technology for web users, and native APPs for mobile users.
- legacy support for an XML integration to retrieve availability, prices and product information from a collection of systems "under the hood".
- multi-nation, multi-language store with a shared product portfolio, but partially limited information on certain nation-language combinations.
- better technical support, if the request comes from a partner vs. a partner in the name of a client
- extended documentation on also older parts which are still relevant in modern Spryker projects
In the correct setup of developers and business, I would always vote Spryker over other e-commerce frameworks like OXID, Magento, or Shopware. Due to its stability and extendibility on the technical side.
- Allows individual extensions for individual customer cases
- Provides a wealth of standardized modules for various business cases
- Drives innovation and encourages customers to think beyond standard usage
- Pace of innovation challenges ability to provide a 100% complete implementation/docs
- Headless-approach/API does not yet cover 100% of features
- Professional B2B service provision through a transactional platform
- Complex availability and ordering models for perishable/seasonal goods
It resolved problems like painful code review and difficult architecture decisions. Spryker’s modular software structure and the separation of backend and frontend interfaces (smartphone, desktop, voice, IoT applications) stand behind these capabilities, ensuring the highest possible performance and enabling agile project execution. For companies with digitization projects, Spryker replaces the standard solutions of software companies to drive IT innovations faster and more efficiently.
- Strong architecture enforcement.
- High frontend speed.
- Less painful code reviews.
- Steep learning curve.
- Heavy vagrant-based setup, docker/SDK solution enabled smoother local environment setup.
- Missing CMS implementation out of the box to choose for the project.
The SLV Group bundles a wide variety of brands, customer groups, products and business models. Therefore, we were looking for a flexible, scalable, future-proof provider and found it with Spryker.
We use Spryker as a central commerce system and as an API layer for the distribution of sales-relevant data.
From a commerce perspective, we were able to greatly expand the relevant share of digital orders based on Spryker B2B software.
Very flexible system to respond to requirements. Good support of the Spryker team in terms of network and in the development of common solutions.
Spryker is also the layer we use to provide our customers with data and accept orders.
With Spryker, we are scaling our business. We are gradually rolling out the infrastructure to all our brands globally.
- The modularization provides the flexibility we need.
- High scalability.
- The support team is very friendly and helpful.
- The learning curve is quite steep.
- Probably not the best solutions for small businesses.
- We don't implement split orders.
- We are able to run a marketplace with suppliers and partners on the same shopping site.
Spryker OS is our solution for a "one product fits all" backend approach:
- quicker testing of mvp products
- reduced dev efforts
- skilled people :)
- clean code
- Front-end performance
- Consistent architecture makes it easier to implement new features
- GLUE API as headless front-end
- Offers a variety of sales channels
- Maintaining (billions of) merchant prices
- Usability of the Zed front-end
- Out-of-the-box SEO capabilities
- 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
- 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 were easily able to implement a feature where customers could filter accessory products in a motorcycle online shop by the bikes they already own.
- Integrated multiple search engines and used them as necessary for a specific context.
- 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
- Development environment could be improved performance-wise
- Experienced developers and architects are needed for customizations
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).
- Implementation of many services like bots. digital advisors, etc.
- Redesign of customer guidance flows
- Placing additional content where it is decisive for purchase
- Bringing a broader customer account functionality to life
- Designing self-speaking product listings
- Implementation of retail media services
- Defines a strict code structure. This eliminates a huge amount of uncertainty at any stage of project development.
- Handles scalability issues out of the box before the scalability solutions may even be needed.
- Provides developers with a high number of possible extensions and therefore reduces the time needed for feature implementation.
- Spryker Cloud Commerce OS requires a lot of boiler plate code. It may be repetitive or overly formal.
- Spryker's core code sometimes is not as high quality as one might expect.
- Great and clean code base acting as reference point and documentation
- Well-defined architecture enabling quick long-term development
- Lots of modules providing standard e-commerce features mostly out of the box
- Extendable and future-proof design
- Steep learning curve
- Requires experienced developers
- Not suitable for small business/project
The Spryker team themselves are effective with resolution of given questions--they respond fast and can provide consultation if need be. I haven't had the need for a lot of direct support, but with the little experience I had, I am satisfied with their technical support.
- Customisable solution for our needs
- Quick implementation - 3 weeks from first offer to go live
- First to understand the business and the needs instead of directly offering a standard product
- Agility of Spryker - much in line with our company DNA
- Be more proactive about what we could do better or in a different way
We solve the following business problems:
- Unify complex legacy landscapes.
- Develop best of breed approaches.
- Fast-time-to-market & optimized TCO by means of MVP approach.
- Large B2C + B2B feature set
- High flexibility to its modular architecture
- High scalability & performance
- Implementation of complex system landscapes
- Development speed
- Expand community
- Improve documentation
- Enablement of developers takes time
- Complex product configurator
- Complex admin roles
- Personalization of the buyer experience
- Distribution of innovative customer self-services
- Quick reaction to requests
- Good overall communication
- Solution-oriented support
- Clean code
- Good overall documentation
- Backend panel can be managed easily
- Easy to add and expand new features due to modular architecture
- Up-to-date technology stack.
- Feature modularization a.k.a. take what you need, leave the rest behind.
- Agency support, enablement services.
- Techstack needs stabilization.
- Development community is still small.
Con: The developer community is fairly small at the moment but has a single hub (Slack channel) that supports the community.
Pro: Enablement services help implementers with difficult tasks.
- Implement complex commerce solutions for our customers.
- Solve high performance issues in e-commerce with the efficient architecture of Spryker.
- Use different solutions (Glue, Yves) in challenging environments.
- High expertise in complex e-commerce scenarios.
- Possibilities to handle complex business logic of our customers.
- Strong support in development of standard solutions.
- Reduce the complexity of the base system.
- Improve the API-driven approach.
- Onboarding process is very complex.
- Commercial video platform - first step in creating a single based e-commerce solutions around all platforms.
- B2C fashion store - high performance issues can be handled efficiently.
- Member checkout for a Sports club - first step in creating a single based e-commerce solutions around all platforms.
Onboarding, workshops and certifications.
Service support from Spryker developers.
For a simple shop which should be set up once and then just run without further investments, I wouldn't use Spryker Cloud Commerce OS. Instead I'd use a standard software like Magento or Shopware.
Using Spryker Cloud Commerce OS comes with a significant learning curve for PHP developers and needs continuous development and maintenance effort. So if you are not willing to invest into a few good developers or a good agency with a longer time horizon, you'd better choose different software.
- Bug reports: They normally react fast but never communicate a timeline for when the bug will be fixed. In addition, in only two years, the bug reporting tool was changed twice and each time a few bugs go missing.
- Feature requests: Same story as bug reports.
- Module development (contracted): Good experience with their requirements engineering; the result was amazing and solved everything we wanted. The development time was pretty good (a few weeks, while we expected a lot more time).
- Community channel: Often beginner questions; hard to find someone to help with hard problems. But a very friendly and welcoming community.
For back-office users, it could be more structured, and a lot of functionality is barely usable within the back office, especially with higher amounts of data. For example, attaching a company user to a company is nearly impossible when the system has more than a few thousand companies. All in all, the back office could be simpler and more workflow-oriented.
- Modular development
- Key checkout functions such as easy payment provider integrations
- Marketplace functions
- Back in store availability
- The Promotion module has room to improve since it is very static. It can be customised in-house though.
- The PDP filters could be more visual and better laid out
- The Content features could be enhanced, the CMS has not been improved in a while
Their latest marketplace releases already deliver top features for companies with complex product catalogs.
We build the digital platform based on Spryker.
A bit heavy for straightforward cases in B2C.
- Data Importers - Spryker is able to cope with large chunks of data ingest e.g. from PIM or ERP. Its integrated Middleware of handling this data.
- Scaling - Modern architecture makes it possible to scale flexible.
- Internationalization - Role our your shop with different assortments, pricing and products with out of the box features.
- Pricing - Spryker supports custom pricing out of the box (volume prices, gross/net prices, customer specific pricing).
- Order Management.
- Marketplace (allow 3rd party distributors to sell via your platform).
- Search (Out of the Box configuration for ElasticSearch could be improved to lead to "better" search results).
- Hosting (usually Spryker is only available hosted via Spryker which is a bit difficult for companies which want to be more independent).
- Have a lot of interfaces to 3rd party systems like ERP or PIM and exchange a lot of data.
- Have huge amount of products and prices e.g. customer specific pricing and a lot of stores (international stores).
- Have very special business process needs which can only be achieved via customization. For instance if you are a steel trading company which has a special business model.
- Very standard end customer ecommerce scenarios e.g. for selling t-shirts to end customers.
- All stores which do not need very customized functionality to fullfil their customers needs.
- Shop which have a turnaround of less than $50 million.
What unites all of them is that all of these platform have a huge customer base which is not able to be handled by other commerce software in terms of scalability and customizability.
We delivered new and innovative business models in different verticals for instance automotive, DIY, heating and sanitary. All of these platforms have different approaches how they sell and deliver to customers which could only be realized by a platform which is as a customizable as Spryker.
On top of that it comes with an open source stack and modern technical framework which gives security and is future proof in the upcoming years.
Spryker Cloud Commerce OS Scorecard Summary
Feature Scorecard Summary
What is Spryker Cloud Commerce OS?
Spryker Cloud Commerce OS Screenshots
Spryker Cloud Commerce OS Videos (2)
Watch Customer Review - Stauff STAUFF is in the machinery and plant engineering sector a leading international manufacturer of hydraulic lines and coordinated solutions along these lines. With Spryker, STAUFF is building a digital platform incl. an open B2B shop.
Spryker Cloud Commerce OS Integrations
Spryker Cloud Commerce OS Competitors
Spryker Cloud Commerce OS Pricing
- Does not have featureFree Trial Available?No
- Does not have featureFree or Freemium Version Available?No
- Has featurePremium Consulting/Integration Services Available?Yes
- Entry-level set up fee?Required
Spryker Cloud Commerce OS Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
Spryker Cloud Commerce OS Technical Details
|Supported Languages:||English, German|