commercetools is an omnichannel eCommerce platform with additional functionality like point-of-sale through cloud deployment.
N/A
Spryker Cloud Commerce OS
Score 6.0 out of 10
N/A
Spryker Cloud Commerce OS is a modular Commerce System that enables B2B, B2C, and Marketplace business models through any customer interface, touchpoint, and device. Boasting extensibility, best-in-class performance, and fast time-to-market, the vendor states Spryker is trusted by brands such as TOYOTA, HILTI, and TomTailor. The Spryker Cloud Commerce OS NOW version has been specifically developed for manufacturers and brands who want to reach customers directly online.
N/A
Pricing
commercetools
Spryker Cloud Commerce OS
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
commercetools
Spryker Cloud Commerce OS
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
—
More Pricing Information
Community Pulse
commercetools
Spryker Cloud Commerce OS
Considered Both Products
commercetools
No answer on this topic
Spryker Cloud Commerce OS
Verified User
Administrator
Chose Spryker Cloud Commerce OS
Spryker Cloud Commerce OS appealed to us because they have open code, the licensing model was better compared to most vendors, and you have a high degree of developer freedom. The approach of composable commerce is good to integrate it into existing infrastructure, which is …
Spryker as a PaaS solution allows individualization on code and project level. Developers enjoy working with Spryker due to its modular structure as it is easy to learn, code and customize.
Verified User
Project Manager
Chose Spryker Cloud Commerce OS
It was mostly the fit for purpose for a proof of concept and the wide variety of out-of-the-box functionality that was convincing. As a platform itself, many aspects were very similar across the different platforms.
Spryker is a PHP and open-source stack-based solution, it's more a component framework, and not a traditional software product. You build your own custom solution based on best practices.
There is Hybris and salesforce which I was thinking to choose as an opportunity. The selection goes to Spryker Cloud Commerce OS, cause it brings in all the most value for us as an agency and much more for our customers. All in all, Spryker Cloud Commerce OS has everything that …
A clear headless / API first architecture is the competitive advantage of the ages Hybris solution. Spryker also shows a cleaner modularisation and with the atomic releases instead of big bang approaches, it takes less effort to stay up to date with the current releases.
Commerce Cloud and Magento were alternative solutions we looked at. Spryker convinced us with the flexibility of the business model through the Packaged Business Capabilities. Furthermore, the headless approach and very flexible by used front-end is to be mentioned as a …
Commercetools is generally a very flexible, smart platform for eCommerce business. It's an API enabled, cloud solution that makes integration seamless and quick to deploy. It's also a modern platform that utilizes API query languages like GraphQl. It lacks some functionalities in pricing and geographic variations of product portfolio but the platform is constantly improving and new functionalities are added.
Spryker is very well suited (B2C and/or B2B) for big companies with complex and individual business models or also if your company needs a certain level of customization. Very good fit, if you need a scalable system. It is rather not the perfect fit for small companies or companies with very basic E-Commerce needs.
Pricing - Commercetools has pricing limitations with respect to customer/SKU combination. If an organization provides lots of custom/contract pricing for customers, Commercetools has difficulty mapping it in. They are working on this to make it more flexible.
Geographic variations in product portfolio - Commercetools has central product master that doesn't provide product activation/enabling based on different geographies/elevation/sales office structures. Some creative mapping skills are needed to overcome this limitation.
Data mapping limitations - Commercetools lacks in out of the box data mapping limitations to full fledged ERP platforms. Extensive data mapping workshops are necessary to fit the functionalities of an ERP platform from order, to delivery , to warehouse operations and billing.
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.
Spryker's usability depends a lot on custom development. Therefore, I would like not to consider usability as something that comes with Spryker Cloud Commerce OS. Spryker Cloud Commerce OS; however, brings all the tools needed to design a solution with great usability.
Support suffered from Spryker Cloud Commerce OS's rapid growth. Contacts, department heads, and support systems changed frequently. Support processes as well as documentation are rather poor. One notices that they are putting more effort into the customers recently, but in the course of growth, there is still a lack of focus here. As a customer, I would like to see growth at a slower pace and a phase of stabilization.
If you compare Spryker with commerce solutions on the market, you will notice that the focus is not on the front end. Spryker assumes that the store is only one of many possible channels through which customers order today and in the future. To understand the differences, one must therefore take a look at Spryker's architecture. This is divided into the Spryker [Cloud] Commerce OS (the backend with all process-related components), the front-end modules for B2C and B2B, as well as the integration modules (middleware) and interfaces (Glue API).
Extending the reach and visibility of the brand through content and commerce.
Increased customer satisfaction through better accessibility (self-service) and easy access to important product information (CAD data, technical documentation, etc.).
Rapid deployment thanks to packaged business capabilities and clear development leads to fast ROI and low TCO.