OXID eSales

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by OXID eSales AG · www.oxid-esales.com

Compare with PrestaShop → Report an error on this page Is this your product? →

Link to this page

OXID eSales: AI-assisted analysis on whats-best.ai OXID eSales: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

OXID eSales at a glance

Vendor
OXID eSales AG
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates OXID eSales 3/5, the mean of 6 judges. OXID eSales AG of Freiburg sells an open-source shop system with a B2B focus, on subscription or purchase licences. how scores are made
As of
Vendor pages captured 15 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

OXID eSales alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

OXID eSales AG of Freiburg sells an open-source shop system with a B2B focus, on subscription or purchase licences. Judges scored it highest on pricing transparency, catalog and checkout, and extensibility, citing customer-specific price lists, tiers and discount logic, order approval workflows, official payment modules for PayPal Checkout, Stripe, Unzer, Adyen and Amazon Pay, and a developer surface of a GraphQL interface, a public code repository and a third-party module ecosystem. Tax and legal and sovereignty score lowest: the pages document country-specific VAT modules and a withdrawal button with §356 BGB timestamps, but we found no public information on VAT-ID validation, reverse charge, OSS reporting, e-invoicing, a merchant data-processing agreement or a published subprocessor list — and since OXID sells licences rather than hosting, data residency follows each merchant's chosen host. Scores sit within a point on six of seven criteria; the widest spread, data control and exit at 5-7, pairs the Data Protection Officer's 5, pressing on export and deletion at contract end, with 7s from judges weighing hosting freedom and public code.

Report an error

Speaks for it

  • All four editions carry public monthly prices with minimum terms — Community Edition 121 € / Monat at Mindestlaufzeit: 36 Monate, Professional 360 € / Monat, Enterprise B2C 1.123 € / Monat, Enterprise B2B 1.583 € / Monat at 48 Monate — plus +173 €/Monat je Sub-Shop and a stated no-revenue-share model
  • B2B selling is documented in depth: customer-specific price lists, tier pricing, discount logic, quotes created in the shop, order approval workflows and buyer management with roles and budgets
  • Official payment modules cover PayPal Checkout, Stripe, Unzer, Adyen and Amazon Pay
  • The developer surface is real: a GraphQL interface named OXAPI, developer documentation with code examples, Academy training, a public code repository with a module template, and modules that install and activate independently of the shop core
  • Structural ownership: free choice of hosting provider across eight named German partners, purchase licences alongside subscriptions, and a documented migration covering the shop core including database structure and content

Report an error

Held against it

  • We found no public information on VAT-ID validation, reverse charge, OSS reporting, invoicing or e-invoicing; tax and legal scores sit at 4-5
  • We found no published merchant data-processing agreement or subprocessor list for the checkout path, and the vendor's own privacy policy shows US transfers under EU standard contractual clauses — a policy about the vendor's website, not merchant shops
  • The documented migration runs one way, into OXID; we found no public information on exporting catalogue, customers and order history, or on data return when a contract ends
  • The technical migration covers only core and database, leaving theme, frontend, template and third-party or custom module work to the customer or partner, with updates to two releases a year applied by customer or partner
  • A full annual total is not computable from public pages: VAT treatment of the listed prices is not stated, hosting cost sits with the freely chosen provider, and the reduction below 100.000 € Jahresshopumsatz names a condition but no figure

Report an error

Best for

  • You sell B2B or mixed B2B and B2C and need customer-specific price lists, tier pricing, quotes in the shop, order approval workflows and buyer management with roles and budgets
  • You want to keep the infrastructure: free choice of hosting provider among eight named German partners, subscription or purchase licences, and source code in a public repository
  • Your team has developers who can work with the GraphQL interface, the documentation and the module ecosystem — and apply the twice-yearly updates
  • You run a German B2C shop facing the electronic withdrawal-button mandate from 19 June 2026

Report an error

