Hybris Multi-Channel Suite – a quick review

Hybris Multi-Channel Suite – a quick review

Recognized for its multi-channel ecommerce offering and a flexible architecture, Hybris poses a strong competition to IBM and Oracle (ATG) in the enterprise eCommerce software space. Hybris Multi-Channel Suite offers to build a consistent customer experience across multiple channels like online web storefront, mobile storefront, print, brick & mortar stores, customer services call center and social media.

Hybris Multi-Channel Suite is a J2EE based multi-tiered eCommerce framework that can deliver most use cases in B2C as well as B2B scenarios. Interestingly, similar to Elastic path, Hybris leverages several Open Source project for it’s eCommerce Suite like Spring Framework, Ehcache, Apache Solr, Hibernate Validator, Apache Commons, Google Guava and Jasper Reports. Hybris adopts a loosely coupled product architecture, that’s based on extensions and modules, making it relatively easy to integrate new features and functionality into your deployment.

Hybris is a good mix of product and framework – when deployed, it offers a functional  B2C storefront out-of-box so you don’t have to develop your storefronts from scratch; it also offers rich API that allows you to customize as well as develop storefronts from scratch. Hybris also offers templates, accelerators and applications that add rich set of features to your deployments – although charged separately, these can reduce your development efforts and time to market. These components include B2B application, web content management capabilities, product information and content management capabilities, B2b, B2C and multichannel accelerators. Hybris offers a developer friendly Eclipse based development framework and web based interface for administrators and business users.

Predominantly a European player, Hybris had it’s initial share of success in the region. Hybris make inroads into the North American geo thought it’s partnerships and partners network  but with limited success. This is expected to change with Hybris acquisition of iCongo in August 2011. iCongo is a Montreal (Canada) based eCommerce vendor and offers Hybris a strong customer base in North America along with an easy access to the market. A strategic move that’ll help Hybris shed it’s European vendor image as well as offers a near shore customer support presence – limitations that has been hindering it’s growth in the region. iCongo also brings Cloud hosting experience, and a strong Order Management and Warehouse Management capabilities to the Hybris product offering.

If you are a non European customer looking to make a decision on the product, do keep in mind that it may not be easy to find experienced Hybris architects and developers; most Hybris partners are also Europe based service providers. That said, I’ve spoken to  several service integrators in the recent past (including a few global players) who have started building expertise on Hybris as the number of customers asking for Hybris expertise is on the rise.

2 thoughts on “Hybris Multi-Channel Suite – a quick review

  1. Pingback: Hybris Multi-Channel Suite – a quick review « The Web & Content Stream

  2. Srini

    Thanks for your article on this. I’d appreciate it if you can shed some light on some questions I have regarding Hybris:

    1. Given that it leverages on several open source projects such as spring, does a developer on this platform has access to the APIs and features of such modules (again such as spring, solr etc.)? – Similar to as if the developer just downloaded the jars and worked with it directly. Or does the developer’s interaction with these features/modules is necessitated via some proprietary container-specific wrappers?

    2. How smooth and timely does the platform support upgrades when the underlying framework has moved on to a newer version (such as spring2.5.6 to spring3.1?

    3. A similar question regarding the build process – if currently building the project based on Ant is supported, how about other approaches to build – using Maven – for instance?

    4. Same question about specific deployment process such as using Jenkins for continuous integration?

    5. And finally, why aren’t there white papers or technical articles I can find for this platform?

    I’d appreciate any insight on all of this.

Leave a Reply

You have to agree to the comment policy.