> 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/faq/add-to-box-button-isnt-showing-on-my-woocommerce-store.md).

# Add to box button isn't showing on my WooCommerce store

When using a WooCommerce theme integrating a different add to cart button on your bundle builder page, you may encounter cases where the button is not showing or may need some additional steps in order to make it work.

This may confuse your customer when using your builder page and increase your page bounce rate.

In this case we implemented a new option in the bundle page allowing you to add a additional button so your customer won't get lost on your page.

<figure><img src="https://3823528938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3z3RATm3FlzqlvbHrX9%2Fuploads%2FAk32MV7q5c1ejL9uo52T%2Fimage.png?alt=media&amp;token=4f6c7497-c0f7-4615-b540-e5da01808425" alt=""><figcaption><p>enable/disable add to box button below the product card</p></figcaption></figure>


---

# 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/faq/add-to-box-button-isnt-showing-on-my-woocommerce-store.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.