Adobe Commerce vs. Drupal

Primarily B2C focused, I think that the B2B features are increasing but the core focus of the platform (and Magento) is really consumer-based. That said, if you are looking for the fastest time to market with minimal investment option then Adobe Commerce is likely not the option that 9 out of 10 people would opt for nowadays.

Incentivized

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

• The ease of use with page builder requiring no developer skills to maintain most of our pages.
• The catalog is straightforward and easy to use and having the ability to update pricing and other key pieces based on customer group is very helpful.
• Many of the extensions Adobe Commerce has help us to do what we need to do more quickly without a great deal of development efforts and cost.

Incentivized

• 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

• Magento Commerce Cloud can be complicated to develop for. In our field, it has been a struggle at times to find qualified developers.
• Our merchandising team sees performance issues from time to time. Updating a product and waiting for the change to clear the queue can take up to an hour in some situations.
• Because of the incredible amount of features that Magento Commerce Cloud offers, training new employees to use Magento takes a long time.

Incentivized

• 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

It has the best overall price point. It is super cheap and the connection between our ERP system is unmatched by any other Ecommerce sites we have talked with. We honestly can't get this level of complex customization without having to spend a fortune somewhere else. It is able to do everything we need it to do for the right price.

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.

Being unable to store quotes for later was annoying. People called up expecting to pay there and then, and having to place them on hold whilst you added items to the basket and input all their customer information in was annoying for them and us, making us look unprofessional.

Incentivized

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

The technical service was impeccable. They were on point and were very knowledgeable.

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.

Great value for an flexible, open source platform.

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

Magento Commerce was previously put into place and used right when I came onboard. We used it for quite some time, but ultimately the need for our company's specific customizations became too difficult to manage during core updates. We specifically needed a more specialized way of calculating shipping, connecting with our 3PL's inventory API, managing specialized discounts and codes, and even the way we showcased information on the product pages.

Incentivized

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

• Great for SEO. We have been able to build out a huge number of highly targeted pages on the site that have propelled our SEO to the next level
• Magento plugs in with many third party tools including ERP's, CRM's, shipping tools. It is a core part of our tech stacks and has allowed us to improve our capabilities as a business.
• Has enabled us to provide a best in class web experience for our customers. We are constantly expanding the capabilities of Magento and to improve sales and grow our business.

Incentivized

• 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