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

# View Product Bundles in Reporting

When a contract includes a product bundle, **Rillet** reports show the bundle as a single line, the same way they would for any other product, rather than breaking out its individual components. This keeps reports consistent no matter how many products a customer's contract bundles together.

### View a Bundle in Revenue Reports

Open the [**ARR/CARR Waterfall**](/EjmEP4KZ9BVp9j2ho4Mh/reporting/metrics/metric-reports/arr-carr-waterfall.md) report under **Reporting**. A contract with a bundle lists the bundle name as its own line beneath the customer and contract, the same way a single product would. The bundle's individual components never appear as separate rows.<br>

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FE1VVEzxC8I4s5h65axe9%2Fimage.png?alt=media&amp;token=7e1a54a8-aa0c-4a28-8d36-de0d32447e2e" alt=""><figcaption></figcaption></figure>

The **Revenue Waterfall** report follows the same pattern. A bundle's recognized revenue appears as one line, spread across the contract period based on how its value is allocated across components.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FBejbhVmvfaOzw4uJziGn%2Fimage.png?alt=media&amp;token=d32c2201-6bab-41c6-8772-021a92d018df" alt=""><figcaption></figcaption></figure>

### Find Bundles on Their Own List

Bundles do not appear on the **Products** tab. Products and bundles are separate lists under **Accounts Receivable > Products**, so open the **Bundles** tab to see bundle-specific columns such as Bundle Price, Component Price Total, and Discount vs Parts. If you have not created a bundle yet, see [**Create and Add a Product Bundle**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-receivable/products/create-and-add-a-product-bundle.md).

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FWLDwPKHvEBEXvZqxHu1n%2Fimage.png?alt=media&amp;token=04f15313-8598-4784-b75e-9b0143e5ab93" alt=""><figcaption></figcaption></figure>

{% hint style="info" %} <mark style="color:$info;">**Note:**</mark>

Bundle lines do not support discounts, so apply any discount to an individual product\
instead.
{% endhint %}

Use this list to review a bundle's own pricing details without opening each of its component products.

### See Also

To learn more about product bundles and reporting in **Rillet**, review these articles:

* [**Create and Add a Product Bundle**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-receivable/products/create-and-add-a-product-bundle.md)
* [**ARR/CARR Waterfall**](/EjmEP4KZ9BVp9j2ho4Mh/reporting/metrics/metric-reports/arr-carr-waterfall.md)


---

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

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

```
GET https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/reporting/view-product-bundles-in-reporting.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 `build a script that syncs our docs to a CMS` 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.
