CommerceV3 vs. Kibo eCommerce

I believe CommerceV3 (CV3) is best suited for small to mid-level catalog companies. You would want to make sure to integrate CV3 with your back end system or you'll be doing a lot of manual entries or manipulating data for table uploads. You can easily manage the templates in CV3 with a basic knowledge of HTML and work up from there

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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• CV3 provides us a plethora of marketing tools to customize offers and campaigns to our customers. I've used BigCommerce and Shopify and neither comes close to the capability of fine tuning sales, offers, and discounts by product, category, customer and more.
• The purpose of partnering with any e-commerce platform is to provide a secure site and stable checkout process for our customers. CV3 has been amazing at keeping our site up and running through peak traffic and attempted hacks. The checkout process has been rock solid and also integrates seamlessly with PayPal. I've used Amazon Payments in the past without incident, but decided to end that option due to Amazon's policies.
• CV3's architecture on the back-end is designed to be plain and simple which provides an easy-to-use interface to streamline our work. The template driven structure to manage the front-end will become a favorite for most programmers in no time at all. In fact, I'm not a programmer, but do customization and design changes almost on a daily basis with ease. Any changes made to a template may be viewed on a staging server before pushing live. Templates, as well as other data may be downloaded any time for backups. Exports and imports of product data is simple and powerful allowing me to change massive amounts of data easily.
• Customer support is always a contentious issue with most providers, however, CV3 has by far been the best I've encountered in over 30+ years of experience with software vendors. They are very responsive and escalate the issue to the proper person without having the redundancy you experience with so many other companies. They understand the issue the first time, and tell you the truth.
• Any e-commerce business is about shipping. CV3 has the most powerful tools to control shipping. It will challenge the most creative minds on how to best merchandise products based on weight, dollar amount, global geographical location, dimensions, category, exception rules, by carrier, all the way down to the sku level which can have it's own set of rules. It gets complicated, but it works great and ties in with the promotional features as well.

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

• An area I'd like to see enhanced is the sku level pricing calendar. You can set specials prices to start and stop at certain dates and times, but it's fixed to certain years. You can't have your chosen items go to seasonal pricing every year at the same time, you have to change the years each year.
• There are multiple product setups: basic, parent with children, and sub-products. Each type exports on the same datasheet all intermingled and this can be tedious isolating the different types for editing and re-import.
• Vendor and Brand are data points on each item, but they are not controlled by a table. We end up with the same vendor or brand misspelled multiple times.
• There is no FTP capability (PCI issue?) and no blog site with the parent domain. These have to be handled using a separate sub-domain.
• The shipping calculator for customers should be available anywhere there is a shipping option presented during checkout.
• Faster live times. Currently, it takes about 5 to 10 minutes to see template/product changes pushed to the live cdn.

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

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

In my view, CV3 meets our needs better by allowing us a much easier way to manage the front end the way the templates are structured. BigCommerce recommended using an FTP tool to download, modify, then upload. Shopify has some very sophisticated templates, which, in my mind, required a senior level programmer or lots of outsourcing for even minor changes. Neither of the other systems come close to CV3's marketing capabilities through their promotional tool without any add-ons. Shopify, for example, is stripped down and if you want a certain feature you have to find one of their approved partners, sign-up, integrate the feature and hope it works. To purchase all the features we're currently using in CV3 you'd have quite a list (and expense) of partners. Examples would be enhanced shipping capabilities or the ability to customize a product purchase. CV3 has features specifically geared for a catalog company, like request forms and capturing key codes. Plus, built-in rewards program, wishlist, gift certificates, bulk email, and data feeds for Google Shopper, Channel Advisor and SingleFeed.

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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• One positive impact has been the use of product reviews. This feature has helped us weed out bad products and promote good ones while allowing customers to share their experience.
• It's a fixed fee user agreement which favors increasing sales.
• The stability of the checkout process has helped conversions and lowered support.
• Having integrated inventory with our back end has helped meet customer expectations.
• The promotional capabilities of CV3 has allowed us to provide new and different offers keeping customers engaged.

• 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