iSpring Market vs. Spryker Cloud Commerce OS

iSpring Market is suited for small organizations with limited staff and limited IT resources. Allowing users to self-register is a huge time-saver for small organizations. SEO, Google Tag Manager and SSO are included and easy to set up. For the most part, the documentation is good and the help desk provides timely customer service. iSpring Market is not the best tool for larger and more sophisticated organization. It's extremely difficult to get global reporting data, it doesn't import data from other systems, and it only exports a limited amount of data for use in other applications such as business intelligence software.

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.

• It is easy to use.
• It works with Stripe.
• The UI is clean and intuitive for customers.

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

Incentivized

• There are few global reporting features. I can get specific information on a user or a course, but there is no easy way to find users who made an account and didn't enroll in a course. You have to look at every user, or download spreadsheets and search.
• There are very few hooks available to Zapier to transfer data to other services.
• You can't transfer data into the iSpring Market using Zapier, so we can't use our member management system to populate courses.

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

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.

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

We picked iSpring Market because of cost, maintenance, and easy of use.

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

• We have saved thousands of dollars a year in licensing fees compared with other products we used.
• We have eliminated the need for contractors, to build content for iSpring Market, saving tens of thousands of dollars, because we can publish directly into the system using iSpring Suite.
• We get 80% fewer help desk requests for enrollment and payment compared to the last two products we used.

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

Incentivized