commercetools
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 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? →
Link to this page
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.
commercetools at a glance
- Vendor
- commercetools GmbH
- Headquarters
- Incorporated in Germany source, captured 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 commercetools 2.5/5, the mean of 6 judges. commercetools GmbH of Munich is an API-first headless commerce platform, and it scores highest exactly where that architecture pays: extensibility at 6-7, catalog and checkout at 5-7 and operations at 5-7, built on a documented product data model with variants, bundles and B2B contract pricing, live cart editing with price override, and real-time stock across every warehouse and store with checkout reservations scaling to 100,000 per minute. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
commercetools GmbH of Munich is an API-first headless commerce platform, and it scores highest exactly where that architecture pays: extensibility at 6-7, catalog and checkout at 5-7 and operations at 5-7, built on a documented product data model with variants, bundles and B2B contract pricing, live cart editing with price override, and real-time stock across every warehouse and store with checkout reservations scaling to 100,000 per minute. Its weakest substantive showing is data control and exit at 2-3: the documented facts stop at deletion and retention handling, and we found no public information on export of catalogue, customers or order history, migration or self-hosting. Tax and legal sits at 4 with no spread — cart calculation through the Vertex partner integration is documented, German specifics such as VAT-ID validation, OSS, e-invoicing and checkout-law wording are not. Sovereignty scores 4-5 on a German contracting entity, with transfers outside the EU under Standard Contractual Clauses acknowledged and no published subprocessor list or default region. The judges' flagged splits came back empty, and the only public pricing fact is a free trial.
Speaks for it
- Extensibility scores cluster at 6-7 on a documented API-first headless architecture with REST APIs, developer documentation, training and a Connect component
- Operations evidence is strong on the stock side: real-time visibility across every warehouse and store, checkout reservations scaling to 100,000 per minute, safety stock, native backorders and pre-orders, and omnichannel fulfilment
- The catalog and cart layer is documented in depth, from variants, bundles and digital or physical products to live cart editing with price override, multiple shipping destinations per cart and B2B contract pricing with account hierarchies and approvals
- The contracting side is German: commercetools GmbH in Munich, registered at Amtsgericht München, with an external data protection officer and a GDPR Article 28 DPA available on request
- A standalone Product Catalog can be deployed alongside an existing commerce stack without replatforming
Held against it
- Data control and exit scores run 2-3, with the documented posture stopping at deletion and retention handling and we found no public information on export of catalogue, customers or order history, on migration or on self-hosting
- Tax and legal scores sit at 4 with no spread, and we found no public information on VAT-ID validation with reverse charge, OSS reporting, XRechnung or ZUGFeRD e-invoicing, or German order-button, withdrawal and price-indication rules
- We found no public information on payment providers or payment methods, guest checkout, abandoned-cart recovery or buy-now-pay-later, and the headless checkout is something the merchant assembles
- We found no public information on returns or refunds, carrier integrations or label printing, or maintained interfaces to named ERP and accounting systems such as DATEV
- Hosting runs on Google Cloud and AWS across Europe, the US and APAC, transfers outside the EU under Standard Contractual Clauses are acknowledged, and we found no published subprocessor list or stated default region
Best for
- You have in-house developers and want to own the checkout and storefront code on a headless, API-first platform rather than a locked template
- You sell B2B and need contract pricing, account hierarchies and approval workflows across markets and channels
- You operate many warehouses and stores and need real-time stock visibility with checkout reservations at peak volume
- You want to modernize your product catalog incrementally alongside an existing stack rather than replatform in one move
Avoid if
- You need to know the cost of leaving before you sign; data control and exit scored 2-3 and the documented posture stops at deletion and retention handling
- You sell to German consumers and expect the vendor's pages to carry the German checkout-law and e-invoicing specifics, rather than cart tax calculation through a Vertex partner integration with the rest left to your own lawyers
- You run a returns-heavy consumer shop; the operations evidence is inventory-centred, and returns, refunds and carrier handling remain a vendor conversation
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 3.5 of 5 |
| Tax & German legal correctness | 2 of 5 |
| Extensibility & developer surface | 3.5 of 5 |
| Order operations & back office | 3 of 5 |
| Data ownership & exit | 1 of 5 |
| European sovereignty | 2 of 5 |
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 — 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.
The Merchant
Variants, bundles and digital or physical products with built-in pricing and localisation are documented, plus a Promotions module pitched at discounting precisely without giving away margin, B2B contract pricing, cart freeze and live cart editing with price override, and a headless setup that leaves the checkout in my hands to shape. We found no public information on payment methods — nothing on PayPal, invoice or direct debit through named providers — or on abandoned-cart recovery and guest checkout, which is exactly the stretch where a consumer shop converts. 4 9 5 4
The B2B Seller
The catalogue and cart side is genuinely deep for a trade seller: variants and bundles in a flexible data model, contract pricing with account hierarchies and approvals for B2B, a promotions module, multi-destination shipping on a single cart and carts that sales teams can edit live with price overrides. The pages never name a payment method or provider, though, and I found no public information on guest checkout, abandoned-cart recovery or buy-now-pay-later. 5 7 4
The Developer
The commerce core is documented in depth: a data model for variants, bundles and digital products, contract pricing for B2B buyers, a promotions module, cart freeze and live cart editing with price overrides, and catalogues structured per market and channel. Headless separation means the checkout is code I own rather than a locked template; we found no public information on named payment providers, guest checkout or abandoned-cart recovery, which keeps this short of the top of the scale. 4 5 4 8
The Operations Lead
The Product Catalog module documents variants, bundles, built-in pricing and localization with a single structured catalogue across brands, regions and channels, B2B contract pricing is named, and the promotions module is pitched at discounting without losing margin. Cart handling is strong — cart freeze, live cart editing with price override, multiple shipping destinations per cart — but we found no public information on payment methods or named providers in the checkout, on abandoned-cart recovery or on buy-now-pay-later. 4 5 7 4
The Data Protection Officer
The product catalog is well evidenced — variants, bundles, digital and physical products, categories, built-in pricing and localization — and cart and order handling is real: reservations during checkout, promotions, subscriptions, live cart editing, multiple shipping destinations. We found no public information on payment methods or named payment providers, guest checkout or abandoned-cart recovery, and as a headless platform the checkout itself is something a merchant assembles rather than receives. 4 9 5 4
The Skeptic
Variants, bundles and built-in pricing sit in a flexible data model, the cart layer supports live editing, price overrides, promotions, multiple shipping destinations and B2B contract pricing, and catalog, pricing and inventory connect across channels and markets. We found no public information on payment providers or payment methods, guest checkout, or abandoned-cart recovery, so the money end of the checkout path stays invisible to a buyer reading these pages. 4 5 7 8
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content 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
Tax runs through a named, partner-maintained integration with Vertex that calculates sales tax and VAT in the shopping cart by product taxability and jurisdiction, updates rates and rules automatically, and covers quotes, invoices and credit memos for B2B and B2C. We found no public information on the German specifics — VAT ID validation and reverse charge, OSS, or the checkout requirements German law imposes on the order button, withdrawal policy and price indications. 6
The B2B Seller
Tax runs through a named integration owned and maintained by Vertex: VAT and sales tax calculated in the cart by product taxability and jurisdiction, rates and rules updated automatically, with quotes, invoices and credit notes as supported tax events. For what decides a B2B deal for me — VAT-ID validation, reverse charge, OSS and the German checkout requirements — I found no public information on these pages. 6 1
The Developer
Tax runs through a named partner integration with Vertex O Series, owned and maintained by Vertex, calculating in the cart by product taxability and jurisdiction with automatically updated rates and rules, covering sales tax and VAT for B2B and B2C. We found no public information on VIES validation, OSS reporting, reverse charge, e-invoicing or the German checkout requirements, so this is calculation capability rather than demonstrated German legal correctness. 6
The Operations Lead
Tax runs through the Vertex integration, owned, maintained and supported by Vertex Inc., which calculates sales tax and VAT in the cart by jurisdiction, cleanses source and destination addresses and updates rates and rules automatically for both B2B and B2C, with Sales Quote, Sales Invoice and Invoice Credit among the supported tax events. We found no public information on the German checkout requirements, VAT-ID validation, reverse charge, OSS reporting or e-invoicing on the captured pages. 6
The Data Protection Officer
Tax runs through a named partner: Vertex calculates sales tax and VAT in the cart by jurisdiction, cleanses source and destination addresses, supports quote, invoice and credit events, and updates rates and rules automatically, with the integration owned, maintained and supported by Vertex. We found no public information on VAT ID validation with reverse charge, OSS reporting data, e-invoicing in XRechnung or ZUGFeRD form, or the German checkout requirements around order button wording, withdrawal and price indication — the merchant's lawyers would carry those. 6
The Skeptic
VAT and sales tax are handled, but through an integration the vendor says is owned, maintained and supported by Vertex Inc.: tax is calculated in the cart by product taxability and jurisdiction, with rates and rules automatically updated and address cleansing on source and destination addresses. We found no public information on German checkout requirements such as order button wording, withdrawal or price-indication rules, on VAT ID validation or reverse charge, on OSS, or on XRechnung and ZUGFeRD invoicing. 6
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 — 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.
The Merchant
This is the core of the offer: API-first headless commerce exposing the backend through APIs, RESTful APIs pitched as easy for any developer to pick up, with developer documentation, training, tutorials and a Connect component for wiring systems and agents together. The frontend is decoupled by design, so I can rebuild the shopfront without touching the commerce logic. We found no public information on rate limits, staging or development environments, or how extensions are versioned. 7 1 8
The B2B Seller
Headless is the product's stated identity — the vendor calls itself the inventor of headless commerce, with RESTful APIs, API-first connectivity across systems and channels, and developer training, documentation and tutorials offered. I found no public information on webhooks for order events, staging environments, documented rate limits or how the named Connect extension framework is governed, so the operational developer surface stays partly dark. 7 1 8
The Developer
API-first headless commerce is the documented architecture, with RESTful APIs, developer documentation, training and tutorials, and the frontend fully decoupled so nothing is trapped in a closed template editor. What we found no public information on is the surface I would maintain for five years: an extension lifecycle, a dependency model behind the Connect components, local development, version control for frontend artefacts, staging environments and documented rate limits. 7 8 1 8
The Operations Lead
Headless is the product's identity: APIs power commerce experiences for hundreds of millions of shoppers daily, the REST APIs are documented as easy for any developer to pick up, and training, documentation, tutorials and a free trial are offered, with Connect appearing as a platform component. We found no public information on documented rate limits, staging or development environments, or the extension lifecycle on the captured pages. 8 7 8 8
The Data Protection Officer
Headless is the product's own self-description — the inventor and leader of headless commerce, API-first connectivity, easy-to-use RESTful APIs and a storefront layer decoupled from backend commerce, backed by developer training, documentation and tutorials. We found no public information on rate limits, staging or development environments, or an extension framework with its own lifecycle, which is what separates the top of the range from a strong API platform. 7 7 1 8
The Skeptic
API-first headless is the pitch and the pages back it: RESTful APIs, API-first connectivity across systems, channels and AI agents, developer training and documentation, a Frontend component, and a standalone catalog that runs alongside an existing stack without replatforming. We found no public information on documented rate limits, staging or development environments, extension lifecycle management, or source availability, so the long-term cost of owning customisations is not derivable from what is published. 7 7 4 8 8
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 — 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.
The Merchant
The inventory story is the strongest documented anywhere here: real-time stock across every warehouse and store, checkout reservations scaling to 100,000 a minute, safety stock, native backorders and pre-orders, mixed inventory in a single cart and omnichannel fulfilment, with InStore and Google Universal Cart as additional intake channels and custom order workflows. We found no public information on returns or refunds, carrier integrations or label printing, or maintained interfaces to named ERP and accounting systems — and in German consumer retail the returns desk is where margin lives or dies. 9 5 8
The B2B Seller
Inventory operations are documented impressively: real-time stock across every warehouse and store, checkout reservations scaling to 100,000 per minute, configurable safety stock, native backorders and pre-orders, and omnichannel fulfilment. But for everything a German merchant asks me about after the sale — carrier label printing, returns and refunds, maintained links to named ERP or accounting systems such as DATEV — I found no public information. 9 5
The Developer
Post-checkout operations are well evidenced on the stock side: real-time tracking across every warehouse and store, inventory reserved while the buyer pays, configurable safety stock, native backorders and pre-orders, mixed inventory in a single cart, omnichannel fulfilment, custom order workflows and a Merchant Center. We found no public information on returns and refunds, carrier or label integrations, or maintained interfaces to named ERP and accounting systems. 1 9 5
The Operations Lead
Stock truth is well evidenced: real-time tracking across every warehouse and store, configurable checkout reservations scaling to 100,000 per minute alongside 1,000 orders per minute, safety stock and quantity thresholds, native backorders and pre-orders, mixed inventory in a single cart, omnichannel fulfilment, plus live cart editing and custom order workflows. We found no public information on returns or refunds (partial or otherwise), carrier integrations, label printing, or maintained interfaces to named ERP or accounting systems such as DATEV — and that is the half of the operation I judge hardest. 9 5
The Data Protection Officer
Stock is the strength: real-time visibility across every warehouse and store, reservations at checkout at scale, safety stock and quantity thresholds, native backorders and pre-orders, mixed inventory in one cart and omnichannel fulfilment, with channel intake such as Google Universal Cart and InStore. We found no public information on returns or refunds — full or partial — on carrier integrations or label printing, or on maintained interfaces to named ERP and accounting systems such as DATEV. 9 5 8
The Skeptic
Inventory is the documented strength: real-time stock across every warehouse and store, checkout reservations scaling to 100,000 per minute, safety stock and quantity thresholds, native backorders and pre-orders, mixed inventory in a single cart, and omnichannel fulfilment with custom order workflows. We found no public information on returns or refunds, carrier integrations or label printing, or maintained interfaces to ERP and accounting systems such as DATEV, so the back office beyond the stock ledger rests on custom work these pages do not describe. 5 9 5
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 — 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.
The Merchant
We found no public information on exporting the catalogue, customers or order history, on a migration path in or out, or on a hosting choice beyond the named cloud regions. The one bearing fact is that deletion requests from data controllers are executed in accordance with applicable instructions, with internal retention and deletion policies defined and enforced. 3
The B2B Seller
The only data-control facts I can rest on are that deletion requests from controllers are executed and that retention and deletion policies are defined and enforced. I found no public information on export of catalogue, customer or order history, on a migration path in or out, or on self-hosting, so what leaving actually costs cannot be judged from these pages. 3 7
The Developer
The pages document a data-protection posture, with a GDPR Article 28 data processing agreement available on request, deletion requests honoured and enforced retention policies. Nothing documents export of catalogue, customers or orders, a migration path, or self-hosting; for a platform I would maintain for five years, the cost of leaving is undocumented. 3
The Operations Lead
The only relevant facts are that deletion requests from data controllers are executed as instructed and internal retention and deletion policies are defined and enforced. We found no public information on export of catalogue, customers or orders, on a migration path in or out, or on self-hosting options. 3
The Data Protection Officer
Deletion requests from controllers are executed in accordance with instructions, retention and deletion policies are defined and enforced, and a GDPR Article 28 data processing agreement is offered on request — all things I look for in a checkout stack. What I cannot see is the exit: we found no public information on export of the catalogue, customers and order history, on return of data on cancellation, or on self-hosting, so what leaving actually costs is not established. 3
The Skeptic
The security page says controller deletion requests are executed and retention and deletion policies are enforced, and REST APIs reach the commerce data, but we found no public information on documented export of catalogue, customers or order history, on a migration path in or out, or on self-hosting — the platform runs on the vendor's GCP and AWS tenancy across three regions. What a merchant can take with them on cancellation, and at what cost, is a question these pages leave open. 3 7
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. 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.
The Merchant
The contracting entity is genuinely German — commercetools GmbH in Munich, registered at Amtsgericht München — and a GDPR Article 28 data processing agreement is offered on request, alongside an external data protection officer, ISO 27001 and 27701 alignment, and a Europe region among the named hosting regions on Google Cloud and AWS. The pages also acknowledge transfers outside the EU under standard contractual clauses, and we found no published subprocessor list with locations and no statement of which region a project uses by default. 2 3
The B2B Seller
The contracting entity is solidly German — commercetools GmbH of Munich, registered at Amtsgericht München — with a GDPR Article 28 data processing agreement offered on request and a Europe region among the hosting regions on Google Cloud and Amazon Web Services. I found no public information on which region is standard for a project or on the subprocessor chain, and the security page itself acknowledges transfers outside the EU under standard contractual clauses. 1 2 3
The Developer
The contracting entity is proven German, commercetools GmbH of Munich with commercial register and VAT details, a data processing agreement is offered, GDPR alignment and Standard Contractual Clauses for transfers outside the EU are stated, and hosting runs on Google Cloud and AWS across Europe, the US and APAC. The captured pages do not establish where a given project's data lives by default or which subprocessors sit in the chain, so this stays below EU hosting as a stated standard. 2 3
The Operations Lead
The contracting entity is commercetools GmbH in Munich with a German commercial register entry and VAT ID, a data processing agreement under GDPR Article 28 is offered on request, and Europe is among the named hosting regions on Google Cloud and Amazon Web Services. Transfers outside the EU under Standard Contractual Clauses are explicitly acknowledged, the default region for a project is not stated, and no subprocessor list with locations is published on the captured pages. 1 2 3
The Data Protection Officer
The contracting side is solidly European: commercetools GmbH in Munich, registered in the Amtsgericht München commercial register with a German VAT ID, an external data protection officer appointed, GDPR commitments stated and a DPA on request, with infrastructure named as Google Cloud and Amazon Web Services across Europe, the US and APAC. Two things keep this from the top of the range: we found no public information on a subprocessor list with locations for the checkout path — CDN, analytics, payment routing, support tooling — and the pages acknowledge transfers outside the EU under Standard Contractual Clauses while leaving unstated which region a project's data calls home. 2 3
The Skeptic
The front door is provably European: commercetools GmbH in Munich, registered at Amtsgericht München, with a data processing agreement offered under Article 28 and Europe named among three hosting regions on GCP and AWS. But the security page acknowledges transfers of data outside the EU under Standard Contractual Clauses, no default region is stated, no subprocessor list is published, and UK and Australian affiliates appear alongside the German entity. 2 3
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 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.
The Merchant
We found no public prices on any page we read — no tier figures, no transaction or revenue-share rates, no billing period or minimum term. The only pricing-related facts are a free trial and Premium support and Expert services offered without figures, so the real annual cost is a sales conversation rather than something I can compute, and I cannot weigh the contribution this platform would make against what it charges. 8 1 8
The B2B Seller
The only pricing-related item on any page I read is a free-trial offer. I found no public information on tier prices, billing periods, order or revenue limits, transaction fees, VAT treatment or minimum terms, so a merchant cannot compute an annual cost from the vendor's public pages before entering a sales conversation. 4 8 1
The Developer
The only pricing fact the pages yield is that a free trial is offered; no tier price, licence fee, transaction rate or revenue share appears anywhere, and premium support and expert services are listed without figures. An annual cost is not computable from what is published. 8 1
The Operations Lead
The captured pages offer a free trial and name the editions (B2C Commerce, B2B Commerce, B2X Commerce and the standalone components), but we found no public prices for any tier, billing period or inclusion. An annual cost is not computable from what was captured; every price appears to be a sales conversation. 8 1
The Data Protection Officer
The only public pricing fact is a free trial; we found no public information on prices for any of the named products — B2C Commerce, B2B Commerce, B2X Commerce, Core Commerce — nor on billing periods, transaction or revenue-share rates, or order limits. For a merchant the annual cost is not computable from the public pages; the number comes from a sales conversation. 4 8 1
The Skeptic
Not one public price on any captured page: the editions are named — B2C Commerce, B2B Commerce, B2X Commerce, Core Commerce — with no figures, no billing period, no transaction or revenue-share rates, and even the audit reports are gated behind a sales contact or a signed NDA. A merchant can compute nothing from these pages except that a free trial exists; the real annual cost is a sales conversation. 3 4 1 5
European sovereignty — proven facts
2 of 6 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
unverified
Why unverified?The security page also names affiliated entities (commercetools Limited UK, commercetools AU Pty Ltd), but no excerpt indicates any parent company seated outside Germany. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?The page names the regions but not which one is default for a given customer project, and it explicitly acknowledges that data may be transferred outside the EU under Standard Contractual Clauses. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | On request | 0/1 pts | 3 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about commercetools
Is commercetools European?
Not determined: the vendor’s pages as captured do not say where commercetools is based. Its vendor, commercetools GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does commercetools store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does commercetools have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to commercetools?
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: commercetools alternatives.
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 — Legal entity. The security page also names affiliated entities (commercetools Limited UK, commercetools AU Pty Ltd), but no excerpt indicates any parent company seated outside Germany.
- Weak sourcing — Hosting location. The page names the regions but not which one is default for a given customer project, and it explicitly acknowledges that data may be transferred outside the EU under Standard Contractual Clauses.
- 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.
- 49 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
- 8 compliance 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
- 5 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
- 1 support 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. 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 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 22 Sep 2026 Details →
- 2 Imprint — found from the homepage commercetools.com Checked 16 Nov 2026 Details →
- 3 Security / trust page — found from the homepage commercetools.com Checked 16 Nov 2026 Details →
- 4 Catalogue & checkout — found from sitemap commercetools.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Catalogue & checkout — found from sitemap commercetools.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 6 Tax & German legal correctness — found from sitemap commercetools.com Checked 16 Nov 2026 Details →
- 7 Extensibility & developer surface — found from sitemap commercetools.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Extensibility & developer surface — found from sitemap commercetools.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 9 Order operations & back office — found from sitemap commercetools.com Checked 16 Nov 2026 Details →