> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/product-configuration/product-bundles.md).

# Product Bundles

A product bundle is a specific type of product which groups several products together so that they can be activated and used with a single license.

### General Process: Working With Product Bundles:

Generally, creating product bundles uses the following workflow:

{% stepper %}
{% step %}

### Initialize a product bundle

Initialize a product bundle.
{% endstep %}

{% step %}

### Issue licenses for the product bundle

Issue licenses for the product bundle.
{% endstep %}

{% step %}

### Activate each product individually using the same license

Activate each product in the bundle separately using the same license.
{% endstep %}
{% endstepper %}

### Initialize a Product Bundle

Product bundles can be created on the Products page in the platform by clicking the button Add new bundle.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/Mk1zpbl78T2kfRSFF4me/xFLRypQZlMRTJD_nfN1HB_image.png)

Enter the bundle name, code, authorization method, and select all the products which are going to be included in the bundle.

![Setting Bundle Values](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/10QPL1JCESjPshpUT1b7/NSZLjERf_0z%20fFMdNcb24_image.png)

{% hint style="info" %}
The bundle code must be unique from other bundle and other product codes.
{% endhint %}

{% hint style="info" %}
You can only bundle products using the same authorization method.
{% endhint %}

{% hint style="info" %}
The bundle code and authorization method cannot be edited after the bundle is created. You can still change the bundle name, and you can add or remove products in the bundle (see Add or remove bundle products).
{% endhint %}

### **Add or remove bundle products**

You can change which products are in a bundle after it is created. Open **Products**, select the bundle, and scroll to the **Products in a bundle** section.

**Add products**

1. Click **Add products**.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FxgIbfcthoBq5gEHkDP3Y%2FScreenshot%202026-10-30%20at%202.19.24%E2%80%AFPM.png?alt=media&amp;token=df7e9047-07ed-4f06-b95b-5abda3f7b966" alt=""><figcaption></figcaption></figure>

* Select the products you want to add to the bundle.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2Fhvj7KLQIvve7aYQmTFZV%2FScreenshot%202026-10-30%20at%202.19.37%E2%80%AFPM.png?alt=media&amp;token=a79272e2-edca-438d-b251-264fea5f0c44" alt=""><figcaption></figcaption></figure>

* Confirm to save.

**Remove a product**

1. In the **Products in a bundle** table, click the delete icon at the end of the product’s row.
2. Confirm to remove it.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FiZQIyxfnRODpS03PXxTz%2FScreenshot%202026-10-30%20at%202.20.49%E2%80%AFPM.png?alt=media&amp;token=78545cbe-5895-4dd4-9378-d18f44e73e8b" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Changes to bundle products apply to future orders only. Licenses that were already issued from this bundle are not affected.
{% endhint %}

{% hint style="info" %}
A bundle must always contain at least one product. You can only add products that use the same authorization method as the bundle.
{% endhint %}

### Issuing Bundle Licenses in the Vendor Platform:

{% hint style="info" %}
An order for bundles can only contain product licenses or bundle licenses, but not both.
{% endhint %}

Start as you normally would with any other license:

{% stepper %}
{% step %}

### Open the Order Creator

Open the Order Creator, and optionally add Customer and order information. Press "Next".
{% endstep %}

{% step %}

### Toggle bundle order and configure

Toggle "Create order for product bundle".

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/ZAyB0m2nD3hhm8OAuCAX/ED9wfbpLrGC3DW1vpzmXx_image.png)

In the product bundle selector:

* Select the bundle you wish to issue licenses for.
* Specify the license policy to be associated for each product individually.
* Click "Confirm", "Next" and "Create order".
  {% endstep %}
  {% endstepper %}

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/bC654WyNX7Mz6i1CJW8c/0zqEVZA0epwYtp%20LbaAzx_image.png)

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/FMRt7IAXjsiYYQuaFNtt/ZtSPENpJGkPzuh8DW%20ZE5_image.png)

The License Key can be found in the order:

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/iv1FwNRRmLqbDp11P5M6/jtJuqJWvqzA2nC2hOWsPD_image.png)

#### **Seats on a user-based bundle**

When the bundle uses user-based licensing, set how many users can be assigned to the bundle license:

1. **Select the bundle.** In the `Products` step of `Issue Licenses`, turn on `Create order for product bundle` and click `Select product bundle`.
2. **Set `Max license users`** ("How many users can be assigned to this bundle license"). It must be 1 or more.
3. **Confirm.** The selected bundle shows the number in the `Max license users` column.

