Skip to main content
Compare

Vendure vs commercetools

Both platforms are API-first. On commercetools, custom logic runs in services beside the platform and the bill is order-based. On Vendure it runs inside one TypeScript backend, on a flat plan.

The short answer

Choose Vendure when

  • PunchOut, Configurator and contract pricing must come in the plan
  • The platform bill should not move with order volume
  • You want the source code and to self-host in any region
  • Custom logic should run inside one TypeScript backend
  • You have no permanent platform engineering team

What you leave behind on commercetools

  • Order-based pricing with no public rate card
  • Advanced B2B APIs and Audit Log Premium sold as add-ons
  • No native CPQ or punchout
  • A 25 API Extension cap and no source access
Pain points

Three things commercetools leaves you to assemble

Vendure B2B capabilities by plan, from 9 of 32 on Starter to all 32 on Enterprise.
1 of 3

CPQ and punchout arrive as partners and add-ons

commercetools has no native CPQ or punchout, so both come through partner integrations, and its Advanced B2B APIs are a paid add-on. On Vendure, quotes come from Starter, contract pricing and order approvals at Scale, and PunchOut and Configurator at Enterprise, each as part of the plan.

On commercetools, logic that must run inside a request is an API Extension, a call out to a service beside the platform, and background work runs on Subscriptions. Vendure plugins run in the same process as Vendure Framework, as TypeScript modules.
2 of 3

Custom logic without a 25-extension ceiling

commercetools gives no source access and caps API Extensions at 25 per project, so logic that must run inside a request becomes a call out to a service your team hosts and monitors. Vendure plugins are NestJS modules in the same process as the Framework, with custom fields that propagate straight into the GraphQL schema.

commercetools runs as multi-tenant SaaS in five Google Cloud and AWS regions, with no self-hosting. Vendure self-hosts on any cloud or on-premises, with data in PostgreSQL, MySQL or MariaDB.
3 of 3

No order metering, and the code runs where you choose

commercetools prices on orders through a sales quote, sells extra regions as add-ons and runs only as multi-tenant SaaS. Vendure has no metering on orders, no GMV charge and no fee per user. The GPLv3 Framework cannot be revoked, and your data sits in your own SQL database, on the cloud or hardware you pick.

How they compare

The same six dimensions on every Vendure comparison. Sources for every commercetools claim are at the foot of the page.

Vendure compared with commercetools across six dimensions: architecture and extensibility, licensing and cost model, B2B depth, hosting and operations, ecosystem and talent, and migration effort.
DimensionVendurecommercetools
Architecture and extensibilityVendureTypeScript end to end on NestJS, with GraphQL Shop and Admin APIs. Plugins sit beside the Framework. No forks, no extension cap.commercetoolsMulti-tenant SaaS, no source access. API Extensions cap at 25 per project, so business logic runs in services beside the platform.
Licensing and cost modelVendureFree open-source Vendure Framework under GPLv3. Four flat, cumulative plans from €199 a month on a 12-month term, with Enterprise from €60,000 a year. No GMV, per-order or per-user fees.commercetoolsSales-quoted, order-based pricing with paid add-ons such as Advanced B2B APIs and additional regions. No public rate card.
B2B depthVendureCompany accounts and quotes from Starter. Organization hierarchy at Growth. Contract pricing, single-level order approvals, the audit log and the Next.js B2B storefront at Scale. PunchOut (cXML), Configurator and multi-level approvals with timeouts and delegation at Enterprise.commercetoolsBusiness units, associates, quotes and approval flows, partly behind a paid add-on. No native CPQ or punchout (partner integrations exist).
Hosting and operationsVendureSelf-host on any cloud or on-premises, in any region. Managed Vendure Cloud is planned for Q1 2027, with a base set of Cloud resources in each paid plan.commercetoolsMulti-tenant SaaS on GCP and AWS, including EU regions. No self-hosting. Additional regions cost extra.
Ecosystem and talentVendureMainstream TypeScript, Node and GraphQL. No proprietary skill silo.commercetoolsStandard web skills plus MACH experience, and a team to build and maintain the services that run beside the platform.
Migration effortVendureImport catalogue and customers, rebuild the storefront on the GraphQL API or start from the Next.js one included from Scale, then re-point integrations.commercetoolsNot applicable.

Vendure pricing: a free open-source framework, then four flat tiers

Vendure Framework is free under GPLv3. Starter, Growth, Scale and Enterprise add B2B capabilities cumulatively, on a flat fee with no GMV, per-order or per-user charges.

Compare tiers and pricing
Migration triggers

When commercetools renewals reopen the platform question

The CTO or head of digital usually reopens the platform at renewal, when licence, add-ons, frontend and the services built around commercetools add up to one annual number.

  • Licence renewal

    where the licence is only part of the annual run cost: frontend, integrations and Connect apps come on top

  • B2B gaps found mid-build

    CPQ and punchout from partner integrations, and B2B APIs in a paid add-on

  • Frontend spend that stays in the budget

    a frontend your team builds and maintains as a permanent line item

  • Code ownership and self-hosting

    which multi-tenant SaaS cannot offer

Moving off commercetools?

Catalogue and customer import, a storefront rebuilt on the GraphQL API or started from the Next.js B2B storefront included from Scale, then integrations re-pointed. Migration guides are being written; the hub has what exists today.

IBMHans Kohler AGBreitlingKlektMunchSwileQVCHemglassFeddersen GroupFlowtechWilhelm WeishäuplSKYdeals

Teams building complex commerce with Vendure

FAQ

Vendure and commercetools, answered

Sources (7) · claims last checked 2026
  1. commercetools API limits: the API Extensions cap, order search indexing window and variant limits · docs.commercetools.com/api/limits
  2. commercetools B2B documentation: business units, associates, quotes, approval flows and the Advanced B2B APIs add-on · docs.commercetools.com/offering/core-commerce-b2b
  3. commercetools pricing: sales-quoted, order-based pricing and paid add-ons such as Advanced B2B APIs, Audit Log Premium and additional regions · commercetools.com/pricing
  4. commercetools API regions: Google Cloud and AWS regions in North America, Europe and Australia · docs.commercetools.com/api/general-concepts#regions
  5. commercetools technology partners: Shopspray Commerce Punchout, a partner punchout integration · commercetools.com/technology-partners/shopspray
  6. commercetools Connect documentation: hosted Connect applications · docs.commercetools.com/connect
  7. Vendure pricing and plans · vendure.io/pricing