> For the complete documentation index, see [llms.txt](https://docs.avada.io/joy-subscriptions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avada.io/joy-subscriptions/settings/email-notifications/store-owner-notifications.md).

# Store Owner Notifications

<figure><img src="/files/OxCmlAVpN90b2ohaHyAr" alt=""><figcaption></figcaption></figure>

### **Introduction**

Store owner notifications help merchants manage their subscriptions more effectively by providing timely updates about stock levels, payment issues, and charge confirmations. With Joy Subscription, you can easily monitor these key events and take necessary actions to maintain smooth operations.

### **Understanding the rule**

These notifications are sent to the store owner by Joy Subscription. Merchants can enable or disable the following notifications:

* **Low stock alert**: Sent when a product's stock falls below the predicted quantity needed for upcoming subscription orders.
* **Error charge processed**: Sent when an automatic subscription payment fails.
* **Charge confirmation**: Sent to confirm a successful payment charge for a customer.

When these conditions are met and notifications are enabled, Joy Subscription will automatically send an email to the merchant.

### **How to set up**

To configure store owner notifications:

1. Go to **Settings**.
2. Select **Email Notifications**.
3. Click on **Store Owner Notifications**.
4. Enable or disable the notifications as you prefer.

<figure><img src="/files/19roWzBW9gcjxKl1wRDv" alt=""><figcaption></figcaption></figure>

### **Overall**

Store owner notifications ensure that merchants are always updated on key events affecting their subscriptions, allowing them to take timely action and keep their operations running smoothly.


---

# 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.avada.io/joy-subscriptions/settings/email-notifications/store-owner-notifications.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.