PrestaShop
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by PrestaShop SA · www.prestashop.com
Compare with OXID eSales → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
PrestaShop at a glance
- Vendor
- PrestaShop SA
- Headquarters
- Not stated on the vendor’s pages as of 8 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 8 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 8 Nov 2026
- Panel verdict
- The AI panel rates PrestaShop 2.5/5, the mean of 6 judges. PrestaShop is an open-source shop system from PrestaShop SA of Paris, majority-held by Italy's MBE Worldwide, and the bench scores it as a strong developer platform with real exit rights around a thin commerce core. how scores are made
- As of
- Vendor pages captured 15 Sep 2026 to 8 Nov 2026; evaluated by the panel 28 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
PrestaShop is an open-source shop system from PrestaShop SA of Paris, majority-held by Italy's MBE Worldwide, and the bench scores it as a strong developer platform with real exit rights around a thin commerce core. Extensibility scores range from 6 to 8: the Admin API runs on API Platform version 3 with OAuth2 and Swagger documentation, native module source sits on GitHub, and version 9.2 bundles a native One Page Checkout — we found no public information on a storefront headless API, webhooks or documented rate limits. Data control and exit scores cluster at 7 to 8 on documented full backups via mysqldump, PhpMyAdmin or the Update Assistant and a core CSV export component. Operations scores spread from 4 to 6 on single-order handling, though we found no public information on stock tracking, status emails or ERP links such as DATEV. Tax and legal as well as sovereignty sit flat at 3 — nothing captured addresses VAT-ID validation, OSS, invoicing, hosting location or subprocessors — and pricing transparency scored 0, with no prices in the captured pages.
Speaks for it
- Extensibility scores 6-8 on an Admin API built on API Platform version 3 with OAuth2, Swagger documentation and CQRS endpoints developers can extend
- Native modules are Composer-managed with source code on GitHub, and the Distribution API reports each module's latest compatible version per core release
- Data control and exit scores cluster at 7-8 on documented full backups of files and database via mysqldump, PhpMyAdmin or the Update Assistant, plus a core CSV export component
- The back office covers real order work — manual order creation from a cart, bulk status changes, returns, carrier and tracking updates, payments and internal notes
- Version 9.2 bundles a native One Page Checkout, with compatibility documentation for module and theme developers
Held against it
- Tax and legal scores sit at 3 — we found no public information on VAT-ID validation, reverse charge, OSS or invoicing, the captured tax reference documents PrestaShop 8 under an outdated warning, and the vendor's German-language site states it is no longer available
- Sovereignty scores sit at 3 — we found no public information on hosting location, subprocessors or a data processing agreement beyond the Paris controller named in the newsletter consent
- Catalog and checkout scores of 3-4 — we found no public information on payment providers by name, guest checkout, product variants or the payment methods German buyers expect
- Operations scores range 4-6 — we found no public information on stock tracking, status emails, label printing or maintained ERP and accounting links such as DATEV
- Pricing transparency scored 0 — we found no public information on licence fees, hosting tiers, billing periods or transaction rates in the captured pages
Best for
- You have in-house developers who want an open-source core with a documented Admin API, OAuth2 and Swagger documentation, and module source on GitHub
- You want to host on a server and provider of your own choosing and value a documented backup and exit path via mysqldump, PhpMyAdmin or the Update Assistant
- Your team runs orders manually and needs back-office order creation, bulk status changes, returns, tracking updates and internal notes
Avoid if
- You need German-market checkout correctness out of the box — ask the vendor: the public pages we read do not show it
- You must document the full subprocessor chain and a data processing agreement before signing — sovereignty scores sit at 3, and the captured pages name the Paris controller but we found no public information on hosting location or subprocessors
- You expect native stock tracking, carrier-label printing or maintained ERP and accounting links such as DATEV — operations scores range 4 to 6 and we found no public information on these interfaces
- You need published prices to build a business case — pricing transparency scored 0 and the captured pages state no licence, hosting or transaction figures
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 2 of 5 |
| Tax & German legal correctness | 1.5 of 5 |
| Extensibility & developer surface | 3.5 of 5 |
| Order operations & back office | 2 of 5 |
| Data ownership & exit | 4 of 5 |
| European sovereignty | 1.5 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and 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.
The Merchant
A native one-page checkout ships in the 9.2 bundle with developer documentation for modules and themes to adapt it, orders record payments by module name, and cart-rule discounts can be applied to orders — real conversion bones. But we found no public information on named payment providers, German payment methods such as invoice or direct debit, guest checkout, product variants or abandoned-cart recovery, so I cannot credit the level where payment breadth converts. 4 10
The B2B Seller
The developer documentation confirms a native One Page Checkout included in the PrestaShop 9.2 bundle, and order commands carry products with payment module names attached, so a catalogue-and-checkout path exists. We found no public information on variants, customer-group pricing, vouchers, guest checkout or the German payment methods trade buyers expect, so this reads as the basic conversion path. 4 10
The Developer
The checkout side is documented and real: version 9.2 ships a native one-page checkout module in the bundle, with a compatibility guide for module and theme developers. The order domain carries cart rules, per-order currency changes and both tax-included and tax-excluded product prices, which is more than a bare order pipeline. We found no public information in the captured pages on payment providers by name, product variants, guest checkout or the payment methods German buyers expect, so I stop short of the middle band. 4 10
The Operations Lead
PrestaShop 9.2 ships a native one-page checkout module in the bundle, and orders accept a payment method, cart rules (my read: vouchers and discounts) and both tax-included and tax-excluded prices. We found no public information on named payment providers, product variants, guest checkout or multi-currency selling, so this sits between a basic catalogue-and-checkout and the full conversion kit. 4 10
The Data Protection Officer
PrestaShop 9.2 ships a native One Page Checkout module in the bundle, order products carry both tax-included and tax-excluded prices, cart rules can be added to an existing order, and payments are recorded against a named payment module. We found no public information on product variants, guest checkout, the payment methods German buyers expect, or abandoned-cart recovery, so this sits just above a basic checkout that takes payment. 4 9 10
The Skeptic
The captured pages show a native One Page Checkout module bundled with version 9.2 and an order domain that records payment module names, products and discount cart rules — enough for a working checkout. But the pages show nothing on product variants, guest checkout, or a single named payment provider, let alone the methods German buyers expect. 4 10
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content 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.
The Merchant
Taxes are configurable with rates and localized names, tax rules groups are fully manageable for version 9, and orders carry both tax-included and tax-excluded prices — the captured version 8 tax reference carries an outdated notice while the tax-rules-group reference is current for version 9. Beyond that we found no public information on destination-country VAT, B2B VAT ID validation, OSS or the German checkout requirements, and the vendor's own German-language site states it is no longer available, which is not comforting for a German shop. 5 6 10 1
The B2B Seller
Taxes are configurable as rates and tax rules groups, and order lines hold both tax-included and tax-excluded prices, so gross and net values live in the data model — though the tax reference page carries a banner that its PrestaShop 8 documentation is outdated. We found no public information on VAT-ID validation, reverse charge for B2B, OSS reporting, invoicing or the German checkout requirements, and the vendor's German-language site is itself no longer available. The merchant assembles European correctness largely on their own. 5 6 10 1
The Developer
Taxes are first-class in the domain model: taxes can be added, edited, bulk-toggled and deleted with rates, tax rules groups have their own full command set, and orders store both tax-included and tax-excluded prices. We found no public information on VAT-ID validation, reverse charge, OSS, invoicing or the German checkout requirements on any captured page. The tax reference I read also carries a banner warning that it documents version 8 and is outdated, which tempers my confidence in how maintained this surface is. 5 6 10
The Operations Lead
Taxes are configurable rates grouped into tax rules groups, and order lines carry both gross and net prices, which covers the arithmetic basics. We found no public information on destination-country VAT determination, B2B reverse charge, VIES, OSS, invoicing content or the German checkout requirements — and the tax reference pages themselves warn that the PrestaShop 8 documentation is outdated, which for a German invoice is not a corner I want to cut. 5 6 10
The Data Protection Officer
Tax rates are configurable with localized names and enable/disable states, tax rules groups carry their own command set, and order products hold both tax-included and tax-excluded values. We found no public information on VIES validation, B2B reverse charge, OSS data, invoicing or the German checkout requirements, and the captured tax reference is itself flagged as covering PrestaShop 8 while the current line is 9. 5 6 10
The Skeptic
Taxes are configurable with rates and enabled flags, grouped under tax rules groups, and orders carry both tax-included and tax-excluded prices. Nothing in the captures addresses destination-based VAT, VAT-ID reverse charge, invoicing, or any German checkout requirement; the tax reference describes version 8 and carries an outdated warning, and the vendor's German-language site is no longer available. 5 6 10 1
Extensibility & developer surface
Show reasoningHide reasoning
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 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development 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.
The Merchant
The developer surface is the strongest thing here: an admin API on API Platform 3 with OAuth2, Swagger documentation, CQRS endpoints developers can extend, multi-shop context, back-office module install and upgrade, Composer-managed native modules with source on GitHub, and a cloud offering with Git integration plus dev, staging and production environments. We found no public information on a storefront API for headless builds or on documented rate limits, which keeps it below the top band. 7 8 2 4
The B2B Seller
A documented Admin API runs on API Platform with OAuth2, Swagger documentation and CQRS endpoints, modules install, upgrade and uninstall through the back office with native module source code on GitHub, and the cloud offering adds Git integration with dev, staging and production environments. Theme and module developers get dedicated checkout compatibility documentation. We found no public information on a storefront API for headless builds, webhooks or documented rate limits, so this stops short of a platform a team fully owns. 7 8 2 4
The Developer
This is my home ground, and the developer surface is genuinely strong: modules install, uninstall and upgrade from the back office, native modules are managed by Composer with source code on GitHub, and the Distribution API reports each module's latest compatible version per core release — a real compatibility model that protects customisations across upgrades. The Admin API sits on API Platform 3 with OAuth2, Swagger documentation and CQRS, developers can add endpoints, and themes are an addressed developer audience. I hold it below the top bands because the captured pages document no storefront API for headless builds, no webhooks, no documented rate limits and no local development workflow, and Git integration appears only inside the vendor's managed hosting offer rather than as a first-class developer facility. 2 4 7 8
The Operations Lead
A serious developer surface: an Admin API on API Platform version 3 with OAuth2, Swagger documentation and documented extension points for new endpoints, native modules managed by Composer with source on GitHub, and module install, uninstall and upgrade from the back office. The cloud offering adds Git integration with development, staging and production environments. We found no public information on a storefront API for headless builds or documented rate limits, which is what keeps it out of the top band. 7 8 2
The Data Protection Officer
Modules install, uninstall and upgrade from the back office with native module source on GitHub, the Admin API ships with OAuth2 and Swagger documentation and lets developers create new endpoints, and the managed hosting offers Git integration with dev, staging and production environments, plus checkout compatibility guidance for module and theme developers. We found no public information on webhooks, a storefront headless API or documented rate limits, which keeps this below the top level. 2 4 7 8
The Skeptic
Modules install, upgrade and uninstall from the back office, native modules are Composer-managed with source on GitHub, and the Admin API ships with OAuth2, Swagger documentation and CQRS endpoints developers can extend, while the vendor's managed hosting adds Git integration and dev, staging and production environments. The captures show no storefront API for headless builds, no webhooks, and no rate limits. 7 8 2 4
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
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.
The Merchant
After checkout the order domain is well covered: back-office pages to create and view orders, add payments with transaction ids, add or cancel individual products, issue returns, update carrier and tracking number, change status in bulk and keep internal notes. We found no public information on stock tracking, named carrier integrations or maintained links to ERP and accounting systems such as DATEV, so this sits at the solid mid-band rather than the operation-running level. 9 10
The B2B Seller
The order domain is genuinely worked: back-office pages to view and create orders, status changes in bulk, added payments, products added or cancelled, issued returns, updated carrier and tracking numbers, currency changes and internal notes. We found no public information on stock levels, partial shipments or refunds, or on interfaces to ERP and accounting systems, so the depth beyond solid single-order handling is unproven. 9 10
The Developer
The order domain is deep and the back office has order detail, order view and add-new-order pages: back-office order creation from a cart, payments, product additions and cancellations, bulk status changes, return issuance, carrier and tracking-number updates, internal notes and cart duplication are all documented commands. We found no public information on stock tracking, status emails, named carrier integrations or label printing, partial refunds, or ERP and accounting links such as DATEV, so I place this between the lower bands. 9 10
The Operations Lead
The back office does real order work: order view and order-creation pages, status updates including bulk changes, adding a product to an existing order, cancelling products within an order, issuing a return, updating carrier and tracking number, and internal notes visible only in the back office — a genuine back office for a shop that ships in December. We found no public information on partial refunds, label printing with named carriers, stock truth across warehouses and channels, marketplace order intake, or maintained links to ERP and accounting systems such as DATEV, which is exactly what I would want before running peak season on it. 9 10
The Data Protection Officer
Order handling is documented in the back office: order detail pages, manual order creation from a cart, status changes including bulk, payments, product cancellation, returns issuance, shipping carrier and tracking updates, and internal notes. We found no public information on stock tracking, status emails, named carrier or label integrations, partial shipments, or maintained interfaces to ERP and accounting systems such as DATEV — the link a German back office actually runs on. 9 10
The Skeptic
The order back office is genuinely deep — commands exist to add orders and payments from the back office, add or cancel products, issue returns, update carrier and tracking number, set internal notes, and change statuses in bulk. What the pages do not show is stock management, status emails, label printing or named carriers, refund handling, or ERP and accounting interfaces. 9 10
Data ownership & exit
Show reasoningHide reasoning
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 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, 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.
The Merchant
Exit is cheap and documented: full backups of files and database via mysqldump, PhpMyAdmin or SSH, automated through the Update Assistant module from the back office or command line, plus a core export component with CSV responses. With a fully managed hosting service from the vendor on one side and my own server on the other, catalogue and order history stay mine; we found no public information on contractual data return. 12 11 2
The B2B Seller
Ownership here is structural: the documented backup path covers files and the whole database through mysqldump or PhpMyAdmin, reached over SSH, RDP, scp or rsync on the merchant's own server, and an Update Assistant automates it from the back office and command line. Core export components including a CSV response are documented, and native module source code sits on GitHub. We found no public information on contractual data return terms, which is the piece that would make leaving costless on paper as well as in practice. 12 11 7
The Developer
Ownership here is structural rather than promised: the update documentation assumes your own server and hosting provider, prescribes full backups of files and database with standard tools — mysqldump, PhpMyAdmin, compressed archives over SSH, FTP or rsync — and the Update Assistant module automates that backup before each update, while the vendor separately sells a fully managed service so both paths exist. A CSV export component is part of the core reference. We found no public information on a documented migration path into the platform or contractual data return on cancellation, which is what keeps me off the top band. 2 11 12
The Operations Lead
Leaving looks cheap and well documented: full backup of files and database through mysqldump, phpMyAdmin, other MySQL clients or the Update Assistant module from the back office or command line, plus an export component with a CSV response in the core, and the backup flow assumes a server of my own choosing on an open-source platform with module source on GitHub. We found no public information on contractual data return on cancellation or a documented migration path in the other direction. 12 11 7
The Data Protection Officer
Exit is covered at the data level: the documentation walks through full backup of files and database via mysqldump, PhpMyAdmin or MySQL clients, with the Update Assistant automating it from the back office and the command line, an export component provides CSV output, and releases are downloadable to run on the merchant's own server. For my own file, though, we found no public information on deletion workflows that execute against customer records in order history, on contractual data return at cancellation, or on a documented migration path. 7 11 12
The Skeptic
Exit here is structural rather than promised: the software is distributed as downloadable releases, and the documentation walks through full backups of files and database — mysqldump, phpMyAdmin, SSH, scp, rsync, ZIP and TAR — with an Update Assistant module automating the process, alongside a vendor-managed hosting option and export components in the developer docs. A documented migration path in both directions and contractual data return are not shown in the captures. 12 7 11 2
European sovereignty
panel opinion
Show reasoningHide reasoning
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. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, 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.
The Merchant
The vendor is recorded as PrestaShop SA of Paris, France, majority-held by MBE Worldwide of Italy, and the newsletter consent names PrestaShop S.A as data controller — one European element proven. Hosting location, subprocessors and a published data-processing agreement are not established in the captured pages, so the rest of the chain stays unknown to me. 1 2
The B2B Seller
One European element is proven: the vendor line names PrestaShop S.A of Paris, and the captured consent text names PrestaShop S.A as controller of its newsletter data. Where customer and order data is hosted, the DPA and the subprocessors in the checkout path remain unstated in the captured pages — for a merchant selling across the EU, that is a conversation to have before signing. 1
The Developer
The vendor is listed as PrestaShop SA of Paris, majority-held by Italy's MBE Worldwide, and the captured homepage names PrestaShop S.A as the controller for newsletter data — European elements I can prove. We found no public information on where hosted shops' customer and order data resides, on subprocessors in the checkout path, or on a data processing agreement, so the rest of the chain stays unknown to me rather than European. 1 2
The Operations Lead
One European element is proven: the newsletter consent names PrestaShop S.A as the controller, and the company presents itself from Paris under majority Italian ownership. We found no public information on where customer and order data are hosted, on the subprocessor chain in the checkout path, or on a data processing agreement, so the rest of the chain stays unstated. 1 2
The Data Protection Officer
The vendor is PrestaShop SA of Paris, France, its newsletter consent names PrestaShop S.A as data controller with an unsubscribe option, and the software can run on a server and hosting provider of the merchant's choosing — one proven European element, and a self-controlled one. For a shop holding addresses and buying histories, we found no public information on where the vendor's managed cloud hosts the data, or on which subprocessors — CDN, analytics, payment routing, support tooling — sit in the checkout path, nor on a published subprocessor list or a data processing agreement. 1 2 12
The Skeptic
One European element is proven: PrestaShop S.A, a Paris company, is named as data controller for the newsletter sign-up on the vendor's own site. The captured pages give no hosting location for the managed hosting service, no subprocessor list and no data-processing agreement, so the rest of the chain stays unknown. 1 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
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 public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
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.
The Merchant not rated — no public information
We found no public information on pricing — no licence tiers, transaction fees, revenue share or billing terms appear in the captured homepage, hosting and checkout pages. As a merchant who judges price against contribution, I have nothing to judge. 1 2 3
The B2B Seller not rated — no public information
We found no public information on pricing: the captured homepage, hosting page and checkout page describe features but state no licence, subscription, transaction or hosting prices, so a merchant cannot compute an annual cost from the pages captured. 1 2 3
The Developer not rated — no public information
We found no public information on prices at all: the captured hosting page describes the scalability and development tooling of the managed service without any figures, and nothing captured states licence, module, transaction or support costs. I cannot compute an annual cost from these pages, and while the platform is presented as open source, no captured page states where the money actually goes. 1 2
The Operations Lead not rated — no public information
We found no public information on pricing: neither the captured homepage nor the hosting page shows licence tiers, transaction fees or a price for the managed hosting offer. I cannot compute an annual cost from what was captured. 1 2
The Data Protection Officer not rated — no public information
We found no public information on licence fees, hosting tiers, billing periods, order limits or transaction rates in the captured pages, so the annual cost of a shop cannot be computed from what was captured. The platform is presented as open source, which moves the money question to hosting and modules — and we found no public information on what those cost. 1 2
The Skeptic not rated — no public information
We found no public information on pricing in the captured pages: the homepage, the managed-hosting page and the checkout page record no licence fee, subscription tier, transaction fee or billing period. The only cost-relevant fact is that the core software is distributed as downloadable releases, which says nothing about what hosting or the checkout solution charge. 1 2 3 7
European sovereignty — proven facts
1 of 6 dimensions provenBuilt 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 |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Self-hostable | 1/1 pts | 13 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about PrestaShop
Is PrestaShop European?
Yes. whats-best.ai classifies PrestaShop as EU-Made.
Where does PrestaShop store data?
Not stated on the vendor’s pages as of 8 Nov 2026.
Does PrestaShop have a free plan?
Not stated on the vendor’s pages as of 8 Nov 2026.
What are the best alternatives to PrestaShop?
As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Shopware (3/5) highest among the other 28 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: PrestaShop alternatives.
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 9 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 9 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (15)
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 →
- 13 Self-hosting / on-premises installation docs — found from the homepage prestashop.com Checked 1 Nov 2026 Details →
- 14 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →
- 15 Structured-data backfill: markup only, no text or screenshot www.prestashop.com Checked 8 Nov 2026 Details →