E-Commerce Platforms & Shop Systems
commercetools
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by commercetools GmbH · commercetools.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 panel's verdict
commercetools sells Sphere, a headless, modular, AI-native platform for enterprise commerce, through commercetools GmbH at Adams-Lehmann-Str. 44, 80797 Munich, Germany, and cites 500+ enterprise customers in 50+ countries. The scoring favors it in one area: extensibility, at 4 to 6, resting on headless commerce APIs, documentation, tutorials, training and a Connect module; the low end of that range is the developer judge, who found no public information on staging environments, local development, version control or rate limits. Weakest are tax and legal and data control and exit, each running 1 to 1 — no public information on VAT determination, OSS, reverse charge, export, deletion or migration paths. Sovereignty runs 3 to 4: the Munich contracting entity is named on the vendor page, but hosting location and subprocessors go unaddressed on the captured pages. Catalog and checkout scores run 2 to 3, as do operations scores, both resting on named modules with little beneath them. Pricing transparency scores run 0 to 0; no price appears anywhere on the captured pages.
Speaks for it
- Extensibility scores run 4 to 6, on headless commerce APIs with documentation, tutorials and training listed as developer resources
- The contracting entity is commercetools GmbH, Adams-Lehmann-Str. 44, 80797 Munich, Germany — a European entity a buyer can pin down
- B2C, B2B and InStore selling are named on a single platform, alongside a Merchant Center and a Connect module
- The vendor page states 500+ enterprise customers in 50+ countries and six consecutive years as a Leader in the Gartner Magic Quadrant for Digital Commerce
Held against it
- Tax and legal scores run 1 to 1, with no public information on VAT determination, OSS or reverse charge and compliance logic framed as merchant-defined
- Data control and exit scores run 1 to 1, with no public information on export, deletion, hosting choice or migration paths
- The checkout path is invisible to a buyer — no public information on variants, bundles, guest checkout or payment methods
- Operations scores run 2 to 3, with no public information on stock, returns, carrier label printing or ERP interfaces beneath named modules
- Sovereignty scores run 3 to 4, with no public information on hosting location or subprocessors and no sovereignty attributes on record
Best for
- You have in-house developers building custom headless storefronts and want API-first extensibility backed by documentation, tutorials and training
- You want B2C, B2B and InStore selling on a single platform instead of separate stacks
- You want to contract with a European entity and are prepared to ask the vendor directly about hosting location and subprocessors
Avoid if
- You need the platform to handle VAT determination, OSS or reverse charge — tax and legal scores run 1 to 1 and compliance logic is framed as merchant-defined
- You need documented export, deletion and migration commitments before committing — data control and exit scores run 1 to 1
- You expect a ready-made German checkout with invoice and direct debit — catalog and checkout scores run 2 to 3 and we found no public information on the checkout path or payment methods
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
The page names a product catalog, a frontend component and headless APIs behind storefronts built in thirty minutes, so the shape of the storefront is at least in the merchant's hands. But I found no public information on variants, bundles, tiered pricing, guest checkout, promotion rules, or the payment methods a German shopper expects starting with invoice and direct debit — and the promotional-sales-lift number is a customer outcome, not a promotions engine. 1
The B2B Seller
The page names a product catalog, B2B commerce with personalized experiences and streamlined B2B workflows, and a case study reporting promotional sales, but we found no public information on variants, bundles, tiered or customer-group pricing, guest checkout, or the checkout path and its payment methods. For a headless platform the checkout lives in what each merchant builds, and the captured page does not show that path. 1
The Developer
A product catalog component, configurable pricing logic, and a customer case citing promotional sales give catalogue sophistication in outline. We found no public information on variants, bundles, tiered pricing, guest checkout, the checkout path itself, or any payment methods, so nothing evidences the conversion work this criterion is about. 1
The Operations Lead
The page names a product catalogue module and claims configurable pricing logic, which is more than a flat list, but we found no public information on variants, bundles, tiered or group pricing, the checkout flow, or any payment method, let alone invoice and direct debit for a German shop. 1
The Data Protection Officer
Catalogue, promotions and unified B2B/B2C selling appear only as marketing labels and customer results; I found no public information on the checkout path, payment methods, guest checkout or variant handling on the captured page. 1
The Skeptic
The captured pages name a product catalogue and headless APIs serving B2C and B2B, but we found no public information on variants, bundles, promotions, the checkout flow or payment methods — the part that converts is invisible to a buyer. Pricing logic appears only as something the merchant defines in automation rules, not as evidenced checkout capability. 1
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
The only relevant line is that merchants "define pricing, compliance and workflow logic" — that is configuration work pushed onto me, not the platform doing it. I found no public information on VAT by destination, OSS, reverse charge for B2B buyers, e-invoicing, or the checkout texts German law demands, so nothing here says a German order is legally correct out of the box. 1
The B2B Seller
The only touchpoint is a sentence that merchants themselves define pricing, compliance and workflow logic; we found no public information on VAT determination by destination and customer type, VAT-ID validation, reverse charge for business buyers, OSS, or legal-text handling at checkout. As someone who sells net to trade customers, a page that never shows how a business buyer reaches net prices and reverse charge leaves me with nothing I can rely on. 1
The Developer
The only signal is positioning copy about defining pricing, compliance and workflow logic. We found no public information on VAT determination by destination, OSS, reverse-charge handling, invoicing formats, or the checkout elements German law requires, so vendor-maintained correctness is invisible to a buyer on these pages. 1
The Operations Lead
The only tax-adjacent wording is configurable compliance logic in the automation pitch; we found no public information on VAT determination, OSS, reverse charge, VAT-ID validation, e-invoicing, or the mandatory German checkout elements. For a platform claiming mission-critical enterprise operations, that silence is telling. 1
The Data Protection Officer
The only signal is that merchants define their own pricing, compliance and workflow logic, which puts the burden of German checkout and VAT correctness on the operator; I found no public information on VAT determination, OSS, reverse charge or e-invoicing. 1
The Skeptic
The only relevant fact is that compliance logic is something the merchant configures in the platform's automation rules; we found no public information on VAT determination, OSS, reverse charge, VAT-ID validation or German checkout requirements. The vendor leaves legal correctness at the merchant's desk, and a German shop would be buying that risk sight unseen. 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 — 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
Headless is the vendor's own pitch — a "headless, modular and AI-native platform" whose APIs power the commerce experiences of hundreds of millions of shoppers — with documentation, tutorials and training named, which is exactly the checkout-changed-without-a-rebuild story I sell on. I stop short of the top band because I found no public information on an app or extension marketplace, webhooks, staging environments or documented rate limits. 1
The B2B Seller
Headless commerce APIs are the stated core of the product — powering high shopper volumes, with the platform described as headless, modular and AI-native — and developer training, documentation and tutorials are all listed. We found no public information on the app or extension framework and its lifecycle, webhooks, rate limits, staging environments or a local development story. 1
The Developer
Headless commerce APIs, a headless and modular platform statement, documentation, training, tutorials, and a module named Connect give an API-first story in outline. As the developer who maintains this for five years, I found no public information on local development, version control for themes, an extension dependency model, staging environments, or documented rate limits, and the promise of storefronts built in thirty minutes says nothing about how that output is versioned or whether it survives upgrades. 1
The Operations Lead
Headless commerce APIs and a modular, AI-native platform are stated outright, and documentation, tutorials, and training are listed for developers; we found no public information on an app or extension ecosystem, webhooks, staging environments, theme versioning, or documented rate limits. 1
The Data Protection Officer
Headless APIs and a modular platform are the vendor's central claim, with documentation, tutorials and training listed as developer resources and a Connect module named; however, I found no public information on rate limits, staging environments or source availability. 1
The Skeptic
Headless commerce APIs powering high shopper volumes are the stated core of the product, with documentation, training, tutorials, a Connect module and open support tickets named alongside — a real developer surface by any reading. We found no public information on extension lifecycle, staging environments, rate limits, theme version control or local development, so the evidence tops out at the API itself. 1
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
A Merchant Center, an InStore component and a claim of digitizing complex B2B workflows is all I get. I found no public information on order workflow, stock, returns, carrier integrations with labels, or maintained links to named ERP and accounting systems; the 27 percent order increase tells me an outcome, not an operation. 1
The B2B Seller
The page names a Merchant Center and an operations module and speaks of running B2C, B2B and everything in between on a single platform, but we found no public information on order workflow, stock across warehouses, returns, carrier integrations with label printing, or interfaces to named ERP and accounting systems. After checkout, this page tells a merchant almost nothing about how the back office works. 1
The Developer
A Merchant Center, an InStore component, and unified B2C and B2B operations across every channel are stated, with enterprise customers described as running mission-critical operations on the platform. We found no public information on multi-warehouse stock, returns and refunds, carrier integrations with label printing, or maintained interfaces to named ERP and accounting systems. 1
The Operations Lead
A Merchant Center, an operations stack, and cross-channel commerce including InStore and physical channels are named, but the page shows nothing beneath those labels. We found no public information on partial shipments, multi-warehouse stock, named carrier integrations with label printing, a returns and partial-refund process, or maintained ERP interfaces — the parts I judge a shop by. 1
The Data Protection Officer
Merchant Center, an operations component and an in-store channel are named, but as labels; I found no public information on order workflow, stock, returns, shipping or ERP interfaces. 1
The Skeptic
A merchant center, an operations module and cross-channel positioning — B2C, B2B and InStore on one platform — are evidenced, which gestures toward multi-channel order intake. We found no public information on stock, returns, carrier label printing or interfaces to ERP and accounting systems, so what happens after checkout rests on naming a module. 1
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
I found no public information on export of catalogue, customers or order history, on hosting choice or self-hosting, or on any documented migration path — the captured page says nothing about what leaving would cost me. For a merchant whose business is the order history, that silence is the whole answer. 1
The B2B Seller
We found no public information on export completeness for catalogue, customers and order history, on self-hosting or hosting choice, or on any documented migration path in either direction. For a commitment of this size, the absence of a stated data-return commitment on the captured page is itself information. 1
The Developer
We found no public information on export of catalogue, customers or order history, on self-hosting or hosting choice, or on a documented migration path in either direction. The headless API claim hints at programmatic access, but nothing on the captured page evidences deletion, media or document export, or contractual data return. 1
The Operations Lead
The captured pages present a hosted platform behind APIs, and we found no public information on export completeness for catalogue, customers, and order history, on deletion, on self-hosting or hosting choice, or on any migration commitment in either direction. 1
The Data Protection Officer
Nothing on the captured page addresses export completeness, deletion against customers and order history, self-hosting or a migration path, and the API positioning does not evidence any of it; I found no public information on data return commitments. 1
The Skeptic
We found no public information on catalogue, customer or order-history export, deletion, hosting choice, or any migration path off the platform — what leaving costs is simply never addressed. For a platform sold on mission-critical enterprise operations, silence on exit is the most expensive kind of silence. 1
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 commercetools GmbH at a Munich street address — that part I can bank. But hosting location is unstated and no subprocessor list appears anywhere on the page, and payment routing in the checkout path is precisely where I need to know who sits in the chain. 1
The B2B Seller
The contracting entity is commercetools GmbH at a Munich address, so a buyer signs with a European entity, and the captured page confirms nothing further on this front. We found no public information on hosting location, the infrastructure behind the platform, or a subprocessor list for the checkout path. 1
The Developer
The contracting entity is commercetools GmbH at an address in Munich, which is a European entity a buyer can pin down. Hosting location is not stated on the captured page, no subprocessor list is published there, and no sovereignty attributes are on record, so I can credit neither named infrastructure nor the processors sitting in the checkout path. 1
The Operations Lead
The contracting entity is commercetools GmbH at a Munich address, which is a European footing, and the vendor lists enterprise customers across 50+ countries. Beyond that we found no public information on where customer and order data are hosted, which subprocessors sit in the checkout path, or any certification. 1
The Data Protection Officer
The contracting entity is confirmed as commercetools GmbH with a Munich address, which is a real and welcome starting point; but I found no public information on hosting location, the subprocessor list, or where CDN and analytics sit, so the checkout chain cannot be assessed beyond the entity. 1
The Skeptic
The contracting entity is evidenced as commercetools GmbH at a Munich address, which is a genuine European anchor. But we found no public information on where customer and order data are hosted, on subprocessors in the checkout path, or on certifications — and nothing on sovereignty was independently sourced. 1
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 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
Not one figure on the page — no licence tiers, no billing period, no transaction or revenue-share rates, no order limits; only premium support and expert services are named. An enterprise sales conversation is not a price, and I cannot judge contribution against an invoice nobody will show me. 1
The B2B Seller
We found no public information on licence tiers, transaction or revenue-share fees, order or GMV limits, hosting costs, minimum terms or VAT treatment anywhere on the captured page; premium support and expert services are offered by name but without prices. From public pages alone an annual cost is not computable in any part. 1
The Developer
The captured page publishes no prices, no tiers and no billing period, and engagement runs through open support tickets, premium support and expert services. A merchant cannot derive any annual cost from public pages; we found no public information on licence cost, transaction fees, revenue share or hosting. 1
The Operations Lead
No price of any kind appears in the captured material — no tiers, no billing term, no transaction or revenue-share rate, no cost for any module — so the real annual cost of running this platform is purely a sales conversation. Enterprise positioning with named competitor comparisons against SAP and Oracle is the only pricing signal on the page. 1
The Data Protection Officer
No prices of any kind appear on the captured page; a merchant cannot begin to compute licence, transaction or hosting costs from public information I can see. 1
The Skeptic
The captured pages contain no price of any kind — no tiers, no transaction or revenue-share fees, no order or GMV limits, no hosting rates, with premium support and expert services named and unpriced. The annual cost is a sales conversation by construction, and for an enterprise platform of this positioning that conversation will not be cheap. 1
European sovereignty — proven facts
2 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 | 2 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 3 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 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. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Subprocessors. GCP and AWS are US-headquartered providers; the page does not state whether hosting is contracted through their EU entities, and it lists data center regions only as Europe, US and APAC.
- 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 could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 27 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
- 3 integrations 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 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. 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 (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page commercetools.com Checked 22 Sep 2026 Details →
- 2 Imprint — found from the homepage commercetools.com Checked 30 Sep 2026 Details →
- 3 Security / trust page — found from the homepage commercetools.com Checked 30 Sep 2026 Details →
- 4 Catalogue & checkout — found from sitemap commercetools.com Checked 1 Oct 2026 Details →
- 5 Catalogue & checkout — found from sitemap commercetools.com Checked 1 Oct 2026 Details →
- 6 Tax & German legal correctness — found from sitemap commercetools.com Checked 1 Oct 2026 Details →
- 7 Extensibility & developer surface — found from sitemap commercetools.com Checked 1 Oct 2026 Details →
- 8 Extensibility & developer surface — found from sitemap commercetools.com Checked 1 Oct 2026 Details →
- 9 Order operations & back office — found from sitemap commercetools.com Checked 1 Oct 2026 Details →