> For the complete documentation index, see [llms.txt](https://docs.homescriptone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.homescriptone.com/wordpress-plugins/doko-bundle-builder-the-ultimate-dynamic-bundle-builder-for-woocommerce/configuration/how-to-display-variable-product-as-a-single-product-instead-of-separate-pro.md).
# How to display variable product as a single product instead of separate ? ( PRO )
By default, Doko Builder plugin separate variations from a variable product as individual product.
On some store, this is not something possible due to some variable product configurations.
In order to be able to see the variable product as a single product, their is a option into the settings page of the plugin.
To do so, go to **Bundles > Settings :**
bundle settings
It will redirect on a page where you can customise this option like you want :
If you define the option to Yes, your custo;ers will be able to see as a single product the variable product and their variations like this :
variable product displayed as a single product
If you define the setting as ***No,*** it will display variations as separate product and hide the main variable product.
---
# 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.homescriptone.com/wordpress-plugins/doko-bundle-builder-the-ultimate-dynamic-bundle-builder-for-woocommerce/configuration/how-to-display-variable-product-as-a-single-product-instead-of-separate-pro.md?ask=&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.