Avoid if

  • You need documented cross-border B2B tax flows — VAT-ID validation, reverse charge, OSS reporting and e-invoicing; the captured pages show country-specific VAT modules but no public information on these, so put them to the vendor before signing
  • You want the platform vendor to guarantee where your shop data lives: OXID sells licences rather than hosting, residency follows your chosen host, and hosting outside the EU is equally possible
  • You need a documented exit — export of catalogue, customers and order history, and contractual data return at contract end; the migration documentation covers moving in
  • You have no development or implementation-partner capacity, since applying updates and handling theme, frontend and module work at migration fall to the customer or partner

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Catalogue & checkout 3 of 5
Tax & German legal correctness 2 of 5
Extensibility & developer surface 3 of 5
Order operations & back office 2.5 of 5
Data ownership & exit 3 of 5
European sovereignty 2 of 5
Pricing transparency 3.5 of 5

Catalogue & checkout

Show reasoning
How this is scored

Products, variants, pricing rules and the path to payment — the part that either converts or does not.

0 — Not a shop: no product catalogue and no checkout of its own.

3 — A product catalogue with categories and a checkout that takes payment through at least one provider.

5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.

8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and buy-now-pay-later where offered.

10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.

Report an error

The Merchant

Payment is well covered with official modules for PayPal Checkout, Stripe, Unzer, Adyen and Amazon Pay, and the commercial machinery is real: customer-specific price lists, tiers and discount logic, campaign quick filters marketing builds itself without a developer, and conditions set per shop in the multi-shop setup. I found no public information on guest checkout, on invoice or direct debit as named methods, or on abandoned-cart recovery and buy-now-pay-later, so I cannot take it to the top band on conversion tooling alone. 7 9 10 1

Report an error

The B2B Seller

This is documented as a shop that has met the trade customer: customer-specific price lists, tier pricing, discount logic, quotes created directly in the shop, order approval workflows, buyer management with roles and budgets, and quick, bulk and scheduled ordering. Payment runs through official modules for PayPal Checkout, Stripe, Unzer, Adyen and Amazon Pay, and the multi-shop capability documents individual assortments and conditions per shop with multilingual category trees built in. We found no public information on guest checkout, multi-currency pricing, abandoned-cart recovery or buy-now-pay-later. 10 1 9

Report an error

The Developer

The evidence shows a real catalogue and checkout: category trees with multilingualism built in, official payment modules from PayPal, Unzer, Stripe, Adyen and Amazon Pay, and serious pricing machinery — customer-specific price lists, tiers, discount logic, per-shop conditions, shipping-cost vouchers and B2B quick order with approval workflows. What keeps me below the top band: we found no public information on product variants, guest checkout, abandoned-cart recovery or buy-now-pay-later, and the checkout's own customisability without a rebuild is not documented. 9 1 9 10 2

Report an error

The Operations Lead

The captured pages show an indented, multilingual category tree, per-category filter configurations that marketing can edit without a developer, and real B2B pricing depth — customer-specific price lists, tiers and discount logic — alongside official payment modules for PayPal, Stripe, Unzer, Adyen and Amazon Pay. That carries it past a plain catalogue-and-payment setup, but we found no public information on product variants, guest checkout, abandoned-cart recovery or multi-currency checkout, so I cannot push it higher on this evidence. 12 1 2 9 7

Report an error

The Data Protection Officer

The captured pages show official payment integrations for PayPal Checkout, Stripe, Unzer, Adyen and Amazon Pay, plus customer-specific price lists with tiers and discount logic, campaign quick filters and shipping-cost vouchers — customer-group and tiered pricing, in short, beyond a basic catalogue. We found no public information on product variants, guest checkout, abandoned-cart recovery or buy-now-pay-later, which holds this short of the higher levels. 10 1 2 7

Report an error

The Skeptic

Customer-specific price lists, tiered pricing, discount logic, approval workflows and quick ordering are documented on the B2B side, official payment modules cover PayPal, Stripe, Unzer, Adyen and Amazon Pay, and merchandising gets per-category filters plus promotion quick filters a marketer can build without a developer. We found no public information on product variants, guest checkout, abandoned-cart recovery or multi-currency, so this sits between the middle and upper levels. 1 9 7 12

Report an error

Extensibility & developer surface

Show reasoning
How this is scored

Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.

0 — A closed shop builder: no themes to edit, no apps or plugins and no API.

