CommerceV3 vs. Drupal

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

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

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

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

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

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

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.

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

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

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs