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
X-Cart
Score 7.8 out of 10
N/A
X-Cart is an eCommerce and shopping cart platform built through PHP code.
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.
X-cart uses Smarty Templates in a PHP environment which means there are many developers who could probably pick it up relatively quickly to provide new features. The smarty template engine is very robust and well documented, and the cost of x-cart is very low which makes it easy for anyone to get started with their e-commerce business. It is a really great e-commerce software and suitable for every business. I actually cannot find any serious objection to what it does. They regularly update it, add new features, fix flaws, offer support. The software itself offers many integrations for shipping and payments, everything you need for sales. Although it covers many things, there will always be something missing, because many things happen in between customer visit and final delivery. Therefore, if you plan to expand your business, also plan to expand your X-Cart - but do not worry, it won't be hard.
For everyone. From small to huge business you get everything out of box. Just setup company details, payment and shipping methods and you are ready to go.
Upgradable. There are many plugins one can integrate with X-Cart. Over time, many of them became part of the software, and you are one click away to enable them.
Well organized code. It uses Smarty template engine, which I find great, specially for debugging (famous Webmaster mode).
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.
Creating new plugins the way X-Cart wants is maybe not complicated, but hard to implement because there are no hooks. One has to manually change each file. This is similar to patching the core and therefore one has to know basics of web development.
Even if you get everything styled correctly with base skin, there is a bunch of unused styles you have to cope with. Start skin should be much cleaner. You may find thousands excess lines of code.
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.
Flexibility in presentation as well as functionality
Full open source software allows for unlimited possibilities with the store function, though some developers who create modules do encode their modules which have errors in their code which therefore can't be fixed
A fully functional professional level application at a fraction of the cost of similar applications such as magento.
