Limio Release Notes - Release 106

Highlights

• B2C & B2B Commerce: A series of new Cart components, including items, total, promo code, and billing schedule.
• Frictionless checkout: Promo Codes v2, Advanced Purchase Links.
• Pixel-perfect Experiences: New generic components, new 60/40 layout
• Analytics: New Checkout Conversion Rate report.

⚠️  Please note there are breaking changes in this release.

• • Issues with favicon at the domain level - affects all customers using favicons

Please remember to perform a hard refresh in your browser after upgrading your environment.

We've updated our Browser Support Policy, read more about it here: Browser Support Policies

In summary, we support Chrome (desktop and Android), Safari (macOS and iOS), Edge, and Firefox (desktop and Android).

New Features and Improvements

New out-of-the-box Cart components for a better checkout experience

We’re excited to introduce new out-of-the-box Cart components that will help you provide a better purchase experience for your customers. These components support a variety of new commerce use cases, like showing multiple offers and add-ons, allowing customers to choose offer quantities, displaying discounts from promo codes, showing tax, and showing the customer their payment amount due today and in the future. 

The components are compatible with all existing Limio features, such as the data layer, analytics and the abandon basket API.

These components can be used to build a dedicated cart page, or can be used alongside our Modular Checkout components. 

Screenshot: The new Cart components can be used to build a dedicated, standalone cart page.

Screenshot: The new Cart components can be used alongside the Modular Checkout

Read more about using these components here: Using Cart Components in the Limio Page Builder

Read more about each specific component here: 

• Component: Cart Items
• Component: Cart Summary
• Component: Billing Schedule
• Component: Initiate Checkout Button

Create discount-based promo codes with Promo Codes v2

We're excited to announce the launch of our new Promo Codes! Previously, our promo codes related directly to a specific offer. Now, our promo codes are percentage (%) or fixed-amount (£ or $) discounts that can be applied to the customers entire cart or just to specific offers or add-ons. Promo codes can be used to apply promotional pricing more easily, or can be used to target specific customers with single-use codes. 

This introductory video gives an overview of the new promo code functionality:

Embedded video: Learn how to use our Promo Codes v2.

In order to use Promo Codes v2, you'll need to switch them on: 

1. Go to Settings > General Settings > Beta.
2. Toggle "use Promo Codes v2 instead of Promo Codes v1" to be on.
3. Click Save.

If you turn on Promo Codes v2, your old Promo Codes v1 will still be available via direct link: {Limio Commerce domain name}/objects/promo_codes/limio

 To support redemption of promo codes in a cart or checkout, use our new Promo Code Redeem component. You can also create promo codes via our API.

Read more about how to use promo codes v2 here: How to configure and implement Promo Codes v2

Apply discounts from promo codes to debit memos

In order to support promo codes being applied to gift offers, a small change has been made to how we create debit memos in Zuora when a gift offer is purchased. We now override the rate plan price on the corresponding debit memo when there are discounts (from a promo code) in the order.

Configure promo codes or multiple offers in Purchase Links

We've added new functionality to our Purchase Links. You can now include a promo code v2 in link, or populate the basket with multiple offers instead of just one.

For example, entice your customers to come back to their abandoned basket with a 5% off promo code: https://www.yourdomain.com/checkout?basket=123&pc=5OFF

Or, you could send your customers to a checkout with a basic subscription offer, plus a promotional discounted offer: https://www.yourdomain.com/checkout?purchase=/offers2/DigitalSubscription&purchase=/offers2/SpecialPromotion

Read about all the possible ways to configure a Purchase Link here: How to configure Purchase Links 

New out-of-the-box components for easier page building

We've introduced 3 new generic components that can be used throughout your Limio pages. These components give you more flexibility without needing to code. You can add styled text anywhere on the page with the Text component, can create more stylish pages with the Separator component, and can use a generic and styled back button with our Back Button component.

Read more about each specific component here:

• Component: Text
• Component: Separator
• Component: Back Button

New 60/40 two column page layout

We've introduced a new two column page layout to complement our new Cart components. The split is 60% left panel and 40% right panel. This can help you build modern and stylish Cart or Checkout pages.

Read more about our different layouts here: How to configure the Layout for your Page Builder

Limio Analytics: New Checkout Conversion Rate report

The Checkout Conversion Rate report displays your conversion rate per checkout for the last 30 days. The conversion rate is calculated by the number of order.new events with status submitted (successful), divided by the number of baskets that entered a checkout. This report can be exported for easy data analysis, and can be helpful for running A/B checkout testing.

The Checkout Conversion Rate report can help answer questions like:

• What is my checkout success rate for each of my checkouts?
• What is my best performing checkout?
• What is my worst performing checkout?

The report can be accessed by clicking "Catalog" in the top left corner, switching to "Analytics", and then selecting "Checkout Conversion" in the left panel.

Screenshot: The Checkout Conversion report shows each of your checkouts along with the conversion rate for each one.

Read more about the new Checkout Conversion report here: Limio Analytics: Checkout Conversion

Unique names for exported analytics reports

Previously, all of the Limio Analytics reports had the same name when exporting, which made it difficult to keep track of downloaded reports. This has been improved so the file name is unique: 

• New and Renew: orders_reporting_datadd-mm-yyyy.csv
• Cancels & Saves: cancelsave_reporting_datadd-mm-yyyy.csv
• Switch Orders: switch_reporting_datadd-mm-yyyy.csv
• Checkout Conversion: checkoutconversion_reporting_datadd-mm-yyyy.csv

Read about all of our Limio Analytics reports in this section: Limio Analytics

Skip payment collection for 0 value gifts

You may want to give away a free gift as part of a promotion. In order to support this use case, we bypass the Zuora payment collection process if the total amount on the created debit memo is 0.

Show credit memo and update subscription order types in the Limio for Salesforce (LFS) Timeline component

The LFS Timeline, which is driven by the Limio Commerce Timeline API, now includes events for credit memo and update subscription order types. 

A credit memo event is triggered when using the credit memo flow in LFS, and the update subscription event is triggered when purchasing an add-on. 

Screenshot: This example displays an update subscription event in the LFS Timeline component.

Read more about our LFS Credit Memo flow here: Manage Subscriptions subflow: Credit Memo

Read more about add-ons in LFS here: Manage Subscriptions subflow: Manage Add-ons

Include critical flag in process steps so Limio for Salesforce (LFS) can use the flag in order processing

Previously, if a non-critical step in LFS failed, the order would process successfully but the screen displayed to the LFS user would show an error. This was confusing to customer service agents who were expecting a success message. In order to improve the LFS screen when an order processes successfully but with errors, we now include a critical flag in each order processing step. This means that LFS will display a success message even if a non-critical step fails. 

Note: This improvement in LFS will not be visible until LFS Release 12.71. 

See the LFS Change Log here: Limio for Salesforce - Change Log

Enhance Preview Order API to include quantity and terms for update subscription orders

When previewing an update subscription order using the Preview Order API, users can now set new terms (term length, term type, term end date) or quantity for the preview. This will align the Preview Order API and the Submit Orders API.

Read more about the Preview API here: Preview Order

Read more about the Submit Orders API here: Submit Order

Refactor Cancel Subscription Buttons to use Limio SDK

The Cancel Subscription Buttons component has been refactored to fully use the Limio SDK. 

Read more about the Cancel Subscription Buttons component here: Component: Cancel Subscription Buttons

Improvements to add-ons

There are 2 new Limio attributes on add-ons: allow_multibuy__limio and default_quantity_options__limio. When allow_multibuy__limio is true, customers will be allowed to purchase multiple quantity of an add-on in one order. The default_quantity_options__limio attribute drives logic around the quantity, including the starting quantity, the increments the add-on quantity can be changed by, and the minimum and maximum quantity. 

These new attributes make the customer experience in the Cart Items component more robust and clear for the user. 

Please note that add-ons have also been more holistically refactored as part of this change. 

Screenshot: In this example using the Cart Items component, the first add-on would have multibuy = true and the second add-on would have multibuy = false. 

Read more about add-ons here: What are Add-Ons and how to configure them

Improved accessibility on the Payments Table component

Previously, there were some buttons in the Payments Table component that were divs instead of buttons. We've made the component more accessible by ensuring that all buttons are of HTML button type. 

Read more about our Payments Table component here: Component: Payments Table

New setting in HPM setup to store payment method

For the implementation of one-time payment flows on CyberSource 2.0, storePaymentMethod must be false, because Zuora currently does not support processing recurring payments in INR through one-time payment flows on CyberSource. 

Read more about Zuora's prerequisites for implementing one time payment flows on CyberSource 2.0 here: Zuora Knowledge Center

As a result, Limio has introduced a new setting in General Settings > Zuora > HPM Pages to control whether or not certain HPM/Gateway configurations should store a payment method. 

Read more about setting up Hosted Payment Methods here: How to set up Zuora Payment Gateways and Hosted Payment Methods for eCommerce in Limio

Bug Fixes

Issue with favicons at the domain level (110304)

