Weekly Business Review and Variance Routing

Plain terms: WBR, variance, CVR, PDP, and acceptance check

WBR means weekly business review. It is not everyone reading numbers; it routes important operating variances to a responsible lead and leaves checkable action.

Variance means a metric or business signal moved away from expectation. Revenue up while contribution profit falls is not "good performance"; it is a profit variance that needs routing.

Gross margin is usually revenue minus product cost, often visible in Shopify profit reports or product finance tables. It helps a WBR read price, discount, and product-cost pressure, but it still excludes ads, payment fees, fulfillment, refunds, and support credits. Do not treat it as contribution profit by itself.

CVR means conversion rate, such as visit-to-purchase or visit-to-add-to-cart. A CVR drop is not always a page problem; it can come from traffic, price, inventory, shipping promise, or offer change.

PDP means product detail page. Users read price, images, specs, reviews, FAQ, shipping, and return promise there. When refunds or support tickets cluster, PDP often needs review together with product and support.

Acceptance check means the evidence used next week to judge whether the action worked. It should be a reviewable metric, screenshot, order sample, or ticket theme, not "optimized."

Primary lead means one role or person accountable for the result. There can be several collaborators, but only one primary lead. Otherwise next week everyone assumes someone else moved the work forward.

Escalation rule defines who can raise an unresolved or high-impact variance to the business lead. Without an escalation rule, the same variance can be discussed for many weeks without a real decision.

Why many WBRs become reporting meetings

Weekly meetings usually fail not because the team lacks data, but because the data is not converted into decisions. Ads brings ROAS. The site team brings CVR. Operations brings inventory. Support brings refunds. Finance brings margin. Each number can be true, but without one variance routing table, the meeting ends with many observations and no operating action.

A useful WBR closes last week before opening this week. The order matters. If last week’s action is not accepted, adding more actions only stacks the problem. For example, if last week’s action was to fix PDP FAQ, and this week the only evidence is a page screenshot with no mobile add-to-cart, checkout start, or refund-reason review, the action should not close. It also should not be rewritten as an ad creative problem.

A WBR also should not try to discuss every possible issue. A 60-minute meeting with twelve charts will not produce twelve strong actions. It usually produces twelve vague impressions. This lesson keeps three to five key variances each week: variances that affect profit, cash, inventory, customer experience, or budget movement.

Route first: do not let the wrong team fix the wrong problem

If margin fell because discount depth was too high, the media team should not rewrite creative first. If revenue fell because of stockout, CRO should not redesign the page first. WBR reduces this wrong-fix pattern.

Previous Action Closure Gate: close old actions before adding new ones

Many WBRs fail not because the team misses variances, but because last week's action is not accepted before new actions are added. Start each WBR with four questions: does last week's action have evidence, did it pass acceptance, should it continue, escalate, roll back, or gather proof?

Evidence intake: each system proves only part of the story

The easiest WBR mistake is treating one metric from one system as the full operating truth. First ask what each system can prove.

• Shopify profit and payment records can verify orders, refunds, payment deductions, item transactions, and profit-report definitions, but cost fields can be incomplete.
• GA4 ecommerce events can verify purchase, refund, item, coupon, discount, and onsite path, but missing event fields first prove a tracking issue.
• Google / Meta Ads can show CPA, ROAS, conversion value, creative, and product-group movement, but ad revenue is not contribution profit.
• Klaviyo can show email/SMS flow, attributed revenue inside the window, unsubscribes, complaints, and segment performance, but attributed revenue is not net profit.
• Support, reviews, and return reasons can show whether page promise, product quality, delivery experience, and support pressure cluster.
• Inventory and fulfillment records can show whether stock coverage, stockouts, delay, replenishment lead time, and parcel cost limit growth.

The order of evidence also matters. Confirm order and profit facts first, then read channel and onsite path, then check support, inventory, and fulfillment limits. Otherwise the team may use ad-platform revenue to explain a profit problem, a page screenshot to explain refunds, or total revenue to hide SKU mix and discount issues.

