Download websites that use Smartstore

About Smartstore

Version data is the part of this record that repays the most attention. Smartstore is self-hosted, which means every merchant upgrades on their own schedule or not at all, and the result is an install base spread across 21 distinct releases rather than a single current build. The release we record most frequently is 6.4.0.0. Anyone who has run a commerce platform in production knows what a spread like that implies: patch levels that differ from site to site, plugin compatibility that has to be verified per install, and upgrades that are real projects rather than a click.

The platform itself is an open-source Ecommerce system written in C# on ASP.NET, developed by SmartStore AG in Germany and published under the LGPL licence. Smartstore began as a fork of nopCommerce and grew into an independent codebase with its own architecture, module ecosystem and multi-store, multi-language and multi-currency handling. First released in 2010, it is aimed at small and mid-sized merchants and at the development shops that serve them, particularly in European markets where the vendor's partner network and German-language documentation matter.

Choosing a C# commerce platform is a decision about an entire environment, not just about a shop. Adoption usually implies an organisation already invested in Microsoft tooling, with developers who work in that ecosystem and hosting arranged to suit it. Merchants in this list therefore behave differently from those running PHP storefronts. They buy fewer marketplace plugins on impulse, commission more work from a partner agency, and replace their platform on a longer cycle, which changes both how you sell to them and how quickly you should expect the population to turn over.

Detection works from what a self-hosted install exposes: generator metadata, predictable static asset paths, and the script and stylesheet names the platform ships with. Version identification is a subset of that, because it depends on a version string being present in the paths or headers a given site serves. A hardened install behind a reverse proxy that strips those hints is recorded as Smartstore without a version, or missed altogether. The version distribution describes the sites that disclose a version, and should be read as a sample of the install base rather than as a full audit of it.

Geography is worth measuring rather than assuming. The vendor's home market and German-language documentation make a European concentration plausible, and the export carries country and TLD fields for every domain, so the distribution is something you can compute directly instead of accepting it from a vendor's origin story.

As of October 2026 we record 218 live storefronts. The questions worth asking of a set like that are population questions. Which releases run where, how fast the install base moves after a security advisory, which payment and shipping providers these merchants integrate, and how many shops drift to a hosted platform between crawls. Plugin and payment vendors selling into the Microsoft commerce ecosystem need the list to reach an audience small enough to be overlooked and specialised enough to be worth reaching. Security researchers need the version field, because an advisory is only actionable against a known distribution of releases. Agencies pitching upgrade work need both at once, and none of it comes from checking one shop at a time.