Profit Reporting and Weekly Business Review
Many teams do not lack data. They lack operating rhythm. Paid media looks at ad dashboards, support looks at tickets, operations looks at products, and leadership looks at revenue screenshots. Everyone has a valid angle, but nobody reviews the business on one table. A weekly business review matters because it puts profit, traffic, merchandising, support, and fulfillment back into one decision-making frame.
Start with the goal: this is not a reporting meeting, it is a decision meeting
If the meeting only repeats numbers, rotates explanations, and ends without actions, it becomes ritual very quickly. A real weekly business review should answer three questions: where the business improved, where it weakened, and which three to five actions matter most next week.
A good weekly review should produce
- A business judgment: is the business truly healthier, weaker, or only superficially stronger?
- Cause hypotheses: is the problem mostly traffic, page quality, product mix, support, fulfillment, or pricing?
- An action list: owner, due date, and validation logic.
The goal is not to review more metrics. It is to lock one stable scoreboard
Operating rhythm breaks when the board changes every week. One week the team looks at revenue, the next at ROAS, the next at sessions. It feels like analysis, but it is really topic drift. A strong weekly review starts with the same board in the same order every cycle.
| Section | What to review | Why it comes first | Typical owner |
|---|---|---|---|
| Outcome page | Revenue, net sales, refunds, ad spend, profit proxy | Confirms whether the business result actually improved | Business lead |
| Channel page | Meta, Google, Organic, Email, Direct | Shows where the business movement came from | Growth or media |
| Merchandising and page page | SKU performance, landing pages, collections, CVR, AOV | Separates traffic issues from conversion or product issues | Ops or CRO |
| Support and fulfillment page | Refunds, ticket themes, delivery failures, poor reviews | Prevents downstream problems from hiding inside top-line growth | Support or fulfillment |
| Action page | The top 3 to 5 actions only | Turns the meeting into execution instead of commentary | All owners |
The most important thing is not perfect profit accuracy. It is stable logic
Many teams think they need perfect finance-level reporting before they can review profit. A more realistic approach is to start with a stable profit proxy. As long as it is calculated the same way every week and reflects trend and risk well enough, it can support better decisions.
A minimum profit logic
The worst case is not low precision. It is changing the logic every week
If the profit proxy changes constantly, you cannot read trend and you cannot tell whether actions worked. Stable logic matters more than perfect logic.
Separate daily, weekly, and monthly rhythm
Many teams force every issue into the weekly review, then wonder why the meeting gets long but weak. A better rhythm is simple: daily checks for incidents, weekly reviews for operating decisions, and monthly reviews for structural change.
| Cadence | Main focus | Purpose | What not to do |
|---|---|---|---|
| Daily | Spend anomalies, site issues, stock risk, shipping incidents | Stop obvious problems from spreading | Do not make strategy shifts on one-day volatility |
| Weekly | Channels, products, pages, profit proxy, support and fulfillment quality | Set next-week priorities | Do not turn the review into a pure number-reading session |
| Monthly | Category roles, pricing structure, channel roles, stock strategy | Make larger structural changes | Do not use monthly meetings to replace weekly follow-through |
Use one fixed weekly business review agenda
The review gets stronger when everyone knows the order before the meeting starts. A fixed agenda protects the meeting from topic drift and keeps the team focused on outcome, diagnosis, and action.
A minimum WBR agenda
The 5 signal groups worth bringing into the review
Route each variance to one owner before the meeting ends
A meeting becomes operational only when each major variance is routed to the team that can actually change it. Do not let “everyone will watch this” replace ownership.
| Variance type | Typical signal | Primary owner | Expected next step |
|---|---|---|---|
| Traffic variance | Sessions, CAC, MER, branded share, new-customer mix | Growth or media | Change channel pacing, campaign structure, or audience control |
| Conversion variance | Landing-page CVR, checkout drop-off, PDP add-to-cart rate | CRO or site owner | Fix page friction, messaging, or technical blockers |
| Merchandising variance | SKU mix, margin pressure, stockouts, weak AOV | Merchandising or ops | Change priority SKUs, pricing, bundles, or stock posture |
| Service variance | Refunds, delayed shipping, support load, poor reviews | Support or fulfillment | Adjust promise, staffing, SLA, or exception process |
High-quality weekly reviews turn conclusions into owned actions
The best weekly reviews are disciplined and selective. They do not try to explain every detail. They look at the outcome, identify the few questions that matter most, and convert those questions into owned actions that can be validated next week.
A steadier action model
Track follow-through on one action sheet
The weekly review should end with one short follow-through sheet, not a vague promise to “look into it.” This keeps the meeting connected to execution.
Minimum follow-through fields
- Problem statement
- Owner
- Due date
- Validation metric
- Status at next review
Community field notes
The most common weekly-review failure modes
- Many teams run a number-reading meeting where everyone knows the metrics but nobody knows the next move.
- Another common pattern is reviewing revenue and ad efficiency only while hiding refunds, tickets, and fulfillment drag.
- Mature teams stick to one board, one logic, and a short action list instead of changing the topic every week.