Sana Commerce

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.

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

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

Link to this page

Sana Commerce: AI-assisted analysis on whats-best.ai Sana Commerce: 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.

Sana Commerce at a glance

Vendor
Sana Commerce B.V.
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Sana Commerce 2/5, the mean of 6 judges. Sana Commerce is a B2B commerce platform built on ERP systems, and scoring is strongest where that architecture shows: operations and catalog and checkout. how scores are made
As of
Vendor pages captured 17 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Sana Commerce alternatives, European ones first →

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

The panel's verdict

Sana Commerce is a B2B commerce platform built on ERP systems, and scoring is strongest where that architecture shows: operations and catalog and checkout. Stock, prices and orders sync in real time to seven named Dynamics and SAP systems; returns run as invoice-based and invoice-free flows with ERP-sourced reasons; shipping integrates with FedEx, UPS, USPS, Purolator and nShift; and checkout takes 24 payment methods, with card data kept out of the shop. Extensibility and sovereignty are the weak points, both scoring 3: the documented surfaces are an App Center and editable admin pages, with no public information on APIs, webhooks or headless builds, and beyond the proven Rotterdam operator, Sana Commerce EMEA B.V. (KvK 24275452), hosting location, data residency, a data processing agreement and the subprocessor chain are unstated on the captured pages. Tax and legal and data control and exit vary by one point on how far configurable tax presentation and ERP-resident master data offset tax calculation living in the ERP and exports limited to shop-database data. No prices appear on the captured pages.

Report an error

Speaks for it

  • Operations scores cluster at 6-7, the strongest criterion
  • Invoice-based and invoice-free return orders with ERP-sourced reasons, per-line comments and confirmation e-mails
  • Real-time shipping with FedEx, UPS, USPS, Purolator and nShift, per-location methods and live order tracking
  • Twenty-four payment methods through Adyen, with card data kept out of the store (the Adyen add-on is deprecated in favour of Sana Pay)
  • Variant catalogs as matrix or dropdown views with side-by-side comparison on one page

Report an error

Held against it

  • Extensibility scores sit at 3, with the App Center and editable admin pages as the documented surfaces and no public information on APIs, webhooks or headless builds
  • Taxes are configured and calculated in the ERP, leaving German checkout compliance to ERP setup
  • We found no public information on VAT ID validation, reverse charge, OSS or order-button wording
  • Export covers only data stored in the shop database, with media as URLs and counts, passwords excluded and ERP data not exportable from the shop
  • We found no public information on hosting location, data residency, a data processing agreement or the subprocessor chain

Report an error

Best for

  • You run Microsoft Dynamics or SAP and want the storefront to sit directly on that ERP with real-time stock, price and order sync
  • Your B2B buyers navigate variant-heavy catalogs and need matrix or dropdown views with side-by-side comparison
  • Your operations team works returns and named-carrier shipping day to day
  • You want card data never to reach the shop, with processing outsourced to a validated provider

Report an error

Avoid if

  • Your developers need documented APIs, webhooks, theme code or headless storefront access to shape the platform
  • Your conversion model depends on in-shop discounts, vouchers and abandoned-cart recovery
  • Your shop must evidence tax compliance itself, rather than defer it to ERP configuration
  • Your exit plan requires exports beyond the documented CSV of shop accounts and product page content

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Catalogue & checkout 3 of 5
Tax & German legal correctness 2 of 5
Extensibility & developer surface 1.5 of 5
Order operations & back office 3 of 5
Data ownership & exit 1.5 of 5
European sovereignty 1.5 of 5

Catalogue & checkout

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

Report an error

The Merchant

Product variants are genuinely strong — matrix or dropdown display, unlimited components, side-by-side comparison on one page, all managed in the ERP — and checkout offers twenty-four payment methods through Adyen including PayPal, SEPA direct debit, Sofortüberweisung and Klarna's pay-later options, plus saved cards for repeat buyers. But I found no public information on discounts, vouchers, rule-based promotions, tiered or customer-group pricing, or abandoned-cart recovery, which are the levers I price my contribution on. 3 4 1

