Salesforce Commerce Cloud vs. Spryker Cloud Commerce OS

Salesforce Commerce Cloud is well suited for medium to large sized eCommerce platforms (mainly B2C but B2B could work as well) who are looking to streamline their web processes and website functionalities while incorporating multiple departments. If you are a small business and have tighter margins, this may not be the best choice for you as there may not be as many opportunities to utilize all of the CRM's features and you may be at a financial loss because of it. Otherwise, this platform is great for organization and providing a helping hand in your eCommerce roadmap!

Incentivized

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.

• Demandware business manager features a very robust set of options to accomplish many merchandising and content tasks out of the box. For typical retailers, there are usually very simple ways to accomplish common tasks.
• The ability to schedule content and tie unique content to session data is particularly useful and fully featured.
• Many features that would typically be missing from a home-grown CMS and would require development are included in business manager and easily controlled by marketers.

Incentivized

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

Incentivized

• The #1 pain with Demandware as a developer has been Pipelines. Originally development on this platform was designed as a visual drag, drop, and configure model. You would create these logic flows (pipelines) in the visual editor, made up of nodes (pipelets) and connectors. These quickly got out of hand and turned into a spiderweb. Worse they were not like anything that most developers are used to. Pipelines save to XML but the markup was not clean and difficult to merge or diff, to say the least. I guess they were aiming for a more simple model but quickly realized that was not sufficient for real-world applications. To their credit, Demandware recognized this and has been steadily moving toward a clean, pure-code model.
• The benefits of SaaS and the quick release cycle can be a mixed blessing. Features and API's can and do change from time to time. When you're using a platform like this you cannot build it and forget about it. It's not obvious to everyone but you're signing up for some amount of maintenance over time to keep things up to date.
• The platform has a flaw that still hasn't been resolved. Each Demandware customer "realm" has many instances for development, staging, production, etc. All of the instances have their own user accounts and passwords, and you have to log in to each instance separately. It's very frustrating as an admin or developer, though less so to business users who will only need to access one instance. Demandware could really use a Single Sign On!
• Demandware has a marketplace for third-party extensions to add pre-build integrations with other systems. While there is a reasonably broad selection of third-party vendors, I have to point out that the quality of many of these components has been sub-par. There are a few gems but many are clunky and quickly cobbled together, and surely require further investment of time. Demandware needs to do a better job of quality assurance with third-party vendors.

Incentivized

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

A huge factor influencing our decision to remain on the Demandware platform is that our new parent company is standardizing all its luxury brands in the US on it. We are fortunate. However, even if we had remained an independent company, I believe we would continue on the Demandware platform for all the reasons outlined in this review. I appreciate the stability the platform has provided to our eCommerce site in the last three years as well as the continuous improvements and technological advances being rolled out that will allow us to keep the site fresh, engaging, modern and stable. I've heard many horror stories from colleagues on other platforms who struggle with the expense and complexity involved with making what should be minor and simple changes and updates to their sites.

The overall ease of using the system. Consolidation in location for our team members. Mobile application for on the go research, as many of our team members are constantly traveling to job sites or to meet clients. No more duplicate calls to current customers, since we have 12 different divisions that span the company. Mostly the ability to look at the database when our team members begin cultivating a new
lead/prospect with a potential customer to see if anyone within the team has a
relationship with that person or the company they work for.

Incentivized

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.

We have only had one instance where the platform went down in the time we have been using it.

They are very responsive and a support technician will be assigned quickly. Even if there is further clarification needed for the ticket, or a solution is not immediately available, you feel that someone is there and staying on top of the issue. Most common issues are resolved quickly and satisfactorily.

Incentivized

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.

Incentivized

The in-person training was thorough. Trainer was pretty dry, but covered everything really well.

Implementation went fairly smoothly.

All relative to your organizational size. Shopify works for small to mid, Magento for small to large, commerce tools would be a large-scale plus. Hire a skilled consultant to help you make a decision of this caliber!

Incentivized

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

• Salesforce Commerce Cloud ends up paying for itself in the long run so long as customers are taking advantage of its full capabilities.
• I would highly recommend trying it or consulting a partner like us about it if you have an interest and think you could benefit. A thorough business analysis will tell you if this segment of Salesforce is right for your objectives.

Incentivized

• Time-To-Market: With Spryker you can run MVPs in less time and you can test new functionality with certain groups of users.
• Due to its speed it is very likely to have reoccurring customer because of a very good customer experience.
• With Spryker our customers increased their revenue especially in times of Corona where orders doubled and Spryker was able to cope with the load with no substantial increase in server power.

Incentivized