> For the complete documentation index, see [llms.txt](https://flicky.gitbook.io/flicky-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flicky.gitbook.io/flicky-docs/user-guide/getting-started.md).

# Install and Enable Flicky On Your Store

## 1. Install the app

1. Open **Flicky: B2B Wholesale Pricing** from the Shopify App Store and click **Install**.
2. Shopify shows a permissions screen listing the data the app needs. Review it and click **Install** to continue.
3. After installation, the app opens inside **Shopify Admin → Apps → Flicky**.

## 2. Complete the setup guide

The first time you open the app, a short **guided setup** welcomes you and highlights the core tools — custom pricing, volume discounts, and quick ordering. Click **Get started** to walk through it, or **Skip** to jump straight in. You can revisit or dismiss it at any time.

![Onboarding screen](/files/2dyh2hLE0XTkHmW5C5KC)

After it finishes, the **Dashboard** becomes your home base. Each feature has its own card with a live count of active rules, so you can see at a glance what's running.

![Flicky dashboard](/files/4OBYSCT2CnP3pG6UFe76)

From the Dashboard you can jump into any feature, or use the left‑hand navigation menu.

## 3. Enable the storefront widget

Flicky displays pricing on your storefront through a **theme app embed**. You only need to enable it once.

1. In Shopify Admin, go to **Online Store → Themes**.
2. On your live theme, click **Customize**.
3. In the theme editor, open **App embeds** (the puzzle‑piece icon in the left sidebar).
4. Find **Flicky B2B** in the list and toggle it **on**.
5. Click **Save**.

> **Shortcut:** you can jump straight to the App embeds panel by opening `https://admin.shopify.com/store/<your-store-handle>/themes/current/editor?context=apps` in your browser — replace `<your-store-handle>` with your store's handle (the part before `.myshopify.com`), then toggle **Flicky B2B** on.

> **Why this matters:** discounts and price rules are calculated by Shopify and the app, but the on‑page messaging (discount tables, custom prices, variant tables) only appears when the app embed is enabled.

> **The embed is per‑theme.** If you publish a new theme — or duplicate your current one — enable the **Flicky B2B** app embed on that theme too, or the storefront messaging won't appear.

## 4. What's next?

You're ready to explore Flicky. Pick the feature that fits your goal:

* Reward larger orders with tiered discounts → [Volume Discounts](/flicky-docs/user-guide/volume-discounts.md)
* Give specific customers their own prices → [Pricing Rules](/flicky-docs/user-guide/pricing.md)
* Let buyers order many variants at once → [Variant Table](/flicky-docs/user-guide/variant-table.md)

## Troubleshooting

**The app embed isn't in the theme editor list.** Make sure the app finished installing, then refresh the theme editor. App embeds only appear after installation completes.

**I enabled the embed but customers don't see anything.** Confirm you have at least one **active** rule, that the rule's schedule (start/end dates) includes today, and that the product or customer matches the rule's targeting and eligibility settings.

**Do I need to re‑enable the embed after changing themes?** Yes. The app embed is enabled per theme. If you publish a new theme, enable the **Flicky B2B** app embed on that theme too.


---

# 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://flicky.gitbook.io/flicky-docs/user-guide/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.