Report an error

The B2B Seller

Variants are managed in the ERP and presented as matrices or dropdowns with variant comparison on one page, and the checkout takes 24 payment methods through Adyen — PayPal, SEPA Direct Debit, Sofortüberweisung and Klarna's buy-now-pay-later among them — with guest ordering possible. Prices and stock sync in real time from the ERP and catalogs can be personalized, which is how customer-specific trade price lists would reach a buyer; we found no public information on promotions or voucher rules, tiered pricing in the shop, or abandoned-cart recovery. Solid merchandising and payment depth, thin on rule-driven conversion. 1 3 4

Report an error

The Developer

The catalogue is ERP-managed with real-time stock and price sync, variants presented as a matrix or dropdowns, and 24 payment methods through Adyen including PayPal, SEPA direct debit and Klarna buy-now-pay-later, with guest orders possible and a checkout that stays on-page. I found no public information on promotions, abandoned-cart recovery, per-market pricing or a checkout customisable without a rebuild, and the Adyen Checkout add-on is deprecated in favour of Sana Pay — pricing logic lives in the ERP rather than in the shop, which works but leaves conversion tooling thin. 1 3 4

Report an error

The Operations Lead

Variants run deep — matrix or dropdown display, unlimited components, managed in the ERP and translated — and checkout takes 24 payment methods through Adyen including PayPal, SEPA direct debit, Giropay and Klarna buy-now-pay-later, with guest orders and saved-card repeat payment. Discounts, vouchers, abandoned-cart recovery and per-market pricing rules are not documented on the pages we read, which keeps this short of the top tier. 1 3 4

Report an error

The Data Protection Officer

Product variants are documented in depth — matrix or dropdown display, unlimited components, variant comparison — with guest ordering and saved-card one-click payment, and payment through a named provider offering twenty-four methods including PayPal, SEPA direct debit, Giropay and Klarna, with Sana Pay announced as successor to the deprecated Adyen add-on. We found no public information on discounts or voucher handling, rule-based promotions, abandoned-cart recovery or checkout customisation. From my chair the checkout keeping card data out of the store and outsourced to a validated processor is the right shape, though only that one processor is named. 3 4

Report an error

The Skeptic

Variants are real — ERP-managed, shown as a matrix or dropdown with all variants compared on one page — and checkout takes payment through named provider Adyen with 24 methods including PayPal, SEPA Direct Debit, Sofortüberweisung and Klarna, alongside configurable guest ordering and saved-card one-click payment. Personalized catalogs and ERP-based recommendations are marketed on the homepage. The captured pages give no figures on discounts, tiered or customer-group pricing, rule-based promotions or abandoned-cart recovery. 1 3 4

Report an error

Extensibility & developer surface

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

Report an error

The Merchant

There is an app centre — external delivery apps install with a single button click — and the system pages behind returns and checkout are editable in the admin, which is more than a closed builder. I found no public information on a documented API, webhooks, custom themes with code access, or a headless storefront, so a checkout I could reshape without a rebuild is not something I can see. 8 7 3

Report an error

The B2B Seller

The Sana App Center installs delivery-service apps with one click, payment comes as exchangeable add-ons — the Adyen Checkout add-on is deprecated in favour of Sana Pay — and return-order system pages are editable in the admin. We found no public information on a storefront API, webhooks, a template language or headless builds. The shop can be extended with apps, but a development team reshaping it is not evidenced. 4 7 8

Report an error

The Developer

Customisation means page layouts, content elements and editable system pages in the admin, plus an App Center whose apps install with a single button click and vendor add-ons like Sana Pay. I found no public information on an API, webhooks, template code access, version control for themes, or a local development setup — as the one maintaining this for five years, a closed admin editor plus a curated app shelf reads as a future migration, not a platform I can own. 3 4 7 8

Report an error

The Operations Lead

