Daily
Get yesterday's BigCommerce revenue by email
A morning email gives yesterday's order count and total revenue.
- Runs
- Daily
- Apps
- BigCommerce
- AI
- Not needed
- Access
- Orders read-only
Send this to your assistant
Create a ClickRuntime automation: every morning at 7am, email me how many BigCommerce orders came in yesterday and the total revenue.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
The owner of an online store on BigCommerce often learns how yesterday went by logging into the admin, opening orders and adding up totals in a head or on a calculator. On busy days it is skipped, so a slow Tuesday or a spike after a mailing goes unnoticed. When a supplier or a partner asks about recent sales, the answer is a rough memory rather than a number from the books.
Each day, ClickRuntime lists the orders created between the start and the end of yesterday, adds up their totals and emails you the revenue and the number of orders. You start the day with a clear idea of how the store performed without opening the admin.
It is intended for store owners and small ecommerce teams who want a daily pulse without building a dashboard.
What you get out of it
Slow days are noticed quickly
A day with half the usual revenue is a reason to check the site, the ads and the stock. Finding out the next morning is far better than at month end.
Campaign results appear overnight
After an email or an ad goes out, the next morning's number shows whether it worked. You learn what drives sales while the details of the campaign are fresh. You learn what really drives sales while the details of the campaign are still fresh.
A running record exists in your inbox
Daily emails create a history of sales that you can search and compare. When someone asks about last month, you have actual figures. When someone asks about last month, you have the actual figures from your own inbox.
Decisions rest on facts
Whether to reorder stock or increase ad spend depends on how sales are really going. A daily number supports those choices better than a general feeling. Reorder and ad spend choices rely on how sales really go, not on a general feeling.
No dashboard to build or maintain
The summary uses the order data BigCommerce already holds. You get a useful daily number without wiring up an analytics tool. You get a useful number every day without wiring up any analytics tool.
How it works
What happens, step by step
Every morning, ClickRuntime collects the orders placed in your BigCommerce store yesterday.
It counts them and adds up the revenue.
You get a one-line email with yesterday's order count and total sales.
Before it runs live
- Connect BigCommerce
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 BigCommerce steps into one automation
Under the hood
The code that runs this automation
from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify
API = "https://api.bigcommerce.com/stores/your-store-hash/v2"
@on_trigger
def run(event):
headers = {"X-Auth-Token": credentials.secret("BIGCOMMERCE_TOKEN"), "Accept": "application/json"}
day = date.today() - timedelta(days=1)
orders, page = [], 1
while True:
resp = http.get(f"{API}/orders", headers=headers, params={
"min_date_created": f"{day}T00:00:00", "max_date_created": f"{day}T23:59:59",
"limit": 250, "page": page})
batch = resp.json() if resp.status_code == 200 else [] # 204 when there are none
orders += [o for o in batch if o["status_id"] not in (0, 5)] # skip incomplete and cancelled
if len(batch) < 250:
break
page += 1
revenue = sum(float(o["total_inc_tax"]) for o in orders)
notify.email_me(f"BigCommerce {day}: {len(orders)} orders, ${revenue:,.2f}",
f"Orders: {len(orders)}\nRevenue: ${revenue:,.2f}")
return {"orders": len(orders), "revenue": revenue}FAQ
Common questions
Does revenue include refunds and cancelled orders?
Which timezone defines yesterday?
Can the email show more than the total?
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
Get warned before BigCommerce products sell out
Slack tells you which SKUs have fallen under their low-stock level, once per item.
See how it worksGet a daily list of new BigCommerce customers
Each evening you see who created an account that day, with their email and customer group.
See how it worksPost each BigCommerce order to Slack
Seconds after checkout, Slack shows the order number, customer and total.
See how it worksKeep exploring
Set up “Get yesterday's BigCommerce revenue by email” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.