> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/product-bundle-integration.md).

# Product Bundle Integration

Bundle mobile with existing brand services to offer converged pricing and discounts.

### Overview

**Product Bundle Integration** lets you bundle mobile with an existing **brand service**. This supports **converged offers** and **bundle discounts** for eligible customers.

* **What it is:** Bundle eligibility and discount support across Reach-powered journeys.
* **Why teams use it:** Improve retention and increase conversion with converged pricing.
* **Who it is for:** Growth, product, and operations teams running bundle offers.

<a href="https://datami.atlassian.net/helpcenter/Boltons/portal/1488/group/1848/create/2353" class="button primary" data-icon="cart-shopping">Buy this bolt-on</a>

### Typical use cases

* Discount mobile for **broadband customers**
* Offer **multi-product pricing tiers** for households
* Maintain **bundle pricing** as customer service changes

<figure><img src="https://3494749437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUFPSUngLZrTzBOau55s%2Fuploads%2Fw2OrOXCO6KMWSFlf8DGn%2Fimage.png?alt=media&amp;token=426e70e6-8522-41c5-89b5-5f8e58df955e" alt=""><figcaption></figcaption></figure>

### Scope

* **What is included:**
  * **Bundle eligibility checks** during purchase and self-care
  * Automatic application of **bundle pricing** or **discounts**
  * Ongoing alignment as customer service status changes
  * Removal of discount upon detection of **ineligibility**
* **What is excluded:**
  * Designing the **bundle strategy** and **pricing**
  * Full **loyalty** or **rewards program** builds

### Brand inputs

* **Eligibility rules**
* **Discount structure**
* **Customer messaging requirements**
* **Approval owner** for go-live

### Requesting this bolt-on

For the standard request process, commercial notes, and support, see [Bolt-ons catalog](/customizations-and-bolt-ons/bolt-ons-catalog.md).

### Technical details

For the implementation-specific setup details, visit: [Product Bundle set-up technical details](https://reachplatform.gitbook.io/reachplatform-docs/technical/~/revisions/b3C3M4tkkLMyqmMcGAsL/bolt-on-setup/product-bundle-integration)

<a href="https://datami.atlassian.net/helpcenter/Boltons/portal/1488/group/1848/create/2353" class="button primary" data-icon="cart-shopping">Buy this bolt-on</a>

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% endhint %}


---

# 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.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/product-bundle-integration.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.