whats-best.ai

E-Commerce Platforms & Shop Systems

Saleor

Provenance unknown 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.

by Saleor Commerce · saleor.io

Report an error on this page Is this your product? →

Link to this page

Saleor: AI-assisted analysis on whats-best.ai Saleor: AI-assisted analysis on whats-best.ai (dark)

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.

Saleor at a glance

Vendor
Saleor Commerce
Headquarters
Not stated on the vendor’s pages as of 13 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 13 Oct 2026
Free plan
Not stated on the vendor’s pages as of 13 Oct 2026
Panel verdict
The AI panel rates Saleor 2.5/5, the mean of 6 judges. Saleor is an open-source, headless commerce platform whose strength is extensibility, where scores cluster at 8–9, resting on a GraphQL API, 160-plus webhooks including synchronous ones, 45-plus dashboard mount points, and mostly forkable, self-hostable apps. how scores are made
As of
Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources

Saleor alternatives, European ones first →

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

The Data Protection Officer

Weighted verdict

The shop holds customers, addresses and buying histories, and the checkout is full of third parties. Wants the subprocessor list, consent handling that survives a complaint, deletion that executes against order history, and an answer on where the CDN and analytics sit.

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

Scored by The Data Protection Officer

Panel median The Data Protection Officer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Data Protection Officer
Catalogue & checkout 2 of 5 2 of 5
Tax & German legal correctness 2 of 5 2 of 5
Extensibility & developer surface 4 of 5 4 of 5
Order operations & back office 3 of 5 3.5 of 5
Data ownership & exit 3 of 5 2.5 of 5
European sovereignty 0.5 of 5 0 of 5

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 Data Protection Officer

The documentation shows a full variant model with attributes, per-channel price listings and discount fields, plus an advertised checkout API. We found no public information on payment methods, guest checkout, bundles or promotion rules — the conversion machinery a German shop needs — so the evidenced catalogue is strong but the checkout path beyond the API name is silent. 1 2 3

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 Data Protection Officer

This is where the platform earns its keep: an open-source core, a GraphQL API, 160-plus webhooks including synchronous events for extending flows, 45-plus dashboard mount points, and apps that are mostly open source and can be forked onto the merchant's own infrastructure. Sandboxes and snapshots give a staging story, though we found no public information on documented rate limits or upgrade guarantees for customisations. 1 6 7

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 Data Protection Officer

Fulfilment is deep: multi-warehouse split shipments, approval and cancellation flows with restocking, partial refunds that can include shipping costs, and returns and replacements that generate draft orders automatically. We found no public information on carrier integrations with label printing or maintained interfaces to named ERP and accounting systems, which is what the back office hinges on. 1 8 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 Data Protection Officer

Product export is real and configurable — selectable fields, warehouse stock columns, asynchronous delivery with a downloadable URL — and the open-source core with forkable apps makes running the shop on one's own infrastructure a genuine exit option. We found no public information on exporting customer records and order history, on a documented deletion process that executes against order data, or on any contractual data-return commitment. 1 6 10 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 Data Protection Officer

Every sovereignty attribute came back unknown — contracting entity jurisdiction, ownership, data residency and subprocessor exposure — and the managed cloud offering is described without naming a location. We found no public information on where customer and order data are processed or which third parties sit in the checkout path, including CDN and analytics, which is the lowest band of evidence. 1

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 Data Protection Officer

The captured pages show no price for the managed cloud, for support, or for extensions; entitlements like direct access to the core team read as a sales conversation. The only cost fact evidenced is the open-source core available on GitHub, which on its own does not make an annual invoice computable. 1

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.

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

Questions about Saleor

Is Saleor European?

Not determined: the vendor’s pages as captured do not say where Saleor is based.

Where does Saleor store data?

Not stated on the vendor’s pages as of 13 Oct 2026.

Does Saleor have a free plan?

Not stated on the vendor’s pages as of 13 Oct 2026.

What are the best alternatives to Saleor?

As of 21 Oct 2026, the panel rates JTL-Shop (3/5), Medusa (3/5) and Shopify (3/5) highest among the other 25 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). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Saleor alternatives.

Where this could be wrong

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.

Sources (11)

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

  1. 1 Vendor page saleor.io Checked 13 Oct 2026 Details →
  2. 2 Catalogue & checkout — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  3. 3 Catalogue & checkout — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  4. 4 Tax & German legal correctness — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  5. 5 Tax & German legal correctness — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  6. 6 Extensibility & developer surface — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  7. 7 Extensibility & developer surface — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  8. 8 Order operations & back office — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  9. 9 Order operations & back office — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  10. 10 Data ownership & exit — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →
  11. 11 Data ownership & exit — found from sitemap docs.saleor.io Checked 13 Oct 2026 Details →