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

# Notifications & Alerts

> Choose which store events reach you by email, Discord and mobile push

You control which alerts you and your team receive for a store under **Store Settings → Notifications**. The page is a grid of store events, each with an **Email** switch and a **Discord** switch, plus mobile push on the native app.

<Note>
  These toggles affect **merchant and team alerts only**. Your customers' emails

  * receipts, delivery notices, subscription reminders - are not controlled here
    and always send.
</Note>

## What you can toggle

| Group              | Events                                                                      |
| ------------------ | --------------------------------------------------------------------------- |
| **Orders**         | Order Delivered, Order Pending, Order Undeliverable                         |
| **Tickets**        | Ticket Created, Ticket Response Added                                       |
| **Reviews**        | Review Added                                                                |
| **Inventory**      | Low Stock, Out Of Stock                                                     |
| **Disputes**       | Order Dispute, Dispute Created, Dispute Resolved, Dispute Evidence Required |
| **Payouts**        | Payout Completed, Payout Failed, Auto Payout Failed                         |
| **Payment Config** | Payment Method Misconfiguration, Chargeback Received                        |
| **Other**          | Configuration Success                                                       |

<Tip>
  If you turn on nothing else, turn on **Order Undeliverable** and **Out Of
  Stock**. Those two are the ones where a delay costs you a sale that has
  already been paid for.
</Tip>

## Discord alerts

To receive alerts in Discord, paste a Discord webhook URL under **Destinations** on the same tab. The badge switches from "Not connected" to "Connected", and the Discord switches stay disabled until a webhook is set ("Configure a Discord webhook below to enable").

Discord receives store-activity events only, delivered as embeds: orders, tickets, reviews, stock, disputes, payouts and payment-configuration events. Account, login, plan and customer-facing emails are never sent to Discord.

### If Discord alerts stop arriving

<Steps>
  <Step title="Check the webhook is still saved">
    **Store Settings → Notifications → Destinations**.
  </Step>

  <Step title="Check the event's Discord switch is on">
    Email and Discord are toggled independently per event.
  </Step>

  <Step title="Check the webhook still exists in Discord">
    Deleting a channel or webhook in Discord silently breaks delivery.
  </Step>

  <Step title="Wait a few minutes">
    Preference changes are cached, so allow a short delay before judging a
    change by the next event.
  </Step>
</Steps>

## Mobile push

On the native mobile app you can enable or re-register push notifications per device from the same Notifications settings.

## Who receives store alerts

Store alerts such as Order Delivered and Order Undeliverable go to team members who hold the relevant store permission. If a team member isn't receiving something they should, check their permissions before assuming the notification is broken. See [Teams & Permissions](/guides/teams-and-permissions).

## Emails that arrive regardless

Account-level email is not controlled by this page. These always send:

* Account verification and security alerts (new logins, password and email changes)
* Plan and billing lifecycle emails, and wallet balance notices
* Data-export notifications and team invitations
* Buyer Protection invoices and claim alerts

## Notifications vs webhooks

Notifications are for humans; [webhooks](/guides/webhooks) are for software. If you want an alert in a channel someone reads, use this page. If you want to sync orders into your own system, fire fulfilment, or drive automation, use webhooks - they are signed, logged, retried and resendable, none of which applies to a Discord message.

<Note>
  Discord notification destinations are configured here, not on the Webhooks
  page. The Webhooks page carries a banner saying exactly that.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Store Webhooks" icon="webhook" href="/guides/webhooks">
    Machine-readable order events for your own systems.
  </Card>

  <Card title="Managing Orders" icon="receipt" href="/guides/orders">
    What to do when an alert tells you something went wrong.
  </Card>
</CardGroup>