There is an App Center — delivery services install with a single click — and system pages and page layouts are editable in the admin, which is editor-level shaping plus a plugin shelf. We found no public information on a documented API, webhooks, headless storefront access or theme code access. 3 7 8

Report an error

The Data Protection Officer

The Sana App Center is the one documented surface: shipping and other add-ons installable with a single button click. We found no public information on theme editing, a developer API, webhooks or headless storefront builds — which also leaves me no documented view of what third parties can attach to the checkout. 8

Report an error

The Skeptic

There is an app ecosystem — delivery services install from the Sana App Center with a single button click, and payment arrives as add-ons (the deprecated Adyen Checkout and its replacement Sana Pay) — plus editable system pages, page layouts and content elements in Sana Admin. We found no public information on a documented API, webhooks, headless storefront access, custom theme code, staging environments or rate limits. 3 4 7 8

Report an error

Order operations & back office

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

Report an error

The Merchant

This is the strong side: return orders are fully worked with invoice-based and invoice-free flows, return reasons retrieved from the ERP, customer confirmation and administrator notification emails, and file attachments; shipping integrates in real time with FedEx, UPS, USPS, Purolator and nShift, with per-location shipping methods and live order tracking; and stock, prices and order data sync in real time with Dynamics and SAP systems. I found no public information on partial shipments or partial refunds, multi-warehouse stock, marketplace order intake, or maintained links to an accounting system such as DATEV. 7 8 1 3

Report an error

The B2B Seller

Returns are worked in depth: invoice-based returns where the customer selects order lines from posted invoices, invoice-free returns processed by a sales manager, ERP-sourced return reasons, per-line comments and confirmation and notification e-mails, across Dynamics and SAP systems. Shipping integrates in real time with FedEx, UPS, USPS, Purolator and nShift, shipping methods can be configured per location, and stock, prices and order information sync live from the ERP. We found no public information on partial shipments, partial refunds, multi-warehouse stock or marketplace order intake, which keeps it one band below the top. 1 7 8

Report an error

The Developer

Returns are worked properly — invoice-based line selection and invoice-free orders, per-line comments, attachments, reasons pulled from the ERP, notifications to customer and admin — alongside real-time stock, price and order sync and named carriers (FedEx, UPS, USPS, Purolator, nShift) with live tracking. Deep, maintained integration to seven named Dynamics and SAP systems is the core of the product, but I found no public information on partial shipments or refunds, multi-warehouse stock, marketplace intake, or DATEV. 1 7 8

Report an error

The Operations Lead

This is the front of an ERP operation: real-time stock, price and order sync into Microsoft Dynamics NAV/AX/Business Central/Finance and Operations and SAP Business One/ECC/S/4HANA, named carrier integrations (FedEx, UPS, USPS, Purolator, nShift) with real-time tracking, and returns customers create themselves — invoice-based picking the exact order lines to return, with ERP-sourced reasons, comments and attachments. Partial shipments, label printing and accounting links such as DATEV are not documented on the pages we read, so it stops short of the complete back office. 1 3 7 8

Report an error

The Data Protection Officer

Returns are worked in the system — invoice-based and invoice-free return orders, per-line comments, ERP-sourced return reasons, confirmation e-mails to customer and administrator — and shipping runs in real time against named carriers (FedEx, UPS, USPS, Purolator, nShift) with per-location methods and order tracking, on top of real-time ERP synchronisation of stock, prices and order information. We found no public information on partial shipments or partial refunds, multi-location stock, or accounting interfaces such as DATEV. 1 7 8

Report an error

The Skeptic

Returns are genuinely worked — invoice-based and invoice-free return orders, ERP-sourced return reasons, per-line comments, file attachments, confirmation emails and admin notifications — and shipping runs real-time against named carriers (FedEx, UPS, USPS, Purolator, nShift) with tracking and per-location methods. Stock, prices and order information sync in real time with the named ERP systems across the Dynamics and SAP families, which the vendor itself maintains as the core of the product. We found no public information on partial shipments, partial refunds, multi-warehouse stock, dropshipping or a DATEV interface. 1 7 8