3 — Themes adjustable in an editor and a set of apps or plugins to add features.

5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.

8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development environments, version control for themes, and documented rate limits.

10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.

Report an error

The Merchant

A real developer surface: modules that install and switch independently of the shop core, a documented GraphQL interface, developer documentation with code examples and trainings, a public code repository with a module template, and a broad third-party ecosystem in the Solution Hub. Templates run on Twig, so the storefront is code a team can shape. I found no public information on webhooks for order events, headless storefront builds, staging environments or documented rate limits. 10 10 14 15

Report an error

The B2B Seller

Developer documentation with code examples, Academy trainings, a module template with best practices and a public code repository give a development team real surfaces, and OXAPI is documented as a flexible GraphQL interface for external systems. The extension model has a documented lifecycle of its own — modules install separately and activate or deactivate at any time, components run platform-wide, and modules sit independent of the shop core for easy updates. We found no public information on a headless storefront API, webhooks for order events, staging environments or documented rate limits. 10 9 15

Report an error

The Developer

This is a genuine developer surface: source code published on GitHub, a module system where extensions install separately, activate or deactivate at any time and are tested with every release, a broad third-party Solution Hub, a GraphQL interface named OXAPI, and developer documentation with code examples and a GitHub module template. My concern is the documented upgrade path: the technical migration covers only core and database, and theme, frontend and template adjustments plus third-party or custom modules are explicitly handed to the customer or partner, with the Smarty-to-Twig switch only partially automated and two releases a year whose updates the customer or partner must apply. We found no public information on rate limits, staging environments or a dependency model between modules. 9 15 10 14 2

Report an error

The Operations Lead

There is a documented GraphQL interface called OXAPI plus an interface for external systems, an ecosystem of official modules tested with every release and third-party modules in the Solution Hub, developer documentation with code examples, Academy training, a GitHub module template and a public GitHub organisation. Modules install, activate and deactivate independently of the shop core, and the Smarty-to-Twig template migration shows real template-code access; we found no public information on webhooks for order events, headless storefront builds, staging environments or documented rate limits. 9 14 10 15

Report an error

The Data Protection Officer

A documented GraphQL interface, developer documentation with code examples and Academy training, a GitHub module template, official modules tested with every release and a third-party ecosystem in the Solution Hub give developers a real surface, and modules can be activated and deactivated independently of the core. We found no public information on webhooks, documented rate limits, staging environments or an explicitly headless storefront API. 9 10

Report an error

The Skeptic

A documented GraphQL interface, developer documentation with code examples and training, a GitHub module template, and an ecosystem of official and third-party modules in a Solution Hub are all on the record, with modules installed independently of the shop core and the template engine moving from Smarty to Twig. We found no public information on webhooks for order events, headless storefront builds, staging environments or documented rate limits. 9 10 14 15

Report an error

Order operations & back office

Show reasoning
How this is scored

What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.

0 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.

3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.

5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.

8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).

10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.

Report an error

The Merchant

Shipping is a strength — methods, rules and assignments on one screen with conflict warnings surfacing in the admin before checkout — and there are automated status emails with editable templates plus ERP modules that synchronise stock, orders and customer data automatically. The withdrawal module also matches returns to orders and notifies customers. I found no public information on named carrier integrations with label printing, partial shipments or partial refunds, or maintained links to accounting systems such as DATEV. 12 8 10

Report an error

The B2B Seller

Stock, orders and customer data are documented as synchronised automatically between shop and ERP, connections to shipping service providers are documented alongside a shipping-rule back office that surfaces conflicts before checkout, and B2B operations get order approval, quick ordering by item number and scheduled ordering, with status emails from adaptable templates. On the deeper back office we found no public information on partial shipments and refunds, multi-warehouse stock, marketplace order intake or maintained interfaces to named accounting systems such as DATEV. 9 8 12

Report an error

The Developer

Back office is documented at the middle band: status emails with customisable templates, a shipping-management surface with rules, overlap and orphan warnings in the admin before checkout, ERP modules that synchronise stock, orders and customer data automatically, and a withdrawal process with automatic order matching and deadline checks. Carrier connection is described generically without named carriers, and we found no public information on refunds or partial shipments, multi-warehouse stock, marketplace intake, or maintained interfaces to named ERP systems such as DATEV. 12 8 9 10

