OXID eSales vs PrestaShop

OXID eSales

Customer-specific price lists, tiered pricing and discount logic are published, with five named payment providers and per-category promotion filters a marketer can build without a developer. But we found no public information on a variant matrix, product bundles, guest checkout or multi-currency — the merchandising core the upper levels are made of — so the pricing engine carries the score, not the catalogue.

PrestaShop

One bright spot in the evidence: PrestaShop 9.2 ships a native One Page Checkout module in the bundle, with developer documentation for making modules and themes checkout-compatible, and payments attach through payment modules in the order commands. Beyond that we found no public information on variants, bundles, tiered pricing, or which payment methods a merchant actually gets at the till.

OXID eSales

Official modules for country-specific tax rules and electronic VAT administration, plus a withdrawal button that documents every revocation with a timestamp under §356 BGB and blocks duplicates within 24 hours, show the vendor maintaining German legal machinery rather than leaving it to the merchant. We found no public information on VAT-ID validation, reverse charge, OSS reporting or e-invoicing, which is what the top of this scale is built from.

PrestaShop

Tax is configure-it-yourself: the domain references expose commands to add taxes with a rate and to build tax rules groups, and the captured tax documentation itself carries an outdated warning. We found no public information on automatic VAT by destination, VAT-ID validation, reverse charge, OSS, e-invoicing, or the checkout elements German law requires — and the vendor homepage announces the German-language site is no longer available.

OXID eSales

A GraphQL interface, developer documentation with training and code examples, a GitHub module template, and modules that run independently of the shop core and can be activated or deactivated at will add up to a genuine developer surface, with a Twig template engine behind it. We found no public information on headless storefront builds, staging environments or documented rate limits.

PrestaShop

The strongest ground in the file: an Admin API on API Platform with Swagger documentation and OAuth2, endpoints developers can extend through CQRS, a module lifecycle of install, uninstall and upgrade in the back office, native modules on Composer with source on GitHub, and Git with dev, staging and production environments on the managed hosting. We found no public information on a storefront API for headless builds, version control for themes, or documented rate limits.

OXID eSales

Stock, orders and customer data synchronize automatically with ERP systems, B2B orders run through approval workflows, quotes and scheduled or collective ordering, and shipping methods and rules sit in one admin view with conflict and orphaned-rule warnings. But we found no public information on partial shipments, multi-warehouse stock, carrier label printing or dropshipping, and no ERP or accounting systems are named.

PrestaShop

The order back office is real work, not an order list and an email: back-office order creation, adding products and payments to existing orders, cancelling individual products, bulk status changes, issuing returns, updating carrier and tracking number, and internal notes visible only in the back office. Around it we found no public information on stock across warehouses, named carrier integrations, label printing, or interfaces to ERP and accounting systems.

OXID eSales

Hosting is the merchant's free choice among eight named German partners, purchase licenses exist alongside subscriptions, and when you move in the vendor itself migrates the shop core and the database structure and content. Every migration page describes coming to OXID, though: we found no public information on export completeness, a documented path out, or a data-return commitment for catalogue, customers and order history.

PrestaShop

Leaving looks cheap, which is rare: the backup documentation walks a merchant through taking the entire files and database with their own tools — mysqldump, PhpMyAdmin, SSH, scp, rsync, ZIP or TAR archives — on a server their hosting provider controls, with an Update Assistant module to automate it, and a CSV export component exists at framework level. We found no public information on contractual data-return commitments or a documented migration path in both directions.

OXID eSales

A German AG with a commercial register entry in Freiburg and eight named German hosting partners is the right half of the picture. But the vendor's own captured pages do not confirm where shop data resides, publish no subprocessor list for the platform, rest US transfers on standard contractual clauses, and the vendor's own site runs Meta, Google and LinkedIn tracking behind Swedish hosting.

PrestaShop

An EU entity is on the record — the homepage's newsletter consent names PrestaShop S.A as controller — but that is where the trail ends, with the managed hosting described as developed by PrestaShop and no location stated. We found no public information on where shop and order data reside, or on any subprocessor sitting in the checkout path.

OXID eSales

All four licence tiers are public with their 36- and 48-month minimum terms, an explicit no-revenue-share statement, a priced per-sub-shop surcharge and a disclosed revenue-linked reduction below 100.000 € Jahresshopumsatz, and even the statutory withdrawal button carries published figures — 0 EUR für Bestandskunden, 50 EUR / Monat für alle anderen. But hosting costs sit with the partners' own price lists, the pages are silent on whether licence prices are net or gross, and the broad extension catalogue is largely unpriced — the licence is computable, the invoice is not.

PrestaShop

We found no public information on prices of any kind — not a licence figure, not a hosting price for the managed service, not a module cost, not a transaction fee — so a merchant cannot begin to compute the real invoice from these pages. The captured hosting page describes on-demand resources and staging environments without stating what any of it costs.