Upcoming changes
A preview of upcoming breaking changes and major feature releases for Commerce Layer, with indicative release timing.
A preview of upcoming breaking changes and major feature releases for Commerce Layer, with indicative release timing.
We're always working to improve Commerce Layer, so check this page regularly for updates and major releases info. You can also browse the changelog to see what's already shipped this year or explore the archive for older history.
On list endpoints, meta.record_count and meta.page_count will become approximate once the matching result set exceeds 10,000 records — below that threshold, counts will stay exact as before. Check the new meta.record_count_estimated flag to know whether the counts you got back are exact or an estimate — when true, don't rely on them as precise totals. Page contents will stay exact either way.
This also resolves intermittent timeouts previously seen on some high-volume list requests.
A complete redesign of the payments part of our Core API is underway — decoupling payments from orders so authorizations, captures, and refunds can evolve independently, with native support for multiple transactions per order, first-class gift cards, richer wallet management, and agent-driven commerce flows. It's too big a change to summarize in a changelog entry, so read all about it on our blog.
The version planned for release in mid-September will be a beta.
Completing the transition announced earlier this year and shipping alongside the Payments API redesign, the resource-level meta object will be reduced to a single field — created_with_version. The mode, organization_id, and trace_id keys will only be available at the document level from this release on.