OXID eSales vs PrestaShop

OXID eSales

Official payment integrations for PayPal, Stripe, Unzer, Adyen and Amazon Pay sit alongside tiered and customer-specific pricing, discount logic and per-shop conditions in a multilingual multishop setup — more than a basic product list. I found no public information on variants, bundles, guest checkout, or invoice and direct debit payment, which is what I would need to see to go higher.

PrestaShop

The captured pages do show a native One Page Checkout shipped in the 9.2 bundle, with documentation telling module and theme developers how to keep their solutions compatible — a real conversion feature and a checkout I can customise without a rebuild. Beyond that I found no public information on variants, bundles, tiered pricing, payment methods, promotions, or multi-currency, so the merchandising side of this criterion rests on nothing visible here.

OXID eSales

The vendor ships its own compliance modules — electronic VAT management, country-specific tax rules, geoblocking — plus a statutory withdrawal button that timestamps every withdrawal under §356 BGB, is free of charge and submittable without login. I found no public information on VAT-ID validation with reverse charge, OSS reporting or e-invoicing, and that caps it.

PrestaShop

Tax is configurable by hand — a full tax domain with rules groups, localised names and rates — but nothing here is automatic: I found no public information on VAT-ID validation, reverse charge, OSS reporting, e-invoicing, or legal checkout texts. The tax reference itself carries a warning that I am reading version 8 documentation while the product is on 9, and the German-language site is no longer available, so this is compliance I would be maintaining alone.

OXID eSales

This is my home ground: modules install separately, deactivate at will and sit independent of the shop core for easier updates, and there is a GraphQL API, developer documentation, code examples, academy training and a GitHub module template — the beginnings of a real plugin architecture. But I found no public information on local development, staging environments, version control for themes, webhooks or documented rate limits, and the OXID 7 migration explicitly hands third-party and custom modules plus theme and template work back to the customer or partner — upgrades that orphan my customisations are exactly the future migration I fear.

PrestaShop

This is what I judge a platform on, and it holds up: open-source core, native modules managed by Composer with per-version compatibility listings served through a Distribution API client I can replace, and an Admin API on API Platform 3 with OAuth2, Swagger documentation and CQRS so I can build my own endpoints. The managed hosting tier adds Git integration with dev, staging and production environments, which is the closest thing to theme version control in this capture. I found no public information on a headless storefront API, documented rate limits, or a local-development and CI story, which is what keeps it from the top band.

OXID eSales

Shipping methods, rules and assignments live on one screen with warnings for overlaps and orphaned rules, ERP synchronises stock, orders and customer data automatically, and the withdrawal process runs in the system with an admin view. I found no public information on partial shipments, multi-warehouse stock, named carrier integrations with label printing, or partial refunds.

PrestaShop

The order domain is genuinely deep — back-office order creation, added payments, product-level edits carrying both tax-included and tax-excluded values, bulk status changes, internal notes, return issuance, and shipping updates with carrier and tracking — so order workflow and returns live in the system rather than in a mailbox. I found no public information on multi-warehouse stock, named carrier integrations with label printing, or maintained ERP and accounting interfaces, which is what the upper band demands.

OXID eSales

Hosting is the merchant's free choice across eight named German partners, there is no revenue share, the migration check is cost-neutral, and the migration moves database structure and contents — that reads like database-level access rather than a promise. I found no public information on export completeness when leaving the platform or a contractual data-return commitment, which keeps it short of the top.

PrestaShop

Ownership is structural rather than promised: open-source software, a documented full backup of files and database through mysqldump or standard hosting tools, automated by the Update Assistant, so catalogue, orders and media can leave intact on my schedule. The only export component documented is a CSV response at framework level, and I found no public information on a documented migration path back in or a contractual data-return commitment, which caps it below the top.

OXID eSales

The contracting entity is a German AG in Freiburg and the hosting-partner network is all-German, including one firm advertising sovereign cloud hosting — but that is where the evidence stops. I found no public information on where shop and order data actually reside or which subprocessors sit in the checkout path, and the vendor's own site runs Google Analytics, Meta's pixel and LinkedIn's tag with US transfers based on standard contractual clauses.

PrestaShop

The controller named in the consent text is PrestaShop S.A and the provenance places the vendor in Paris under Italian majority ownership, but the managed hosting pages state no data-residency location, and I found no public information on subprocessors anywhere in the checkout path. An absent subprocessor list plus unstated hosting location leaves the hosted chain unverifiable from these pages; only the self-hosted, open-source route would put it under my own control.

OXID eSales

Four edition prices with minimum terms stated, an explicit no-revenue-share commitment, a per-subshop surcharge and published module subscription prices make the licence side of the annual cost computable. Hosting cost sits with the freely chosen provider, and I found no public information on the VAT treatment of the listed prices, so the real annual total still needs assembly.

PrestaShop

None of the captured pages states a price — no licence tiers, no hosting cost, no transaction fees, no module pricing — so a real annual cost cannot be computed from what is public here. The hosting page describes scalability and tooling without a single figure, and even for an open-source licence I found no captured statement of where the money actually goes.