Release Change Log (118+)
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.
v118.0.43
Improvement — Browser tab titles. Every page in the Limio app now sets its own browser tab title, so you can tell tabs apart when several are open.
Improvement — Security update. The cookies Limio sets are now marked so that JavaScript running on the page cannot read them. No action is needed.
Fix — The Style Editor opened unstyled and covered the page builder header. In the page builder, the Style Editor rendered without its styles until you clicked Full Screen, and in full screen the page builder header stayed visible behind it. The editor now opens styled, and full screen fills the screen.
Fix — The page builder previewed with the wrong styles. Components built with CSS modules rendered unstyled, and the page builder loaded the default design system instead of your own. Previews now use your design system and your components' own styles.
Fix — Custom component builds failed. A build failed for every component when the root tsconfig extended a package the builder does not install, and a bundle failed to load when one of its dependencies required an external package. Both now build and load.
Fix — A shop build stopped on a missing component file. If a catalog asset URL named a component file that no longer exists, the shop build stopped instead of continuing.
Fix — A template family page showed an error in place of its content. Opening a template family reported that permissionScope is not defined. The page now loads.
Fix — A dropdown was unreadable on a coloured background. Form controls took their text colour from whatever sat behind them, so a select on a coloured bar could disappear. Form controls now set their own text colour.
v118.0.39
Feature — Stripe payment provider. Checkouts can now be routed to Stripe. Select the Stripe integration in your config set and the correct payment path is chosen automatically at runtime.
Feature — Delete permission. A delete permission level is now available in data permissions. It is off for every role until you grant it, so existing access is unchanged.
Feature — Order API: structured failure detail. When an order fails, the admin order API now returns a structured breakdown of the reason — payment failure detail or risk decision — alongside the status. This makes it easier to surface a clear message to the customer and to route failures programmatically.
Improvement — Admin session stability. Admin users were logged out every 30 to 60 minutes due to a session fingerprint mismatch. Sessions now stay valid for the expected duration. The device, network, and location used at sign-in are also recorded, giving your team better visibility when a session behaves unexpectedly.
Improvement — Created and updated timestamps on user records. The date each management user record was created and last updated is now recorded and shown in the admin app.
Improvement — Account avatar in the app header. Your account avatar now appears in the Limio app header.
Improvement — Security updates. A wildcard injection vulnerability in the catalog API location search was closed. Several third-party libraries were also upgraded to address reported vulnerabilities. No action is needed.
Fix — Shop pages failed to render after rebuild. After a shop was rebuilt or republished, pages often loaded with no components visible, and the checkout form did not appear on certain design systems. Both issues are resolved and shops now render correctly after every build.
Fix — Partner checkout page was blank. The partner checkout displayed a blank page because a basket permission check returned a 403 error. The check is now correct and the page loads.
Fix — Catalog filter bar picklist. The picklist dropdown in the catalog filter bar appeared outside the bar, and selected values appeared below the input rather than inside it. Both now render in the correct position.
Fix — AI Agents list was capped at 25 entries. The agents list showed only 25 agents in no order and had no way to reach the rest. The list now returns all agents.
Fix — Deleting an agent did not remove it. The delete action returned a success response but left the agent in place. The agent is now removed correctly.
Fix — Rate Plan and Product Code fields did not show the selected value. Selecting a rate plan or product code in the admin app left the field looking empty. The selected value now appears.
Fix — Catalog URLs containing placeholders were rejected. Saving a catalog item was rejected when the checkout URL contained a Handlebars placeholder. Placeholder syntax is now accepted.
Fix — Missing country codes on payment pages. Several countries were absent from the payment page country selector, so shoppers from those countries could not complete a purchase. The missing codes are now present.
Fix — Selected quantity was lost during an upsell swap. When a shopper swapped an item in the cart, the quantity they had selected was reset. The selected quantity is now carried across the swap.
Fix — Future-dated subscription offers returned malformed. Fetching a subscription that included future-dated offers returned a malformed response. Future-dated offers are now included correctly.
Fix — Order preview failed with unpriced add-ons. Previewing an order that included an unpriced add-on returned an error. Unpriced items are now excluded from the currency check and the preview completes.
Fix — Agent outcome editor kept deleted tools active. Removing a tool from an agent's steps left the tool still applied to the outcome. Deleted tools no longer apply after they are removed.
Fix — Several checkout journey errors were corrected. Errors in the purchase link flow, subscription switch flow, and partner checkout flow could prevent a customer from completing their purchase. All three have been corrected.
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.
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.
Last updated
Was this helpful?