E-Commerce Platforms & Shop Systems

PrestaShop

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Merchant v1.0 · The B2B Seller v1.0 · The Developer v1.0 · The Operations Lead v1.0 · The Data Protection Officer v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 5 Oct 2026

Compare with OXID eSales → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Merchant

Weighted verdict

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.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Merchant

Catalogue & checkout

How this is scored

Products, variants, pricing rules and the path to payment — the part that either converts or does not.

0 — Flat product list with one price and no variants; checkout is a form and one payment method.

3 — Variants and categories with a standard checkout and two or three payment methods, but no bundles, no tiered pricing and no guest checkout worth the name.

5 — Full variant matrix, product bundles, tiered and customer-group pricing, guest checkout, and the payment methods a German shop needs including invoice and direct debit.

8 — Configurable products, per-channel pricing, promotions and vouchers with rules, a checkout that can be customised without a rebuild, and payment via the major providers plus buy-now-pay-later where offered.

10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.

Report an error

The Merchant

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

Report an error

Tax & German legal correctness

How this is scored

VAT determination, OSS, B2B reverse charge, and the checkout requirements German law actually imposes — judged on what the platform does, not on a plugin someone could buy.

0 — A single VAT rate applied everywhere; no B2B handling, no country logic, no legal-text handling in checkout.

3 — Per-country VAT rates configurable by hand, net prices for B2B possible with effort, and legal texts as free-form pages.

5 — Automatic VAT by destination and customer type, VAT-ID validation with reverse charge, gross and net display per customer group, and the mandatory checkout elements (order button wording, withdrawal policy, price indications) handled.

8 — OSS thresholds tracked and reported, correct invoicing per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.

10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.

Report an error

The Merchant

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. 5 6

Report an error

Extensibility & developer surface

How this is scored

Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.

0 — Fixed templates, no app ecosystem, no API.

3 — Theme editing within limits and a small app store; a read-mostly API and no local development story.

5 — Custom themes with a template language, an app or plugin ecosystem, a documented REST API, and webhooks for the core order events.

8 — Full storefront API for headless builds, an extension framework with its own lifecycle, staging environments, version control for themes, and documented rate limits.

10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.

Report an error

The Merchant

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. 7 8 2

Report an error

Order operations & back office

How this is scored

What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.

0 — An order list and an email; stock is a number nobody trusts, returns are manual.

3 — Order statuses and basic stock, one shipping integration, and returns handled by hand.

5 — Order workflow with partial shipments, multi-warehouse stock, named carrier integrations with label printing, and a returns process in the system.

8 — Multi-channel order intake, automated fulfilment routing, supplier and dropshipping flows, and maintained interfaces to named ERP and accounting systems.

10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.

Report an error

The Merchant

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. 10 9

Report an error

Data ownership & exit

How this is scored

Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.

0 — Export is a partial CSV; order history and customer records cannot leave intact, and hosting is the vendor's alone.

3 — CSV export of products and customers, order history partial, no self-hosting, no documented migration path.

5 — Complete export of catalogue, customers and orders via API or dump, documented deletion, and a stated data-return commitment.

8 — Full-fidelity export including media and order documents, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.

10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.

Report an error

The Merchant

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. 12 11

Report an error

European sovereignty

How this is scored

Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline.

0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — CDN, analytics, payment routing, support tooling — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.

Report an error

The Merchant

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. 1 2

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.

0 — No public prices at all; every tier is a sales conversation.

3 — A monthly headline exists, but transaction fees, mandatory apps or hosting costs are unstated — the invoice is unknowable from the page.

5 — Tier prices public with billing period stated and transaction fees given, but at least one commonly needed piece (a required app, hosting, payment gateway rate) is unpriced.

8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.

10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.

Report an error

The Merchant

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

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Not determined	—	uncited Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined	—	uncited Report an error
Subprocessors	Not determined	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

We found no public information on pricing on the pages we read (prestashop.com/de, prestashop.com/hosting, prestashop.com/essentials/prestashop-checkout, devdocs.prestashop-project.org/9/modules/checkout, devdocs.prestashop-project.org/8/development/architecture/domain/references/tax, devdocs.prestashop-project.org/9/development/architecture/domain/references/tax-rules-group and 6 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
We found no public information on compliance on the pages we read (prestashop.com/de, prestashop.com/hosting, prestashop.com/essentials/prestashop-checkout, devdocs.prestashop-project.org/9/modules/checkout, devdocs.prestashop-project.org/8/development/architecture/domain/references/tax, devdocs.prestashop-project.org/9/development/architecture/domain/references/tax-rules-group and 6 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
21 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
5 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
5 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us

Do you know more about PrestaShop? Tell us Report an error on this page

Sources (12)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor homepage www.prestashop.com Checked 15 Sep 2026 Details →
2 Security / trust page prestashop.com Checked 30 Sep 2026 Details →
3 Catalogue & checkout — found from sitemap prestashop.com Checked 1 Oct 2026 Details →
4 Catalogue & checkout — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
5 Tax & German legal correctness — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
6 Tax & German legal correctness — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
7 Extensibility & developer surface — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
8 Extensibility & developer surface — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
9 Order operations & back office — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
10 Order operations & back office — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
11 Data ownership & exit — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →
12 Data ownership & exit — found from sitemap devdocs.prestashop-project.org Checked 1 Oct 2026 Details →