Download websites that use Shopware

About Shopware

An ecommerce platform is one of the few pieces of software a company rarely swaps on a whim. A catalogue, a payment integration, a warehouse connection and a trained team all accumulate around it, so the platform a storefront runs on is a reasonable proxy for company size, budget cycle and the kind of agency work the business buys. Shopware sits squarely in that world as a Ecommerce platform written in PHP, published by Shopware AG and distributed under a MIT licence.

Development began in 2000, which puts Shopware among the older commerce codebases still under active work, and the roots show in how it gets deployed. Shopware AG is a German company, and the platform grew up serving mid-market and enterprise retailers across continental Europe rather than the global self-service crowd. A site running it is more likely to belong to a business with an internal ecommerce team or a retained implementation partner than to a weekend shop, because the software expects somebody to run a server, manage releases and own a staging environment.

Version numbering is where detection gets genuinely useful. The current line, 6, was a rewrite rather than an upgrade, moving the product onto an API-first architecture with a decoupled administration interface, so a shop on that line and a shop on the previous generation are effectively running different products with different extension ecosystems and different consultants. We record 3 distinct version values across the installed base, a narrow spread compared with plugin-style software but wide enough to separate shops that have made the jump from shops still sitting on the older generation and facing a migration they have not yet budgeted.

As of October 2026 we see Shopware on 19,114 sites. Checking one domain tells you whether a single merchant is a prospect. The downloadable list answers a different question: which merchants exist at all, how they cluster by country and domain suffix, what else runs alongside the storefront, and which of them sit on a version old enough to make a replatforming conversation realistic. Agencies build migration pipelines from exactly that. Extension vendors size an addressable market before committing to a port. Payment, tax and logistics providers use it to find integration targets that already employ the technical staff needed to finish an integration.

Detection is inferential and worth stating as such. Shopware can run behind a reverse proxy, in a headless configuration, or with template output customised until the usual fingerprints are gone, and a headless build serving a bespoke front end may be invisible to us while quietly processing orders all day. Version strings are only as good as what the storefront chooses to expose, and a hardened deployment reports nothing at all. Read the counts as a floor on real deployment rather than a census, and read the version breakdown as a view of the shops that have not gone out of their way to stay quiet.