OXID eSales vs PrestaShop

OXID eSales

Merchandising and B2B pricing are genuinely strong — per-category filters with campaign quick filters built without a developer, customer-specific price lists with tiers and discount logic, and five named payment integrations including Unzer and Adyen. I found no public information on a variant matrix, product bundles, guest checkout, or invoice and direct debit as named methods, so I cannot take this to the level a full catalogue conversion story would need.

PrestaShop

PrestaShop 9.2 ships a native one-page checkout with developer documentation for making modules and themes compatible with it, which is a genuine conversion feature. Beyond that I found no public information on variants, bundles, tiered or customer-group pricing, guest checkout, or which payment methods sit inside that checkout. A checkout I can see on one page but cannot price or pay through on paper sits in the low band.

OXID eSales

Tax and legal work arrives as official modules — country-specific tax rules, electronic VAT management, geoblocking, GDPR opt-in — and the withdrawal button handles the statutory duty from 19 June 2026 with timestamped documentation under §356 BGB, free of charge from OXID. I found no public information on automatic destination VAT with reverse charge, VAT-ID validation, OSS reporting or e-invoicing, so the merchant still owns the hard parts of the tax logic.

PrestaShop

The tax domain shows rates and tax rule groups configurable by hand — add, edit, toggle, bulk-delete — which is per-country VAT a merchant maintains personally, on documentation flagged as covering the outdated version 8. I found no public information on OSS reporting, VAT-ID validation with reverse charge, e-invoicing, or the mandatory German checkout texts, and the German-language site itself states it is no longer available. Legal correctness here is the merchant's job, not the vendor's.

OXID eSales

A flexible GraphQL interface, developer documentation with code examples and academy training, a GitHub module template, and a module ecosystem where extensions sit independent of the shop core and are tested with every release — that is a developer surface I could build an operation on. I found no public information on headless storefront builds, webhooks, staging environments or documented rate limits.

PrestaShop

This is a real developer platform: modules install, uninstall and upgrade from the back office, native modules are Composer-managed with source on GitHub, the Admin API is documented with Swagger, OAuth2 and multi-shop context, developers can add endpoints through CQRS, and the cloud offering has Git integration with dev, staging and production environments. I found no public information on a storefront API for headless builds, webhooks for core order events, or documented rate limits — precisely the surface an ERP connection lives on.

OXID eSales

The back office is credible: shipping methods and rules on one screen with conflict warnings surfaced before checkout, automatic ERP synchronisation of stock, orders and customer data through vendor modules, B2B order approval workflows, and a withdrawal process handled in the system with timestamps and duplicate detection. But I found no public information on partial shipments, multi-warehouse stock, named carriers with label printing or partial refunds — a shop that cannot show me a partial refund does not get past this mark.

PrestaShop

The order domain is worked, not decorative: orders can be created from the back office, payments added, products added with tax-included and tax-excluded prices, individual products cancelled, returns issued, carrier and tracking number updated, internal notes set and statuses changed in bulk. But December is made of the rest, and I found no public information on stock across warehouses or channels, partial shipments, carrier label printing, refunds including partials, or maintained interfaces to named ERP and accounting systems. Order machinery yes; a fulfilfulment operation not evidenced.

OXID eSales

Hosting is the customer's free choice among eight named German partners, the licence carries no revenue participation, and migrations move shop core files plus database structure and content — real ownership structure. I found no public information on complete export of catalogue, customers and orders, the documented migration path runs into the platform rather than out of it, and minimum terms of 36 or 48 months make leaving an expensive decision.

PrestaShop

Exit is credible: the documentation spells out backing up files and database, with mysqldump, PhpMyAdmin, several MySQL clients, compressed archives over FTP, SSH or rsync, and backup automation through the Update Assistant module from the back office or CLI. Releases are published with download links and module source sits on GitHub, so the merchant can run the shop on their own infrastructure, and an export component with CSV response handling is part of the core reference. That is full-fidelity export at the database level rather than a promised CSV.

OXID eSales

A German contracting entity in Freiburg and eight German hosting partners, one of them marketing itself on sovereign cloud hosting, give the platform a solid European base. The product's own data residency is not confirmed on the captured pages, no subprocessor list for the platform is published, and the vendor's own website runs US analytics and social embeds under standard contractual clauses with Sweden-hosted serving.

PrestaShop

The captured pages give me PrestaShop S.A named as newsletter controller and a managed hosting service developed by PrestaShop that adds resources on demand — but I found no public information on where that hosted data resides, which infrastructure carries it, or any subprocessor list. Where my customers' and orders' data physically sits and who processes it is unanswered on these pages.

OXID eSales

Every edition carries a public monthly price with the minimum term stated — Community 121 € / Monat, Professional 360 € / Monat, Enterprise B2C 1.123 € / Monat, Enterprise B2B 1.583 € / Monat — plus a stated sub-shop surcharge of +173 €/Monat and a clear statement of no revenue participation, and individual OPALs are quoted at 20 €/Monat, 50 EUR / Monat or 0 EUR für Bestandskunden. What a merchant still cannot compute from these pages: hosting cost, payment gateway rates, VAT treatment of the listed prices, and the price of most extensions beyond the OPALs.

PrestaShop

I found no public pricing information at all: the captured hosting page describes managed hosting, cache systems and scalability in detail without stating a price, billing period, transaction fee or VAT treatment, and no other captured page carries a figure. A merchant cannot compute even the licence line of an annual cost from these pages.