Drupal Commerce vs. Adobe Commerce
Adobe Commerce’s paid edition ships the deepest out-of-the-box B2B module of any mainstream platform. It comes with a flexible catalog, native multi-store support, and for the past nine years, has been a Gartner Magic Quadrant Leader. It can do almost anything.
It will also invoice you for almost everything, including license fees that scale with gross merchandise value (GMV) and separate licenses if you want anything beyond the included Page Builder. And it asks for more in return: a heavy infrastructure stack to host and staff, annual upgrades that often break extensions, and security vigilance after three exploited critical vulnerabilities since 2024.
Drupal Commerce gives you the same code ownership without license fees, without a paid tier holding back the important features, and with an enterprise content management system (CMS) built-in. The tradeoff is that more of your B2B workflow gets built to fit rather than simply switched on.
Adobe Commerce and Drupal Commerce have more in common than most platform pairings. Both are PHP applications. Both can be self-hosted. Both let you own your code and reshape the platform deeply.
Adobe Commerce is really a family of products. Magento Open Source is free. Adobe Commerce adds a commercial feature layer, including the B2B module, for a fee. Adobe also sells it as a managed platform as a service (PaaS) called Adobe Commerce on Cloud, and a newer, multi-tenant SaaS edition (Adobe Commerce as a Cloud Service, or ACCS). Picking Adobe Commerce means picking one of those four first.
Read moreFrom Pakistan to DrupalCon Rotterdam: Community, AI, Advocacy and the Future of Drupal
Quality incidents for Drupal Commerce: from the customer's complaint to the repaired item on its way back
A customer writes in: the sole of the left shoe has come away, three weeks after delivery. Someone answers the email, someone else notes it in a spreadsheet, the repair is agreed by phone with the workshop, and when the pair is ready, a shipment has to be made for an order that shipped a month ago. Six months later, nobody can say whether gluing fails more often than stitching, or on which model.
Commerce Quality Incident turns that complaint into a record in the store itself, attached to the order, the order item and the SKU that failed, with its own number, workflow and history. It is free software under GPL-2.0-or-later, published on drupal.org, and it builds on what a Commerce site already has: orders, State Machine, Commerce Log and Commerce Number Pattern. Version 1.1.0 adds the last step: the shipment that takes the repaired or replaced item back to the customer.
What are Drupal Recipes and how do you create one?
Government Summit Speakers Outline Practical Paths to Digital Sovereignty
Qué es Drupal y para qué sirve
Drupal vs WordPress en 2026: cuándo elegir cada uno
Drupal vs WordPress in 2026: when to choose each
What is Drupal and what is it used for
Working with a Drupal agency: roles, responsibilities, and governance
Working with a Drupal agency should give your team room to focus on the business, with a technical partner you can rely on. That gets easier when everyone knows which decisions they can make and when to bring someone else into the conversation. Win an in-kind DEVSUP Drupal 11 Upgrade for your non-profit
The Next Test of Drupal’s Contribution Model
Drupal has long relied on organisations and individuals who contribute beyond their immediate needs. Yet that responsibility remains unevenly distributed. According to figures published by the Drupal Association in February 2025, just 219 of the 1,440 organisations active on Drupal.org accounted for 96% of recorded contributions in 2024. The challenge is not simply attracting more contributors, but making responsibility for Drupal's upkeep more widely shared.
Two proposals outlined by Drupal Association Interim CEO Tiffany Farriss on 28 October 2026 suggest how that might happen. A broader Drupal Certified programme could recognise makers, patrons and advocates, extending recognition beyond agencies. Alongside it, a dedicated maintainers fund could help organisations without development capacity financially support the people maintaining software they depend on.
Together, these proposals revisit Dries Buytaert's long-standing makers-and-takers argument. They also raise questions about what counts as a fair contribution. Financial support cannot automatically substitute for technical responsibility, and certification must recognise different capacities without favouring organisations that can afford to pay. How funding reaches maintainers, and how their work is valued, will matter as much as the proposed framework itself.
Drupal CMS Multilingual Setup: Enabling the Recipe and Translation
In the Open: Security in the age of AI
In the Open is a weekly series from Drupal Association Interim CEO Tiffany Farriss, sharing what she is hearing across the Drupal community and where the Association is headed. In this episode: how AI is changing vulnerability discovery for everyone, what the Drupal Security Team and the Alpha-Omega funded SEIR program have achieved in five months, and how site owners, hosts, and organizations can help.
"In Drupal now that finding these bugs is really cheap, fixing them and fixing it safely is not."
The following is a transcript of Tiffany’s remarks, lightly edited for readability.
What’s changing for everyoneToday I want to talk about security. I think Drupal’s story is about a community that is adapting pretty well to some pretty trying times.
I want to talk about what’s changing for everybody, what we do, what we’ve seen so far, and then how you can help and get involved.
It’s a completely new situation in the last 12 months. AI-assisted analysis is making finding vulnerabilities cheap and automatable in commercial software and open source software. It’s not a Drupal problem. It’s not an open source problem. It’s an everyone problem.
AI is astonishingly good at finding vulnerabilities. And it’s not just individual vulnerabilities, it’s about chaining them together. In COVID, we all learned about the Swiss cheese model of safety, the idea being that the holes in the cheese don’t line up in the various layers. But AI is just so good at figuring out how to chain one vulnerability to another one, to another one, and it navigates it at a pace and in a way that we just haven’t ever seen before.
From an open source perspective, we know that open source is in almost everything. 96% of all applications use open source libraries, and every vendor’s product inherits the security of all of the dependencies, whether they’re in your software or they’re in open source.
Agentic Web Census, el censo mensual de webs preparadas para agentes de IA
Agentic Web Census, the monthly census of websites ready for AI agents
Financial Services Website Design: What the 50 Biggest US Banks Ship, and Where Drupal Fits
CMS for Publishers: What the 50 Biggest US News Sites Run, and Where Drupal Fits
Migrate Redirect Map 1.0: Drupal Redirects for Every Old Drupal 7 URL
PHPStan level 3, constructor property promotion, and other disruptive commits this week in advance of Drupal 12.0.0-rc1
Drupal 12.0.0 and 11.5.0 are scheduled for the week of December 7, 2026. In preparation for these upcoming releases, our schedule targets release candidates for these versions for less than two weeks from now, the week of November 9.
Before we create our release candidates, we will commit several "beta target" changes that are likely to conflict with existing core merge requests. These include issues to increase Drupal's PHPStan rule level to 3 for improved testing of coding standards and static analysis, and specific large cleanups like adopting constructor property promotion and removing a legacy test annotation format. New PHPStan failures are also likely on existing merge requests.
These beta targets need to be committed in a certain order, and will conflict with each other as well as many other merge requests in the Drupal core issue queue. Commits that introduce merge conflicts with the beta targets may be reverted in order to ensure these large changesets can land smoothly without needing to be repeatedly regenerated.
Once the beta targets are completed, Drupal 12.0 and 11.5 will enter their release candidate phase, and all disruptive changes (aside from critical dependency updates and similar issues) will begin targeting Drupal 12.1.