What are Add-Ons and how to configure them

Add-ons in Limio allow you to sell a product alongside a core product, for example a Premium Support add-on alongside a Pro plan. They are either bought alongside a core product (called Offers) or can be added to a Subscription that already has a core product. 

Add-ons will generally inherit the Term and Auto-Renew settings from the parent Offer or Subscription. Therefore adding or removing an add-on will be co-termed with the parent offer or subscription.

When to use add-ons

Add-ons can be used in various commercial scenarios, such as:

• For a SaaS company, to sell additional products alongside a core package.
  Examples: analytics package, AI feature bundle, training services, or premium support.
• For a media company, to extend a digital package.
  Examples: adding a game subscription to a digital plan, or including event access.

Key behaviours of add-ons

• For new orders, the Add-Ons will inherit the term of the Offer.
• For self-service, the Add-Ons will be co-termed with the parent Subscription.
  • If added mid-term, prorated charges apply for the remainder of the billing period.
• How order processing works for add-ons:
  • For new Subscriptions, add-ons are included as part of the Create Subscription order in Limio.
  • For self-service updates, customers can add or remove add-ons via the Update Subscription action in Limio.
    • This triggers a corresponding Add Product Order, Remove Product Order, or a combination of both in Zuora.
  • Learn more at: How Limio Events updates Zuora for Commerce
• Add-ons cannot be cancelled independently.
  • Cancellation is applied at the Subscription level. Cancelling a Subscription removes all associated Offers, including the base Offer and any add-ons.
  • However, as mentioned above, you can remove an Add-On from a Subscription.

Depending on your use case, consider the following alternatives:

• Separate Subscriptions: Useful if the additional product requires its own Term, billing cycle, or auto-renewal settings.
• Offer Switch: For cases where the customer is upgrading or changing their core Offer, rather than adding something alongside it. More details on Switch here.
• Bundle Offers: When multiple products are always sold together as a package, consider grouping them in a single Offer

Creating Add-Ons in Limio

The process of creating a subscription add-on is similar to the core Limio Offer concept. Go to 'Add-ons' from the left hand navigation and fill in the necessary information.

Out of the box, these are the fields available for configuration:

Field	Description	Required?
Name	The add-on name. This is only visible in the Limio app	Yes
Add-on display name	The add-on name that will be visible to the end user	Yes
Label	The label used to include add-ons to a page
Description	The description the end user will see
Price	The price for this add-on. This can be defined in Limio or it can be pulled externally.
Add-on type	You can define types for add-ons for easy categorisation
Rate plan	The corresponding Zuora rate plan for this add-on	Yes
Allow Multibuy	If true, the customer can add multiple of this add-on to their basket.
Default Quantity	Defines the starting quantity, the increments the add-on amount can be changed by and the minimum and maximum quantity.

You can create an add-on template in order to customise the view based on your specific needs, for example, you can hide certain fields.

Publishing Add-Ons

Add-Ons, just like Offers, are versioned and need to be published to be available to the sales channels, including Limio for Salesforce. This gives you greater control over your catalog and ensures updates are only visible once the corresponding page is republished. It also helps manage version control when selling through Limio Shop or Limio for Salesforce. Learn more at Published Offers and Add-ons.

New Order Process

If add-ons are selected during the new order journey, they will be incorporated during order processing and will appear in the Zuora subscription.

Limio's Cart Items and Cart Summary support Add-Ons. Learn more at:

• Component: Cart Items
• Component: Cart Summary

Self-Service

To use the add-ons concept within Self-Service, please use Custom Component and the Limio SDK.

Using add-ons with the Limio SDK

Accessing add-ons via the SDK

After constructing and publishing a page, you can access the available add-ons in the Limio SDK using the useCampaign hook.

[Limio Page]
|
└── useCampaign()
     ├── offers[]
     └── addOns[]

Example:

import { useCampaign } from '@limio/sdk'

const CustomComponent = () => {
  const { offers = [], addOns = [] } = useCampaign()

  // You can now display or interact with the available add-ons
}

 

Example addOn object:

{
  "name": "AddOn",
  "record_type": "add_on",
  "baseTemplate": "/config/templates/add_ons/default",
  "attributes": {
    "display_name__limio": "Add On display name",
    "label__limio": ["any"]
  },
  "user": "[e-mail]",
  "path": "/add_ons/addOnPath",
  "created": "2023-10-09T13:28:28+00:00",
  "modified": "2023-10-09T13:28:39+00:00",
  "productBundles": [
    {
      "product_path": "/product/path",
      "revenue_split": "100",
      "rate_plan": "add on rate plan"
    }
  ],
  "products": ["/product/path"]
}

 

Adding add-ons in new order or self-service

If you are building a custom new order or self-service custom component, you can use the Limio SDK to programmatically add add-ons to a customer's order.

➡️ See the SDK documentation

When using addToBasket, keep in mind:

• You must include each add-on in the addOns array.
• A quantity is required for each add-on to process the order correctly.

Example usage:

addToBasket(offer, {
  addOns: [
    {
      addOn: selectedAddOn,
      quantity: 1 || userSelection
    }
    // Add additional add-ons here if needed
  ]
})

This will correctly include the selected add-on(s) in the basket for processing.