OXID eSales vs PrestaShop

OXID eSales

EU-Made

Sovereignty: 2 of 6 dimensions proven

Full evaluation →

PrestaShop

EU-Made

Sovereignty: 1 of 6 dimensions proven

Full evaluation →

As of 17 Nov 2026, the panel rates OXID eSales 3/5 and PrestaShop 2.5/5 in E-Commerce Platforms & Shop Systems. Weighted by what each judge cares about, 5 of the 6 judges pick OXID eSales and 1 picks PrestaShop. OXID eSales scores higher on 4 of 6 criteria (Catalogue & checkout, European sovereignty, Tax & German legal correctness, plus 1 more). PrestaShop scores higher on 2 of 6 criteria (Data ownership & exit and Extensibility & developer surface). Provenance — OXID eSales: EU-Made, Germany; PrestaShop: EU-Made. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.

The short answer

On catalog and checkout (6.3 to 3.7), tax and legal (4.2 to 3.0), sovereignty (4.3 to 3.0) and pricing transparency (6.8 to 0.0), six judges lean OXID eSales and zero lean PrestaShop; operations (5.2 to 4.5) goes four for OXID eSales with two ties. PrestaShop takes data control and exit (7.8 to 6.2), six lean PrestaShop, zero OXID eSales, and its extensibility mean of 6.8 to 6.2 splits the bench: three lean PrestaShop, three tie. Weighted totals split by judge — five of six favor OXID eSales (merchant 5.7 to 4.9, B2B seller 5.6 to 4.0, developer 6.4 to 5.7, operations lead 5.8 to 5.3, skeptic 5.4 to 4.7), while the data protection officer's favors PrestaShop, 4.9 to 4.7. Pricing transparency was not weighted in PrestaShop's verdicts; the vendor publishes no prices. Both list hosting options as self-hostable; legal entity jurisdiction is DE for OXID eSales, unknown for PrestaShop.

Choose OXID eSales if

  • You run B2B sales that need customer-specific price lists, tiers, discount logic and order approval workflows in checkout — catalog and checkout leans OXID eSales six judges to zero, 6.3 to 3.7.
  • You must show country-specific VAT modules and a withdrawal button with §356 BGB timestamps — tax and legal leans OXID eSales six judges to zero, 4.2 to 3.0.
  • Your procurement requires published prices up front — OXID eSales publishes prices and took 6.8 on pricing transparency, while no prices appear in PrestaShop's captured pages and the criterion was not weighted in its verdicts.
  • Your fulfillment goes beyond the occasional single order — operations leans OXID eSales 5.2 to 4.5 (four judges for OXID eSales, two ties), and we found no public information on stock tracking, status emails or ERP links such as DATEV for PrestaShop.
  • Your vendor governance needs a known legal seat — OXID eSales's legal entity jurisdiction is listed as DE; PrestaShop's is listed as unknown.

Choose PrestaShop if

  • You need documented exit and data control — full backups via mysqldump, PhpMyAdmin or the Update Assistant, plus a core CSV export; data control and exit leans PrestaShop six judges to zero, 7.8 to 6.2.
  • Your developers build against a documented API — PrestaShop's Admin API runs on API Platform version 3 with OAuth2 and Swagger documentation, and its extensibility mean leads 6.8 to 6.2, with three judges leaning PrestaShop and three tied.
  • Your data protection officer holds the deciding vote — theirs is the one weighted total favoring PrestaShop, 4.9 to 4.7.
  • You want a native One Page Checkout in the core — version 9.2 bundles it — and native module source on GitHub, points cited in PrestaShop's extensibility evidence.

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

The Developer

Will maintain this for five years. Wants local development, version control for themes, a plugin architecture with a dependency model, and upgrades that do not orphan the customisations. Reads a closed template editor as a future migration.

OXID eSales

This judge's pick

PrestaShop

Criterion by criterion

Catalogue & checkout

OXID eSales

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.

PrestaShop

The checkout side is documented and real: version 9.2 ships a native one-page checkout module in the bundle, with a compatibility guide for module and theme developers. The order domain carries cart rules, per-order currency changes and both tax-included and tax-excluded product prices, which is more than a bare order pipeline. We found no public information in the captured pages on payment providers by name, product variants, guest checkout or the payment methods German buyers expect, so I stop short of the middle band.

