The AI Weekly Report Your Shopify Store Needs

A good weekly store report is 12 numbers, each shown against last week and against a target, plus a short list of alerts for anything that broke a threshold. That is the whole spec. Most stores either skip the report or drown in a 40-metric dashboard nobody opens.

This is the design for a report you will actually read in five minutes. It covers exactly which numbers earn a place, which comparisons make a number mean something, which alerts belong at the top, and how to read the finished thing fast. For where a standing report fits among the other things AI does for analytics, see how D2C brands use AI for analytics.

Why a Weekly Report, Not a Dashboard

A dashboard waits for you to open it. A report arrives. That single difference is why the report gets read and the dashboard does not.

The other difference is discipline. A dashboard tempts you to add every metric you can compute, and 40 numbers with no hierarchy is noise. A report forces a choice: what are the few numbers that would actually change a decision this week. Making that choice once, then having the same numbers arrive every Monday, is the entire value. Weekly is the right cadence for a store doing dozens to low-hundreds of orders a day. Daily is too noisy to act on. Monthly is too slow to catch a problem while it is cheap to fix.

The 12 Numbers That Earn a Place

Every number here answers a decision, not curiosity. Group them into acquisition, conversion, profit, and retention, so the report reads as a funnel from traffic to repeat revenue.

#	Metric	Group	Why it earns a place
1	Sessions	Acquisition	The top of the funnel. A revenue drop starts here or below.
2	Blended CAC	Acquisition	What a new customer actually costs across all channels.
3	Ad spend	Acquisition	The denominator behind CAC and ROAS. Watch it move.
4	Conversion rate	Conversion	Whether traffic is turning into orders.
5	Orders	Conversion	Volume, the plain count of what sold.
6	Average order value	Conversion	Basket size, the third lever behind every revenue change.
7	Total revenue	Profit	The headline, but never read alone.
8	Gross margin	Profit	What you keep before overhead. A margin slip hides inside flat revenue.
9	Net profit after ad spend	Profit	The number that decides if the week was worth it.
10	Return rate	Profit	Returns that quietly erase margin on strong products.
11	New vs returning revenue split	Retention	Whether growth is paid or earned.
12	Repeat purchase rate	Retention	The slow signal that your base is growing or leaking.

The two bolded numbers, AOV and net profit after ad spend, are the ones stores most often leave out and most need. Revenue plus AOV plus conversion together explain almost any weekly move: a revenue drop is always fewer sessions, a lower conversion rate, or a smaller basket, and this set lets you see which.

The Two Comparisons That Make a Number Mean Something

A number on its own is trivia. Revenue was 48,000 dollars tells you nothing. Every number on the report needs two comparisons to become a decision.

Week over week. The same number seven days ago, shown as a percent change. This catches movement. A 12 percent drop in conversion rate week over week is a flag before it is a trend.

Versus target. The number you decided this metric should hit. This catches drift that week-over-week misses. A metric can be flat week to week and still be quietly 20 percent under where it needs to be, and only the target comparison shows it.

Skip a third comparison unless you have a real reason. Year-over-year is useful for seasonality once you have the history, but for most small brands it adds a column and little signal. Two comparisons per number is the sweet spot between meaning and clutter.

The Alerts That Belong at the Top

The report has 12 numbers, but you should not have to scan all 12 to find the one that matters. That is the job of an alert section at the very top: a short list of only the numbers that crossed a threshold you set.

A useful alert is specific and pre-agreed. Not "revenue changed," but "gross margin fell below 50 percent" or "blended CAC rose above 35 dollars" or "return rate on any single product jumped more than 4 points." Each alert names the metric, the threshold, and the actual value, so you know what broke and by how much without opening anything else.

Good default alerts for a D2C store:

• Blended CAC rose above your target ceiling.
• Gross margin fell below your floor.
• Any discount code ran below break-even.
• Return rate on a single SKU jumped week over week.
• Conversion rate dropped more than 10 percent week over week.
• A fast-selling SKU is projected to stock out within its reorder lead time.

If the alert section is empty, the week was fine and you can stop reading. That is a feature, not a gap.

How to Read It in Five Minutes

The report is designed to be read top to bottom in one pass. Here is the pass.

1. Read the alerts first. If the section is empty, skim the 12 numbers for anything red and you are done. If it has entries, each names a metric and a threshold, so you already know where to look.
2. For each alert, check the two comparisons on that metric. Week over week tells you if it is sudden. Versus target tells you if it is drift. Sudden and off-target together is the urgent one.
3. Trace a revenue miss down the funnel. If revenue is down, the cause is fewer sessions, a lower conversion rate, or a smaller AOV. The report has all three, so read them in that order until one explains it.
4. Glance at margin and net profit, always. Revenue can be up while profit is down. Never close the report without reading number 9.
5. Note the retention trend, but do not act on one week. Read the monthly direction, not the weekly wobble.

Five minutes, once a week. The point is not to study the report. It is to catch the one thing that needs you and move on.

Turn the Spec Into a Standing Report

You can assemble this by hand every Monday, and most owners intend to and stop after three weeks. The version that lasts is the one that arrives on its own.

That is what Daymark's report generator builds: it connects your sources, computes the 12 numbers with consistent cross-source margin and CAC math, applies your comparisons and alert thresholds, and delivers the report on a schedule. The design in this post is the specification. The generator is one way to run it without babysitting a spreadsheet.

Frequently Asked Questions

What metrics should a weekly ecommerce report include?

Twelve is a good ceiling: sessions, blended CAC, and ad spend for acquisition; conversion rate, orders, and average order value for conversion; total revenue, gross margin, net profit after ad spend, and return rate for profit; and the new-versus-returning split plus repeat purchase rate for retention. That set explains almost any weekly move. More than a dozen numbers turns a report you read into a dashboard you ignore.

How often should I review my store's KPIs?

Weekly is right for most D2C stores doing dozens to low-hundreds of orders a day. Daily readings are too noisy to act on, since a single slow day says little. Monthly is too slow to catch a bad discount code or a margin slip while fixing it is still cheap. Keep slow-moving retention metrics on the weekly report for continuity, but only act on their monthly trend, not one week.

Should a weekly report compare to last week or to a target?

Both, on every number. Week over week catches sudden movement, like a conversion rate that dropped 12 percent in seven days. Versus target catches slow drift that week-to-week comparison misses, like a metric sitting flat but 20 percent under where it needs to be. Two comparisons per number is the sweet spot. A third, like year over year, usually adds a column and little signal for a small brand.

How do I read a weekly store report quickly?

Start with the alert section, which lists only metrics that crossed a threshold you set. If it is empty, the week was fine and you can stop. If it has entries, check the two comparisons on each flagged metric, then trace any revenue miss down the funnel through sessions, conversion rate, and average order value. Always glance at margin and net profit before closing. The whole pass takes about five minutes.

Why does my revenue look fine but my profit is falling?

Because revenue hides three things a weekly report should separate: gross margin, ad spend, and returns. Flat or rising revenue can sit on top of a margin that slipped a few points across the catalog, ad spend that crept up, or a return rate that quietly erased the margin on a strong product. That is why net profit after ad spend belongs on the report as its own number, read every single week.

Conclusion

A weekly report works when it is small enough to read and pointed enough to act on. Twelve numbers, two comparisons each, an alert section that is usually empty, and a five-minute pass. Build it once and have it arrive, rather than rebuilding a spreadsheet you will abandon.

For the numbers behind the report, browse the question library. To generate the report from your connected sources, see Daymark's report generator.