Download websites that use Drupal Commerce

About Drupal Commerce

Every Drupal Commerce store is a Drupal site first, and the ordering matters more than it sounds. The framework is not a product a merchant buys and switches on. Somebody decided to run Drupal, then decided to sell from it, which usually means the organisation already had a content operation, a development team or a retained agency, and treated the shop as another part of the site rather than a separate platform bolted onto the side.

What that implies commercially is a buyer profile quite unlike hosted commerce. A hosted store is a subscription decision. A PHP framework released under GPL v2 is a build decision, with hosting, upgrades, card data scope and security patching all sitting with the operator or its agency. Sites in the Ecommerce category run from a single embedded buy button to a full order management stack, and this framework sits at the heavy end, which is why the population leans towards public sector, publishing, membership organisations and business to business catalogues rather than small independent retail.

Commerce Guys released the framework in 2011 and it has stayed open source since, which creates a specific gap. No company holds a billing list of who runs it, because nobody is billed. As of October 2026 we detect it on 519 sites, and for a product nobody licenses, a crawl is the only reason that number exists at all.

Detection is inferential and the limits are real. We identify the framework from markup, asset paths and route patterns that the module family leaves behind in delivered pages. A store with a heavily customised theme, an aggressive edge cache, or a decoupled front end that talks to Drupal only through an API can look like something else entirely, or like nothing in particular. We hold no version data for this entry either, so questions about which major release a given site runs cannot be answered from our file.

The people who need the whole list rather than a single lookup are the ones selling into it. Payment gateways and shipping integrations want stores whose module architecture makes them straightforward to plug into. Agencies want replatforming candidates, particularly sites whose surrounding technology suggests an ageing stack. Security researchers want a defined population to measure exposure across. Each row also carries the other technologies detected on the same domain, which turns the file into a map of what these stores are assembled from rather than a flat list of names.