The same field is there when you add a bundle to an existing order (`Issue new Licenses` on the order). Key-based bundles don't have it.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FSyLBDESSLMT4BmnehTuo%2F26-platform-bundle-seats.png?alt=media&amp;token=753007ca-1ef0-4ca4-a845-40509d5a0475" alt=""><figcaption></figcaption></figure>

### Activating Licenses for Bundled Products

The License created for the bundle can be used to activate the products within the bundle. The products need to be activated separately. For example, you cannot use the bundle code to activate the license for all of the products in that bundle.

### Assigning Users to User-Based Product Bundles

Users are assigned to the user-based bundle license and can then log in to the individual products using the same credentials separately.

{% hint style="warning" %}
There is no way to assign users to individual products of a bundle. In other words, a user will be assigned to all products within the bundle. The `Max users` will therefore be the smallest value of the `Max users` of all the individual license policies used.
{% endhint %}

### **Changing the seats on a bundle license**

Open the bundle license and click `Edit` on `License details`. Change `Max license users` and save. It can't be lower than the number of users already assigned.

The bundle license's `Users` tab shows the seats in use as `Available number of users: <assigned> / <max>`. Assign users there with `Assign license user` or `Batch license assign`, and remove them with `Batch remove users` (see [License Detail View](https://docs.licensespring.com/vendor-platform/orders/license-detail-view)).

> With the Management API, set the seats with `max_license_users` on the bundle item of the order. See [Create order](https://docs.licensespring.com/management-api/order/create-order).

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FAyzydk3Q1bkLRvfyPP5T%2F27-platform-bundle-users-tab.png?alt=media&amp;token=2c8a891d-efe7-491a-bd44-2872c5bfc35f" alt=""><figcaption></figcaption></figure>

### Activating Licenses of Bundles through the LicenseAPI

The API interfaces remain consistent, as we continue to operate with standard licenses for processes such as activation and verification.

For instance, consider a license bundle named "Bundle PRO" with the code "bunpro," which is associated with a key-based license having the serial number 1111-2222-3333-4444. This bundle encompasses two products: "Product One" (code: prodone) and "Product Two" (code: prodtwo).

To initiate the license activation for "Product One" within the bundle, the procedure involves employing the bundle license key, the code for "Product One," and the hardware ID of the relevant device. It's important to note that the bundle license functions as a mere placeholder, serving to manage the license key and LicenseUsers information.

{% code title="activate\_bundle.js" %}

```javascript
const axios = require('axios');
const data = JSON.stringify({
  "product": "prodone",
  "license_key": "1111-2222-3333-4444",
  "hardware_id": "test-hardware-id-1",
});

const config = {
  method: 'post',
  url: 'https://api.licensespring.com/api/v4/activate_license/',
  headers: { 
    '\'Content-Type\'': '\'application/json\'', 
    'Date': 'Thu, 28 Jan 2021 09:07:27 GMT', 
    'Authorization': 'algorithm="hmac-sha256",headers="date",signature="9Km8AoACsFfRf9+JW4gcnHMmvWoPaZIwlaZ3HeZxdgQ=",apikey="5225d654-f6e5-41f0-af90-4237a597134b"', 
    'Content-Type': 'application/json'
  },
  data : data
};

axios(config)
.then(function (response) {
  console.log(JSON.stringify(response.data));
})
.catch(function (error) {
  console.log(error);
});
```

{% endcode %}

### Working with Product Bundles with the Management API

There are two primary, product bundle-specific API calls:

* [**List Products in a Bundle**](https://docs.licensespring.com/management-api/product/list-products-in-a-bundle.md) shows all products in a bundle the requesting manager has access permissions to.
* [**List Bundles for a Product**](https://docs.licensespring.com/management-api/product/list-bundles-for-a-product.md) shows all bundles for a product the requesting manager has access permissions to.

### bundle\_code

{% hint style="warning" %}
When using user based bundle licensing, it can happen that the same license user has multiple licenses for the same product - one license being standalone, and another as a part of the bundle. To make sure that License API recognizes which license needs to be used, you need to send the **bundle\_code** param with every call to License API.
{% endhint %}

![Bundle code](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/JtE2SKhxK7oET5P0h4h5/4B3GLW6NrtNB87ddBrtwo_scr%2020240402%20kayu.png)


---

# 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.licensespring.com/product-configuration/product-bundles.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.
