Multi-store7 min read
Shopify Order Alerts in Discord and Telegram, Done Safely
Get Shopify order alerts where your team already talks, without leaking customer names, emails or addresses into chat. What to send and what to leave out.
In this guide
Email notifications are where Shopify order alerts go to be ignored. Many teams already live in Discord or Telegram, so it makes sense to send order alerts there: big orders, failed payments, orders waiting too long to ship. Done carelessly, though, it also copies your customers’ personal data into a chat app where everyone in the channel, and every integration on it, can read it.
This guide covers which alerts are worth sending, which fields belong in them, how to connect Shopify to a chat channel, and how to keep the channel useful when order volume spikes.
What Shopify gives you out of the box
Shopify sends staff notifications by email. In Settings > Notifications > Staff notifications you can add recipients for new order emails, either a staff member or another email address, and pause a recipient without deleting them. The account owner receives new order emails by default (Shopify Help Center).
That works for a solo merchant. For a team it has two limits: every order produces the same email, so the important ones drown, and the inbox is personal, so nobody else can see that an alert was already handled. A shared chat channel solves both, as long as you control what goes into it.
What alerts are worth sending
An alert should lead to an action. If nobody would do anything after reading it, it does not belong in the channel.
| Alert | When it fires | What someone does |
|---|---|---|
| High-value order | Order total above a threshold you set | Checks the order before it ships |
| Payment problem | Payment pending or failed, order flagged for review | Contacts the customer or holds fulfillment |
| Cancellation | An order is cancelled | Stops the parcel if it is already packed |
| Shipping delay | Unfulfilled past your usual handling time | Finds out why and ships or updates the customer |
| Dispute or chargeback | A dispute is opened | Gathers evidence before the deadline |
| Key-customer tracking | Tracking update on a wholesale or VIP order | Keeps the account manager informed |
Avoid alerting on every order once volume grows. A channel that pings fifty times an hour gets muted, and then the important alert is missed too.
What to leave out of chat
Chat channels are not built to hold customer data. Members come and go, messages are rarely deleted, and bots and integrations can read the history. Keep alerts to what the team needs to act:
| Include | Leave out |
|---|---|
| Order number | Customer name |
| Order total and currency | Email address |
| Store name | Phone number |
| Status (paid, unfulfilled, cancelled) | Shipping or billing address |
| Tracking number and carrier | Payment details |
| Reason for the alert | Order notes written by the customer |
The order number is enough to open the order in Shopify admin, where access is controlled by staff permissions. Anyone who needs the customer’s details looks them up there.
Customer notes deserve a special mention. They look harmless, but customers often type phone numbers, gate codes or full addresses into them. Treat any free-text field written by a customer as personal data.
Why this matters more than it seems
- People leave. A former contractor still in the Discord server can scroll back through months of alerts.
- History is long. Chat apps keep messages until someone deletes them, and nobody does.
- Bots read everything. Every bot added to the server for another purpose may be able to read the channel.
- Screenshots travel. An alert shared in another chat to ask a question takes the customer’s data with it.
If the alert never contained the data, none of these matter.
How to connect Shopify to Discord or Telegram
There are three common routes. All of them end with a message posted to a channel, so the field rules above apply to each.
1. Shopify Flow with an HTTP request
Shopify Flow is a free Shopify app for automating workflows from triggers, conditions and actions. Its Order created trigger starts a workflow when an order is placed, and the Send HTTP request action can post to a web address, such as a Discord webhook. Note the plan limit: Shopify states the Send HTTP request action is only available on the Shopify Plus, Advanced and Grow plans (Send HTTP request).
Flow lets you store tokens as secrets, which are hidden in the Flow interface and redacted from run logs. Use that rather than pasting a bot token into the URL field.
2. An app
Several apps forward Shopify events to chat. Before installing one, check which fields it sends and whether you can turn fields off. An app that posts the full order, address included, by default is the problem this guide is about.
3. A small custom integration
A custom app that listens for order webhooks and posts a trimmed message gives you full control over the fields. It is also one more thing to maintain. Our guide on Shopify integrations that don’t break covers what to check before you build one.
Setting up a safe alert flow
- Create a dedicated channel for alerts, separate from general chat, with only the people who act on them.
- Use a fixed list of fields. Decide the fields once and reject anything outside the list, so a later change cannot quietly add personal data.
- Keep the bot’s token private. Treat a Discord webhook URL or Telegram bot token like a password; anyone with it can post as your bot. If one leaks, delete it and create a new one.
- Separate stores clearly. With several stores, put the store name in every alert, or use one channel per store.
- Set thresholds, not floods. Alert on orders above a value, delays past a time, or specific statuses, rather than every order.
- Name an owner per alert type. “Someone will see it” means nobody acts.
- Review alert rules quarterly. Remove the ones nobody acts on.
A good alert message is short and scannable:
[Store: EU shop] Unfulfilled 48h
Order #10482 · 214.00 EUR · paid
Reason: past handling time
Everything a person needs to decide, and nothing about who bought it.
Alerts across several stores
When you run more than one store, the same alert from two stores can look identical. Put the store name first in every message, and decide early whether you want one shared channel or one per store:
- One channel is easier to watch for a small team covering every store.
- One channel per store suits agencies, where each client’s team should see only that client’s orders. It also limits who sees what, which matters once you hire temporary help; see our guide to seasonal staff access across multiple Shopify stores.
For the wider setup, read how to manage multiple Shopify stores.
Preparing alerts for BFCM
Black Friday falls on November 27, 2026 and Cyber Monday on November 30. Order volume during that weekend can turn a quiet alert channel into noise. A few weeks before:
- Raise the high-value threshold for the weekend so it still flags the unusual orders.
- Keep payment problems, cancellations and disputes as they are; those still need a person.
- Check that every token and webhook still works by sending a test alert.
- Agree who watches the channel at which hours.
Our BFCM 2026 checklist for multiple Shopify stores covers the rest of the preparation, and bulk fulfilling and tagging orders helps once the delayed-order alerts start arriving.
Quick checklist
- Does every alert lead to a named action and owner?
- Is the field list fixed, with customer name, email, phone, address and notes left out?
- Are webhook URLs and bot tokens stored as secrets, not in shared documents?
- Does every alert name its store?
- Is the channel limited to people who act on alerts?
- Did you review the rules in the last three months?
FAQ
Can Shopify send order notifications to Discord or Telegram directly?
Shopify’s built-in staff notifications are sent by email. To reach Discord or Telegram you need a workflow, an app or a custom integration that posts to the chat. Shopify Flow’s Send HTTP request action can do it on the Plus, Advanced and Grow plans.
Is it safe to put customer names in order alerts?
It is safer not to. Chat history is long-lived and visible to every member and bot in the channel. The order number is enough to find the order in Shopify admin, where access is controlled.
How do I stop the alert channel from getting too noisy?
Alert on exceptions, not on every order: high values, payment problems, cancellations, delays and disputes. Use thresholds, give each alert type an owner and delete rules nobody acts on.
Should each store have its own alert channel?
If different people handle different stores, yes. If one small team covers everything, one channel with the store name at the start of every message is usually enough.