OXID eSales vs PrestaShop

OXID eSales

Customer-specific price lists, tiers and discount logic are evidenced for trade customers, together with quick order by article number, quotes, approval workflows and buyer management, and five payment providers are named as official modules. We found no public information on a variant matrix, product bundles, guest checkout, or invoice purchase and direct debit named for German buyers, so merchandising depth beyond trade pricing stays unproven.

PrestaShop

The captured pages show a native one-page checkout bundled with version 9.2 plus developer guidance for making modules and themes compatible with it — a real conversion feature. Beyond that we found no public information on variants, bundles, tiered or customer-group pricing, payment methods, or net-price display for trade customers, so I cannot confirm this shop meets a business buyer at checkout.

OXID eSales

Country-specific VAT rules and an electronic VAT administration ship as official modules, and the statutory withdrawal button with automatic §356 BGB timestamp documentation is genuine German checkout law handled in the shop. For trade commerce we found no public information on VAT-ID validation, reverse charge, net display per customer group, OSS or XRechnung/ZUGFeRD e-invoicing — exactly the pages a B2B buyer needs before signing.

PrestaShop

Taxes are configurable by hand — rates with localised names, grouped into tax rules groups, with commands to add, edit and bulk-toggle — and beyond that we found no public information on automatic VAT by destination, VAT-ID validation, reverse charge, net display per customer group, OSS or e-invoicing, which are exactly what my EU trade customers need. The captured tax pages also carry a notice that they document an older major version.

OXID eSales

A GraphQL interface, a Solution Hub with third-party modules plus official ones tested with every release, a Smarty-to-Twig template engine, developer documentation, academy training and a GitHub module template evidence a real developer surface, and the module-versus-component model with its own activation lifecycle points beyond the basics. We found no public information on staging environments, documented rate limits, or local development and CI support.

PrestaShop

This is a genuine developer surface: an Admin API on API Platform 3 with OAuth2, Swagger documentation, CQRS endpoints and multi-shop context, a module ecosystem with install, uninstall and upgrade through a distribution API, Composer-managed native modules with source on GitHub, and a managed hosting tier with Git integration and separate dev, staging and production environments. We found no public information on a storefront API for headless builds or documented rate limits, which is what separates this from the top band.

OXID eSales

ERP, PIM, CRM and inventory synchronisation of stock, orders and customer data are promised, the shipping-rule engine that warns about conflicts before they reach checkout is strong back-office material, and statutory withdrawals are processed in the system even without login. The ERP systems stay unnamed, and we found no public information on partial shipments, multi-warehouse stock, carrier label printing or operational reporting.

PrestaShop

The back office can create an order from an existing cart, record a payment with method, amount and transaction id, add products priced both tax-included and tax-excluded, change statuses in bulk, set internal notes, issue a merchandise return and update carrier and tracking number — enough for phone orders and payment on account. We found no public information on stock and warehouse handling, carrier label printing, or maintained interfaces to ERP and accounting systems.

OXID eSales

Free choice of hosting provider with eight named German hosting partners, plus a fixed licence without revenue share, keep the stack portable, and a free technical migration check documents a serious migration path inbound. We found no public information on export completeness for catalogue, customers and order history or on a documented exit; the only data-return statement captured is the general GDPR portability right on the website.

PrestaShop

Leaving is well documented: back up files and database, with mysqldump or phpMyAdmin for a full dump, ZIP or TAR archives moved over FTP, SSH, RDP, scp or rsync, and an Update Assistant module that automates the backup from the back office or CLI — on a platform whose source is public and which also offers managed hosting. We found no public information on documented deletion, a stated data-return commitment, or a migration path in either direction.

OXID eSales

A German contracting entity with German addresses, banking and EFRE funding, hosting partners all German and the vendor's own site hosted in Sweden, with US transfers for analytics named on an EU Standard Contractual Clauses basis and Munich-based Usercentrics for consent. We found no public information on a published subprocessor list for the platform or on where production customer and order data reside.

PrestaShop

The company presents as Paris-based and names PrestaShop S.A as the controller for its own newsletter, and managed hosting is offered — but we found no public information on where shop and checkout data are hosted, the jurisdiction of the contracting entity, ownership, or any named subprocessor. For a trade customer's order data I want more on the page than that.

OXID eSales

Every edition is priced publicly with billing period and minimum term — Community at 121 € / Monat for 36 months, Professional at 360 € / Monat, Enterprise B2C at 1.123 € / Monat, Enterprise B2B at 1.583 € / Monat for 48 — plus the stated "+173 €/Monat je Sub-Shop", an explicit "Klare Preise, keine Umsatzbeteiligung", sampled module prices such as "20 €/Monat" and "50 EUR / Monat", and a free migration check. We found no public information on VAT treatment of the licence prices, hosting costs at the partners, or prices for the wider module catalogue, which keeps the real annual invoice one conversation short of fully computable.

PrestaShop

No captured page states a price of any kind — not for managed hosting, not for modules, not a transaction fee — so a merchant cannot compute an annual cost from public pages alone. The open-source distribution implies the licence itself is free, but we found no public statement of what the hosting or the extensions a real shop needs actually cost.