Download websites that use OXID eShop

About OXID eShop

A commerce platform that shipped before hosted storefronts became the default answer has two ways to end up. Either it disappears, or it settles into a defined community with agencies, extension vendors and long lived installations around it, and the second outcome is what OXID eShop looks like from the data.

OXID eSales AG publishes it under the GPL v2 license, written in PHP, with our earliest record for it at 2003. The vendor name carries a corporate form used in German speaking jurisdictions, which is a fact about the name and not a fact about where the customers are. Our record holds no country breakdown for the platform, so anybody who needs the geography has to derive it from the domain list rather than accept a claim from us.

Presence carries an operating model with it. An open source, self hosted commerce platform means somebody pays for hosting, upgrades, security patching and integration work directly, rather than renting all of it inside a monthly fee. Sites running one are usually maintained by an agency or an in house team, have been customised against their own business processes, and carry a switching cost measured in project months rather than in an export followed by an import. Replatforming conversations with these owners are long, expensive and infrequent, which is exactly why the ones that do happen are worth so much to whoever is on the other side of them.

As of October 2026 we detect OXID eShop on 26 sites. We hold no version data for the platform, and the gap is worth stating clearly, because two very different questions ride on it. Sizing a community needs the domains and nothing else. Judging maintenance or exposure needs to know which release is running, and our list cannot separate a recently upgraded install from one that has not been touched in years. Anyone asking the second kind of question should plan to fetch and check the domains themselves, using our list as the input to that work rather than as the answer to it.

The audiences are the ones that gather around any self hosted platform. Agencies looking for maintenance and migration work. Extension and theme vendors sizing the community they sell into. Payment, search, shipping and marketing tools that need a named platform to build an integration for and a population to justify building it. Competing platforms running displacement campaigns. All of them need the same artefact, and a per domain check is not it. The artefact is the enumeration: every domain where the fingerprint matched, in a file, with enough surrounding attributes that you can sort the population before spending an hour on it.