Monitoring a store means watching more than whether it loads.

The six things worth watching

Store owners usually arrive at monitoring after an incident — a quiet Tuesday that turned out to be a broken payment gateway, or a bulk price edit that ran on the wrong collection. The list below is ordered by how much revenue each failure costs per hour it goes unnoticed, not by how easy it is to check.

• Orders — whether the store is still selling. A checkout that fails silently produces no error page and no support ticket until someone emails you.
• Prices — whether every product is priced the way you set it. A bulk edit, a CSV import, or a repricing app can change hundreds of variants in one action.
• Availability — whether the store answers, on the right domain, with a valid certificate. Includes the two dates nobody diarises: SSL expiry and domain registration expiry.
• Stock — whether the things people are trying to buy still exist. A sold-out bestseller is an ad budget burning against a dead landing page.
• Content and SEO — titles, descriptions, canonicals, structured data, broken links and missing images. Slow to hurt, slow to recover.
• Speed — how the store performs on a phone on mobile data, which is not how it performs on your laptop.

How often each check needs to run

Detection latency is the only number that matters. A check that runs once a day has an average detection delay of twelve hours; a check that runs every five minutes has an average delay of two and a half. The right cadence is the one where the cost of the delay is smaller than the cost of the check.

These are the intervals Cassian™ uses. They differ by plan because the underlying cost differs — an HTTP request is cheap, a full crawl with content analysis is not.

Detection is only half of it — the alert has to reach you

A monitoring tool that emails a dashboard you check on Mondays has not solved the problem. Alerts have to arrive where you already are, and they have to be specific enough to act on without opening anything.

Cassian™ sends to email on every plan. Telegram and webhooks — which auto-detect Slack and Discord URLs and format natively for each — are on Protector and above. Every channel has its own minimum severity, so the 3am pager can be reserved for the things that are actually worth 3am.

What to set up first

If you are starting from nothing, this is the order that catches the most revenue per hour of setup.

1. 1Connect the store, so order and catalog data is available. Read-only is enough — no theme edits, no code changes.
2. 2Turn on zero-order alerting. It is the single highest-value check and it runs on the free plan.
3. 3Set your alert channel and its severity floor, so critical alerts reach a phone and everything else reaches an inbox.
4. 4Add uptime and certificate monitoring before your next high-traffic day, not during it.
5. 5Run a full scan and fix the critical findings once. After that, monitoring only has to tell you what changed.