Report an error

Data ownership & exit

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

Report an error

The Merchant

Shop accounts export to and import from CSV in the admin — passwords excluded — and product pages move between webstores and environments as CSV for backup and bulk editing. But the product-page export carries only custom titles, descriptions and metadata with default values left out, new products cannot be created by import, and data held in the ERP cannot be exported from the shop; I found no public information on order export, full-fidelity export including media and documents, or data return and deletion on cancellation. 9 10

Report an error

The B2B Seller

The admin exports shop accounts to CSV — passwords excluded — and product pages to CSV for backup, bulk editing and moving translations between webstores, with only custom values exported. Export is explicitly limited to data stored in the Sana database and ERP data cannot be exported from the shop; we found no public information on order export or on data return when a contract ends. Catalogue and price data live largely in the merchant's own ERP, but leaving the platform is evidenced only as partial CSV files. 9 10

Report an error

The Developer

CSV export of shop accounts and of product page content runs from the admin, with the stated limit that only data stored in the Sana database can be exported — ERP-held master data and passwords are excluded, and the exported product fields stop at page content and media URLs. I found no public information on order history export, a documented migration path out, or what happens to the data on cancellation; the consolation is structural, since the catalogue master stays in the merchant's own ERP. 9 10

Report an error

The Operations Lead

The admin exports shop accounts and product pages to CSV, with the stated limits that only data Sana stores is exportable, media come out as counts rather than files, and passwords never leave; on the other side of the ledger, the master data — products, prices, stock — sits in the merchant's own ERP by design and syncs in real time. We found no public information on order-history export or data return on cancellation. 1 9 10

Report an error

The Data Protection Officer

Shop accounts and product pages export to CSV from the admin with an import round-trip between webstores, but the export covers only data stored in the shop database — data in the ERP is documented as not exportable from the shop, default values are dropped, media leave as URLs and counts, and passwords are not exported. We found no public information on export of order history, deletion or return of data on cancellation, or self-hosting. The order history is exactly what a deletion request lands on, so that gap decides it for me. 9 10

Report an error

The Skeptic

Sana Admin exports shop accounts and product pages to CSV, and that is the whole documented exit: the vendor states only data already stored in the Sana Commerce Cloud database can be exported, the catalogue itself lives in the ERP, passwords are excluded from the export, and the product-page export carries custom titles, descriptions and media URLs rather than the media files. We found no public information on order-history export, data deletion or return on cancellation, a migration path in either direction, or self-hosting. 9 10

Report an error

European sovereignty panel opinion

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

Report an error

The Merchant

One European element is proven: the German imprint names Sana Commerce EMEA B.V. as the website operator, with a Rotterdam address, a Dutch commercial-register number and a Dutch VAT number. Everything behind that — hosting location, data residency, the subprocessor chain and a data-processing agreement — is unstated on the captured pages, so the rest of the chain is unproven in either direction. 2

Report an error

The B2B Seller

The German imprint names Sana Commerce EMEA B.V., Westblaak 180, 3012 KN Rotterdam, as the operator, with KvK number 24275452 and VAT ID NL857142677B01, so a European contracting entity is proven. Data residency, hosting options, a data-processing agreement and the subprocessor chain — including who routes Adyen and Sana Pay payments — are unstated on the captured pages. One European element proven, the rest unknown. 2

Report an error

The Developer

The imprint proves a Dutch contracting entity — Sana Commerce EMEA B.V. in Rotterdam with a KvK number and a Dutch VAT ID — and card processing is outsourced to validated third-party providers who are not named. Data residency, hosting options, a DPA and subprocessor locations are unstated on the captured pages, so one European element is proven and the rest of the chain is unknown. 2 4

Report an error

The Operations Lead

