Likelihood to Recommend The platform has flexibility at its core and we have made full use of that capability. Even if Kibo [eCommerce] hasn't been ready to provide features and functions we need, we have the opportunity to build them ourselves. The platform started as Mozu and while it was relatively well-developed for DTC, it lacked a lot of basic B2B functionality. As a result, when we were ready to move into that arena, we built a lot for ourselves (including a multi-level account system and a tool to manage it). Keep in mind, too, that Kibo eCommerce is part of a larger suite of tools. The company has purchased a mobile Point-of-Sale system, Baynote, Certona, Monetate, and an OMS. If you need a full-scale solution, they can offer a lot. As I mentioned previously, their support and documentation need shoring up. They're not terrible, but they hinder (rather than help) when it comes to fulfilling the platform's promise of letting the customers be self-service in building out their capabilities.
Read full review 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.
Read full review Pros Mozu offers a flexible multi site setup where you can feed multiple sites from the same product and order database. Mozu allows you to create as many attributes as you would like across customer, orders, and products. This flexibility can be really powerful. Read full review 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. Read full review Cons Prebuilt Integration - There is not currently a large number of preexisting integrations, but custom integrations are fairly quick Time to Deploy - Don't get me wrong, We have deployed in the timeline we expected, but if you are trying to get something off the ground fast, Kibo might not be right for you. It is a robust platform that take some time to get up and running. Complicated Shipping - if you have a complicated shipped process, you might want to look for a tool to help, Kibo does not have very robust out of the box shipping capabilities. Read full review 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. Read full review Usability 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.
Read full review Support Rating One positive note is that I have always been able to get someone on the phone in support whenever I have called, even at 1 AM. Getting someone on the phone is only half the battle though. In the first few months of using Mozu it often seemed that support didn’t know anymore about Mozu than we did. This has slowly started to change, but as a daily user you are likely to be on par with support in terms of knowing what to do when you encounter a problem. The support phone number is really most useful for having them put in a support ticket for you rather than typing it all out yourself and emailing it. It is very rare that the support reps are actually empowered to solve the problem at hand. Unless the issue you are having is user error, they will just take your information and pass it on the proper department. Your request or problem will then be ignored for months on end. Some day, it might actually get fixed but you are unlikely to be notified that this has happened. Most of these issues are assigned an internal ID that they use for tracking. Support is more than happy to pass this ID along, but it is useless. There is no way to actually see where the issue lies in the endless queue of similar issues.
Read full review 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.
Read full review Implementation Rating At the time of our implementation Mozu did not have any processes or procedures set up around going live. We basically were forced to just wing it and hope for the best
Read full review Alternatives Considered We had a custom, in-house ecommerce website before moving to Kibo. It was brittle, slow, and wasn't going to scale nearly well enough or fast enough to keep up with our requirements
Read full review 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).
Read full review Return on Investment Kibo has always delivered rapid & exceptional support to our organization Kibo has been cost-competitive when considering other vendors The platform continues to add value without requiring substantial additional investments Read full review 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. Read full review ScreenShots Kibo eCommerce Screenshots Spryker Cloud Commerce OS Screenshots