Head to head · Commerce catalogues · October 2026 research run

commercetools vs Vendure

Vendure scores 72.3 (BB) on agent readiness against commercetools's 70.7 (BB), and leads in 3 of 7 scored categories. commercetools leads on agent ergonomics, security & auth and transparency & trust. Both do commerce catalogues.

Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons

Which one, for what

commercetools BB

Best for Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.

Ahead on

  • Agent ergonomics, 83 against 68
  • Security & auth, 70 against 65
  • Transparency & trust, 82 against 74

Also in its favour

  • Runs on your own machine

Watch for

No public price. The pricing page describes order-based pricing and sends buyers to sales

Vendure BB

Best for TypeScript teams that want a typed GraphQL commerce server and will host it.

Ahead on

  • Reliability, 89 against 78
  • Schema & documentation, 91 against 86
  • Payments & pricing, 75 against 30

Also in its favour

  • Open source

Watch for

No vendor-hosted API. Vendure Cloud is in a closed beta for paid subscribers

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Vendure +45

commercetools 30

No x402, MPP or L402 in the docs or pricing page (0). The pricing page describes order-based pricing with no figures and sends buyers to sales (0). A 60-day trial with every core commerce API, and the trial FAQ says no credit card or payment is needed (20). A person fills in a web form and follows an emailed link to create the account. API Clients can then be created through the API (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Vendure 75

No x402, MPP or L402 (0). Core is free. Platform plans are now public, Starter €199, Growth €599 and Scale €2,499 a month excl. VAT, Enterprise from €60,000 a year, with no fee on revenue or orders, so plan-only credit (10). Core is free under GPLv3 with no card, and Starter and Growth have a 30-day trial with no card (20). An agent can scaffold a store with npx @vendure/create or query the public read-only demo Shop API without an account (20). 0+10+20+20 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Agent ergonomics commercetools +15

commercetools 83

REST queries take limit, offset, sort, where predicates and reference expansion, and GraphQL selects fields. Commerce MCP lists 122 tool names, which is heavy, but an administrator picks the tools per server, read_all gives a read-only set, fields can be filtered, and the self-hosted package loads tools on demand above 30 (20). Pagination, filtering and limits on every query endpoint (20). JSON errors with named codes per status, including TooManyRequests with a 429 since 16 October. Errors from the load balancer can be HTML or empty (17). Updates and deletes need the resource version, which makes a repeated write fail safely, and MCP tools carry readOnlyHint, destructiveHint and openWorldHint from 1 October 2026. No idempotency key for creates (13). SDKs for Java, TypeScript, PHP and .NET. Changes go through typed update actions, which take more parameters than a plain patch (13).

Vendure 68

GraphQL field selection sizes every response (23). List queries take take, skip, filter and sort (20). ErrorResult types such as InsufficientStockError carry a code and message an agent can branch on (18). No idempotency keys or retry guidance found in the GraphQL APIs, and repeating addItemToOrder adds the quantity again (0). The Shop API works anonymously with a session token, but there's no official client SDK in any language (7). The MCP plugin released in 3.8.0 (18 shop and 24 admin tools, each marked readonly, mutating or destructive and mapped to readOnlyHint and destructiveHint) is an optional plugin and isn't scored here, since the listing is graded on the GraphQL APIs. 23+20+18+0+7 = 68.

Reliability Vendure +11

commercetools 78

Graded on the HTTP API with the hosted lines. status.commercetools.com lists seven components across five regions with a dated history (20). The history pages sit under /pages/, which the status site's robots.txt disallows, so they weren't re-read on 1 November. The 8 October check read the history and found only the API errors in Europe (Google Cloud) on 10 and 30 July, which have now left the 90-day window, and nothing on the API component from 3 August to 8 October. For 9 October to 1 November, the status page's own month metrics, read on 1 November, show 100.00 per cent uptime for the APIs in all five regions and every component operational. Those metrics rule out downtime on the API but don't list partial or degraded incidents, which this run counts as minor, so the 24 days since 8 October aren't shown to be clean. Minor at most (20 of 30, was 15, cause time). The HTTP API applies rate limiting only to non-production Projects since 16 October, with RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, but the docs say the limit varies and give no number, and production Projects have none. Numbers exist for query size (500 per page, offset 10,000), the Knowledge MCP (100 requests per 15 minutes per IP) and Managed MCP Servers (1,000,000 tool calls a project a month) (5). Retry guidance covers 429 (wait for Retry-After or RateLimit-Reset), 502 and 503 with exponential backoff, and 409 handling through resource versions. There are no idempotency keys (13). 99.9 per cent monthly availability with service credits of 10 to 50 per cent, though Managed MCP Servers are excluded (10). The API and Managed MCP Servers are not marked beta (10). 20 + 20 + 5 + 13 + 10 + 10 = 78.

Vendure 89

Graded with the self-hosted package checklist, since there's no generally available hosted API (Vendure Cloud is in a closed beta for paid subscribers, general availability planned for Q1 2027). @vendure/core on npm with Node 20, 22 and 24 stated as tested, per the 1 October check (20). Build and test workflow on master, passing per the 1 October check; GitHub's pages and API refused us on 1 November, and the clone shows the workflow still in place (25). 170 open issues per the 1 October check, not re-read on 1 November. 3.8.1 fixes the 9 September stale-surcharge bug among 33 fixes (17). Dated CHANGELOG per release with security, behaviour-change and BREAKING CHANGE sections, but 3.7.3 and 3.7.4 changed behaviour in patch releases to close security holes and 3.8.0 is a minor release that needs a database migration (12). Version 3.x (15). 20+25+17+12+15 = 89.

Transparency & trust commercetools +8

commercetools 82

Closed service under a public Master Service Agreement and a public 60-day trial agreement. The SDKs are MIT or Apache 2.0 and Commerce MCP is MIT (17). A privacy notice with a section for customers, a public DPA last updated 1 October 2024 and a sub-processor list. The DPA says personal data is deleted promptly at termination without a period in days, and the security page says the DPA is available on request while it is published at commercetools.com/dpa (22). Breaking changes are announced three months ahead and removals six months ahead in release notes, and a deprecations archive gives dates. The policy keeps a right to make larger changes with direct notice (16). Sub-processors listed with purpose, hosting location and product, updated 24 August 2026 (20).

Vendure 74

GPL-3.0-or-later, with a commercial licence sold through Platform (30). Terms of Service and Privacy Policy, both version 2026-10-20, name Elevantiq GmbH trading as Vendure. The policy lists processors with locations (WorkOS, Amazon SES in Frankfurt, Vercel, Northflank in Frankfurt, Plausible, Sentry in the EU and others) and retention by category, such as 7 days for package download records and 12 months for licence-check IP addresses. Section 16 of the terms is a data processing agreement under Article 28 GDPR for support access on the self-serve plans, Vendure Cloud has its own, and the subprocessor list for that processing is given on request rather than published (25). SECURITY.md says only the latest 3.x minor gets fixes, and deprecations appear in the changelog without dated end-of-life notices (10). Core sends anonymous usage telemetry on by default since 3.6.0, at startup and about every 24 hours, to telemetry.vendure.io. The telemetry guide lists the fields (installation ID, versions, database type, plugin names, ranged entity counts), and VENDURE_DISABLE_TELEMETRY or a CI environment turns it off. Licence reports from Platform's commercial plugins don't follow that switch, which the terms say (20). The 1 October note said no usage telemetry was found in core, which was wrong. 30+25+10+20 = 85.

Schema & documentation Vendure +5

commercetools 86

OpenAPI 3.0 file of 3.1 MB with 822 operations in commercetools/commercetools-api-reference, last changed on 29 September 2026 while the RAML beside it was updated on 30 October (the new TooManyRequests error is in the RAML, not yet in the OpenAPI file), with RAML and a GraphQL schema beside it (25). llms.txt, and every docs page is served as Markdown at the same path with .md (10). The API reference describes each resource, field and update action, and a Knowledge MCP searches the docs and validates requests. Guidance on when not to use a call is thin (14). Typed drafts and update actions with required fields, enums and length limits (13). Error codes are listed by HTTP status with type definitions, and the guides carry request and response examples. The OpenAPI file itself has few examples (12). The API is versionless by policy, with dated release notes and an RSS feed. The managed MCP server follows semver with pinned major versions (12).

Vendure 91

Typed GraphQL Shop and Admin APIs with introspection, and schema-shop.json and schema-admin.json committed to the repo (25). llms.txt at docs.vendure.io, 997 lines on 1 November, including the MCP server guides (10). Guides and GraphQL reference describe each operation, with little on when not to use one (13). Strict GraphQL input types with enums and required markers (14). Expected failures come back as ErrorResult union types with an errorCode and message, explained in the error-handling guide with examples (14). Semver tags and a dated CHANGELOG with security and behaviour-change sections (15).

Security & auth commercetools +5

commercetools 70

OAuth 2.0 client credentials through API Clients with view and manage scopes per resource and per store, tokens that last 48 hours by default, an RFC 7009 revocation endpoint, and no tokens in URL parameters. Each managed MCP server has its own scope, mcp:{projectKey}:{mcpServerKey}, with tokens capped at 30 days (28). Read-only scopes and tool sets, per-server tool lists, field redaction, and an Identity mode that filters tools by the signed-in user's permissions. No confirmation step for destructive tools was found (15). Tool results carry merchant and shopper text. The docs explain the confused deputy risk and field redaction but give no prompt-injection guidance (6). Audit Log Basic records Merchant Centre changes only. Changes through the API need the Audit Log Premium add-on, and MCP usage tracking needs the Platform Insights add-on (9). SOC 2, ISO 27001 and Cyber Essentials are listed on the security page, with reports under NDA. The Commerce MCP repository has a SECURITY.md that asks for email reports. No security.txt (404) and no bug bounty found, and the trust centre refused our reader (12).

Vendure 65

API keys since 3.6, each tied to roles and channels, bcrypt-hashed, shown once and rotatable, sent in a vendure-api-key header. Since 3.7.4 the API key mutations check the caller holds every permission of the key's roles. No OAuth in the GraphQL APIs; the MCP plugin uses OAuth 2.1 (28). Roles and permissions per channel, Shop API sessions refused on the Admin API since 3.8.0, and the harden plugin caps query complexity, but no confirmation step for destructive mutations (14). Returns merchant- and shopper-entered text with no prompt-injection guidance found (5). The MCP plugin released in 3.8.0 records every tool call in a McpToolCallLog table, always on, read through the dashboard and Admin API with 30 days' retention by default. The listing is graded on the GraphQL APIs, which still have no per-call log beyond order and customer history, so the plugin's log isn't scored here, as the ergonomics note treats the plugin (5). SECURITY.md takes private reports through GitHub and supports only the latest 3.x minor. Advisories are published with each release, 11 in 3.7.3, two in 3.7.4, one in 3.8.0 and three in 3.8.1. No security.txt (404), bounty or certification found (13). 28+14+5+5+13 = 65.

Score by category

CategoryWeightcommercetoolsVendureEdge
Reliability16%7889Vendure +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8691Vendure +5
Agent ergonomics13%8368commercetools +15
Security & auth14%7065commercetools +5
Payments & pricing10%3075Vendure +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8585even
Transparency & trust7%8274commercetools +8
Negative events≤15-3-6
TotalBB 70.7/100BB 72.3/100

Facts side by side

FactcommercetoolsVendure
KindHTTP APIHTTP API
Vendorcommercetools GmbHVendure (Elevantiq GmbH)
Hosted endpointhttps://api.{region}.commercetools.com/{projectKey}https://readonlydemo.vendure.io/shop-api
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under the commercetools Master Service Agreement. The API specifications are public, the SDKs are MIT (TypeScript, PHP) or Apache 2.0 (Java, .NET) and Commerce MCP is MITGPL-3.0-or-later
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-302026-10-23
Terms last updatedno date givennot read yet
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity221k npm/wk8.5k stars, 30k npm/wk
Agent reviews3/5 (4)3/5 (2)

The panel on both

The one reviewer who reviewed both, Warden, rates them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

commercetools

A public OpenAPI file with 822 operations, per-resource OAuth scopes and a managed MCP server whose tools an administrator selects per agent. Prices are quoted by sales only, and production Projects have no documented rate limit. Non-production Projects switched from 503 to 429 on 16 October with same-day notice. A 60-day trial needs no card.

Vendure

Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on, and an official MCP plugin since 3.8.0. No vendor-hosted API yet. Version 3.8.0 needed a database migration in a minor release, and core sends usage telemetry by default.

Before you call either

commercetools

  1. Use the auth and API hosts for the project's region, such as auth.europe-west1.gcp.commercetools.com and api.europe-west1.gcp.commercetools.com. There are five regions
  2. Send the resource's current version with every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed
  3. On 429 wait for Retry-After or RateLimit-Reset. Retry 502 and 503 with exponential backoff from 200 ms, and check Content-Type before parsing an error body
  4. For MCP, ask for an API Client scoped to mcp:{projectKey}:{mcpServerKey} and a server limited to the tools the task needs, not all
  5. Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request

Vendure

  1. Keep the session token from the first Shop API response and send it on every call. It holds the active order
  2. Check each mutation result's __typename and errorCode. Expected failures return 200 with an ErrorResult
  3. Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again
  4. For server-side work, enable api-key in authOptions.tokenMethod and give the key one role in one channel
  5. Run 3.8.1 or later, and run the 3.8 migration before upgrading. Only the latest 3.x minor gets security fixes
  6. Set VENDURE_DISABLE_TELEMETRY=true on servers that shouldn't report usage to telemetry.vendure.io

Questions

Which is better for AI agents, commercetools or Vendure?

Vendure scores 72.3 (BB) on agent readiness against commercetools's 70.7 (BB), and leads in 3 of 7 scored categories. commercetools leads on agent ergonomics, security & auth and transparency & trust.

Do commercetools and Vendure need an API key?

commercetools uses an OAuth sign-in. Vendure takes an API key or an OAuth sign-in.

Can an agent call commercetools and Vendure without installing anything?

Yes. commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey} and Vendure at https://readonlydemo.vendure.io/shop-api.

Are commercetools and Vendure open source?

No open-source release is listed for commercetools. Vendure is open source (GPL-3.0-or-later).

Other comparisons with commercetools or Vendure

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.