whats-best.ai

E-Commerce Platforms & Shop Systems · head-to-head

OXID eSales vs PrestaShop

OXID eSales

EU-Made

Panel rating

Sovereignty: 1 of 4 dimensions proven

Full evaluation →

PrestaShop

EU-Made

Panel rating

Sovereignty: not determined

Full evaluation →

The written short answer is being updated after a re-evaluation. The scores below are current.

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

The Data Protection Officer

The shop holds customers, addresses and buying histories, and the checkout is full of third parties. Wants the subprocessor list, consent handling that survives a complaint, deletion that executes against order history, and an answer on where the CDN and analytics sit.

OXID eSales

This judge's pick

PrestaShop

Criterion by criterion

Catalogue & checkout

OXID eSales

Customer-specific price lists, tiered pricing and discount logic are documented for B2B, filter configuration per category is editable in the admin without a developer, and official payment modules cover PayPal, Stripe, Unzer, Adyen and Amazon Pay. We found no public information on bundles, guest checkout, multi-currency pricing or conversion features such as abandoned-cart recovery, which is what separates this from the top bands.

PrestaShop

A native one-page checkout shipped in the 9.2 bundle is the strongest captured fact here, with cart-rule commands that let vouchers act on orders; we found no public information on payment provider coverage, guest checkout, variants, bundles or tiered pricing on the captured pages.

Tax & German legal correctness

OXID eSales

Country-specific VAT rules and electronic VAT management ship as official modules, and the withdrawal handling is unusually concrete — a button stated as legally mandatory from 19 June 2026, automatic timestamp documentation of every withdrawal under §356 BGB, and submission without login. We found no public information on VAT-ID validation with reverse charge, OSS reporting, e-invoicing, or any statement that rates and thresholds are maintained by the vendor rather than configured by the merchant.

PrestaShop

Taxes and tax-rule groups are configurable by hand through back-office commands and the Admin API, which puts determination in the merchant's hands rather than the vendor's; we found no public information on destination-based VAT, VAT-ID validation or reverse charge, OSS tracking, or e-invoicing, and the German-language vendor site has been discontinued while the tax documentation carries its own warning that it covers an older major version.

Extensibility & developer surface

OXID eSales

A GraphQL API, a broad third-party ecosystem in the Solution Hub, developer documentation, trainings, a GitHub module template and a Twig template engine give a genuine developer surface, with modules described as independent from the shop core and individually activated or deactivated. We found no public information on headless storefront builds, staging environments, webhooks or documented rate limits.

PrestaShop

An OAuth2, Swagger-documented Admin API with CQRS extension points, a module ecosystem installable from the back office with native module source on GitHub, and Git-integrated dev, staging and production environments make a credible developer surface; we found no public information on a storefront or headless API, webhooks, or documented rate limits.

Order operations & back office

OXID eSales

Shipping methods, rules and assignments sit on one screen with automatic conflict warnings, ERP modules synchronise stock, orders and customer data automatically, and statutory withdrawals are processed in the shop with timestamp documentation and duplicate detection. We found no public information on partial shipments, multi-warehouse stock, named carriers with label printing or refund handling, and the ERP, PIM and CRM interfaces are described generically without named systems.

PrestaShop

The order domain is genuinely built out — orders can be created in the back office, products added or cancelled individually, statuses changed in bulk, returns issued, shipping and tracking numbers updated, and internal notes kept out of the storefront; we found no public information on stock or warehouse management, carrier integrations with label printing, or ERP and accounting interfaces.

Data ownership & exit

OXID eSales

Hosting is the merchant's free choice among eight named German partners, and the migration service explicitly covers the database structure and contents, so the shop's data travels with the installation rather than into a proprietary vault. We found no public information on complete export of catalogue, customers and order history, on documented deletion procedures, or on a documented path for leaving the platform.

PrestaShop

Exit is structural rather than promised — the core is open source with module source published, and the documented backup covers the complete files plus a full database dump via mysqldump or phpMyAdmin, so catalogue, customers and order history can leave intact; we found no public information on a documented deletion routine for order history or a contractual data-return commitment.

European sovereignty

OXID eSales

The contracting entity is a German AG registered in Freiburg, and hosting runs through named German partners, one of which markets sovereign cloud hosting. The vendor's own privacy policy names its processors — Google Analytics, Meta Pixel and LinkedIn Insight Tag, with US transfers based on the EU Commission's standard contractual clauses and consent technology from Usercentrics in Munich. We found no public information on where shop and checkout data reside by default, or on a subprocessor list covering the platform's own checkout chain.

PrestaShop

The captured pages publish no subprocessor list, no data-residency statement and nothing on where CDN, analytics or payment routing sit, and the only consent artifact captured names PrestaShop S.A as controller for the vendor's own newsletter; managed hosting is offered by PrestaShop with no stated location, and although the open-source platform can run on the merchant's own server, nothing captured evidences EU-standard hosting or named infrastructure.

Pricing transparency

OXID eSales

All four editions carry public monthly prices with minimum terms of 36 to 48 months, a sub-shop surcharge of 173 €/Monat is stated, and the vendor publishes "Klare Preise, keine Umsatzbeteiligung". We found no public information on extension and module prices, the captured pages show different figures for different offerings — among them 20 €/Monat, 0 EUR für Bestandskunden and 50 EUR / Monat für alle anderen — and nothing on VAT treatment of the listed figures, so the real annual cost is not computable from the pages alone.

PrestaShop

The captured pages contain no prices at all — not for managed hosting, not for modules — so a merchant cannot compute an annual cost from anything public; the downloadable releases and GitHub-hosted modules show the licence itself is free, but we found no public statement of where the money actually goes.

Sovereignty, side by side

Dimension OXID eSales PrestaShop
Legal entity Incorporated in DE Not determined
Ownership Not determined Not determined
Data residency Not determined Not determined
Subprocessors Not determined Not determined