whats-best.ai
Search Sign in

E-Commerce Platforms & Shop Systems

Sana Commerce

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

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

by Sana Commerce B.V. · www.sana-commerce.com

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

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

Variant handling is real and deep — matrix or dropdown presentation across seven named ERP systems, all variants compared on one page, translatable variant names — and the payment set is broad, twenty-four methods including direct debit and Klarna pay-later, with guest ordering referenced in the payment documentation. I found no public information on bundles, tiered or customer-group pricing rules, or promotions and vouchers; pricing in fact arrives live from the ERP rather than from any rule engine I can see. One caution: the captured pages give different states for the payment add-on, with the Adyen Checkout add-on marked deprecated in favour of Sana Pay. 3 4 1

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

The only developer surface in evidence is the App Center, where delivery-service apps install "with a single button click", plus editable system pages for return orders in the admin. I found no public information on theme customisation, APIs, webhooks, a headless storefront, staging environments or any local development story. 8 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

Returns are genuinely worked — invoice-based and invoice-free return orders with per-line comments, file attachments, ERP-sourced return reasons and administrator notification — and there is real-time integration with named carriers FedEx, UPS, USPS, Purolator and nShift, on an architecture that syncs stock, prices and order information live with seven named ERP systems. I found no public information on label printing, partial shipments, multi-warehouse stock, dropshipping flows or operational reporting a merchant could run the business from. 7 8 1 3

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

Export from the platform is CSV only — shop accounts with the password field left blank, and product pages without default values and without the media files themselves, only counts and URLs — while data that sits in the ERP must be exported from the ERP on the merchant's side, which does mean order history ultimately lives in the merchant's own systems. I found no public information on a documented deletion routine, an API or database-level export, a data-return commitment, self-hosting, or any migration path in either direction; return-order attachments sit on the vendor's web server file system. 9 10 7

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

The imprint names an EU operator in Rotterdam with a KvK number and a Dutch VAT ID, though the captured pages give different company names — the vendor header says Sana Commerce B.V. while the imprint names Sana Commerce EMEA B.V. — and the contracting entity for the cloud product is not stated. I found no public information on where customer and order data are hosted, on any subprocessor list, or on where the CDN and analytics sit, and card processing is described only as "outsourced to validated third-party service providers" with the payment chain naming Adyen and a successor add-on. 2 4 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

I found no public information on pricing at all: no tier prices, no billing periods, no transaction or revenue-share fees, and no costs for the App Center apps or the payment add-on. The homepage and the help pages name capabilities without attaching a price to any of them, so the real annual cost is a sales conversation, not a computation. 1 8 4

Report an error

European sovereignty — proven facts

1 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

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.

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

Sources (10)

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

  1. 1 Vendor homepage www.sana-commerce.com Checked 17 Sep 2026 Details →
  2. 2 Imprint www.sana-commerce.com Checked 17 Sep 2026 Details →
  3. 3 Catalogue & checkout — found from sitemap support.sana-commerce.com Checked 1 Oct 2026 Details →
  4. 4 Catalogue & checkout — found from sitemap help.sana-commerce.com Checked 1 Oct 2026 Details →
  5. 5 Tax & German legal correctness — found from sitemap support.sana-commerce.com Checked 1 Oct 2026 Details →
  6. 6 Tax & German legal correctness — found from sitemap help.sana-commerce.com Checked 1 Oct 2026 Details →
  7. 7 Order operations & back office — found from sitemap support.sana-commerce.com Checked 1 Oct 2026 Details →
  8. 8 Order operations & back office — found from sitemap support.sana-commerce.com Checked 1 Oct 2026 Details →
  9. 9 Data ownership & exit — found from sitemap support.sana-commerce.com Checked 1 Oct 2026 Details →
  10. 10 Data ownership & exit — found from sitemap support.sana-commerce.com Checked 1 Oct 2026 Details →