> 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/hooks-for-developers/public-hooks.md).
# Public Hooks
Below are the filters you may need to customise the look, feel or content of the Bundle Builder page in the Doko Bundle Builder plugin for WooCommerce.
**Actions :**
NA
**Filters :**
* ***doko\_display\_variations\_as\_many :*** \
This filter allows you to decide whether variations of products on the bundle page should be displayed as a single product or multiple products.
* ***doko\_skip\_product\_in\_shortcode\_loop :*** \
This filter allows you to decide whether a specific product in the bundle shouldn't be displayed.
* ***hs\_doko\_btn\_add\_to\_box\_link :*** \
This filter allows you to customise the "Add to Box" button displayed in the various bundle steps.
* ***doko\_get\_total\_price :*** \
This filter allows you to change the bundle total price and include custom fees after customers has added to the cart their products.
* ***doko\_add\_box\_contents :*** \
This filter allows you to add a custom product with a custom price to the bundle present in the WooCommerce cart and checkout.
* **doko\_cart\_contents\_element :** \
This filter allows you to include custom information before the bundle is added to the cart item object. Whether you want to add a custom product or another option to the basket, use this.
* ***doko\_js\_data\_boxpage :*** \
This filter allows you to add a custom variable or secret word to the bundle page. To use it, just get the value of your custom variable from ***doko\_object***.
---
# 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/hooks-for-developers/public-hooks.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.
