Text version of this lessonExpand
Many ecommerce teams do not lack data. They lack one operating rhythm. Paid media brings ROAS, operations brings SKU notes, support brings refund reasons, and leadership brings revenue screenshots. The meeting becomes a round of explanations instead of a decision system. A weekly business review, or WBR, should put profit facts, path evidence, root causes, and next-week actions into one decision ledger.
Lesson output: one WBR decision ledger
After this lesson, you should be able to turn the weekly review into one checkable table: what changed, which evidence proves it, whether the issue is revenue, cost, page, product, support, or fulfillment, who owns the action, when it will be reviewed, and which metric will judge progress.
| Review layer | Question to answer | Output to keep |
|---|---|---|
| Profit facts | Did the business improve, or did refunds, discounts, ads, and fulfillment costs eat the gain? | Net sales, refunds, ad spend, margin, or profit proxy |
| Path evidence | Which channel, page, SKU, buyer group, or promotion changed the result? | Channel, page, SKU, AOV, CVR, and order-quality segments |
| Exception routing | Should ads, merchandising, site, support, fulfillment, or the business lead fix it? | Owner, due date, validation metric |
| Action closure | Did last week's action finish, and did it change the metric? | Continue, close, escalate, or add action |
Align profit facts before discussing growth
WBR breaks when everyone uses a different meaning of profit. Shopify sales, GA4 purchase events, ad-platform ROAS, and support refund reasons are not the same thing. Each source is useful, but it needs the right job in the review.
| Fact type | Plain meaning | How WBR uses it | Common misread |
|---|---|---|---|
| gross sales / net sales | Gross order value versus sales after discounts and returns. | Start with net sales and refund movement before channel debate. | A revenue screenshot hides refunds and cancellations. |
| cost per item | The product or variant unit cost behind many margin reads. | Check whether the cost table is current and SKU margin is reliable. | Supplier cost changes, but the review still uses old cost data. |
| GA4 purchase / refund | Behavior events that describe the user path. | Diagnose channels and pages, not final finance profit. | Missing events distort channel or page judgment. |
| Ad ROAS / CPA | Revenue return and cost per acquisition from the ad view. | Put it into the profit proxy with refunds, margin, and fulfillment cost. | Good ROAS is treated as permission to scale immediately. |
Shopify's profit reports need cost per item to make gross profit and margin more useful. Shopify also documents why sales reports can differ because of timing and reporting logic. So the WBR question is not only "how much revenue did we make?" It is "is this fact stable enough for a decision?"
Profit proxy can be rough, but the logic must stay stable
Some teams wait for perfect finance reconciliation before talking about profit. That makes the weekly review too slow. A better starting point is a stable profit proxy. It is not the final finance statement, but it must use the same calculation every week and be good enough to show trend and risk.
A practical minimum logic
The worst case is not low precision. It is changing the formula every week.
If ad spend is included this week but ignored next week, if refunds are read by order date this week and refund date next week, or if old costs mix with new costs, the trend is no longer trustworthy.
Write exceptions as reviewable actions, not meeting conclusions
"Watch refunds," "the page may have a problem," and "ads look unstable" are not WBR actions. A useful action has an owner, due date, validation metric, and next review state. Without those fields, next week's meeting repeats the same debate.
| Exception | Evidence | Good action | Next check |
|---|---|---|---|
| Meta spend rises while profit proxy falls | CAC moves from $18 to $26 and refund rate rises. | Ads owner pauses low-margin SKU scaling and recalculates the ad profit guardrail. | CAC, refund rate, SKU margin, and contribution profit return inside guardrail. |
| Google Shopping gets clicks but conversion is low | High-click SKUs have mismatched price, stock, and page promise. | Product data owner fixes feed and page facts before budget review. | Feed status, page promise, add-to-cart rate, and purchase rate. |
| Organic traffic grows but revenue stays flat | New clicks land on informational posts with weak internal links and buying CTAs. | SEO owner adds collection links and buying-guide CTAs. | Collection clicks, PDP entries, and assisted conversions. |
| Refunds concentrate around shipping timing | Tickets and refund reasons both point to delay expectations. | Support / fulfillment owner changes page promise and email timing. | Refund reasons, delay tickets, bad reviews, and pre-delivery questions. |
Use one fixed meeting order: outcome, path, cause, action
The fastest way to improve WBR quality is not adding more metrics. It is using the same order every week. Once the order is fixed, the team stops jumping between revenue, ROAS, support, and inventory without making decisions.
Separate daily, weekly, and monthly rhythm
Not every issue belongs in WBR. Daily incidents should be handled the same day, weekly review should set operating priorities, and monthly review should change structure. If every issue goes into one WBR, the meeting gets longer and decisions get weaker.
| Rhythm | Main focus | Purpose | Do not |
|---|---|---|---|
| Daily check | Spend anomaly, site issue, stock risk, shipping incident. | Stop incidents from spreading. | Change strategy because of one-day noise. |
| Weekly review | Channels, products, pages, profit, support, and fulfillment quality. | Set next-week priorities. | Turn the meeting into number reading. |
| Monthly review | Category role, pricing, channel role, budget structure, inventory strategy. | Make structural changes. | Use monthly review to replace weekly follow-through. |
Source boundary: events show paths, reports show orders, WBR creates actions
GA4 ecommerce measurement and GA4 recommended events can help define purchase and refund path events. Shopify reports are better for returning to order, sales, and cost logic. University of Washington research on adoption pathways also supports the operating idea that different entry paths can lead to different later behavior. WBR turns those signals into a short list of reviewable actions.
Final packet: leave only these 5 fields after the meeting
Next, do not make another pretty report. Bring this WBR decision ledger into next week's meeting, close last week's actions first, then add new ones.