Upgrading from Drupal 10 to Drupal 11: what actually changes
Drupal 11 is a far smaller step than the Drupal 7 to 9 migration was. Here is what the upgrade touches, what breaks, and the order to do it in.
ZooBieDoo Infotech Engineering TeamRead
Key takeaways
- Let the unusual requirements decide, not the feature comparison tables.
- Shopify for speed to launch; WooCommerce for content-led; Drupal Commerce for complexity.
- Integration with stock, pricing and finance is usually the real work.
- Model total cost over three years, not headline pricing.
Start with the awkward requirements
Every e-commerce platform handles a simple catalogue and a card payment. The decision is made by the requirements that are unusual for you: complex product configuration, contract pricing per customer, mixed physical and digital fulfilment, unusual tax treatment, or deep integration with an existing ERP.
List those first. They eliminate more options than the feature comparison tables do.
Where each one fits
- Shopify — fastest to launch, strong hosted operations, and the right answer when your model fits its assumptions. Costs rise with bespoke behaviour.
- WooCommerce — sensible when the site is content-led and commerce is a component rather than the whole business.
- Drupal Commerce — strongest where the product model is genuinely complex, pricing rules are unusual, or commerce must sit inside a larger content and workflow platform.
The integration question
For most established businesses the real work is not the storefront, it is the connection to stock, pricing, fulfilment and finance systems. A platform that makes that integration awkward will cost far more over three years than one with a slightly weaker storefront.
Ask how each candidate handles asynchronous updates from your systems of record, and what happens when they disagree.
Total cost over three years
Compare licence or transaction fees, hosting, the cost of the integrations you actually need, and the cost of maintaining them. A platform with no licence fee but three bespoke integrations to maintain is not the cheap option.
Model it explicitly rather than comparing headline prices.
Questions to ask before you choose
A structured evaluation beats an opinion, and the questions that separate the candidates are rarely the ones on the vendor comparison page.
Ask how the platform models a product that is configured rather than picked from a list. Ask what happens when the price depends on the customer rather than the product. Ask how returns, partial shipments and cancellations flow back into finance. Ask what the upgrade path looks like when the platform releases a major version, and who is responsible for it.
Then ask each candidate to demonstrate your two most awkward requirements rather than a generic storefront. The demonstration you are shown by default is always the one that works well.
Frequently asked questions
It can be, but the strength of Drupal Commerce is flexibility, and flexibility has a setup cost. For a small, conventional catalogue where commerce is the whole business, a hosted platform usually gets you trading sooner for less.
Yes, and it is a common reason to choose Drupal. Keeping editorial content and commerce in one platform avoids duplicated content models and gives one place to manage navigation, search and access control.
Separating the storefront from the commerce engine is a reasonable pattern when you sell through several channels. For a single web storefront it usually adds integration work without a corresponding benefit.
