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

# Settings

The settings page shows whether the core services required for bundles are set up and lets you choose how bundles display on your storefront.

## Setup Status

The setup section can show the status of:

* Storefront token
* Cart transform
* Discount
* Web pixel

These services are created automatically when the app is installed and authenticated.

If one of these shows **Failed**, contact support. Most merchants do not need to manually configure these services.

## Bundle Display

The **Bundle display** setting controls where customers see the bundle builder.

### Product Page

Recommended for most stores.

In this mode, the bundle builder appears on the bundle product page and replaces the normal product-page content.

Use this when:

* You want a simple launch.
* You want bundle links to behave like normal product links.
* You want customers to understand they are buying a Shopify product.

### Dedicated Page

In this mode, the bundle opens on a standalone bundle page.

Use this when:

* You want a more focused campaign page.
* You want to send traffic directly from ads or email.
* You do not want the normal product page layout around the bundle.

## Support

The settings page includes support access. Use **Chat now** when:

* A setup service shows failed.
* The storefront does not render the bundle.
* Checkout discounts are not applying.
* Analytics look incorrect.
* You need help choosing a display mode.

Typical response time is around 10 minutes during IST business hours, with a maximum wait of 1 business day.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.elitebundleapp.com/installation-and-requirements/settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.