IBM Digital Commerce vs. Kibo eCommerce

I think WebSphere Commerce is well suited for customers looking to sell products online that need robustness and scalability as a priority. It provides a complete order cycle out of the box, or you can integrate with your existing order fulfillment. Online shopping models like digital subscriptions or a marketplace are not well suited as it requires a lot of customization

Incentivized

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.

Incentivized

• Websphere commerce provides efficient contract based pricing. Contract based pricing greatly helps in handling prices for different business
• Catalog filtering is one other strength of websphere commerce, as it helps to filter the show only those products that the customer is entitled to
• Extended site model is one other strength of WCS as it greatly helps in having multiple e-commerce sites for different demographics, for branding etc

Incentivized

• 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.

• The e-Marketing spots contain content associated with marketing activities to target customer segment - needs some improvement. The algorithm to set up the priority of each of the Web Activity with in eMarketing spot is little bit confusing.
• The catalog load can be simplified.
• WebSphere Commerce is a huge application - someone needs to spend at least 5-6 years to learn about the whole application.

Incentivized

• 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.

The scalability and various configurations of the product allows for a wide range of e-commerce site features. It provides a storefront to begin with so it helps with speeding up development.

Incentivized

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.

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

IBM Digital Commerce was a lot more customizable and had a good engine for us to make enhancements. We were not locked down to certain integrations and we were able to utilize a lot of the features outside of the box vs using a prescribed set of features and functionality that other tools would force us to use

Incentivized

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

Incentivized

• For our clients in the apparel industry, the flexibility that WCS provides to scale up really helped their online business to grow tremendously.
• Our client in the restaurant industry can't quite leverage what WCS has to offer though as it doesn't really fit their shopping model.
• Another positive impact is that it allows our clients to streamline their commerce system in interacting with their backend.

Incentivized

• 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