Kibo eCommerce vs. Optimizely Commerce Connect

Mozu is currently not suited for use at any company, small or large. The bugs and lack of features and integrations make it too difficult to use.

Very strong fit for mid-sized organizations that need more flexibility and customization as compared to canned or template-based offerings, but also want the efficiency and externalization that comes with a pre-existing, cloud-hosted platform (as compared to a full custom offering). Works well with a PIM and more mature catalog data in order to fully leverage the dynamic data capabilities.

Incentivized

• Single admin tool for multiple sites is a huge plus. Eliminates much duplication of labor and a shared code base is also much simpler.
• Native responsive design in the latest version is great.
• Dynamic product categories is a big win.

Incentivized

• Web content management -- the interface is drag and drop and makes it very easy for business users to create product pages.
• In site search with Episerver Find -- it is easy to promote attributes and make quick tweaks to fine-tune results.
• Integrate with other systems -- we have integrated with our ERP, our product information management system, our digital asset management system and our marketing automation system to take advantage of investments we have already made in content and customer data.

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.

• Support. Episerver used to have direct support and access to the tech team to discuss and resolve issues. The new support portal is not enough for developer needs.
• Quality Assurance. We find issues in the Episerver code that should have been resolved in QA before release.
• Sales. Episervers sells the framework as a solution while showing Alloy. While it helps Episerver sell more, it puts the implementation partner into trouble as the client thinks they bought the solution. Episerver does not provide a solution. It provides a framework that you can build a solution on.

Incentivized

Really want to be able to spend more time and resources on rolling out new things with Episerver but at the moment we seem to be fixing alot of issues and pain points with the way our system was setup.

Incentivized

The job functionality is one of the strongest benefits Optimizely offers. It allows a savvy user to quickly go in to a given job, see the job history to find errors and then even take the steps of a job, copy the code and paste it back into your source to diagnose a potential issue.

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.

We had an incredible team at Episerver Supporting us with the go live, reviewing our integration, and pushing our integration partner to deliver a quality product

Incentivized

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

Fully understand what is OOTB feature of the platform before proceeding to develop. Then implement a customization of key features once you can prove they are working as OOTB to make them more user friendly and productive for the business. Eg pre order and e gift card

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

Stibo STEP MDM was a powerhouse. It seems we could do anything we could dream up, but we also had an in-house IT dev team to support it. The cost was the reason we went with Optimizely Commerce Connect. We did not explore HubSpot for this project.

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

• Positive: We have a usable website - better than what we had before and we are seeing a constant increase in adoption.
• Positive: Counter associates are using the website to help customers.
• Negative: Too much time being spent QCing previous work.

Incentivized