Dashboard

What goes in an e-commerce sales dashboard in Metabase?

An e-commerce sales dashboard is the revenue roll-up for a store: net sales, orders, average order value, and where the revenue comes from. It's the daily number the whole team steers by. Build it from store data synced into a database — see Shopify, WooCommerce, or BigCommerce for the connection.

For: Founders, e-commerce managers, finance. Refresh: hourly to daily. Source: modeled orders with net totals, discounts, refunds, and channel.

Which cards belong on an e-commerce sales dashboard?

Headline KPIs

Trend & mix

  • Net revenue by week (with prior-period comparison)
  • Orders and AOV by week
  • Revenue by channel / source
  • Revenue by region and by discount vs. full price
  • Top products by revenue (table)

What data does an e-commerce sales dashboard need?

  • A modeled orders table with a monetary total, discounts, tax, shipping, and refunds.
  • A financial/payment status to exclude unpaid or cancelled orders.
  • Channel, region, and campaign fields for the mix cards.

How do you build an e-commerce sales dashboard?

  1. Sync your store into a database (Shopify, WooCommerce, or BigCommerce).
  2. Define net revenue once — net of discounts and refunds, excluding tax and shipping — and reuse it.
  3. Build revenue, orders, and AOV cards; add prior-period comparisons.
  4. Add filters for channel, region, and date range.

Example card SQL

Net revenue, orders, and AOV by weekPostgreSQL
-- Net revenue, orders, and AOV by week.
SELECT
  date_trunc('week', o.created_at)                        AS week,
  COUNT(*)                                                AS orders,
  ROUND(SUM(o.net_total), 2)                              AS net_revenue,
  ROUND(SUM(o.net_total) / NULLIF(COUNT(*), 0), 2)        AS aov
FROM orders o
WHERE o.financial_status = 'paid'
GROUP BY date_trunc('week', o.created_at)
ORDER BY week;

Integrations

Analytics

Dashboards

Metrics

FAQ

What should count as net revenue?
Define it once and hold it: usually revenue net of discounts and refunds, excluding tax and shipping (pass-through amounts). Consistency matters more than the exact choice — every card and the AOV calculation should use the same definition.
Why build this in Metabase instead of using Shopify analytics?
Built-in store analytics are convenient but locked to one platform and one definition. Modeling orders in your warehouse lets you blend Shopify with marketplaces or a second store, join to marketing and cost data, define net revenue once, and share governed dashboards.
How do I compare performance across periods?
Add prior-period and year-over-year comparisons to the revenue and orders cards, and watch AOV alongside order count so you can tell whether growth came from more orders or bigger baskets.