Release Notes

You can now process and manage Recurring Orders in Checkout using the new Recurring Payments API and Recurring Payment Jobs API.

You can now have commercetools Checkout collect payment for a Recurring Order before the subsequent Order is created.

We have fixed a bug that allowed a Channel referenced by a Standalone Price to be deleted.

You can now replace InStore POS UI modules with external ones that you create.

Agent Registry helps administrators discover available agents, review scopes, and track installations across Projects.

You can perform unrelated Category writes with fewer Category tree lock conflicts.

Commerce MCP supports the 2026-07-28 MCP specification, provides structured tool output, includes tool titles and safety annotations, and lets you set the authentication mode of Managed MCP Servers. It's available in the Managed Commerce MCP and in the version 4.2.0 of the self-hosted Commerce MCP.

You can now configure a Cancel button for credit payments and refunds.

You can now issue InStore refunds using your external payment processors.

You can now control whether an Attribute value is copied onto Line Items when a Product is added to a Cart.

You can now create Shopping Lists from unstructured customer requests in the Merchant Center using the Intake Agent.

You can now use ShoppingList as an output type in the Intake Agent API to create Shopping Lists from unstructured input.

You can filter on createdBy.attributedTo and lastModifiedBy.attributedTo, including by attribution source.

You can now assign Categories to specific Stores, and access them through new in-Store endpoints.

We have moved Modular Catalog from public beta to general availability. Product Search for Modular Catalog is available in public beta.

We have deprecated the InStore device CLI due to changes in the underlying APIs.

You can now configure API Extensions that are triggered by Product create and update requests.

You can now use the Product Enrichment Agent to base suggestions on store-based values and save enriched data to specific Stores or the main Product.

The Change History API now supports filtering by multiple resource IDs and user IDs in a single request.

You can now choose whether the net price or the tax amount is rounded when tax is included in the price.