> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/limio-commerce-release-notes/limio-commerce-release-notes/releases.md). # Releases Every customer-facing change to Limio Commerce, newest first. Subscribe with the RSS button at the top of this page to get each release as it ships. {% updates format="full" %} {% update date="2026-09-02" %} ## v118.0.29 This release contains internal maintenance changes only. No customer-facing behaviour changed in this version. {% endupdate %} {% update date="2026-08-28" %} ## Release 118.0.26 This release contains internal maintenance changes only. No customer-facing behaviour changed in this version. {% endupdate %} {% update date="2026-08-28" tags="Improvement,Fix" %} ## Release 118.0.25 **Improvement** — **AI agent response speed.** Limio Agents now responds to messages faster. Each message no longer waits for background telemetry to flush before the agent sends its response. **Fix** — **Page Builder block components.** When you added a Block component to a page, the canvas became unresponsive and you were unable to select or edit other components. Block component overlays now stay inside the canvas. **Fix** — **Catalog offer updates.** Changes made to offers were not applied to the catalog index, so published changes did not appear in the catalog. The catalog indexer now applies offer updates correctly. **Fix** — **Admin login.** The username field on the admin login screen was labelled "Email" and rejected entries that were not email addresses. The field is now labelled "Username" and accepts any valid username. **Fix** — **Checkout events.** The `checkout.initiated` event was not recorded when a shopper started a checkout, because the write ran without the required permissions. The event is now recorded correctly. **Fix** — **Agent editor tab counts.** The item counts on the tabs in the agent editor were not visible. The counts now appear on every tab. {% endupdate %} {% update date="2026-08-24" tags="Breaking,Feature,Fix,Improvement" %} ## Release 118.0.19 #### New Features **More granular permissions** Permissions have been rebuilt, so you can be precise about what each role is allowed to do. * **Choose which parts of Limio a role can reach.** A role no longer sees a page it has no access to * **Set read and write separately** on each type of record, rather than in bundled groups * **Scope partners to their own data.** Each partner organisation sees only its own subscriptions and orders * **The same rules apply everywhere** — the product catalog, publishing, bulk edit, catalog jobs and search, over the API, and through the MCP server, which runs as the user's own login Your existing access carries over, so every user keeps what they have today. **Create catalog items from your own systems** Offers, products, add-ons, discounts and pages can now be created in Limio directly from your own systems, in a single call. Limio checks each item against your own catalog templates before saving it, so a request that is not valid is refused with a clear reason and nothing half-made is saved. Previously every item had to be entered by hand. If you add products in volume, this saves a considerable amount of time. **Limio Agents can take a shopper through to checkout** * **Hand a shopper a real checkout.** An agent can build a basket for the offer they chose and give them a secure link, so the order ties back to the conversation. Previously the link created nothing in Limio and the sale could not be attributed * **Set tool behaviour per outcome,** so an agent works differently depending on what a conversation is trying to achieve * **Conversations survive navigation.** Moving between pages or refreshing no longer loses the thread, so a visitor never re-explains what they want #### Improvements **Sign in on your own domain** Signing in to the Limio app now happens on a Limio-branded page on your own domain. Previously it used a page hosted by Amazon on a different domain, which password managers treated as a separate site, so credentials were often not saved or filled. Nothing changes in how your team signs in, including single sign-on. **A dedicated API for placing and previewing orders on a customer's behalf** Two new endpoints, `/admin/order` and `/admin/order/preview`, let your own systems place an order for a customer and see what it will cost first. Each call runs with the permissions the caller actually holds. **A corrected API reference** The published API reference now matches what the API actually does. Request and response shapes, required fields and error responses were wrong or missing in places. **Consistent tables throughout the Limio app** Lists and tables across the Limio app now share one frame and spacing. An empty table says so, where previously it showed a header row with nothing beneath it. **The Team field has been removed from user settings** The Team field and its dropdowns are gone from the user screens. Nothing in Limio read it — access has always been decided by a user's role. **Strengthened platform security** Following our latest penetration test, Limio applies stricter ownership checks to account data, and several third-party components have been updated. #### Bug Fixes **A £0 order paid by card now completes** A fully discounted or compensation offer can now be bought through the standard card checkout. Previously the order failed during processing, no subscription was created, and the customer saw a failed checkout. **External prices now appear in the cart total** Items with an externally set price are now included in the cart total and on preview invoices. Previously they were left out of both, so the total a customer saw was too low. **Cooling-off cancellations work for Direct Debit orders** Cancelling within the cooling-off period now works for a Direct Debit order with nothing yet to refund. Previously the refund step failed and blocked the cancellation. **A refused basket can be recovered** Where a basket is refused, trying again now works. Previously the next page load picked the same refused basket back up, so the customer met the same failure. A dropped connection no longer discards a basket either, so a customer on a poor connection does not lose one they spent time filling. **An abandoned order no longer blocks a subscription claim** A customer who previously abandoned an order can now claim their subscription. Previously the leftover order counted as a second subscription and the claim was refused. **User details save without a Team** Editing a user in the Limio app now saves without selecting a Team. Previously the save was rejected for any user who had never been given one. *Please remember to perform a hard refresh in your browser after upgrading your environment.* {% endupdate %} {% endupdates %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.limio.com/limio-commerce-release-notes/limio-commerce-release-notes/releases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.