Commerce KPIs Dashboard: The Metrics Worth Tracking in One Place
by Trivas.ai
|
8 min read
Sep 27, 2026
A commerce KPIs dashboard is supposed to answer one question fast: are we making money, and where. Most teams instead have five browser tabs open, a spreadsheet with yesterday's numbers, and a nagging feeling that something's off with CAC but no time to prove it. This post covers the specific metrics worth putting in one view, why platform-native numbers still matter even inside a blended dashboard, and where teams usually get the setup wrong.
What a Commerce KPIs Dashboard Actually Is
A commerce KPIs dashboard pulls revenue, ad spend, and customer data from Shopify, Amazon, your ad platforms, and GA4 into one screen. Instead of five logins and five different definitions of "conversion," you get one number for each metric, refreshed on a schedule you control.
That's different from a generic BI dashboard. A generic BI tool will happily show you a revenue line chart trending up and call it a day. Commerce needs more granularity than that. You need order-level and SKU-level detail, because a revenue chart going up while your best-selling SKU is out of stock is telling you a story the top-line number hides completely.
Who actually opens this thing every day? Founders checking morning numbers before coffee. Growth leads deciding whether to push more budget into Meta or pull it back. Ops people checking whether fulfillment is keeping pace with orders, because a dashboard that only shows marketing metrics is only half a dashboard. Each of these people needs a different slice of the same data, which is exactly why one shared source beats five separate ones.
The Core KPIs Every Commerce Dashboard Should Track
Start with revenue, but net revenue, not gross. Gross revenue after a heavy discount code push or a spike in returns looks fine on a chart and terrible on a P&L. Net revenue after returns and discounts is the number that actually tells you if the business made money that day.
AOV and units per order come next, and they need to be tracked by channel, not blended. Amazon and Shopify AOVs often differ by 20 to 40 percent depending on the category, so a single blended AOV number just averages away the insight.
CAC matters, but blended CAC across all paid channels matters more than any single platform's self-reported number. Last-click Meta or Google numbers will tell you a comforting story. Blended CAC, calculated as total spend divided by total new customers, tells you the real one.
Customer LTV and repeat purchase rate deserve a permanent spot, especially if you sell anything subscription or replenishment-based. A low CAC means nothing if customers buy once and vanish.
ROAS is fine as a channel-level metric, but MER (marketing efficiency ratio, total spend over total revenue) is the guardrail number. It's the one that catches you when every individual channel reports a great ROAS but total spend is still creeping up faster than revenue.
Round it out with conversion rate by traffic source and inventory turnover. Conversion rate by source tells you which channel is actually converting versus just driving cheap traffic. Inventory turnover catches a stockout risk before it shows up as a revenue drop you can't explain.
Why Platform-Specific KPIs Still Matter Inside One Dashboard
Blending everything into one view doesn't mean flattening it. Some metrics only exist, and only matter, on a specific platform.
Amazon has its own vocabulary. Buy Box percentage tells you how often you're actually winning the sale on a listing. TACoS (total advertising cost of sale) tells you how much of your total sales, not just ad-attributed sales, are being eaten by ad spend. FBA storage fees quietly chip away at margin in a way that never shows up until you check the report specifically. None of this exists in a Shopify context, and a dashboard that ignores it because it's "Amazon-specific" is missing real margin data. This is one reason a dedicated view for Amazon still matters even inside a unified dashboard.
Shopify has its own set too: cart abandonment rate, discount code usage, subscription churn if you're running a subscription model. These metrics explain a lot of the "why" behind a revenue dip that Amazon data can't touch. The Shopify integration needs to surface these natively, not force them into a generic ecommerce template built for a different platform.
Ad platforms need context too. Meta CPM trends and Google Ads CPC behave completely differently and respond to different levers. Blending them into one "average ad cost" number hides which channel is actually working and which one is quietly draining budget.
GA4 funnel data rounds this out: landing page bounce rate, add-to-cart rate. These explain why a KPI moved, not just that it moved. A conversion rate drop with a rising add-to-cart rate is a checkout problem. A conversion rate drop with a rising bounce rate is a landing page or traffic quality problem. Same top-line metric, completely different fix.
Real-Time Data vs the Monday Morning Spreadsheet
A dashboard backed by a warehouse like Redshift, refreshing hourly, behaves very differently than a spreadsheet somebody rebuilds every Monday. One shows you what's happening. The other shows you what happened, days after it stopped mattering.
Teams doing manual reporting often spend 3+ hours a week just reconciling Amazon, Shopify, and ad platform exports before they can even start looking at trends. That's before any analysis happens. Three hours of copy-paste and formula-checking, every single week, just to get to a starting point.
The real cost isn't the hours. It's the decision that didn't get made. A CAC spike that starts on a Tuesday can sit unnoticed for a full week if nobody catches it until Monday's report. By then you've spent five extra days of budget at an unprofitable acquisition cost, and the fix that would've taken ten minutes on day one now needs a full spend reallocation.
Common Mistakes When Setting Up a Commerce KPI Dashboard
The most common one: tracking vanity metrics. Impressions, follower counts, social engagement, none of it ties directly to revenue or margin, and yet it takes up dashboard real estate that should go to numbers that actually move a P&L.
Second mistake: building a separate dashboard per channel. One for Amazon, one for Shopify, one for ads. This feels organized, but it makes cross-channel comparison nearly impossible, since you end up manually eyeballing three tabs to answer a question a single blended view could answer in one glance.
Third: skipping attribution logic entirely and treating platform-reported ROAS as ground truth. Every ad platform has an incentive to report generous attribution for itself. Meta and Google will both claim credit for the same conversion if you let them, and if your dashboard just pulls their self-reported numbers without any deduplication logic, you're not looking at reality, you're looking at marketing.
Fourth: no alerting, no thresholds. A dashboard that requires someone to remember to open it every morning is only as good as that person's memory. The better setup flags a KPI when it crosses a threshold, so the team finds out the moment something breaks instead of five days later.
Build vs. Automate: How Teams Actually Get These Dashboards Running
Spreadsheets are the cheapest way to start, and for a brand with two SKUs and one channel, they're honestly fine. But they break down fast past a handful of SKUs or a second channel. Every new data source is another manual export, another formula to maintain, another place a broken link quietly corrupts a number nobody double-checks until it's badly wrong.
Native platform dashboards, Shopify's built-in analytics, Amazon Seller Central, are good at what they cover. But neither can blend Meta ad spend against Shopify revenue in one view, because neither was built to look outside its own platform. You end up back in the five-tabs problem, just with nicer-looking individual tabs.
Automated commerce analytics tools that pull from a warehouse and refresh without manual exports solve the reconciliation problem directly. This is the layer Trivas's BI reporting is built around: Amazon, Shopify, ad platforms, and GA4 landing in one Redshift-backed view, refreshed on a schedule instead of a Monday scramble.
When you're actually choosing between these options, weigh setup time, whether the tool handles both Shopify and Amazon natively instead of bolting one on as an afterthought, and whether there's any layer that can explain why a KPI shifted instead of just charting the fact that it did. A dashboard that just draws a line is table stakes. One that tells you the line moved because of a landing page change or a competitor price drop is the one worth paying for.
Getting Your KPIs Into One View
The short list worth repeating: revenue (net, not gross), AOV, CAC, LTV, ROAS and MER together, conversion rate, and the channel-specific metrics like TACoS or cart abandonment that explain the "why" behind the headline numbers.
This section covers what belongs on the dashboard. How to actually structure the thing, layout, permissions, refresh cadence, is a separate question worth its own read if you're setting one up from scratch.
If you're tired of reconciling five exports every Monday, it's worth seeing how Trivas blends these metrics automatically. No pressure to commit, just worth a look at what a working version actually looks like.
Content author and contributor at Trivas.ai, sharing insights on e-commerce analytics, business intelligence, and data-driven strategies to help businesses grow.
Continue Reading
explore more insights
Leveraging Cross-Device Attribution for Business Growth
3 min read
Ecommerce Analytics That Shows True Channel ROAS (Not Blended): Trivas vs Triple Whale vs Northbeam vs Polar
3 min read
AI Ecommerce Insights: Spot Revenue Drops 3x Faster (2025)
.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.ai
