2026

Removing both the shipping and billing addresses from an order with an associated tax calculator now resets all previously computed tax amounts to zero. On top of that, other smaller updates ship with this release:

We've launched a dedicated documentation section covering everything you need to integrate AI agents and coding assistants with Commerce Layer. The foundation is a set of three purpose-built MCP servers, each targeting a specific kind of agent interaction:

We've defined a clear data retention policy for event stores — which will consequently affect the replay stream of the event stream hub — with different retention windows depending on the type of resource, its mode, and the event type involved. Check the docs for the full details — including specifics on deleted resources, test mode data, and which event types are stored for each resource.

API responses now include mode, organization_id, and trace_id at the document level, inside a root meta object (alongside the pagination fields already present in list responses) — in addition to the existing resource-level meta information.

Filter predicates belonging to the _cont family are now case-sensitive. If you need case-insensitive matching, make sure to update your integration to use the newly introduced _i_cont, _i_cont_any, _i_cont_all, _not_i_cont_any, and _not_i_cont_all counterparts.

A new inspect button is now available on order and promotion detail pages. It opens a panel showing the full resource details — attributes and a chronological event log covering status changes, attribute updates, and who triggered each action (user, worker, or application).

Two small but handy Dashboard enhancements ship with this release:

The versions endpoint and all the corresponding relationships across previously versionable resources have been permanently removed. This resource has been deprecated since August 2025, when version storage was discontinued.

On top of that, two smaller updates ship with this release:

We're introducing anomaly detection as a new capability inside Commerce Layer. The system continuously monitors your order workflows in real time, automatically identifying deviations from expected behavior — such as discrepancies between order placement and approval, or unusual shifts in payment method distribution. Instead of relying on static thresholds, it learns what "normal" looks like over time and triggers immediate alerts when something is off, so your team can investigate and act before issues impact customers or revenue.

The Metrics dashboard is now live — a single place inside Commerce Layer where commerce teams can monitor performance, explore trends, and go from insight to action without jumping across tools.

All metrics are updated in real time and the dashboard launches with four key sections: Orders, Promotions, Returns, and Carts. Every element is fully interactive, with flexible time range comparisons, powerful filtering by dimensions like market, currency, country, and tags, and one-click drill-downs into the underlying orders.

The returns resource in the Metrics API now exposes two new fields — return_line_items.name and return.currency_code — available across all query types (breakdown, date breakdown, stats, search, and export). This makes it possible to group and analyze return data by product name or currency, enabling insights like which products are returned most frequently, return quantities per product, and multi-currency return aggregations.

Exports just got a significant upgrade. There is now no limit on export size — large jobs are processed in multiple rounds, prioritizing reliability, with new attributes available to monitor how things are going (number of processed exports, estimated completion time, etc.). On top of that, you can now interrupt a running export at any time and restart it from where it left off, making it much easier to manage long-running jobs.

Now you can check the total number of coupons created for a specific promotion by inspecting the related attribute on the single promotion type. On top of that, in the past few days, we released the following minor (but still relevant) updates:

The Metrics API now supports a new query type. The export query is a CSV-flavored variant of the search query that returns matching records as a plain text/csv file, sorted and filtered to your needs. Available for orders, returns, and carts, with up to 100K records per export.

We just shipped two new Rules Engine capabilities that expand what you can express in your rules — one on the actions side, one on the conditions side:

We just powered the whole set of our supported payment gateways with a couple of new options:

Now you can overwrite the default list of resources included in the request payload of all the external resources (external order validations excluded) and specify a custom one. The allowed includes are based on the target resource required by the external request. Providing an invalid include for the target resource will result in an error. On top of that, in the past few days, we released the following minor (but still relevant) updates: