Overview: How to customise the legacy Limio Checkout (legacy)

⚠️ This article is about the legacy Limio checkout, relying on the component Single Page Checkout. For the new Modular Checkout, go to Overview: How to customise the Limio Modular Checkout.

The Limio checkout is a critical part of the purchasing experience. As such, it's likely that companies will need to customise it in order to achieve their UX, conversion, and compliance needs.

This document will give you an overview of the customisation available for the checkout. If you are looking for a detailed document on the Limio Component, go here: Component: Single Page Checkout.

Made for subscription companies (and beyond): Limio delivers its checkout primarily via the Single Page Checkout component. The Single Page Checkout is made to handle many typical scenarios for a subscription business in any currency:

• Show delivery fields for physical products
• Show gifting fields for gift products
• Capture company information for business orders
• Allow for quantity-based products 
• Sell multiple products in one transaction
• Sell one-off products
• Run tax and complex pricing calculation
• Have renewal checkout for existing termed subscription

In the background, a basket or cart is created and persist. The cart can be displayed and can also be used for abandon basket campaign.

Conversion optimised: It is also optimised to accelerate input, for example:

• Prefill fields from identity solutions such as name and email
• Add express checkout options such as Apple Pay, PayPal and Google Pay as soon as possible
• Provide integrations to prefill addresses such as Loqate

Configurable via no code: It is fully configurable within the Limio app, via props or the Style editor. Props can allow for example to:

• Configure copy of all fields, error messages, and consent/T&Cs
• Configure the order of fields
• Display offer specific information

Analytics in mind: The Limio Checkout also works well with analytics and reporting solution, for example to capture user events from the checkout and making sure orders pass through parameters such as UTM tags.

A/B test and experiments: It is possible to have as many checkouts as possible, allowing to A/B tests checkout, deliver specific checkout for specific Limio Offer, in different languages, or to support brand-specific or product-specific UX.

Compliance: There is also a range of off-the-shelf enforcement components for the checkout, such as Block Related Purchase Component or Block Purchase Dialog to prevent duplicate orders.

Extensible with code: Finally, it also supports adding more components, whether Limio Component or custom components, that can handle logic externally to the Single Page Checkout or interact with it. Those components can leverage the Limio SDK, for example to:

• Display custom fields that require external validation and lock the checkout before those validation rules are met.
• Show the basket in a different manner than the Limio basket.
• Enforce specific rules based on who the customer is and what they have in their basket.

Below is an overview of the customisation possible with the Limio checkout based on the intended change:

Limio is working on introducing even more flexibility to the checkout experience via our Single Page Checkout component and the Limio SDK. We're keen to hear your feedback on our Feature Request page.