> 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/components/component-library/self-service-components/component-compatible-add-ons.md).

# Component: Compatible Add-ons

**Available from:** Release 112

The **Compatible Add-ons** component displays a list of available add-ons that a customer can purchase during the Update Subscription flow. It is designed to work alongside other update components, such as **Update Cart Items**, and supports a more compact layout that the **Cross-sell** component to accommodate a large number of available add-ons.

{% embed url="<https://69c2cf3a42a094f3cd354b8d-hbwumtssfk.chromatic.com/?path=/story/shop-components-self-service-compatible-add-ons--multiple-add-ons-available&full=1&shortcuts=false&singleStory=true&embed=true>" %}

## Behaviour

* Displays add-ons listed in the selected offer’s **Cross-sell add-ons** attribute
  * Excludes add-ons that have the same SKU as other add-ons the customer may already own
* Each add-on card displays:
  * Title: **Cross-sell display name** (`cross_sell_display_name__limio`) add-on attribute
  * Description: **Cross-sell display description** (`cross_sell_display_description__limio`) add-on attribute
  * Price: Pricing configured on the add-on

{% hint style="info" %}
From Release 116, the component reads the same **Cross-sell display name** and **Cross-sell display description** attributes used by the Cross-sell component at acquisition, so add-ons are described consistently in both journeys. In earlier releases the description did not render.
{% endhint %}

\* When compatible add-ons are used in the \[Create Update Subscription Experience]\(<https://docs.limio.com/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-configure-an-update-subscription-flow> "mention"), existing add-ons will be retained if they are compatible with the new update offer. An add-on is considered compatible if it is included in the update offer's \*\*Cross-sell add-ons\*\* attribute. Add-ons that are not compatible with the update offer will be removed on the order effective date.

## Props

| Prop name               | Prop type | Default            | Notes                                                              |
| ----------------------- | --------- | ------------------ | ------------------------------------------------------------------ |
| Heading                 | string    | Compatible add-ons | Controls the heading displayed at the top of the component         |
| Add add-on button label | string    | Add                | Label used on the button for adding an add-on to the Update Basket |
| No add-ons heading      | string    | empty              | Displays when there are no add-ons to display                      |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/components/component-library/self-service-components/component-compatible-add-ons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.