> 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/get-started/getting-started.md).

# Getting started

Install Elite Bundle Builder, set up theme integration, and launch your first bundle in your Shopify store.

Three things stand between a fresh install and a live bundle: the app, one app embed, and a bundle set to **Active**.

## 1. Install the app

Install [Elite Bundle Builder](https://apps.shopify.com/elite-bundle-builder) from the Shopify App Store and approve the requested permissions. The app needs them to create bundle products, render on the storefront, apply automatic discounts and record analytics. After installation the app opens inside your Shopify admin.

## 2. Enable the Elite Embed Core app embed

Every bundle renders through this one app embed. It also runs cart protection. Enable it once per theme.

{% stepper %}
{% step %}

### Open the theme editor

In Shopify, go to **Online Store → Themes** and click **Customize** on your live theme.
{% endstep %}

{% step %}

### Open App embeds

Click the **App embeds** icon in the left sidebar.
{% endstep %}

{% step %}

### Turn on Elite Embed Core

Toggle it on and click **Save**.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The embed is per theme. After you publish a new theme, enable it again on that theme or bundles will show a plain product page.
{% endhint %}

<details>

<summary>Optional: the Multi-Option Bundle app block</summary>

Multi-option bundles render just above the theme's Add to cart button by default. Add the **Multi-Option Bundle** app block only when you want the selector somewhere else on the product template. The quickest route is the **Add app block** step in the editor's **Publish** tab, which opens the theme editor with the block ready to place. Manually: **Customize → product template → Add block → Multi-Option Bundle → Save**.

</details>

## 3. Create and publish a bundle

{% stepper %}
{% step %}

### Create bundle

On the dashboard click **Create bundle**, choose a type, name it.
{% endstep %}

{% step %}

### Add products

Add steps (or options) and the products or collections in each.
{% endstep %}

{% step %}

### Save and preview

Keep the status **Unlisted** and open the direct link to test.
{% endstep %}

{% step %}

### Go live

Set the status to **Active**.
{% endstep %}
{% endstepper %}

The full walkthrough is in [Create your first bundle](/create-bundles/create-your-first-bundle.md).

## Bundle statuses

| Status   | What it means                 | Use it for                 |
| -------- | ----------------------------- | -------------------------- |
| Draft    | Hidden from shoppers          | Work in progress           |
| Unlisted | Reachable by direct link only | Testing, private campaigns |
| Active   | Public                        | Published bundles          |

## You are ready when

* [ ] The app dashboard opens and the setup guide shows your first bundle task
* [ ] **Elite Embed Core** is enabled on the live theme
* [ ] You know which products or collections go in the bundle


---

# 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/get-started/getting-started.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.