A monthly review should connect evidence with decisions. Keep the data summary focused enough to leave time for priorities, owners and follow-up.
Prepare the Data Before the Meeting
No one should be looking at a metric for the first time in a monthly review. Distribute a pre-read package at least 24 hours before the meeting with all the data already compiled and formatted. This allows attendees to arrive with questions and observations rather than spending meeting time on comprehension.
The Right Metrics for a Monthly E-commerce Review
Revenue vs target by channel. Gross margin vs target. Customer acquisition cost trend. Top 10 SKU performance. Inventory status and upcoming risk. Marketing spend and ROAS by channel. Return rate trend. Open issues from the prior month's review.
Leave Time for Decisions
If revenue missed target, spend two minutes on the data and thirty minutes on the diagnosis and action plan. What specifically caused the miss? What are we changing? Who owns the change? By when? The purpose of reviewing what happened is to inform what to do next.
Document Every Action Item
Every discussion that results in a decision should produce an action item: what will be done, who is responsible, and by when. The first agenda item of the next review is a status check on every action item from the previous one. If action items aren't being completed, you have a prioritization or accountability problem that needs to be addressed.
The fix: Add the action item log from your last review to the agenda of your next one as the first agenda item. If you don't have an action item log, start one this month.
Start with decisions, not slides
Build the agenda around the few questions leadership needs to answer: where performance changed, why it changed, which risks need action and what decisions are required before the next review.
Use one definition for each KPI
Document source, owner, calculation and reporting period. If teams calculate revenue, inventory or service metrics differently, the meeting will be spent debating numbers instead of actions.
Explain variance with evidence
Separate known drivers such as stockouts, promotions, assortment changes and timing from hypotheses that still need investigation. Do not force a narrative when the data is inconclusive.
End with owners and due dates
Every action should identify who owns it, what output is expected and when it will be reviewed. Carry open actions into the next meeting until they are resolved.
For dashboarding and management reporting, see e-commerce systems & reporting.
Use a standard pre-read
Send the KPI summary, major variances, risks and decision requests before the meeting. Attendees can spend meeting time resolving issues rather than reading slides for the first time.
Close the loop on prior actions
Start each review with open commitments from the last one. Mark completed, delayed or changed, and explain why. A business review loses credibility when action lists disappear between meetings.
Limit the meeting to material variances
Routine metrics that are on plan can stay in the pre-read. Use meeting time for decisions, risks and performance changes that require cross-functional action.
Record decisions separately from discussion notes
Keep a concise decision log with owner and due date. This makes follow-up easier than searching through a long meeting transcript.