2025
Commerce Layer changelog for software updates, new features, and general improvements.
Last updated
Was this helpful?
Commerce Layer changelog for software updates, new features, and general improvements.
Last updated
Was this helpful?
Now sales channels the tags associated with a specific subset of (at the moment: , , , and all types). On top of that, in the past few days we released the following minor (but still relevant) updates to our APIs:
— we've enhanced the _fulfill trigger attribute operation. Now it can be sent not only if the associated shipments are cancelled, shipped, or delivered, but also if the order is just approved.
— we now expose the name and image URL of the associated line items.
We've released a relevant chunk of updates regarding our Dashboard. As you may have noticed, the biggest one involves the UI, specifically the navigation menu. Now the old Apps section has been replaced by multiple dropdowns that group the apps by area/functionality:
Fulfillment — including Orders, Shipments, Customers, Returns, Stock transfers, and Subscriptions apps.
Products — including SKUs, SKU lists, Prices, and Inventory apps.
Marketing — including Promotions, Bundles, and Gift cards apps.
Data — including Imports, Exports, and Tags apps.
Developers — including the Webhooks app alongside the API credentials, Resources, and Custom apps sections.
This grouping is replicated also in the application membership section where you can choose to which app a member have access.
Sign up or log in to see for yourself and feel free to share your feedback!
As previously announced the old Admin Area has been definitively sunset and is no longer accessible from the Dashboard.
As a first release, the two new tax calculators are available via API only. The Dashboard Settings section will be updated soon — stay tuned!
On top of that, we released the following minor (but still relevant) tax-related updates to our APIs:
Resource attributes computed dynamically are now exported with their original name, instead of using the delegated method’s one (e.g. item_type instead of item_resource_type). This could introduce a potential breaking change in case you're relying on a logic dependent on the old (wrong) exported attribute names. Speaking about , we also made them . On top of that, in the past few days we released the following minor (but still relevant) updates to our APIs:
— we added the tax_code attribute that you can leverage to define a custom tax code for your shipment tax calculation (currently supported by only).
— we added the on_behalf_of and transfer_group attributes, which are also available in the associated order payment_source_details.
Stripe Tax and Vertex have just come in addition to the list of we support out-of-the-box. You can now leverage the new and endpoints to manage tax calculations for your markets seamlessly.
— we exposed the events relationships on all the types of tax calculators.
— we added a new tax_exemption_code attribute to identify the reason for a specific customer's tax exemption.
We've extended to all the (with the only exception of ). Now, as a result of a successful response, you can ensure that external resources automatically add to the resource they are called for, specifically:
can add notifications on the patched line item.
can add notifications on the patched shipping method.
Each 's transaction (except for ) can add notifications to the associated order.
can add notifications to the order on which they are performing the discount computation.
can add notifications to the order on which they are performing the tax computation.
Still talking about external resources, we also added the option to pass two Trace Context so that you can easily trace the calls to your external endpoints on your APM. On top of that, we released the following minor (but still relevant) updates to our APIs:
— to enable the above, we added the relationship with the associated .
— we added a new timestamp that traces the time at which the resource was processed by the API.
— now we try to fulfill the associated order not only anytime a shipment is shipped but also when a shipment is cancelled (useful especially if the shipment cancellation is triggered ).