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 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

Customer-specific price lists, tiers and discount logic are evidenced, and marketing can build campaign quick filters in the category frontend without a developer — the promotion control I sell on. Five official payment providers including Unzer and Adyen are listed with Unzer described only as flexible payment options, and we found no public information on variant handling, product bundles or guest checkout.

PrestaShop

The 9.2 release ships a native one-page checkout that pulls the whole purchase onto a single page, with developer documentation for adapting modules and themes to it — a checkout I can reshape without a rebuild. But we found no public information on the payment methods German shoppers expect such as invoice and direct debit, nor on variants, bundles, tiered pricing or promotions with rules, so I cannot credit conversion machinery beyond that.

Tax & German legal correctness

OXID eSales

Official modules for electronic VAT management and country-specific tax rules cover destination-based tax, and the vendor's withdrawal button — free of charge, tied to the 19 June 2026 statutory date, with every withdrawal timestamped under §356 BGB — shows a legal element maintained by the vendor rather than the merchant. We found no public information on VAT-ID validation with reverse charge, OSS reporting, gross/net display per customer group, or e-invoicing.

PrestaShop

Taxes are managed by hand: commands exist to add, edit and group tax rates, which is per-country rates configured manually and nothing more. We found no public information on automatic VAT by destination and customer type, VAT-ID validation with reverse charge, OSS handling or the German checkout legal texts, and the captured tax page itself carries a warning that it documents an older version and is outdated.

Extensibility & developer surface

OXID eSales

A documented GraphQL interface, a module ecosystem with its own activate/deactivate lifecycle independent from the shop core, a GitHub module template, developer documentation and academy training give a team a real surface, and the Twig template engine is evidenced through the migration tooling. We found no public information on staging environments, documented rate limits, webhooks or headless storefront use.

PrestaShop

This is the part I care about: a module ecosystem with native module source code on the GitHub organization, install and upgrade from the back office, and an Admin API on API Platform 3 with OAuth2, Swagger documentation and new endpoints creatable via CQRS — plus Git integration and dev, staging and production environments in the hosted offering. We found no public information on a storefront API for headless builds, webhooks or documented rate limits, which keeps it below the top band.

Order operations & back office

OXID eSales

Shipping types, rules and assignments on one screen with overlap warnings surfaced before checkout, automatic ERP synchronisation of stock, orders and customer data, B2B order approval with budgets, and a withdrawal process documented in the system give the back office real depth. We found no public information on carrier label printing, partial shipments, multi-warehouse stock or interfaces to named ERP and accounting systems.

PrestaShop

The order back office is genuinely worked: I can create an order from a cart, add payments and products afterwards, change statuses in bulk, issue a merchandise return, update carrier and tracking number and keep internal notes, with prices tracked both tax-included and tax-excluded. We found no public information on multi-warehouse stock, carrier label printing or maintained links to ERP and accounting systems, which is what separates a shop from an operation.

Data ownership & exit

OXID eSales

Free choice among eight named German hosting partners and a migration offering that moves the shop core and the database's structure and content give a merchant hosting control and a documented path in. We found no public information on export completeness for catalogue, customers and orders out of the platform, documented deletion, or a contractual data-return commitment on the way out.

PrestaShop

The backup documentation assumes my server and walks through a full dump of files and database with standard tools — mysqldump, phpMyAdmin, SSH, rsync — plus automated backup via the Update Assistant module, so catalogue, customers and order history leave with me at the database level, with a CSV export component documented on top. We found no public information on a documented migration path in both directions or a contractual data-return commitment, so I stop short of the top.

European sovereignty

OXID eSales

The contracting entity is German with eight named German hosting partners, and US transfers in the vendor's own web chain are disclosed on the EU Commission's standard contractual clauses with a German consent provider named. We found no public information on where shop and checkout data are hosted as standard, or which subprocessors sit in that chain.

PrestaShop

PrestaShop S.A appears as the data controller in the newsletter consent and the hosting is a managed service developed by PrestaShop, but there the trail ends: we found no public information on where that hosting runs, on data-residency guarantees, or on any subprocessor list for the checkout path that I could hand a lawyer. The published subprocessor information is absent, and the vendor publishes no sovereignty statement for its own services.

Pricing transparency

OXID eSales

Four editions are priced monthly with minimum terms stated — Community Edition at 121 € / Monat up to Enterprise Edition B2B at 1.583 € / Monat — alongside a clear no-revenue-share line and individually priced add-ons such as the withdrawal button at 0 EUR für Bestandskunden. Hosting costs, the price of the payment and ERP extensions most shops need, and the VAT treatment of the stated prices are not given on the captured pages, so the annual invoice is not fully knowable from the pages alone.

PrestaShop

The platform is open source, so the licence itself carries no fee — and that is the only cost fact I have: the captured hosting page describes managed hosting, on-demand resources and development environments without a single price, and we found no public information on transaction fees, marketplace module costs, order limits or term and VAT conditions. A merchant trying to compute a real annual cost from these pages cannot.

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