One European element is proven: the operator of the German site is Sana Commerce EMEA B.V., registered in the Dutch trade register under KvK 24275452 at Westblaak 180, Rotterdam, with a Dutch VAT number. Hosting location, data residency, a published DPA and the subprocessor chain are unstated in the captured pages, so the rest of the chain remains open. 2

Report an error

The Data Protection Officer

The captured imprint establishes one European element: the site operator is Sana Commerce EMEA B.V. in Rotterdam with a Dutch trade register number and VAT ID, though the parent's seat is not stated. Beyond that we found no public information on hosting location, a data processing agreement, or a subprocessor list with locations for the CDN, analytics and payment routing — the payment processor is identifiable as Adyen by its add-on, and nothing captured places where that processing sits. 2 4

Report an error

The Skeptic

The captured imprint names Sana Commerce EMEA B.V. at Westblaak 180, Rotterdam, with KvK number 24275452 and Dutch VAT ID NL857142677B01, so an EU contracting entity is proven. The rest of the chain is unstated: we found no public information on hosting location, data residency, a data processing agreement or subprocessors, and the pages name a local entity without stating the parent's seat, while support numbers are listed for both Germany and the USA. 2

Report an error

Pricing transparency not rated — the vendor publishes no price

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

Report an error

The Merchant not rated — no public information

I found no public information on pricing — no tier prices, no transaction or revenue-share rates, no billing period or minimum term — on the vendor homepage or the imprint I read, so an annual cost cannot be computed from public pages alone. 1 2

Report an error

The B2B Seller not rated — no public information

We found no public information on pricing: the captured homepage, imprint and help-centre pages state no licence tiers, transaction fees, billing periods or minimum terms, so a merchant cannot compute an annual cost from them. 1 2

Report an error

The Developer not rated — no public information

We found no public information on pricing — the homepage and imprint captured give no tier, licence fee, transaction rate, revenue share or billing period. A merchant cannot compute a real annual cost from these pages alone. 1 2

Report an error

The Operations Lead not rated — no public information

We found no public information on pricing — no tiers, licence fees or transaction rates appear on the captured homepage or imprint pages, so an annual cost cannot be computed from public pages alone. 1 2

Report an error

The Data Protection Officer not rated — no public information

We found no public information on pricing: the captured homepage, imprint and support documentation show no tier prices, billing terms or transaction fees, so a merchant cannot compute an annual cost from what we read. 1 2 4

Report an error

The Skeptic not rated — no public information

We found no public information on pricing in the captured pages — the homepage and imprint carry no tier, licence figure, transaction fee, order limit, minimum term or VAT treatment. As a buyer I cannot compute even the licence line of the first year's invoice from what was captured. 1 2

Report an error

European sovereignty — proven facts

0 of 6 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.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited 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 Sana Commerce

Is Sana Commerce European?

Yes. whats-best.ai classifies Sana Commerce as EU-Made.

Where does Sana Commerce store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Sana Commerce have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to Sana Commerce?

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: Sana Commerce 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 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 16 Nov 2026 Details →
  4. 4 Catalogue & checkout — found from sitemap help.sana-commerce.com Checked 16 Nov 2026 Details →
  5. 5 Tax & German legal correctness — found from sitemap support.sana-commerce.com Checked 16 Nov 2026 Details →
  6. 6 Tax & German legal correctness — found from sitemap help.sana-commerce.com Checked 16 Nov 2026 Details →
  7. 7 Order operations & back office — found from sitemap support.sana-commerce.com Checked 16 Nov 2026 Details →
  8. 8 Order operations & back office — found from sitemap support.sana-commerce.com Checked 16 Nov 2026 Details →
  9. 9 Data ownership & exit — found from sitemap support.sana-commerce.com Checked 16 Nov 2026 Details →
  10. 10 Data ownership & exit — found from sitemap support.sana-commerce.com Checked 16 Nov 2026 Details →
  11. 11 Structured-data backfill: markup only, no text or screenshot www.sana-commerce.com Checked 8 Nov 2026 Details →