CommerceV3 vs. Yo!Kart

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

Yo!Kart is well suited for a multivendor market, an online market with multiple shops selling products. Yo!Kart would work well for an organization with limited resources and little to no software engineers. The FatBit team is very competent and skilled at making the changes needed to support your needs.

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

• It has a very simple to use user interface
• They provide us many revenew options, such as PPS and more.
• The customer service is magnificent!

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

• Providing individual sellers more access to their customer's contact information.
• Update their documentation to reflect recent upgrades.
• better support for Third Party Integrations.

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 tested almost 10 different products and Yo!Kart was a clear winner for us. The possibility to customize the marketplace and add all new functionalities was better than on the other products.

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

• It has allowed our vision for a resource marketplace to become a reality.
• We are below our budget estimate for the project development.
• A negative impact has been the long development process.