Report an error

The Operations Lead

Order status emails with editable templates per status, automated withdrawal intake with deadline calculation and customer notification, B2B approval workflows, and a shipping screen that flags rule overlaps and orphaned rules before they reach checkout are all documented. The vendor maintains an official ERP module that synchronises stock, orders and customer data automatically — the ERP link I insist on — while the shipping modules describe carrier connections only generically, and we found no public information on label printing, partial shipments, partial refunds, multi-warehouse stock or marketplace order intake. 12 8 9 10

Report an error

The Data Protection Officer

Order approval and rejection workflows, automatic status emails with adaptable templates, ERP modules syncing stock, orders and customer data, and shipping methods and rules managed on one screen with conflict warnings are all documented. We found no public information on partial shipments or refunds, multi-warehouse stock, marketplace order intake or maintained interfaces to named ERP and accounting systems such as DATEV. 12 8 10

Report an error

The Skeptic

Shipping methods and rules are managed in one administrative view with conflict and orphaned-rule warnings, ERP modules synchronise stock, orders and customer data automatically, and the withdrawal extension matches orders to emails, checks deadlines and sends status emails with editable templates. Carrier connections are described only generically as integration with shipping providers, and we found no public information on partial shipments, multi-warehouse stock or interfaces to named accounting systems such as DATEV. 12 8 9 10

Report an error

Data ownership & exit

Show reasoning
How this is scored

Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.

0 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.

3 — CSV export of products and customers, or of orders, from the admin.

5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.

8 — Full-fidelity export including media and order documents, a documented migration path in and out, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.

10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.

Report an error

The Merchant

Ownership leans structural rather than promised: the merchant keeps free choice of hosting provider across eight named partners, several running German data centres, the licence carries no revenue share, and the code sits in a public repository. The vendor's migration work explicitly covers the database structure and contents, so shop data is not locked in a black box. I found no public information on documented export of catalogue, customers and orders, or contractual data return on cancellation. 2 5 14 15

Report an error

The B2B Seller

The merchant keeps the infrastructure: the hosting provider is free choice across a certified partner network, licences come as subscription or purchase, the code is public in a repository, and a cost-neutral migration check plus a documented technical migration covering core and database keep version moves predictable. We found no public information on documented export of catalogue, customers and orders, or on data return when a contract ends, so exit rests on hosting freedom rather than a published exit path. 2 5 14 15

Report an error

The Developer

Structural ownership is real: the merchant chooses their own hosting provider, an eight-partner German hosting network is published, the source code sits on GitHub, and the licence is fixed-price with no revenue share — nothing meters a migration out of reach. The documented migration path runs in one direction only, into OXID, covering core files and the database structure and content, and we found no public information on exporting catalogue, customers and order history outward or on contractual data return on cancellation. 15 2 5 14

Report an error

The Operations Lead

The merchant keeps free choice of hosting provider, with a network of eight certified German hosting partners as an option, purchase licences exist alongside subscriptions, and the vendor's documented migration service moves the shop core including the database structure and content, preceded by a free technical migration check. We found no public information on documented export of catalogue, customers and orders, or on data return and deletion when a contract ends, so ownership here rests on hosting freedom and database access rather than a promised export path out. 2 5 14 15

Report an error

The Data Protection Officer

Hosting is the merchant's free choice among eight named German partners, and the vendor's documented migration moves the shop core together with the database structure and content — operational control that matters for who holds the customer and order data. We found no public information on exporting catalogue, customers and order history out of the platform, nor on deletion or return of data when a contract ends, which is what I would press on before signing. 2 5 14

Report an error

The Skeptic

Free choice of hosting provider across eight named German partners, purchase licences alongside subscriptions and a public code repository give structural control over where the data sits, and the documented migration covers database structure and content. That migration documentation describes moving in; we found no public information on export tooling or exit terms for taking catalogue and order history out of the platform. 2 5 14 15

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline. Dimensions the evidence does not establish are unknown, not non-EU.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.

