The Ecommerce Team KPI Dashboard: What to Track Daily, Weekly, and Monthly
Which KPIs an ecommerce operations team should track daily, weekly, and monthly across stores — formulas, owners, healthy ranges, and review cadence.
When you run one store, you can feel your way through the numbers. When you run five, ten, or thirty, feel stops working — a store can quietly bleed refunds or sit on unfulfilled orders for a week before anyone notices. An ecommerce team KPI dashboard fixes this: a small, shared set of numbers, each with a formula, an owner, and a review cadence. This guide covers exactly which KPIs to track daily, weekly, and monthly across a store portfolio, who should own each one, and when a spreadsheet is enough versus when you need a realtime dashboard.
Why Multi-Store Teams Need One KPI Set, Not Ten Analytics Tabs
Shopify's built-in Analytics dashboard is genuinely good for a single store — it updates within about a minute and covers sales, sessions, and fulfillment metrics. The problem is that it's per store. Unless you're on Shopify Plus with organization analytics, there is no native view that says "here's revenue, open disputes, and stuck shipments across all 12 stores this morning."
What happens without a shared KPI set:
- Every store manager reports their own numbers, calculated their own way. One counts refund rate by order count, another by dollar amount. The numbers aren't comparable, so the weekly meeting turns into an argument about definitions instead of decisions.
- Problems surface late. A dispute rate creeping toward card-network thresholds is invisible until the warning email arrives. A fulfillment backlog on store #7 only shows up when customers start emailing.
- Nobody owns anything. If "someone" watches refunds, no one does.
The fix is not more data. It's fewer numbers, defined once, assigned to named people, and reviewed on a fixed rhythm. Teams that already run all their Shopify stores from one dashboard have a head start, because the raw data is consolidated — but the KPI discipline matters even if you start in a spreadsheet.
The Core KPI Table
Here is a working set for a multi-store operations team. Formulas are exact; the "healthy range" column is a rule of thumb from operating practice, not an industry benchmark — your niche, price point, and shipping lanes will move these, so treat them as starting alarm thresholds and recalibrate against your own trailing 90-day baseline.
| KPI | Formula | Cadence | Rule-of-thumb range | Owner |
|---|---|---|---|---|
| Revenue per store | Gross sales − discounts − returns, per store per day | Daily | Within ±25% of trailing 7-day average | Ops manager |
| Fulfillment latency | Avg. hours from order paid → fulfillment created | Daily | Under 24–48h; investigate anything over 72h | Fulfillment lead |
| Orders unfulfilled > 48h | Count of paid, unfulfilled orders older than 48h | Daily | Trending toward zero each morning | Fulfillment lead |
| Stuck shipments | Trackings with no new carrier scan in 7 days (domestic) / 12–14 days (international) | Daily | < 2–3% of in-transit shipments | Logistics/ops |
| MER (blended) per store | Total revenue ÷ total ad spend, per store | Daily | Set per store vs. margin; alarm on 3-day decline | Media buyer |
| Support first response time | Avg. time from ticket created → first human reply | Daily | Under 24h for email; faster during disputes season | Support lead |
| Refund rate | Refunded amount ÷ gross sales (trailing 30 days) | Weekly | Watch the trend; any week-over-week jump > 30% gets a root cause | Ops manager |
| Dispute rate | Disputes ÷ transaction count (trailing month) | Weekly | Stay far below network thresholds (see below) | Ops manager / finance |
| SLA attainment | % of tickets answered within target ÷ all tickets | Weekly | ≥ 90% of your own stated target | Support lead |
| Dispute win rate | Disputes won ÷ disputes responded to | Monthly | Improving quarter over quarter | Ops manager |
| Net margin per store | (Revenue − COGS − shipping − fees − ad spend − refunds) ÷ revenue | Monthly | Positive and stable; rank stores by it | Finance |
| Payout reconciliation | Payouts matched to bank deposits ÷ total payouts | Monthly | 100%, no exceptions | Finance |
A few of these deserve unpacking.
Fulfillment latency and stuck shipments
Fulfillment latency is your earliest leading indicator: refunds, disputes, and "where is my order?" tickets all start as slow fulfillment. Measure it from payment to fulfillment created, not to delivery — you control the first interval directly.
Stuck shipments are the second leading indicator. A tracking number with no carrier movement for a week is a future chargeback with a timestamp on it. Checking this manually across thousands of shipments is impossible, which is why bulk shipment tracking through 17TRACK with automated stuck-shipment alerts is one of the first automations worth setting up in a multi-store operation. The daily question is simple: how many shipments are stuck, on which store, with which carrier?
Dispute rate — the one KPI with hard external thresholds
Most KPI ranges are yours to set. Dispute rate is different, because the card networks set them for you. Per Stripe's documentation of the network monitoring programs, Visa's dispute monitoring program enrolls merchants at a dispute ratio of 0.9% (with at least 100 disputes in a month) at the Standard level, and 1.8% at the Excessive level. PayPal separately applies its High Volume Dispute fee to sellers with more than 100 sales transactions over the previous three months and a dispute rate of 1.5% or higher — and at that tier you pay the fee regardless of the dispute outcome.
The operational takeaway: don't manage to 0.9%. Set your internal alarm at a fraction of it — many operators use 0.3–0.5% as the "all hands" line (again, a rule of thumb, not a published standard) — because dispute rate is a trailing metric and by the time it prints high, the orders that caused it shipped weeks ago. Track it per store: one bad store can sit inside an acceptable portfolio average while its own payment account heads toward enrollment.
Refund rate
Resist the urge to compare your refund rate to a number you read somewhere. Refund rates vary enormously by vertical — apparel with sizing returns is not phone cases. What is universally diagnostic is the trend: a week-over-week jump points at a specific cause — a bad supplier batch, a misleading new creative, a carrier melting down on one lane. Track it by store and by product, and treat every spike as a root-cause exercise. If you're doing serious volume, wire refunds into your per-store profit tracking so a "profitable" store isn't quietly giving it all back.
Every KPI Gets Exactly One Owner
A KPI without a named owner is a screensaver. Assign each number to a person — not a team — who is expected to know why it moved before the review meeting starts.
- Fulfillment lead owns latency and the unfulfilled-orders count. Their morning starts with the oldest unfulfilled order in the portfolio.
- Logistics/ops owns stuck shipments and carrier performance by lane.
- Media buyer(s) own MER per store and are accountable for spend against a margin floor, not just ROAS.
- Support lead owns first response time and SLA attainment. If you're formalizing this, define a support SLA that works across all your stores first, then measure against it.
- Ops manager owns dispute rate, refund rate, and the dashboard itself — the meta-responsibility that definitions stay consistent and the data keeps flowing.
- Finance owns net margin per store and payout reconciliation.
If one person wears three of these hats, fine — that's normal at five stores. The point is that when the dispute rate ticks up, exactly one person is expected to arrive with an explanation. Ownership also makes delegation and hiring cleaner: the KPI list doubles as a job description when you hire and train a VA for store operations.
The Review Cadence: Daily Scan, Weekly Meeting, Monthly Deep Dive
KPIs only change behavior if they're attached to a rhythm.
Daily (10 minutes, async). Each owner scans their daily-cadence numbers first thing and posts one line per anomaly in a shared channel: "Store 4 latency at 61h — 3PL short-staffed, clearing by Thursday." No meeting. The discipline is that silence means "all green," so silence has to be trustworthy. This scan slots naturally into a broader daily and weekly store operations checklist.
Weekly (45 minutes, everyone). A fixed agenda, same order every week:
- Portfolio snapshot (5 min): revenue, MER, and margin direction across all stores. No discussion yet.
- Red metrics (20 min): any KPI outside its range. Owner presents cause and fix; the group decides only if it's cross-functional.
- Trends (10 min): anything moving three weeks in one direction, even if still "green." This is where you catch dispute rate at 0.4% instead of 0.9%.
- Decisions and owners (10 min): every action leaves with a name and a date, recorded in the same doc every week.
Monthly (90 minutes, leads + finance). Per-store P&L review, dispute win rate, payout reconciliation, and one structural question: which store gets more investment, which gets fixed, which gets shut down. Monthly is also when you re-baseline the "healthy ranges" against actual trailing data.
Write the agenda down and keep it identical every week — cadence beats intensity. If your team already runs on documented processes, the KPI review is just one more page in your multi-store SOP library.
Spreadsheet vs. Realtime Dashboard: An Honest Trade-off
You do not need software to start. You need definitions, owners, and a cadence. But the tooling question arrives fast, so here's the honest comparison.
| Spreadsheet | Realtime dashboard | |
|---|---|---|
| Cost to start | Free | Paid tool or build |
| Setup time | An afternoon | Days to weeks |
| Data freshness | As of last export — often yesterday | Minutes |
| Daily-cadence KPIs | Painful; someone exports every morning | Native |
| Weekly/monthly KPIs | Excellent — flexible analysis, pivots | Often weaker for ad-hoc analysis |
| Alerting (stuck shipment, dispute filed) | None | The main reason to upgrade |
| Breaks when… | Store #6+ joins, or the maintainer goes on holiday | The vendor's sync breaks (ask about uptime) |
The realistic answer for most teams is both, in sequence and then in parallel:
- Under ~3–5 stores: a spreadsheet fed by weekly exports is genuinely fine for weekly and monthly KPIs. Its weakness is the daily layer — nobody sustains a manual morning export routine, so daily KPIs silently stop being daily.
- Beyond that: the daily layer needs to be automatic. This is the gap tools like StoreFleet exist to fill — one realtime dashboard for orders, revenue, and shipping across dozens of Shopify stores, with stuck-shipment alerts and disputes sorted by evidence deadline, so the "daily scan" is reading a screen rather than compiling one.
- Keep the spreadsheet anyway. Finance and trend analysis live comfortably in Sheets; the trick is feeding it automatically instead of by hand. Auto-syncing Shopify orders to Google Sheets gives you the flexible analysis layer without the manual export tax.
The failure mode to avoid is the opposite order: buying a dashboard before defining KPIs and owners. A realtime view of numbers nobody owns is just a more expensive screensaver.
Start With Five Numbers
If the full table feels heavy, start Monday with five: revenue per store, orders unfulfilled > 48h, stuck shipments, dispute rate, and first response time. Assign five owners, book the 45-minute weekly, and run it for four weeks before adding anything. A small dashboard the team actually reviews beats a complete one nobody opens — once the cadence is a habit, expanding the table is the easy part.