Most operational problems aren’t sudden crises — they’re slow-moving trends that were visible in the data weeks before they became emergencies. A stockout that was building for 6 weeks. A 3PL SLA that’s been slipping for a month. A customer service backlog that doubled in two weeks. A weekly operations review exists to catch these trends before they become problems.
In our experience, the teams that run well are the ones that have a regular, structured cadence for reviewing what’s working and what isn’t — not just reacting to fires. This guide gives you a practical framework for a weekly ops review you can actually sustain.
Who Should Attend
Keep it small. The weekly ops review isn’t an all-hands — it’s a working session for the people responsible for operational execution. For most e-commerce and small business contexts:
- Founder/CEO (for companies under $5M where ops is still close to the top)
- Operations Manager or Head of Ops
- Inventory/Purchasing lead (if separate)
- Customer Service lead
- Finance lead (for cash and margin review, or async if not needed weekly)
Five people or fewer is ideal. This meeting should be 30–45 minutes, not 90.
The Agenda Structure
1. Metrics Review (10 minutes)
Review a pre-built dashboard or shared document. Each person reviews their numbers; anomalies get flagged. No deep discussion yet — that comes next.
2. Issues and Escalations (15 minutes)
What’s off track? What issues came up this week that need the group’s attention or decision? Each person has 2 minutes maximum. The goal is to surface issues, not solve them in the meeting — complex problems get parked for follow-up with the right people.
3. Priorities for the Coming Week (10 minutes)
What are the top 1–3 operational priorities for the next 7 days? Who owns each one? What does “done” look like?
4. Open Items and Decisions (5 minutes)
Anything that needs a decision or approval from the group that couldn’t be handled async. Keep this minimal.
The Metrics That Belong in a Weekly Ops Review
Resist the temptation to review 30 metrics. Weekly ops reviews work best with 8–12 key indicators, organized by function:
Fulfillment and Operations
- Orders shipped — total and by channel
- On-time ship rate — % of orders shipped within your committed SLA
- Fill rate — % of orders shipped complete (no partial shipments due to stockout)
- 3PL SLA compliance — if using a 3PL, are they hitting their committed ship times?
Inventory
- Out-of-stock SKUs — count of SKUs at zero or below reorder point
- Days of stock on hand — for top 10 SKUs by revenue
- Incoming POs — expected delivery dates and any at-risk shipments
Customer Service
- Ticket volume — total week-over-week; spikes indicate a fulfillment or product issue
- First response time — are you meeting your SLA?
- CSAT score — customer satisfaction from closed tickets
- Top ticket categories — what are customers most commonly contacting you about?
Finance (Monthly or as-needed)
- Cash on hand vs. prior week
- Outstanding payables and upcoming large expenses
How to Build the Dashboard
The metrics above should be pre-populated before the meeting — not pulled during it. Options:
- Shopify + a reporting tool (Looker Studio, Triple Whale) for fulfillment and orders
- Your IMS (Extensiv, Cin7) for inventory metrics
- Your help desk (Zoho Desk, Gorgias) for CS metrics
- A shared Google Sheet or Notion page where each function owner updates their numbers before the meeting
The simplest approach that works: a shared Google Sheet where each function lead fills in their 3–4 metrics on Monday morning, and the team reviews it together in the meeting. Don’t let the perfect dashboard block you from starting.
Common Failure Modes
- Turning it into a status meeting — if people are just reading out what they did last week, you’re wasting time. Focus on deviations and decisions.
- No agenda, no prep — metrics should be ready before the call. If people are pulling numbers in real time, the meeting will run long and lose focus.
- Not following up on action items — every issue raised should have an owner and a next step. Review open action items at the start of each meeting.
- Making it too long — 45 minutes maximum. If you need more time, break it into functional sub-meetings.
Frequently Asked Questions
What should be covered in a weekly operations meeting?
Metrics review (fulfillment KPIs, inventory, CS), issues and escalations, priorities for the coming week with named owners, and any decisions needing group input. 30–45 minutes with a pre-built dashboard reviewed in advance.
What KPIs should an e-commerce operations team track weekly?
Core weekly KPIs: on-time ship rate, fill rate, out-of-stock SKU count, days of stock on hand for top SKUs, CS ticket volume, first response time, and CSAT. Add 3PL SLA compliance if using a 3PL. Track 8–12 metrics total.
How long should a weekly operations review be?
30–45 minutes. If it consistently runs over, the agenda isn’t tight enough, too many people are attending, or issues are being solved in the meeting rather than flagged for follow-up.
How do I build a weekly operations dashboard?
Start simple: a shared Google Sheet where each function lead updates their 3–4 metrics before the meeting. Don’t let perfect dashboard design block you from starting — a manual spreadsheet updated consistently beats an automated dashboard that never gets built.
Build the Operating Cadence Your Business Needs
OpsStack helps growing businesses design their operational review cadences — weekly, monthly, and quarterly — so leadership spends less time in reactive mode and more time building. Get in touch to talk about your ops rhythm.