3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.

5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.

Report an error

The Merchant

The contracting entity is German beyond doubt — OXID eSales AG in Freiburg, registered at the Freiburg court — and hosting is selectable from an all-German partner network advertising GDPR-conformant German data centres. The platform itself sells licences and does not host, so where a given shop's data lives follows the merchant's chosen host, and I found no public information on a merchant data-processing agreement or a published subprocessor list for the checkout path. 3 5

Report an error

The B2B Seller

The contracting entity is OXID eSales AG in Freiburg, registered at the Freiburg court, and EU hosting is selectable through a named partner network with German data centres — solid European elements a German buyer wants to see. The vendor's own pages also name their processors, including Usercentrics in Munich and a Swedish website host, with US transfers based on EU standard contractual clauses. A data processing agreement offered to merchants is not established on the captured pages, and the locations of payment processors in the checkout path are unstated. 3 5 4

Report an error

The Developer

The contracting entity is unambiguously European — OXID eSales AG in Freiburg, registered at the Freiburg district court — and eight named German hosting partners, including Profihost and SysEleven with German data centres, make EU hosting selectable, though the free choice of host means a shop can equally run outside the EU. The captured privacy policy describes the vendor's own website processing data through a Swedish host and US analytics under EU standard contractual clauses, which says nothing about a merchant's shop. We found no public information on platform data residency, a data-processing agreement offered to merchants, or the subprocessors in the checkout path. 4 3 5

Report an error

The Operations Lead

The contracting entity is proven German at register level — OXID eSales AG in Freiburg, registered at Amtsgericht Freiburg, with a second location in Halle and European regional-development funding — and EU hosting is selectable through certified German partners advertising data centres in Germany and the EU, with self-hosting open since the vendor sells licences rather than hosting. We found no public information on a data-processing agreement offered to merchants or on a published subprocessor list with locations, and where shop data resides follows the hosting provider each merchant chooses. 2 3 5

Report an error

The Data Protection Officer

The contracting entity is a German Aktiengesellschaft registered in Freiburg, and EU hosting is selectable through eight German hosting partners, two of which state German or EU data centres; the vendor itself notes EFRE funding. We found no published subprocessor list with locations and no merchant-facing data processing agreement on the captured pages, and the vendor's own privacy policy shows transfers to the USA resting on the EU Commission's standard contractual clauses — so one cannot verify who sits in the checkout path. 4 2 3 5

Report an error

The Skeptic

The contracting entity is proven German down to register court, VAT ID and an office in Halle, and every named hosting partner operates from Germany advertising GDPR-conform hosting; the vendor sells licences rather than hosting, so the shop's data residency is the merchant's decision. We found no public information on a data processing agreement offered to merchants or a published subprocessor list covering the shop's checkout path. 3 5 2

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier.

5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.

8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.

10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.

Report an error

The Merchant

Every edition is priced publicly — Community Edition at 121 € / Monat, Professional at 360 € / Monat, Enterprise B2C at 1.123 € / Monat, Enterprise B2B at 1.583 € / Monat — each with its minimum term, the sub-shop surcharge of +173 €/Monat, inclusions listed per tier, and the explicit promise of no revenue share, with module prices visible too (shipping management at €20/month, the withdrawal button free on maintenance contracts, 50 EUR / Monat for everyone else). What stops full computability: we found no public information on the VAT treatment of these prices, and hosting cost sits with the merchant's chosen host. 8 2 2 12

Report an error

The B2B Seller

All four editions are priced publicly with terms — Community Edition "121 € / Monat" at "Mindestlaufzeit: 36 Monate", Professional Edition "360 € / Monat", Enterprise Edition B2C "1.123 € / Monat", Enterprise Edition B2B "1.583 € / Monat" — plus "+173 €/Monat je Sub-Shop" and an explicit "Keine Umsatzbeteiligung". Individual accelerators are priced too: the product filter at "35 €/Monat" and the withdrawal button at "0 EUR für Bestandskunden" and "50 EUR / Monat für alle anderen". A trade buyer still cannot see whether the licence prices are net or gross, and hosting cost sits with the freely chosen provider, so the full annual total is not computable from the captured pages. 2 2 7 8