Tax & German legal correctness

OXID eSales

Compliance is shipped as maintained vendor modules rather than left to the merchant: Country VAT Administration and eVAT for destination-based tax, Geoblocking for the EU regulation, and a withdrawal-button module that documents every revocation with a timestamp under §356 BGB including automatic deadline checking, order matching and customer notification. We found no public information on VIES validation of VAT IDs, OSS reporting, e-invoicing, or how the order-button wording and price-indication rules are handled.

PrestaShop

Taxes are first-class in the domain model: taxes can be added, edited, bulk-toggled and deleted with rates, tax rules groups have their own full command set, and orders store both tax-included and tax-excluded prices. We found no public information on VAT-ID validation, reverse charge, OSS, invoicing or the German checkout requirements on any captured page. The tax reference I read also carries a banner warning that it documents version 8 and is outdated, which tempers my confidence in how maintained this surface is.

Extensibility & developer surface

OXID eSales

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.

PrestaShop

This is my home ground, and the developer surface is genuinely strong: modules install, uninstall and upgrade from the back office, native modules are managed by Composer with source code on GitHub, and the Distribution API reports each module's latest compatible version per core release — a real compatibility model that protects customisations across upgrades. The Admin API sits on API Platform 3 with OAuth2, Swagger documentation and CQRS, developers can add endpoints, and themes are an addressed developer audience. I hold it below the top bands because the captured pages document no storefront API for headless builds, no webhooks, no documented rate limits and no local development workflow, and Git integration appears only inside the vendor's managed hosting offer rather than as a first-class developer facility.

Order operations & back office

OXID eSales

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.

PrestaShop

The order domain is deep and the back office has order detail, order view and add-new-order pages: back-office order creation from a cart, payments, product additions and cancellations, bulk status changes, return issuance, carrier and tracking-number updates, internal notes and cart duplication are all documented commands. We found no public information on stock tracking, status emails, named carrier integrations or label printing, partial refunds, or ERP and accounting links such as DATEV, so I place this between the lower bands.

Data ownership & exit

OXID eSales

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.

PrestaShop

Ownership here is structural rather than promised: the update documentation assumes your own server and hosting provider, prescribes full backups of files and database with standard tools — mysqldump, PhpMyAdmin, compressed archives over SSH, FTP or rsync — and the Update Assistant module automates that backup before each update, while the vendor separately sells a fully managed service so both paths exist. A CSV export component is part of the core reference. We found no public information on a documented migration path into the platform or contractual data return on cancellation, which is what keeps me off the top band.

European sovereignty

OXID eSales

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.

PrestaShop

The vendor is listed as PrestaShop SA of Paris, majority-held by Italy's MBE Worldwide, and the captured homepage names PrestaShop S.A as the controller for newsletter data — European elements I can prove. We found no public information on where hosted shops' customer and order data resides, on subprocessors in the checkout path, or on a data processing agreement, so the rest of the chain stays unknown to me rather than European.

Pricing transparency

OXID eSales

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.

PrestaShop

We found no public information on prices at all: the captured hosting page describes the scalability and development tooling of the managed service without any figures, and nothing captured states licence, module, transaction or support costs. I cannot compute an annual cost from these pages, and while the platform is presented as open source, no captured page states where the money actually goes.

Sovereignty, side by side

Dimension OXID eSales PrestaShop
Legal entity Incorporated in DE Not determined
Hosting location Not determined Not determined
Hosting options Self-hostable Self-hostable
Open source Not determined Not determined
Data processing agreement Not determined Not determined
Transfer impact assessment Not determined Not determined

Questions about OXID eSales and PrestaShop

Which is better, OXID eSales or PrestaShop?

As of 17 Nov 2026, the panel rates OXID eSales higher: 3/5 against 2.5/5. Weighted by what each judge cares about, 5 of the 6 judges pick OXID eSales and 1 picks PrestaShop. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.

Is OXID eSales or PrestaShop European?

OXID eSales is European (EU-Made, Germany). PrestaShop is European (EU-Made). Provenance is read from each company’s own legal pages: who builds it and who owns it.