Ibexa, headquartered in Oslo, helps B2B companies to stay relevant and succeed by transforming traditional sales strategies into frictionless buying experiences, with their eponymous digial experience platform (DXP).
$20,143.81
per year
Spryker Cloud Commerce OS
Score 6.4 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.
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
More Pricing Information
Community Pulse
Ibexa DXP
Spryker Cloud Commerce OS
Features
Ibexa DXP
Spryker Cloud Commerce OS
Security
Comparison of Security features of Product A and Product B
Ibexa DXP
9.0
1 Ratings
10% above category average
Spryker Cloud Commerce OS
-
Ratings
Role-based user permissions
9.01 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Ibexa DXP
8.0
1 Ratings
1% below category average
Spryker Cloud Commerce OS
-
Ratings
API
7.01 Ratings
00 Ratings
Internationalization / multi-language
9.01 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Ibexa DXP
5.4
1 Ratings
28% below category average
Spryker Cloud Commerce OS
-
Ratings
WYSIWYG editor
7.01 Ratings
00 Ratings
Code quality / cleanliness
5.01 Ratings
00 Ratings
Admin section
7.01 Ratings
00 Ratings
Page templates
3.01 Ratings
00 Ratings
Library of website themes
2.01 Ratings
00 Ratings
Publishing workflow
8.01 Ratings
00 Ratings
Form generator
6.01 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Ibexa DXP
5.6
1 Ratings
18% below category average
Spryker Cloud Commerce OS
-
Ratings
Content taxonomy
9.01 Ratings
00 Ratings
SEO support
5.01 Ratings
00 Ratings
Bulk management
2.01 Ratings
00 Ratings
Availability / breadth of extensions
6.01 Ratings
00 Ratings
Community / comment management
6.01 Ratings
00 Ratings
Online Storefront
Comparison of Online Storefront features of Product A and Product B
Ibexa DXP
-
Ratings
Spryker Cloud Commerce OS
7.9
64 Ratings
2% above category average
Product catalog & listings
00 Ratings
8.360 Ratings
Product management
00 Ratings
7.560 Ratings
Bulk product upload
00 Ratings
8.152 Ratings
Branding
00 Ratings
8.253 Ratings
Mobile storefront
00 Ratings
8.451 Ratings
Product variations
00 Ratings
7.863 Ratings
Visual customization
00 Ratings
7.456 Ratings
CMS
00 Ratings
7.258 Ratings
Online Shopping Cart
Comparison of Online Shopping Cart features of Product A and Product B
Ibexa DXP
-
Ratings
Spryker Cloud Commerce OS
8.6
58 Ratings
12% above category average
Abandoned cart recovery
00 Ratings
8.842 Ratings
Checkout user experience
00 Ratings
8.358 Ratings
Online Payment System
Comparison of Online Payment System features of Product A and Product B
Ibexa DXP
-
Ratings
Spryker Cloud Commerce OS
8.4
55 Ratings
1% above category average
eCommerce security
00 Ratings
8.455 Ratings
eCommerce Marketing
Comparison of eCommerce Marketing features of Product A and Product B
Ibexa DXP
-
Ratings
Spryker Cloud Commerce OS
7.6
59 Ratings
1% below category average
Promotions & discounts
00 Ratings
7.957 Ratings
Personalized recommendations
00 Ratings
6.842 Ratings
SEO
00 Ratings
8.151 Ratings
eCommerce Business Management
Comparison of eCommerce Business Management features of Product A and Product B
I always recommend Ibexa DXP to my fellows. The only scenario that I would not recommend it is if the site is either too small, too simple, or that they simply cannot afford to stand it up properly.
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.
Content Taxonomy: Content is managed in a tree. Though taxonomy vs folksonomy is a near-religious debate among professionals, clients seeing the system for the first time just seem to "get it" more often.
Content Flexibility: Common content types such as blog posts and articles are available out of the box. However, customizing these and creating new content types is very easy.
Developer Friendly: Developers need only a little PHP experience to get started. Of course being an expert doesn't hurt and opens the door for the development of custom modules.
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.
It is quite easy to navigate through the backend and also, you can directly work in frontend view. Dynamic content can be created on the fly. Their Landing page features are awesome. You create a page by drag & drop.
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.
They are directly reachable and help you to deal with other services, e.g. if would like to set up a CDN for China or if you would like to integrate a tool like HubSpot. If there is anything you are missing, they help you to find a workaround until they can deliver such items - like local language versions.
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.
eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:
Developers, system administrators, and project manager can all speak the same language during the development and maintenance cycles of a site.
End-user training is very straight-forward.
Vendor support is available.
Client IT departments can access if need (developers/designers/sysadmins).
The community is there (forums) and there are solid contributions (extensions) from both the vendor and the community.
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’ve priced other enterprise products and found Ibexa DXP to be a bit more expensive. However, not enough to dissuade us from staying with the product.
The partner ecosystem is small. However, we've worked with two Ibexa partners over the last 10 years. They were very skilled. They were great companies. We've interviewed other Ibexa partners in North America. We found them all to be professional with solid resumes.
Common knowledge: By making eZ a core offering, developers, system administrators, and project managers were able to communicate with each other effectively.
Training: Due to its content taxonomy, end-user training often went well.
Support: In our case, we had Gold support from eZ Publish which saved time and helped with customizations.
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.