2026

Commerce Layer changelog for software updates, new features, and general improvements.

New free gift action and date-based dynamic values

Rules Engine	February 24, 2026

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).

Birthday coupons and spend limits with Commerce Layer.

Learn how to use Commerce Layer’s Rules Engine to create birthday discounts, limit eligibility with customer metadata, and manage dynamic spend thresholds with precision.

Read more on our blog Contact sales

Added option to disable payment gateways, and more️

Core API	January 21, 2026

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_at timestamp 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_payments option is false. Set it to true on 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️

Core API	January 15, 2026

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 is false) 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.