> For the complete documentation index, see [llms.txt](https://orbit-b2b.gitbook.io/orbit-b2b-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbit-b2b.gitbook.io/orbit-b2b-docs/b2b-prices-app-embed/enable.md).

# Enable the embed

The embed is OFF by default after installation. Turn it on once in the theme editor and it works across your entire storefront.

## Steps

1. From your Shopify admin, open **Online Store → Themes → Customize** on the theme you want to add B2B pricing to.
2. In the theme editor, click the **App embeds** icon in the left sidebar (the plug / puzzle icon at the top).
3. Find **Orbit B2B Wholesale** in the list of available embeds. The toggle is OFF when you first open it.
4. Click the toggle to ON.
5. Click **Save** at the top right of the theme editor.

That's it. The next time a customer loads a product detail page, collection page, or search page, the embed runs:

* For B2B-eligible customers → retail prices are replaced with their effective B2B price (combined Wholesale + Volume)
* For non-eligible customers (guests, retail customers, customers in no group) → retail prices show unchanged

## What changes for you

| Before v1.0.4                                           | After enabling the embed       |
| ------------------------------------------------------- | ------------------------------ |
| Drag `Wholesale Price` block onto each product template | One toggle, applies everywhere |
| Drag `Card Prices` block onto each collection template  | Same toggle handles cards      |
| Two separate blocks to maintain                         | One embed                      |
| Theme code touched in editor                            | No theme code touched          |

## Verifying the embed loaded

1. Log into the storefront as a B2B customer (or any customer in one of your customer groups)
2. Open any product detail page
3. Open the browser DevTools console
4. Type:

```js
window.orb2bWholesale.data
```

You should see the JSON payload with `shop`, `customer`, `product`, `rules.wholesale`, `rules.volume`, `settings.priceDisplay`, etc. If the object is `undefined`, the embed isn't enabled or the theme editor save didn't apply.

## What if I had the old blocks?

After enabling the embed, you can safely remove the old `Wholesale Price` and `Card Prices` blocks from your theme sections — they're no longer needed and were deprecated in v1.0.4. Leaving them in is harmless (they're removed from the extension), but the duplicate code would just sit unused.

If you don't see the embed listed, the extension may still be propagating to Shopify's CDN. Wait a minute, refresh the theme editor, and try again.

## Next

* [Pick a display mode](/orbit-b2b-docs/b2b-prices-app-embed/display-mode.md) — strikethrough vs. replace
* [Theme support & custom selectors](/orbit-b2b-docs/b2b-prices-app-embed/theme-adapters.md) — what to do if your theme is exotic


---

# 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://orbit-b2b.gitbook.io/orbit-b2b-docs/b2b-prices-app-embed/enable.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.