New stores: 14 days of Protector freeFirst 25 stores.Uptime, daily scans, Slack and Telegram alerts. No card.See what’s included
Store Monitoring

The useful kind of sales alert tells you when sales stop.

There are two things people mean by real-time sales notifications, and only one of them is monitoring. The first pings you on every order — pleasant early on, unreadable at volume, and silent in exactly the situation you would want to hear about. The second watches the shape of your order flow and speaks up when it changes. This is how to set up both, and why the second is the one that protects revenue.

Free plan, no credit cardRead-only connectionAlerts to email, Telegram, Slack or Discord

Per-order pings versus anomaly alerts

A per-order notification fires when something good happens. An anomaly alert fires when something expected stops happening. The difference matters because silence is ambiguous: a quiet hour looks identical to a broken checkout, and by definition a per-order alert cannot fire to tell you it did not fire.

Per-order notificationAnomaly alert
Fires whenAn order is placedOrders stop, drop sharply, or decline steadily
Useful atLow volume, or for a specific segmentAny volume
At 500 orders a dayUnreadable, then mutedStill one alert, only when it matters
Catches a broken checkoutNo — it goes quiet, which looks like a quiet hourYes — that is the trigger
Needs a baselineNoYes, built from your own history

How to set up real-time sales notifications on Shopify

Three routes, from least to most robust. All three assume a connected store; none requires a theme change.

  1. Native Shopify notifications cover order confirmations to customers and can email staff on new orders. Fine at low volume; no baseline, no anomaly detection, and nothing fires when orders stop.
  2. A Shopify Flow automation or a webhook into Slack gives you per-order messages with filtering — by value, tag, SKU or country. Still per-order, so still silent on failure.
  3. An anomaly alert on top: connect a monitor that reads order counts on a schedule, builds a baseline from your own history, and alerts on zero-order periods, sharp drops and gradual declines. This is the one that fires during an incident.

What Cassian™ sends, and when

Cassian Sentinel™ ingests order counts hourly and runs an analysis pass on a cadence that depends on your plan. Three patterns raise an alert.

  • Zero orders in a period that historically has them — critical, on every plan including free.
  • A significant drop against expected volume for this hour and day — Analyst and above.
  • A gradual multi-hour decline that no single reading would show — Protector and above.
  • Recovery notices when order flow returns to normal, so an incident closes rather than trailing off.

Where alerts land

Email is on every plan. Telegram, Slack and Discord arrive on Protector — the webhook channel auto-detects Slack and Discord URLs and formats natively for each, with Block Kit on Slack and colour-coded embeds on Discord.

Each channel carries its own minimum severity. The practical setup is critical to your phone, everything else to email, so the channel that interrupts you stays worth being interrupted by.

What Cassian™ actually does

Specific checks, with the plan they run on.

Cassian Sentinel™ queries your platform’s order count API hourly and analyses it against a weighted historical baseline every 1 to 6 hours depending on plan.

Every plan. 3-hourly on Inspector, 6-hourly on Analyst, 2-hourly on Protector, hourly on Guardian and above.

A zero-order period raises a critical alert on every plan, including the free one.

Every plan.

Incidents open, update and resolve automatically, with a recovery notification when orders resume — so you are told the problem ended, not left wondering.

Every plan.

Alerts deliver to email on every plan, and to Telegram or a webhook — auto-formatted for Slack and Discord — on Protector and above, each with its own severity floor.

Email on every plan. Telegram, Slack and Discord on Protector and above.

FAQ

Common questions

How do I set up real-time sales notifications for my Shopify business?
Decide first whether you want to hear about every order or about problems. For per-order pings, Shopify’s built-in staff order notifications or a Shopify Flow automation into Slack will do it, with filtering by value, tag or country. For problem alerts — which is what protects revenue — you need something that reads order counts on a schedule, builds a baseline from your own history, and alerts when a period that should have orders has none. Cassian™ does the second: connect the store read-only, and zero-order alerts run from the first baseline on every plan including free.
Which services provide real-time alerts for Shopify store issues?
Three categories. Generic uptime monitors — UptimeRobot, Better Stack, Pingdom — alert when a URL stops responding, but cannot see orders, prices or stock. Shopify App Store monitoring apps such as Alertly, Observa and ShopStatus watch store-side signals like sessions, conversion and inventory. Store-aware platforms like Cassian™ connect through the platform’s admin API and alert on order flow, price changes, stock-outs, availability, links, speed and SEO from one place, delivering to email, Telegram, Slack or Discord.
Will I be notified on every single order?
Not by Cassian™, deliberately. Per-order pings stop being readable somewhere around a few dozen orders a day, and they cannot tell you when orders stop. If you want them, Shopify Flow or a per-order alert app is the right tool, and running one alongside anomaly alerting is a sensible combination.
How quickly does an alert arrive after orders stop?
On the next analysis pass: within an hour on Guardian and above, two hours on Protector, six on Analyst, three on the free Inspector plan. Order counts are ingested hourly on every plan; the cadence difference is how often the analysis runs over them.

Imagine if your store could tell you when something's wrong.

Free scan, results in minutes. Zero-order alerts on every plan, including the free one.