Kibo Software offers Kibo eCommerce (formerly Mozu), designed to support retailers with online offer creation and deployment, content publishing and landing pages, and many tools and widgets out of the box with a retail-oriented ecommerce solution.
Mozu was acquired by Kibo Software from Volusion in October 2016.
N/A
Webflow
Score 8.3 out of 10
N/A
Webflow headquartered in San Francisco offers what they describe as a visual solution to web design, with a CMS for editors, designers, and developers that they state allows users to create needed content structures, add content (by hand, from a CSV, or via our API), and then design it visually. Webflow service plans also include website hosting, with a basic plan for sites that don't need a CMS as well as CMS, Business, and Enterprise plans. Webflow's ecommerce plans are designed to support new…
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.
Webflow is great for designing pages and creating a really nice looking website, without needing to be a pro designer. However, trying to scale a company blog for SEO leaves a lot of room for desire. There are various SEO-related shortcomings (like how canonical tags are added to pages) and I also need to add a lot of custom code elements to blog posts to get the desired control. This means adding new posts and getting them looking the way we want takes way more time than it should do. Also doesn't support next-gen images, which is impacting our page speed scores and leaving us behind when it comes to Core Web Vitals update. Finally, the fact that only one person can enter the designer at one time is really annoying. I get that the Editor should be the solution to this, but it's so so so slow and jumpy that this is essentially unusable.
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.
It is extremely easy to use, especially with available templates and guides. It is used primarily by accounts and creative rather than dev. It is also easy to import/export projects or duplicate them for re-use and modification for another client. While it is rarely the end platform for a deliverable, it is often instrumental in pitching.
In my experience, their customer service is an absolute joke, I tried reaching out to them they took forever. I had to keep following up with them as if they never received it in the first place. It’s a new platform, so guidance is needed. Tried the university they offer, in my opinion, it is completely useless, I would just completely move on from this website.
In my opinion, it is horrible, the rendering takes forever. I have the newest MacBook and the platform will still lag and slow down on me. I’m not a developer, I am a designer which makes it worst because I am using the features they are providing not extra coding features. In my opinion, it is a horrible platform really, stay away.
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 pay hundreds of dollars a month to Webflow, yet their support is worse than a typical free SaaS product. We were prevented from deploying changes to our site because of how Webflow structures its support. It delayed a product launch for the whole company. Support options? Beg for help on community forums, it took a threat to email the CEO to finally get movement. If there were easy alternatives, we would switch. But for now we just pray nothing breaks and that we don't need to interact with Webflow support.
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
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
The code quality and speed can't even be compared to Elementor; Webflow is simply a much better tool. Instapage has a cool feature for dynamic landing pages, which changes according to Google Ads Keyword, which I miss; however, amazing webflow community members recreated that functionality with a custom script. For the majority of users, it's a safer bet than WordPress in terms of speed and code quality. WordPress could provide amazing results if hosted properly (nginx, caching configuration) and requires best practices to maintain code quality. Webflow solves these issues out of the box at a fraction of cost.
I feel it doesn’t perform the way it’s supposed to and it doesn’t have any beneficial factors to it. In my opinion, there is no reason to use a platform like this when Wix and Shopify, and WordPress exist. I believe Webflow is a platform that shouldn’t exist and it’s only popular because of the hype it received. I tried it and hate it completely.
