> For the complete documentation index, see [llms.txt](https://docs.shop-studio.io/shopware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shop-studio.io/shopware/extensions/back-in-stock-notification-cloud/setup.md).

# Setup

To enable the notifications, you have to go to `Extensions > My Extensions > Apps` in the admin. and then at the app "Back in stock notification" right click on `... > Configuration` on the right.

Now you are in the settings for the app. You now have to perform the following two steps:

* First, you have to activate the app for your sales channels via the checkbox `Activate`.
* Choose how emails should be sent — see [Email delivery](/shopware/extensions/back-in-stock-notification-cloud/email-template.md). The recommended path uses Shopware's own mailer and lets you edit the email template in the admin. No SMTP credentials are required.

Finally, you need to press the `Save` button. That was all!

![](/files/-MhUxflpQrm1BOivIKPn)

{% hint style="warning" %}
**Attention**

The entry of the email addresses in the product detail pages is only visible if the associated product is not available. Usually this means that the `Stock` is set to `0` and the `Clearance sale` is set to `on`. However, this can differ slightly per store, as other extensions can also have an influence on the availability.
{% endhint %}

{% hint style="info" %}
**Tip**

Emails to customers are only sent when a product that was previously unavailable (e.g. due to lack of stock), now becomes available again. It is exactly at this transition that the delivery happens.
{% endhint %}

## Notification base URL (optional)

By default, the product links inside the back-in-stock emails point to the sales channel domain that your shop selects automatically. If you want those links to use a specific domain instead, open the `Notification` card in the app configuration and enter it in the `Notification base URL` field.

When a value is set, this base URL is used for the product links instead of the automatically selected domain. Leave the field empty to keep the automatic selection. Pick the protocol via the `https://` / `http://` selector next to the field and enter only the domain (for example `www.example.com`).

![](/files/pxh1svSSrrt4j5hBa9dN)

{% hint style="info" %}
**Availability**

The `Notification base URL` field is available from Shopware 6.6.
{% endhint %}

{% hint style="info" %}
**Is your shop behind a firewall or Cloudflare?**

This app reaches your shop through Shopware's API from our servers. Firewalls or services like Cloudflare can block this — especially in busy shops with many changes per day. To make sure updates always get through, allowlist our IP addresses:

```
74.220.51.43
74.220.51.44
74.220.51.45
```

More details under [Common sources of errors](/shopware/extensions/back-in-stock-notification-cloud/common-sources-of-errors.md).
{% endhint %}


---

# 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.shop-studio.io/shopware/extensions/back-in-stock-notification-cloud/setup.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.