> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sellauth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> Choose which shop events reach you, and whether they arrive by email, Discord, Telegram or webhook.

Notifications tell you when something happens on your shop without you watching the dashboard. Configure them under [**Notifications**](https://dash.sellauth.com/notifications), where each event can be routed to whichever channels you want.

## Channels

| Channel | What it needs |
| - | - |
| **Email** | Nothing, it uses your account address |
| **Discord** | A Discord webhook URL. The message and embed can be customized, see below |
| **Telegram** | A bot token and a chat ID |
| **Webhook** | An endpoint URL on your own server |

The webhook channel posts to your own server. For building against it, see [HTTP Notifications](/developers/http-notifications).

## Customizing Discord embeds

On the Business plan and higher, every Discord notification has a **Customize embed** link under its Discord toggle. It opens an editor with a live preview of the message as Discord will show it.

You can change:

* **Message**: text posted above the embed. Put a role mention here, for example `<@&123456789>`, so genuinely urgent events ping someone rather than sitting in a channel unread.
* **Title, description, color, footer and images**: every part of the embed, including an optional author line and a timestamp.
* **Fields**: drag to reorder, remove the ones you do not need, or add your own. Order notifications also have an **Order items** block whose fields repeat for every item in the order, and lists such as the item custom fields expand into one field per entry.
* **Buttons**: up to five link buttons rendered in a row under the embed, each with a label and a link. A button whose link is a variable that turns out empty is left out of the message.

Text can include variables such as `{{ invoice.price_formatted }}` or `{{ customer.email }}`. They are the same variables the email templates use; values meant for display carry a `_formatted` suffix, raw numbers do not. Click a variable in the side panel to insert it into the field you are editing. Variables of the items block, such as `{{ item.name }}`, only work inside that block. A field whose only content is an empty variable is left out of the message, which is how optional details like the customer's Discord account disappear when there is nothing to show.

**Send test** posts the current draft to your webhook with sample data, and **Reset to default** restores the standard layout. Discord allows at most 25 fields and 6000 characters per embed; anything over that is trimmed automatically.

## Events

Events cover the shop's activity, including:

* **Orders**: created, processed, moved to confirming
* **Stock**: a product or variant running out, and an order that could not be delivered because stock ran out
* **Support**: a ticket opened, a message added to one
* **Reviews**: feedback received or edited, and dispute outcomes
* **Subscriptions**: customer subscriptions starting, cancelling, expiring, and renewals failing or overdue
* **Money**: affiliate payout requests, reseller applications, withdrawal requests
* **Shop**: errors, plan changes, and platform announcements

## Choosing what to enable

Enabling every event on every channel produces enough noise that you stop reading any of it. A workable split:

**Act on immediately**, so route somewhere that interrupts you: out of stock after a sale, shop errors, failed subscription renewals. Each of these costs money or leaves a buyer waiting.

**Check regularly**, so email or a quiet Discord channel: new orders, tickets, reviews, payout requests.

**Rarely urgent**: plan changes and announcements.

Orders created is the event most sellers enable first and disable soon after. At any volume it becomes constant, and urgent events are easily missed inside it.

## Next steps

<CardGroup cols={2}>
  <Card title="HTTP notifications" icon="code" href="/developers/http-notifications">
    Receiving events on your own server.
  </Card>

  <Card title="Managing invoices" icon="receipt" href="/guides/invoices">
    Acting on what a notification tells you.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.