Daily
Get a morning Adobe Commerce sales report
Each morning you see yesterday's orders split by status and the revenue they brought in.
- Runs
- Daily
- Apps
- Adobe Commerce
- AI
- Not needed
- Access
- Magento_Sales::sales read
Send this to your assistant
Create a ClickRuntime automation: every morning at 7:30, email me yesterday's Adobe Commerce orders grouped by status (pending, processing, complete, canceled) with the day's total revenue.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Running a Magento or Adobe Commerce store means checking numbers that sit in several places: the order grid, the dashboard, a payment provider report. The owner who wants to know how yesterday went has to open the admin, filter orders by date, add up grand totals and count how many are pending, processing or canceled. Many skip it on busy days, and a sudden drop or a pile of orders stuck in pending is spotted a week later.
Every day, the automation searches orders by their created_at date for the previous day, groups them by status, sums the grand_total and sends the result in an email. The first thing you read is how many orders came in and how much they were worth.
It suits store owners, finance teams and anyone who reports sales to someone else.
What you get out of it
The first number of the day is trustworthy
Yesterday's orders and revenue arrive in your inbox the same way each morning. You start the day knowing how the store did, not guessing from a half-remembered dashboard. There is no need to open the admin to find out.
Orders stuck in pending are visible
A large number of orders sitting in pending or on hold usually points to a payment or fulfillment problem. Seeing that count each morning means it is fixed in a day, not discovered at month end.
Sales trends need no spreadsheet
A daily email builds a record you can scroll through to compare weekdays, spot the effect of a promotion and see whether a campaign lifted orders. Over weeks it shows what a good day looks like for your store, which makes bad days stand out.
Cancellations and refunds are tracked
Seeing canceled orders by status shows whether a spike in cancellations coincides with a stock issue, a payment gateway problem or a bad batch of leads. Linking the pattern to a known cause lets you act on it, not just notice it.
Finance gets figures without admin access
Sending the summary by email means accountants and partners see daily revenue without a login to the Magento admin, which keeps access tight. That is safer than sharing credentials, and it keeps the number in front of the people who use it.
How it works
What happens, step by step
Every morning, ClickRuntime collects yesterday's orders from your Adobe Commerce store.
It counts them by status: pending, processing, complete and canceled.
It adds up the revenue, leaving out canceled orders.
You get an email with the count for each status and the day's revenue.
Before it runs live
- Connect Adobe Commerce
What you get
Build your own
Need it to work differently?
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
from collections import Counter
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][{}]"
@on_trigger
def run(event):
day = date.today() - timedelta(days=1)
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]": 1000}
resp = http.get(f"{BASE}/orders", params=params,
headers={"Authorization": f"Bearer {credentials.secret('ADOBE_COMMERCE_TOKEN')}"})
resp.raise_for_status()
orders = resp.json()["items"]
by_status = Counter(o["status"] for o in orders)
revenue = sum(o["grand_total"] for o in orders if o["status"] != "canceled")
lines = [f"{s}: {by_status.get(s, 0)}" for s in ("pending", "processing", "complete", "canceled")]
notify.email_me(f"Orders {day}: {len(orders)}, revenue {revenue:,.2f}",
"\n".join(lines + ["", f"Revenue (excl. canceled): {revenue:,.2f}"]))
return {"orders": len(orders), "revenue": revenue}FAQ
Common questions
Does revenue include tax and shipping?
What time zone defines yesterday?
Does it include orders from all store views?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Catch Adobe Commerce orders that have stalled
A daily email names orders still pending or processing after two days, so none sit unnoticed.
See how it worksGet alerted when orders drop off
If a day's orders fall far below the usual level, Slack tells you that evening.
See how it worksGet a daily list of products running low
A morning email lists products with fewer than your chosen number in stock, lowest first.
See how it worksKeep exploring
Set up “Get a morning Adobe Commerce sales report” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.