E-Commerce Platforms & Shop Systems
OXID eSales
EU-Made Report an errorPanel 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 OXID eSales AG · www.oxid-esales.com
Compare with PrestaShop → 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 panel's verdict
OXID eSales, a German AG registered at Amtsgericht Freiburg (HRB 701648), scores highest on pricing transparency: all four tiers are public — Community Edition 121 €/month, Professional Edition 360 €/month, Enterprise Edition B2C 1.123 €/month, Enterprise Edition B2B 1.583 €/month — with minimum terms of 36–48 months, a no-revenue-share statement, a possible reduction below 100.000 € annual shop revenue, and a +173 €/month sub-shop surcharge. Catalogue & checkout follows at 4-5 for customer-specific price lists, tiers, discount logic and order approval workflows, though no payment method, variant, bundle or guest checkout appears in the evidence. The weakest criteria are tax & German legal correctness (1-2: no VAT determination, OSS, reverse charge or checkout legal texts) and extensibility (2-3: no API, theme system or plugin ecosystem evidenced). Data ownership & exit rests on the buyer's free hosting choice and purchase licences, not a documented export path. On sovereignty, scores spread 3-5: the evidence's sovereignty attributes are all unknown (0 of 10), yet judges credited the German registration and SCCs disclosed for US transfers on the vendor's own site, while lower scores flagged unstated shop-data residency and no platform subprocessor list.
Speaks for it
- Four publicly priced tiers (121–1.583 €/month) with stated minimum terms of 36–48 months and an explicit no-revenue-share promise.
- Customer-specific price lists, tiered pricing, discount logic, in-shop quotes and order approval workflows are concretely evidenced.
- Free choice of hosting provider plus purchase licences alongside subscriptions keeps ownership structural rather than promised.
- Contracting entity is a German AG with commercial register entry (Amtsgericht Freiburg i. Br., HRB 701648), a German VAT ID and EFRE funding.
- US transfers on the vendor's own site are SCC-based, with consent tooling from a named Munich subprocessor (Usercentrics).
Held against it
- No evidence of VAT determination, OSS, reverse charge, VAT-ID validation or checkout legal texts (tax & German legal correctness scored 1-2).
- No payment method, variant, bundle or guest checkout documented anywhere in the evidence.
- No API, theme system, plugin ecosystem, webhooks or local development surface evidenced.
- No ERP or accounting system named, and shipping, carriers, returns, refunds and stock handling are unevidenced.
- No platform export of catalogue, customers or order history, no documented migration path, and shop-data residency plus the checkout subprocessor chain are unstated.
Best for
- You sell B2B and need customer-specific price lists, buyer roles with budgets, in-shop quotes and order approval workflows evidenced out of the box.
- You want a German contracting entity with fixed, public licence prices, no revenue share, and the freedom to choose your own hosting provider.
- You run multiple brands or countries and need central multishop management with a priced +173 €/month sub-shop surcharge.
Avoid if
- You need evidenced VAT handling (OSS, reverse charge, VAT-ID validation, net prices for business customers) for German-market sales.
- Your roadmap depends on a documented API, theming layer or plugin ecosystem you can build against.
- You need the checkout path confirmed before buying — ask the vendor: the public pages we read do not show it
- You need post-checkout operations — a named ERP integration, carrier label printing, returns and refunds — before a 36- or 48-month term.
The scores
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 — 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.
The Merchant
Customer-specific price lists, tiers and discount logic are evidenced, and marketing can build campaign quick filters in the category frontend without a developer — the promotion control I sell on. Five official payment providers including Unzer and Adyen are listed with Unzer described only as flexible payment options, and we found no public information on variant handling, product bundles or guest checkout. 1 6 9 10
The B2B Seller
Customer-specific price lists, tiers and discount logic are evidenced for trade customers, together with quick order by article number, quotes, approval workflows and buyer management, and five payment providers are named as official modules. We found no public information on a variant matrix, product bundles, guest checkout, or invoice purchase and direct debit named for German buyers, so merchandising depth beyond trade pricing stays unproven. 2 1 9 10
The Developer
Official payment integrations for PayPal, Stripe, Unzer, Adyen and Amazon Pay sit alongside tiered and customer-specific pricing, discount logic and per-shop conditions in a multilingual multishop setup — more than a basic product list. I found no public information on variants, bundles, guest checkout, or invoice and direct debit payment, which is what I would need to see to go higher. 1 9 10
The Operations Lead
Merchandising and B2B pricing are genuinely strong — per-category filters with campaign quick filters built without a developer, customer-specific price lists with tiers and discount logic, and five named payment integrations including Unzer and Adyen. I found no public information on a variant matrix, product bundles, guest checkout, or invoice and direct debit as named methods, so I cannot take this to the level a full catalogue conversion story would need. 1 6 7 9 10
The Data Protection Officer
Customer-specific price lists, tiered pricing and discount logic are documented for B2B, filter configuration per category is editable in the admin without a developer, and official payment modules cover PayPal, Stripe, Unzer, Adyen and Amazon Pay. We found no public information on bundles, guest checkout, multi-currency pricing or conversion features such as abandoned-cart recovery, which is what separates this from the top bands. 2 1 6 7 9
The Skeptic
Customer-specific price lists, tiered pricing and discount logic are published, with five named payment providers and per-category promotion filters a marketer can build without a developer. But we found no public information on a variant matrix, product bundles, guest checkout or multi-currency — the merchandising core the upper levels are made of — so the pricing engine carries the score, not the catalogue. 1 7 9
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, and the checkout requirements German law actually imposes — judged on what the platform does, not on a plugin someone could buy.
0 — A single VAT rate applied everywhere; no B2B handling, no country logic, no legal-text handling in checkout.
3 — Per-country VAT rates configurable by hand, net prices for B2B possible with effort, and legal texts as free-form pages.
5 — Automatic VAT by destination and customer type, VAT-ID validation with reverse charge, gross and net display per customer group, and the mandatory checkout elements (order button wording, withdrawal policy, price indications) handled.
8 — OSS thresholds tracked and reported, correct invoicing per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant
Official modules for electronic VAT management and country-specific tax rules cover destination-based tax, and the vendor's withdrawal button — free of charge, tied to the 19 June 2026 statutory date, with every withdrawal timestamped under §356 BGB — shows a legal element maintained by the vendor rather than the merchant. We found no public information on VAT-ID validation with reverse charge, OSS reporting, gross/net display per customer group, or e-invoicing. 8 9 10
The B2B Seller
Country-specific VAT rules and an electronic VAT administration ship as official modules, and the statutory withdrawal button with automatic §356 BGB timestamp documentation is genuine German checkout law handled in the shop. For trade commerce we found no public information on VAT-ID validation, reverse charge, net display per customer group, OSS or XRechnung/ZUGFeRD e-invoicing — exactly the pages a B2B buyer needs before signing. 8 9 10
The Developer
The vendor ships its own compliance modules — electronic VAT management, country-specific tax rules, geoblocking — plus a statutory withdrawal button that timestamps every withdrawal under §356 BGB, is free of charge and submittable without login. I found no public information on VAT-ID validation with reverse charge, OSS reporting or e-invoicing, and that caps it. 8 9
The Operations Lead
Tax and legal work arrives as official modules — country-specific tax rules, electronic VAT management, geoblocking, GDPR opt-in — and the withdrawal button handles the statutory duty from 19 June 2026 with timestamped documentation under §356 BGB, free of charge from OXID. I found no public information on automatic destination VAT with reverse charge, VAT-ID validation, OSS reporting or e-invoicing, so the merchant still owns the hard parts of the tax logic. 8 9 10
The Data Protection Officer
Country-specific VAT rules and electronic VAT management ship as official modules, and the withdrawal handling is unusually concrete — a button stated as legally mandatory from 19 June 2026, automatic timestamp documentation of every withdrawal under §356 BGB, and submission without login. We found no public information on VAT-ID validation with reverse charge, OSS reporting, e-invoicing, or any statement that rates and thresholds are maintained by the vendor rather than configured by the merchant. 8 9 10
The Skeptic
Official modules for country-specific tax rules and electronic VAT administration, plus a withdrawal button that documents every revocation with a timestamp under §356 BGB and blocks duplicates within 24 hours, show the vendor maintaining German legal machinery rather than leaving it to the merchant. We found no public information on VAT-ID validation, reverse charge, OSS reporting or e-invoicing, which is what the top of this scale is built from. 8 9 10
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 — 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.
The Merchant
A documented GraphQL interface, a module ecosystem with its own activate/deactivate lifecycle independent from the shop core, a GitHub module template, developer documentation and academy training give a team a real surface, and the Twig template engine is evidenced through the migration tooling. We found no public information on staging environments, documented rate limits, webhooks or headless storefront use. 9 10 14
The B2B Seller
A GraphQL interface, a Solution Hub with third-party modules plus official ones tested with every release, a Smarty-to-Twig template engine, developer documentation, academy training and a GitHub module template evidence a real developer surface, and the module-versus-component model with its own activation lifecycle points beyond the basics. We found no public information on staging environments, documented rate limits, or local development and CI support. 9 10 14
The Developer
This is my home ground: modules install separately, deactivate at will and sit independent of the shop core for easier updates, and there is a GraphQL API, developer documentation, code examples, academy training and a GitHub module template — the beginnings of a real plugin architecture. But I found no public information on local development, staging environments, version control for themes, webhooks or documented rate limits, and the OXID 7 migration explicitly hands third-party and custom modules plus theme and template work back to the customer or partner — upgrades that orphan my customisations are exactly the future migration I fear. 9 10 13
The Operations Lead
A flexible GraphQL interface, developer documentation with code examples and academy training, a GitHub module template, and a module ecosystem where extensions sit independent of the shop core and are tested with every release — that is a developer surface I could build an operation on. I found no public information on headless storefront builds, webhooks, staging environments or documented rate limits. 9 10
The Data Protection Officer
A GraphQL API, a broad third-party ecosystem in the Solution Hub, developer documentation, trainings, a GitHub module template and a Twig template engine give a genuine developer surface, with modules described as independent from the shop core and individually activated or deactivated. We found no public information on headless storefront builds, staging environments, webhooks or documented rate limits. 9 10 14
The Skeptic
A GraphQL interface, developer documentation with training and code examples, a GitHub module template, and modules that run independently of the shop core and can be activated or deactivated at will add up to a genuine developer surface, with a Twig template engine behind it. We found no public information on headless storefront builds, staging environments or documented rate limits. 9 10 14
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 — 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.
The Merchant
Shipping types, rules and assignments on one screen with overlap warnings surfaced before checkout, automatic ERP synchronisation of stock, orders and customer data, B2B order approval with budgets, and a withdrawal process documented in the system give the back office real depth. We found no public information on carrier label printing, partial shipments, multi-warehouse stock or interfaces to named ERP and accounting systems. 2 8 9 10 11
The B2B Seller
ERP, PIM, CRM and inventory synchronisation of stock, orders and customer data are promised, the shipping-rule engine that warns about conflicts before they reach checkout is strong back-office material, and statutory withdrawals are processed in the system even without login. The ERP systems stay unnamed, and we found no public information on partial shipments, multi-warehouse stock, carrier label printing or operational reporting. 2 8 9 11
The Developer
Shipping methods, rules and assignments live on one screen with warnings for overlaps and orphaned rules, ERP synchronises stock, orders and customer data automatically, and the withdrawal process runs in the system with an admin view. I found no public information on partial shipments, multi-warehouse stock, named carrier integrations with label printing, or partial refunds. 8 9 12
The Operations Lead
The back office is credible: shipping methods and rules on one screen with conflict warnings surfaced before checkout, automatic ERP synchronisation of stock, orders and customer data through vendor modules, B2B order approval workflows, and a withdrawal process handled in the system with timestamps and duplicate detection. But I found no public information on partial shipments, multi-warehouse stock, named carriers with label printing or partial refunds — a shop that cannot show me a partial refund does not get past this mark. 8 9 10 11 12
The Data Protection Officer
Shipping methods, rules and assignments sit on one screen with automatic conflict warnings, ERP modules synchronise stock, orders and customer data automatically, and statutory withdrawals are processed in the shop with timestamp documentation and duplicate detection. We found no public information on partial shipments, multi-warehouse stock, named carriers with label printing or refund handling, and the ERP, PIM and CRM interfaces are described generically without named systems. 2 8 9 11 12
The Skeptic
Stock, orders and customer data synchronize automatically with ERP systems, B2B orders run through approval workflows, quotes and scheduled or collective ordering, and shipping methods and rules sit in one admin view with conflict and orphaned-rule warnings. But we found no public information on partial shipments, multi-warehouse stock, carrier label printing or dropshipping, and no ERP or accounting systems are named. 2 9 12
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 — 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.
The Merchant
Free choice among eight named German hosting partners and a migration offering that moves the shop core and the database's structure and content give a merchant hosting control and a documented path in. We found no public information on export completeness for catalogue, customers and orders out of the platform, documented deletion, or a contractual data-return commitment on the way out. 2 5 13 14
The B2B Seller
Free choice of hosting provider with eight named German hosting partners, plus a fixed licence without revenue share, keep the stack portable, and a free technical migration check documents a serious migration path inbound. We found no public information on export completeness for catalogue, customers and order history or on a documented exit; the only data-return statement captured is the general GDPR portability right on the website. 2 4 5 13
The Developer
Hosting is the merchant's free choice across eight named German partners, there is no revenue share, the migration check is cost-neutral, and the migration moves database structure and contents — that reads like database-level access rather than a promise. I found no public information on export completeness when leaving the platform or a contractual data-return commitment, which keeps it short of the top. 2 5 13 14
The Operations Lead
Hosting is the customer's free choice among eight named German partners, the licence carries no revenue participation, and migrations move shop core files plus database structure and content — real ownership structure. I found no public information on complete export of catalogue, customers and orders, the documented migration path runs into the platform rather than out of it, and minimum terms of 36 or 48 months make leaving an expensive decision. 2 5 13 14
The Data Protection Officer
Hosting is the merchant's free choice among eight named German partners, and the migration service explicitly covers the database structure and contents, so the shop's data travels with the installation rather than into a proprietary vault. We found no public information on complete export of catalogue, customers and order history, on documented deletion procedures, or on a documented path for leaving the platform. 2 5 13 14
The Skeptic
Hosting is the merchant's free choice among eight named German partners, purchase licenses exist alongside subscriptions, and when you move in the vendor itself migrates the shop core and the database structure and content. Every migration page describes coming to OXID, though: we found no public information on export completeness, a documented path out, or a data-return commitment for catalogue, customers and order history. 2 5 13
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.
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.
The Merchant
The contracting entity is German with eight named German hosting partners, and US transfers in the vendor's own web chain are disclosed on the EU Commission's standard contractual clauses with a German consent provider named. We found no public information on where shop and checkout data are hosted as standard, or which subprocessors sit in that chain. 3 4 5
The B2B Seller
A German contracting entity with German addresses, banking and EFRE funding, hosting partners all German and the vendor's own site hosted in Sweden, with US transfers for analytics named on an EU Standard Contractual Clauses basis and Munich-based Usercentrics for consent. We found no public information on a published subprocessor list for the platform or on where production customer and order data reside. 3 4 5
The Developer
The contracting entity is a German AG in Freiburg and the hosting-partner network is all-German, including one firm advertising sovereign cloud hosting — but that is where the evidence stops. I found no public information on where shop and order data actually reside or which subprocessors sit in the checkout path, and the vendor's own site runs Google Analytics, Meta's pixel and LinkedIn's tag with US transfers based on standard contractual clauses. 3 4 5
The Operations Lead
A German contracting entity in Freiburg and eight German hosting partners, one of them marketing itself on sovereign cloud hosting, give the platform a solid European base. The product's own data residency is not confirmed on the captured pages, no subprocessor list for the platform is published, and the vendor's own website runs US analytics and social embeds under standard contractual clauses with Sweden-hosted serving. 3 4 5
The Data Protection Officer
The contracting entity is a German AG registered in Freiburg, and hosting runs through named German partners, one of which markets sovereign cloud hosting. The vendor's own privacy policy names its processors — Google Analytics, Meta Pixel and LinkedIn Insight Tag, with US transfers based on the EU Commission's standard contractual clauses and consent technology from Usercentrics in Munich. We found no public information on where shop and checkout data reside by default, or on a subprocessor list covering the platform's own checkout chain. 3 4 5
The Skeptic
A German AG with a commercial register entry in Freiburg and eight named German hosting partners is the right half of the picture. But the vendor's own captured pages do not confirm where shop data resides, publish no subprocessor list for the platform, rest US transfers on standard contractual clauses, and the vendor's own site runs Meta, Google and LinkedIn tracking behind Swedish hosting. 3 4 5
Pricing transparency
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 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.
The Merchant
Four editions are priced monthly with minimum terms stated — Community Edition at 121 € / Monat up to Enterprise Edition B2B at 1.583 € / Monat — alongside a clear no-revenue-share line and individually priced add-ons such as the withdrawal button at 0 EUR für Bestandskunden. Hosting costs, the price of the payment and ERP extensions most shops need, and the VAT treatment of the stated prices are not given on the captured pages, so the annual invoice is not fully knowable from the pages alone. 2 5 8 9
The B2B Seller
Every edition is priced publicly with billing period and minimum term — Community at 121 € / Monat for 36 months, Professional at 360 € / Monat, Enterprise B2C at 1.123 € / Monat, Enterprise B2B at 1.583 € / Monat for 48 — plus the stated "+173 €/Monat je Sub-Shop", an explicit "Klare Preise, keine Umsatzbeteiligung", sampled module prices such as "20 €/Monat" and "50 EUR / Monat", and a free migration check. We found no public information on VAT treatment of the licence prices, hosting costs at the partners, or prices for the wider module catalogue, which keeps the real annual invoice one conversation short of fully computable. 2 8 11
The Developer
Four edition prices with minimum terms stated, an explicit no-revenue-share commitment, a per-subshop surcharge and published module subscription prices make the licence side of the annual cost computable. Hosting cost sits with the freely chosen provider, and I found no public information on the VAT treatment of the listed prices, so the real annual total still needs assembly. 2 8 12
The Operations Lead
Every edition carries a public monthly price with the minimum term stated — Community 121 € / Monat, Professional 360 € / Monat, Enterprise B2C 1.123 € / Monat, Enterprise B2B 1.583 € / Monat — plus a stated sub-shop surcharge of +173 €/Monat and a clear statement of no revenue participation, and individual OPALs are quoted at 20 €/Monat, 50 EUR / Monat or 0 EUR für Bestandskunden. What a merchant still cannot compute from these pages: hosting cost, payment gateway rates, VAT treatment of the listed prices, and the price of most extensions beyond the OPALs. 2 8 11 12
The Data Protection Officer
All four editions carry public monthly prices with minimum terms of 36 to 48 months, a sub-shop surcharge of 173 €/Monat is stated, and the vendor publishes "Klare Preise, keine Umsatzbeteiligung". We found no public information on extension and module prices, the captured pages show different figures for different offerings — among them 20 €/Monat, 0 EUR für Bestandskunden and 50 EUR / Monat für alle anderen — and nothing on VAT treatment of the listed figures, so the real annual cost is not computable from the pages alone. 2 8 11 12
The Skeptic
All four licence tiers are public with their 36- and 48-month minimum terms, an explicit no-revenue-share statement, a priced per-sub-shop surcharge and a disclosed revenue-linked reduction below 100.000 € Jahresshopumsatz, and even the statutory withdrawal button carries published figures — 0 EUR für Bestandskunden, 50 EUR / Monat für alle anderen. But hosting costs sit with the partners' own price lists, the pages are silent on whether licence prices are net or gross, and the broad extension catalogue is largely unpriced — the licence is computable, the invoice is not. 2 5 8
European sovereignty — proven facts
1 of 4 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 | Incorporated in DE | 3/3 pts | 3 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 31 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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.
- 24 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
- 7 legal 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
- 3 pricing 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
- 3 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
- 2 subprocessors 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.oxid-esales.com Checked 15 Sep 2026 +1 earlier capture: 31 Aug 2026 Details →
- 2 Pricing www.oxid-esales.com Checked 15 Sep 2026 Details →
- 3 Imprint www.oxid-esales.com Checked 15 Sep 2026 Details →
- 4 Privacy policy www.oxid-esales.com Checked 15 Sep 2026 Details →
- 5 Security / trust page www.oxid-esales.com Checked 30 Sep 2026 Details →
- 6 Catalogue & checkout — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 7 Catalogue & checkout — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 8 Tax & German legal correctness — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 9 Extensibility & developer surface — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 10 Extensibility & developer surface — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 11 Order operations & back office — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 12 Order operations & back office — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 13 Data ownership & exit — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →
- 14 Data ownership & exit — found from sitemap oxid-esales.com Checked 1 Oct 2026 Details →