Users who used multiple domains for their shops faced an issue with favicons. Users set favicons at the domain level, but due to an issue with our favicon logic, the favicon would always be overwritten with the default Limio favicon in SEO search results. 

In order to support different favicons for different shop domains, we've improved the logic so that the domain-level favicon will not be overwritten.

⚠️ Note: This enhancement has a breaking change for everyone using favicons and Apple Touch icons.

We've also needed to change how the favicon and Apple Touch Icon relate to each other, so these are two separate settings now in both the general Shop settings (General Settings > Shop) and in the domain-level settings (Config > Templates > Pages > Domain).

Screenshot: Instead of automatically converting your favicon to Apple Touch icon format, you now need to upload a specific Apple Touch icon.

In order to avoid your favicons and Apple Touch Icon settings breaking, please upload a new Apple Touch icon in either the domain settings or the Shop settings. 

If you are using favicons and Apple Touch icons at the shop level:

1. Navigate to Limio Settings > Shop.
2. Add an Apple Touch icon to the "Apple Touch Icon" field. 
3. Click Save.
4. Rebuild and republish your pages.

If you are using favicons and Apple Touch icons at the domain level:

1. Navigate to Config.
2. Expand Templates.
3. Expand Pages.
4. For each page template you use, click into the Domain tab and add an Apple Touch icon to the Apple Touch Icon URL field, and click Save.
5. Rebuild and republish your pages.

End of term previews for subscriptions that renew to evergreen (110401)

There was an issue where renew to evergreen subscriptions could not be properly switched at end of term. This has been fixed so that an existing subscription can be previewed beyond the term end date. 

Display original offer information in Limio Analytics when source is salesforce

We have consolidated the handling of original offer data for switch, cancel, and save events by moving this processing to the backend, reducing the need for front-end API calls. 

This will fix the known issue from Release 104 where original offer information was not displayed in the Cancel & Saves report and Switch Orders reports in Limio Analytics. 

Improved error handling for rate plan syncs in Limio (110300)

Enhanced error handling prevents the page from crashing when a rate plan SKU is edited in Zuora and synced with Limio, ensuring existing offers remain stable.

Fixed account number handling in orders (110411)

An issue was identified where the account number was used instead of the invoiceAccountOwnerNumber, as required by Zuora. This discrepancy caused order failures when the two numbers differed. The issue has been resolved by consistently using the invoiceAccountOwnerNumber, ensuring proper handling of subscriptions and accounts in both existing and new order flows.

Fixed overlapping issue with Link List component in the Page Builder

We resolved an issue where the Link List component would float or overlap other items in the Page Builder. It now is positioned as expected.

Improved Analytics tables for large data sets

The Limio Analytics reports previously errored for customers with large datasets due to oversized responses and inefficient data retrieval. This has been resolved, so reports with large data sets will always load.

Enhanced rate plan pagination on the front end (110544)

An issue was identified where some rate plans were not displayed after synchronization, due to a pagination issue with large datasets. We resolved this by optimizing data fetching and handling of large queries, ensuring all rate plans are now displayed correctly.

Improved validation for text area subcomponent in Modular Checkout (110599) 

Previously, regex patterns didn’t work for Field subcomponents of type text area in the Form component. Now, if a regex pattern is provided, it will be used for validation. If not, the default validation will apply. This ensures textarea fields can support regex-based validation correctly.

Fixed address mapping issue causing errors in Zuora (110622)

An issue was identified where orders failed in Zuora because the state field was not populated correctly when address details were incomplete. This prevented account creation in certain cases. We introduced fallback logic to ensure the state field is populated from alternative address details if the primary information is missing. This fix improves reliability and prevents similar errors during order processing.

Fixed intermittent errors in data synchronization with DynamoDB (110482)

We identified an issue where data synchronization occasionally failed due to inefficient handling of database connections. To resolve this, we implemented a global client cache to improve connection reuse and prevent errors. A setting was also added to allow the cache to be disabled if needed, ensuring flexibility for different use cases.

Enhanced past payment schedule accuracy for subscriptions (110681) 

An issue was identified where only a single past payment was being recorded for subscriptions, due to an incorrect assumption about how invoices are returned by Zuora's API. This caused incomplete past payment schedules to be created after syncing or applying certain orders. We resolved this by updating the logic to account for all invoices returned by the API, ensuring accurate creation of past payment schedules. Subscriptions with multiple past payments now correctly reflect their full payment history.

Enhanced usability for prop editor with long component names

An issue was identified where components with very long names caused the top prop label in the prop editor to be hidden, making it difficult to view or interact with the first prop. To ensure the header remains visible while scrolling, we replaced the fixed header with a sticky header.