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 Merchant
Sells to consumers and lives on conversion. Wants a checkout that can be changed without a rebuild, the payment methods German shoppers expect including invoice, and promotions with rules. Judges price against contribution, not against a competitor's tier.
OXID eSales
This judge's pick
PrestaShop
Criterion by criterion
Catalogue & checkout
OXID eSales
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.
PrestaShop
A native one-page checkout ships in the 9.2 bundle with developer documentation for modules and themes to adapt it, orders record payments by module name, and cart-rule discounts can be applied to orders — real conversion bones. But we found no public information on named payment providers, German payment methods such as invoice or direct debit, guest checkout, product variants or abandoned-cart recovery, so I cannot credit the level where payment breadth converts.
Tax & German legal correctness
OXID eSales
Official modules for country-specific VAT rules and electronic VAT administration put tax on the platform, and the withdrawal-button module is genuinely German-legal: a button directly in the order overview, automatic deadline checks with section 356 BGB timestamps, order matching and customer notification, free on a maintenance or subscription contract. I found no public information on B2B VAT-ID validation with reverse charge, OSS reporting, invoicing from orders or e-invoicing, which is why I keep this one moderate.
PrestaShop
Taxes are configurable with rates and localized names, tax rules groups are fully manageable for version 9, and orders carry both tax-included and tax-excluded prices — the captured version 8 tax reference carries an outdated notice while the tax-rules-group reference is current for version 9. Beyond that we found no public information on destination-country VAT, B2B VAT ID validation, OSS or the German checkout requirements, and the vendor's own German-language site states it is no longer available, which is not comforting for a German shop.
Extensibility & developer surface
OXID eSales
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.
PrestaShop
The developer surface is the strongest thing here: an admin API on API Platform 3 with OAuth2, Swagger documentation, CQRS endpoints developers can extend, multi-shop context, back-office module install and upgrade, Composer-managed native modules with source on GitHub, and a cloud offering with Git integration plus dev, staging and production environments. We found no public information on a storefront API for headless builds or on documented rate limits, which keeps it below the top band.
Order operations & back office
OXID eSales
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.
PrestaShop
After checkout the order domain is well covered: back-office pages to create and view orders, add payments with transaction ids, add or cancel individual products, issue returns, update carrier and tracking number, change status in bulk and keep internal notes. We found no public information on stock tracking, named carrier integrations or maintained links to ERP and accounting systems such as DATEV, so this sits at the solid mid-band rather than the operation-running level.
Data ownership & exit
OXID eSales
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.
PrestaShop
Exit is cheap and documented: full backups of files and database via mysqldump, PhpMyAdmin or SSH, automated through the Update Assistant module from the back office or command line, plus a core export component with CSV responses. With a fully managed hosting service from the vendor on one side and my own server on the other, catalogue and order history stay mine; we found no public information on contractual data return.
European sovereignty
OXID eSales
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.
PrestaShop
The vendor is recorded as PrestaShop SA of Paris, France, majority-held by MBE Worldwide of Italy, and the newsletter consent names PrestaShop S.A as data controller — one European element proven. Hosting location, subprocessors and a published data-processing agreement are not established in the captured pages, so the rest of the chain stays unknown to me.
Pricing transparency
OXID eSales
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.
PrestaShop
We found no public information on pricing — no licence tiers, transaction fees, revenue share or billing terms appear in the captured homepage, hosting and checkout pages. As a merchant who judges price against contribution, I have nothing to judge.
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.