2026
Commerce Layer changelog for software updates, new features, and general improvements.
Versions endpoint removed, and more
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.
If you haven't migrated yet, event stores are the recommended replacement. Enterprise customers can also connect to the event stream hub for real-time updates without polling.
On top of that, two smaller updates ship with this release:
All payment gateways now expose a
credential_keysattribute, returning the last digits of each configured API credential key. Gateways that provide an official client — Adyen, Braintree, Checkout.com, PayPal, and Stripe — also expose a new_checktrigger attribute to validate credentials against the gateway's API directly.All timestamp attributes across resources have been updated from type
datetimeto typestring(withdatetimeformat), aligning with JSON Schema conventions.
Anomaly detection and alerting, now available
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.
Available for Enterprise customers — enable it from your organization settings in the Dashboard or ask your account manager.
Meet the new Metrics dashboard
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.
Available for Enterprise customers — request access from your Dashboard or get in touch with your account manager.
Introducing the Metrics Dashboard.
Get a clear, actionable, real-time view of your commerce performance. Explore trends, compare results, and understand what’s driving your business — all in one place.
More sections are already in the works, including Customers insights, Fulfillment analytics, and a Metrics Agent.
New queryable fields for returns
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.
Removed export size limit
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.
Coupons count info for promotions, and more
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:
Transactions — now you can get information about the payment method used in a transaction (available for all transaction types).
Shipping methods — now you can add and remove tags to shipping methods like any other taggable resource.
New free gift action and date-based dynamic values
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:
Free gift action — A new free gift action type is now available for flex promotions. It applies a 100% discount to specific line items added to the cart as free gifts, with full control over which items are eligible and how many units are discounted. Remember that Commerce Layer also exposes two dedicated order relationships that targets the available free SKUs and bundles to make it easy to surface a gift selection UI at checkout.
Date-based dynamic values — Condition values now support date expressions, making it straightforward to write time-sensitive rules without hard-coding any dates. You can reference the current date, extract date parts, match birthdays, or define date windows — all using the same notation already available for dynamic values (see some example and real use cases on our latest blog post).
Option to disable payment gateways, and more
We just powered the whole set of our supported payment gateways with a couple of new options:
Disable / enable — Now you can disable the payment gateways you don't use anymore (and possibly re-enable them, if needed) by passing a new trigger attribute on the specific payment gateway type. Active / inactive payment gateways can be retrieved by filtering / sorting the list by the new
disabled_attimestamp with the proper query.Force payments — the force payments option is now available on additional payment gateways beyond Stripe (for which it was already enabled by default). For those gateways (including Adyen, Axerve, Checkout.com, Satispay, and all external gateways), the feature is not enabled, meaning that the value for the
force_paymentsoption isfalse. Set it totrueon the specific gateway if you want incoming payment events to automatically align the order’s payment source with the one used by the transaction (as long as the order is still editable).
Custom include list for external resources, and more
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:
Imports — we added a new boolean parameter that you can set to
true(default isfalse) to disable the interruption of an import even if the number of errors exceeds the 10% threshold. We also enabled the possibility to add and/or remove tags directly when importing taggable resources.