Through the ability to consolidate disparate knowledge repositories either through synchronous\asynchronous, API batch, synchronization or other custom methods, I can disseminate as much or as little data through the widest variety of channels. Redundancy is minimized. The creation and re-use of content is easier. Multithreaded workflow processes minimize bottlenecks.

Generally, as a customer, you will visit the store, purchase the product and the store may deliver on the same day or on the next day or whenever. It is a physical visit and then you're going to get the delivery. You visit the store, you pay and then you come back and the particular product will be delivered to your home. In our case, the customer can be anywhere. He or she visits the particular website and selects the product online. They can see all the features, and then pay online. The website itself will suggest on so and so date it'll be delivered. Based on the date provided, that particular product will be delivered. Post delivery, you can call the customer care. They will come and install. It is all online. You need not go to a physical store. With the click of few buttons with your mobile device or with your notebook or laptop you can purchase the products at your home. Whatever household appliances, it can be refrigerators, microwave ovens, washing machines. We really have lot of products.

We can set up catalogs for our Hybris customers. One is an inventory catalog and another is a product catalog. Every catalog comprises two things, the daily version and the online version. These are figures that you can see for review purposes to determine that everything is fine. Once you approve the changes, it is clearer on the online version and readily available to the customer.

Furthermore, in the online catalog you can provide all your content pages, like your home pages, your product pages, your cart pages. What do they all look like? You can drop a component, and at the same time you can design a component. Let's suppose you want to create a subscription component from your homepage for the very first user. You can wrap, you can get the full component, do modeling in your code, just do a small reflection in the JSP. You configure the JSP, and create a particular component and drop into your home page at any place.

You have to create a slot across their few sets of slots, slowly providing you a better hybrid. For the slot, the main slot, the right and left slot, and center slot. But if you want a particular slot to be created for a particular component, you can create those slots by writing in a text file - just the configuration. Those slots are then available on your page. You just need to map them your JSP page, on the front-end file, and drop your components into the index. The index is another feature of Hybris. It basically allows you to import and export the data from the Hybris system.

When you drop a component there's an ingredient level on that site. So I can do everything. The back-end mapping is already there. Whenever they are forcing some data, it is back-end and needs to be written by the developer. It basically captures the front-end information from the form you entered and stores it in the DB.

So behind that layer are all Spring MVC models. We can look at the structure. You enter the data and Hybris builds the information and storage. It uses all MVC packets to handle this.

One of the clients that I'm working with is a post office, and they have a very large volume of traffic. In fact, they have nearly one million unique users per day. With this level of traffic, they wanted to use it for other things as well. To best take advantage of it, they decided to build a marketplace into their website.

SAP Hybris provides very good integration for a market place. There is a solution called Mirakl, which has a partnership with Hybris and they provide ready-to-use code for building a marketplace. The whole project took between six and eight months for the first version, and it was a huge success. In one year, we spent eight months developing and four months testing all of the processes, but we have a marketplace ready and currently, we are receiving a great benefit from it.

We have another client in France that had an event running, and they wanted to present their e-commerce websites at the event. We didn't have much time, perhaps five or six months, and they wanted to have a first version ready. It was a really complicated project, but since SAP Hybris provides all of the core features and our team is experienced, we successfully created the first working version in the allotted time. In turn, they were able to present their first version at the yearly event. That was another success.

All products reside in SAP and all other systems access and update their products and prices in one place. It reduces redundancy

It is still under study, but we think that this tool will achieve its objective according our experience during the PoC.