Report an error

The Developer

Prices are public and structured: 'Community Edition 121 € / Monat' with 'Mindestlaufzeit: 36 Monate', Professional at '360 € / Monat', Enterprise B2C at '1.123 € / Monat', Enterprise B2B at '1.583 € / Monat', plus '173 €/Monat je Sub-Shop' and individual OPAL prices such as '35.00' for the product filter and '20.00' for shipping management, all with a stated zero revenue share. Hosting cost is left to the merchant's own provider and VAT treatment is not stated, so the licence line of the invoice is computable from public pages while the full annual cost is not. 7 8 12 2

Report an error

The Operations Lead

Every edition is priced publicly with its billing period and minimum term — Community Edition 121 € / Monat at 36 months, Professional Edition 360 € / Monat, Enterprise B2C 1.123 € / Monat, Enterprise B2B 1.583 € / Monat at 48 months — plus +173 €/Monat per sub-shop, a stated no-revenue-share model, and public accelerator prices including 35 €/Monat for the product filter, Price €20/month for shipping management and 0 EUR für Bestandskunden for the withdrawal button. Hosting cost sits with the freely chosen provider rather than on the vendor's pages, and we found no public information on VAT treatment of the listed prices or complete per-module pricing across the extension catalogue. 8 2 6 12

Report an error

The Data Protection Officer

All four editions carry public monthly prices with minimum terms and per-tier inclusions — Community Edition 121 € / Monat at 36 months up to Enterprise Edition B2B 1.583 € / Monat at 48 months — plus a stated sub-shop surcharge of +173 €/Monat je Sub-Shop, the statement 'Klare Preise, keine Umsatzbeteiligung', and public accelerator prices such as Versandverwaltung at 20 €/Monat. VAT treatment of the prices is not stated and hosting cost sits with the freely chosen provider, so a full annual total is not computable from public pages alone. 12 2 2 8

Report an error

The Skeptic

Four editions are priced publicly, from 121 € / Monat to 1.583 € / Monat with minimum terms of 36 and 48 Monate and +173 €/Monat je Sub-Shop, with no revenue share and several extension prices on the record (0 EUR für Bestandskunden, 50 EUR / Monat für alle anderen on the withdrawal button, 35 €/Monat for the product filter). Still not computable from these pages: VAT treatment, hosting costs (hosting is chosen elsewhere), and the reduction offered below 100.000 € Jahresshopumsatz, which names a condition but no figure. 2 2 8 7

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

OXID sells licenses and does not host customer data itself; the pricing page gives customers 'die freie Wahl bei deinem Hosting-Anbieter', so hosting outside the EU is equally possible.

— uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

The finding rests on free choice of hosting provider and a hosting-partner network rather than an explicit "self-hosted" or "on-premises" statement.

1/1 pts 2 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about OXID eSales

Is OXID eSales European?

Yes. whats-best.ai classifies OXID eSales as EU-Made. Its vendor, OXID eSales AG, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does OXID eSales store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does OXID eSales have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to OXID eSales?

As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Shopware (3/5) highest among the other 28 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: OXID eSales alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (15)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.oxid-esales.com Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 19 Oct 2026, 15 Sep 2026 Details →
  2. 2 Pricing www.oxid-esales.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 19 Oct 2026 Details →
  3. 3 Imprint www.oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  4. 4 Privacy policy www.oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  5. 5 Security / trust page www.oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  6. 6 Catalogue & checkout — found from sitemap oxid-esales.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  7. 7 Catalogue & checkout — found from sitemap oxid-esales.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  8. 8 Tax & German legal correctness — found from sitemap oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  9. 9 Extensibility & developer surface — found from sitemap oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  10. 10 Extensibility & developer surface — found from sitemap oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  11. 11 Order operations & back office — found from sitemap oxid-esales.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
  12. 12 Order operations & back office — found from sitemap oxid-esales.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
  13. 13 Data ownership & exit — found from sitemap oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  14. 14 Data ownership & exit — found from sitemap oxid-esales.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  15. 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →