Daily

Get alerted when orders drop off

If a day's orders fall far below the usual level, Slack tells you that evening.

Runs: Daily
Apps: Adobe Commerce
AI: Not needed
Access: sales read

Send this to your assistant

Create a ClickRuntime automation: every evening at 9pm, compare today's Adobe Commerce order count with the average of the last 4 weeks and message #ecommerce in Slack if it's 40% lower or more.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A Magento or Adobe Commerce store can lose most of its sales without anything looking broken. A checkout JavaScript error after a theme update, a payment gateway outage or a misconfigured shipping rule may keep customers from completing purchases, while the site itself loads fine. The owner finds out the next day, or when the monthly report is lower than expected, after hours or days of lost revenue.

Each day, the automation counts today's orders and compares the number with the typical count kept in its stored counters. If today's total is far below normal for the time it runs, it sends an alert so someone can check checkout, payment and shipping before more sales are lost.

It is aimed at stores with steady daily order volume, where a drop is a meaningful signal, and at teams that deploy changes to the site often.

What you get out of it

Checkout failures are found within hours
A silent break in checkout costs money every hour it lasts. An alert when orders are far below normal gives you a chance to test and fix it the same day.
Payment outages are noticed quickly
If a gateway or wallet option stops working, orders drop sharply. The alert prompts you to test it and contact the provider while the problem is still recent. A fast check of the payment methods often finds the failing one within minutes.
Deployments carry less risk
A team that releases updates knows that a drop in orders after a release is flagged. That makes it safer to ship changes and quicker to roll them back. It acts as a safety net after theme, extension or Magento version upgrades.
The baseline adapts to your store
Because comparison uses your own stored counters, a store with 20 orders a day and one with 500 each get alerts that fit their normal level, instead of a fixed number.
Fewer false alarms than a fixed limit
Weekends and quiet days are usually lower. Comparing against stored history avoids alerts on a regular Sunday dip while still catching a real collapse. That keeps the alert meaningful, so people take it seriously when it arrives.

How it works

What happens, step by step

Once a day, ClickRuntime counts today's orders in your Adobe Commerce store.
It compares that number with the average for the same weekday over the last four weeks.
If today is 40% or more below normal, a message goes to your #ecommerce Slack channel with both numbers and the drop, so you can check checkout and payments. On a normal day nothing is sent.

Before it runs live

Connect Adobe Commerce

What you get

RunsDaily

Get alerted when orders drop offtoday, 9:00Succeeded

Slack · #ecommerce📉 Only 41 orders today vs a 96 average for a Tuesday (-57%). Worth checking checkout and payments.

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Adobe Commerce steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

unusual_order_volume_alert.pyexample

from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify

BASE = "https://yourstore.com/rest/V1"
F = "searchCriteria[filter_groups][{}][filters][0][{}]"

def count(day, token):
    params = {F.format(0, "field"): "created_at", F.format(0, "value"): f"{day} 00:00:00",
              F.format(0, "condition_type"): "gteq",
              F.format(1, "field"): "created_at", F.format(1, "value"): f"{day} 23:59:59",
              F.format(1, "condition_type"): "lteq", "searchCriteria[pageSize]": 1}
    return http.get(f"{BASE}/orders", params=params,
                    headers={"Authorization": f"Bearer {token}"}).json()["total_count"]

@on_trigger
def run(event):
    token = credentials.secret("ADOBE_COMMERCE_TOKEN")
    today = date.today()
    now = count(today, token)
    average = sum(count(today - timedelta(weeks=w), token) for w in range(1, 5)) / 4
    if average and now <= average * 0.6:
        notify.slack(f"📉 Only {now} orders today vs a {average:.0f} average for a {today:%A} "
                     f"({now / average - 1:+.0%}). Worth checking checkout and payments.", channel="#ecommerce")
    return {"today": now, "average": average}

FAQ

Common questions

How does it know what is normal?

It keeps counters of past daily order counts in its state and compares today's count with them. The more days it has seen, the more representative the baseline becomes. After a couple of weeks the comparison reflects the true weekday and weekend pattern of your store.

What happens on a new store with no history?

Until it has a few days of counts, it can compare against a number you supply. Once it has collected enough history it can use that instead. The supplied number can be your rough average from the last month.

Does it alert if orders are unusually high?

The current steps look for low volume. A high-side alert for fraud or a flash sale can be added if you want to know about spikes as well as drops. Many stores want both directions, because a spike can mean a viral post or bot-driven fake orders.

What permissions does it need?

sales read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Daily