20oz tumbler weekly review drill

This week a 20oz tumbler has higher revenue but lower contribution profit. The ads team says creative performs well and wants more budget; finance sees free-shipping subsidy rising; support sees more size and lid questions. A good WBR does not start by raising budget. It writes one variance: revenue up but contribution profit down. Evidence: discount share, shipping subsidy, refund reasons, and support tickets. Primary route: operations / finance. This-week action: recalculate offer guardrail. Next-week acceptance: contribution profit returns to threshold and refund/ticket themes do not worsen.

If contribution profit recovers next week, close the action and restore budget slowly. If only the page changed but behavior evidence is missing, continue observation. If the same SKU remains open for two weeks, escalate to the business lead. If discount makes platform ROAS look better but profit worse, roll back the discount action.

30-minute WBR decision ledger practice

This is not meeting notes. It turns the WBR into a ledger that can be reviewed next week. You can use a spreadsheet, Notion, Google Sheet, or a project tool. The format does not matter. The fields do.

A strong row sounds like this: variance is revenue up but contribution profit down; evidence is discount share, free-shipping subsidy, SKU mix, and refund reasons; first route is operations / finance; this-week action is to recalculate the offer guardrail and pause low-margin SKU scaling; next-week acceptance is contribution profit back to threshold, refund themes not worse, and inventory coverage not below replenishment lead time; if open for two weeks, escalate to the business lead.

A weak row sounds like this: keep optimizing ads, page, and inventory, everyone watches it. It has no variance definition, no primary lead, no action object, and no acceptance check. Next week the team can only argue about it again.

60-minute WBR meeting script

First 10 minutes: close last week’s actions only. Decide close, continue, escalate, roll back, or gather evidence. Do not debate new solutions yet.

Minutes 10 to 25: select this week’s three to five key variances. Priority comes from profit, cash, inventory, customer experience, and budget impact. Any fluctuation without evidence goes into the evidence-needed list.

Minutes 25 to 45: route each variance. Decide whether it is a price, ads, page, product, inventory, fulfillment, support, or definition issue, then assign one primary lead. Do not let every team present a full report in this block.

Minutes 45 to 55: write this-week action and next-week acceptance. Every action needs an object, timing, responsible lead, and evidence. Evidence can be contribution profit, CPA, add-to-cart, checkout start, refund reason, ticket theme, stock coverage, or payment record.

Final 5 minutes: confirm escalation rules. Variances that affect budget, inventory, or customer experience and stay open for two weeks must escalate. Next week starts by closing old actions, not restarting the same discussion.

Common mistakes and the fix

Mistake 1: turning WBR into report reading. Fix it by limiting the meeting to three to five key variances and moving the rest into an appendix.

Mistake 2: routing the variance to the loudest team. Fix it by reading first evidence before assigning the lead. If profit fell, start with discount, shipping subsidy, refunds, and SKU mix instead of asking ads to rewrite creative.

Mistake 3: actions without acceptance checks. Fix it by writing the evidence next week will use. Page changed is not acceptance. Mobile add-to-cart, checkout start, refund reasons, and ticket themes are acceptance.

Mistake 4: unresolved variances never escalate. Fix it by escalating anything open for two weeks to the business lead. Do not keep writing cross-team collaboration in progress.

Public source boundary

This lesson uses official sources only as system boundaries: Shopify profit reports, Shopify payments reports, GA4 ecommerce events, Google Ads conversion value rules, and Klaviyo message attribution. They help you understand what each system records and misses. Closing a WBR variance still depends on your own order, cost, channel, inventory, support, and action evidence.

• Shopify profit reports
• Shopify payments reports
• GA4 ecommerce events
• Google Ads conversion value rules
• Klaviyo message attribution

Closeout: WBR copyable lesson notes

Before the next weekly review, leave one clean version: current pressure, first evidence, variance, evidence, first route, single primary responsible lead, this-week action, blocked move, next-week acceptance, previous-action status, review window, next route, escalation rule, and most likely counter-signal.