Shopify dashboard

A Shopify dashboard shows the shop owner and finance lead what Shopify's own data says about sales by channel, discounts, refunds and when last month can be called final. ShopifyQL pulls those figures, in the admin's editor or through the Admin API, and a weekly snapshot records how far each month moves after close.

Last reviewed · Virgo Analytics

One month read seven times, example

September by order date fell £14.2K in the five weeks after close

Example data

September net sales

Read every Thursday, 1 Oct to 12 Nov

By processing date

£186.4K

By order date, 12 Nov

£177.0K

September, order-dated, after close

−£14.2K

One month read seven times, example. September by order date fell £14.2K in the five weeks after close. By processing date: £186.4K on every read. By order date: 1 Oct (close) £191.2K, 8 Oct £185.1K, 15 Oct £180.7K, 22 Oct £178.1K, 29 Oct £177.2K, 5 Nov £177.0K, 12 Nov £177.0K.£174K£178K£182K£186K£190K£194K1 Oct8 Oct15 Oct22 Oct29 Oct5 Nov12 Nov−£14.2K1 Oct (close): By order date £191.2K, By processing date £186.4K8 Oct: By order date £185.1K, By processing date £186.4K15 Oct: By order date £180.7K, By processing date £186.4K22 Oct: By order date £178.1K, By processing date £186.4K29 Oct: By order date £177.2K, By processing date £186.4K5 Nov: By order date £177.0K, By processing date £186.4K12 Nov: By order date £177.0K, By processing date £186.4KOne month read seven times, example. September by order date fell £14.2K in the five weeks after close. By processing date: £186.4K on every read. By order date: 1 Oct (close) £191.2K, 8 Oct £185.1K, 15 Oct £180.7K, 22 Oct £178.1K, 29 Oct £177.2K, 5 Nov £177.0K, 12 Nov £177.0K.£174K£178K£182K£186K£190K£194K1 Oct8 Oct15 Oct22 Oct29 Oct5 Nov12 Nov−£14.2K1 Oct (close): By order date £191.2K, By processing date £186.4K8 Oct: By order date £185.1K, By processing date £186.4K15 Oct: By order date £180.7K, By processing date £186.4K22 Oct: By order date £178.1K, By processing date £186.4K29 Oct: By order date £177.2K, By processing date £186.4K5 Nov: By order date £177.0K, By processing date £186.4K12 Nov: By order date £177.0K, By processing date £186.4KProcessing£186.4KOrder date£177.0KOne month read seven times, example. September by order date fell £14.2K in the five weeks after close. By processing date: £186.4K on every read. By order date: 1 Oct (close) £191.2K, 8 Oct £185.1K, 15 Oct £180.7K, 22 Oct £178.1K, 29 Oct £177.2K, 5 Nov £177.0K, 12 Nov £177.0K.£174K£178K£182K£186K£190K£194K1 Oct8 Oct15 Oct22 Oct29 Oct5 Nov12 Nov−£14.2K1 Oct (close): By order date £191.2K, By processing date £186.4K8 Oct: By order date £185.1K, By processing date £186.4K15 Oct: By order date £180.7K, By processing date £186.4K22 Oct: By order date £178.1K, By processing date £186.4K29 Oct: By order date £177.2K, By processing date £186.4K5 Nov: By order date £177.0K, By processing date £186.4K12 Nov: By order date £177.0K, By processing date £186.4KProcessing£186.4KOrder date£177.0KOne month read seven times, example. September by order date fell £14.2K in the five weeks after close. By processing date: £186.4K on every read. By order date: 1 Oct (close) £191.2K, 8 Oct £185.1K, 15 Oct £180.7K, 22 Oct £178.1K, 29 Oct £177.2K, 5 Nov £177.0K, 12 Nov £177.0K.£174K£178K£182K£186K£190K£194K1 Oct8 Oct15 Oct22 Oct29 Oct5 Nov12 Nov−£14.2K1 Oct (close): By order date £191.2K, By processing date £186.4K8 Oct: By order date £185.1K, By processing date £186.4K15 Oct: By order date £180.7K, By processing date £186.4K22 Oct: By order date £178.1K, By processing date £186.4K29 Oct: By order date £177.2K, By processing date £186.4K5 Nov: By order date £177.0K, By processing date £186.4K12 Nov: By order date £177.0K, By processing date £186.4KProcessing£186.4KOrder date£177.0K
Processing date: October's refunds land in October, so September never movesOrder date: settles at £177.0K, £9.4K under the processing figure

Refunds against September orders, processed by each date

Refunds against September orders, processed by each date: 1 Oct (close) £9.8K, 8 Oct £15.9K, 15 Oct £20.3K, 22 Oct £22.9K, 29 Oct £23.8K, 5 Nov £24.0K, 12 Nov £24.0K.£9.8K1 Oct8 Oct15 Oct22 Oct29 Oct5 Nov£24.0K12 NovRefunds against September orders, processed by each date: 1 Oct (close) £9.8K, 8 Oct £15.9K, 15 Oct £20.3K, 22 Oct £22.9K, 29 Oct £23.8K, 5 Nov £24.0K, 12 Nov £24.0K.£9.8K1 Oct£15.9K8 Oct£20.3K15 Oct£22.9K22 Oct£23.8K29 Oct£24.0K5 Nov£24.0K12 NovRefunds against September orders, processed by each date: 1 Oct (close) £9.8K, 8 Oct £15.9K, 15 Oct £20.3K, 22 Oct £22.9K, 29 Oct £23.8K, 5 Nov £24.0K, 12 Nov £24.0K.£9.8K1 Oct£15.9K8 Oct£20.3K15 Oct£22.9K22 Oct£23.8K29 Oct£24.0K5 Nov£24.0K12 NovRefunds against September orders, processed by each date: 1 Oct (close) £9.8K, 8 Oct £15.9K, 15 Oct £20.3K, 22 Oct £22.9K, 29 Oct £23.8K, 5 Nov £24.0K, 12 Nov £24.0K.£9.8K1 Oct£15.9K8 Oct£20.3K15 Oct£22.9K22 Oct£23.8K29 Oct£24.0K5 Nov£24.0K12 Nov
September orders, gross sales less discounts
£201,000
Refunds processed in September against August orders
£4,800
Example data: an invented online shop's September 2026, net sales excluding VAT, read every Thursday from 1 October. The processing-dated figure was fixed at close. The order-dated figure kept falling as returns came back, then stopped once the return window had passed.
Show the numbers
September 2026 net sales by read date, example data
Read onBy processing dateBy order dateRefunds against September orders, processed by each date
1 Oct (close)£186.4K£191.2K£9,800
8 Oct£186.4K£185.1K£15,900
15 Oct£186.4K£180.7K£20,300
22 Oct£186.4K£178.1K£22,900
29 Oct£186.4K£177.2K£23,800
5 Nov£186.4K£177.0K£24,000
12 Nov£186.4K£177.0K£24,000

Shopify dashboard KPIs and how to calculate them

ShopifyQL's datasets, or the orders and refunds behind them, supply all six rows. Net sales on this page is gross sales less discounts and returns, excluding VAT and shipping, as Shopify's own net sales leaves out shipping too. Contribution per order, after every cost, is worked through on ecommerce analytics.

KPIFormulaA good readingThe common mistake
Net sales by sales channelNet sales for the period, grouped by the sales channel Shopify records on each sale Each channel moving in line with its own plan Folding every channel into one total. A fall in one channel hides under growth in another.
Channel shareA channel's net sales ÷ net sales across all channels × 100 Moving the way the plan expects Reading a rising share as growth. If another channel fell, the share rises with no extra sales.
Discount rateDiscounts ÷ gross sales × 100, both from the sales dataset Inside the promotion plan, and higher only in the weeks a promotion ran Leaving shipping discounts unstated. Decide whether they count and write it into the definition.
Close revision(Net sales for the month by order date, read today − the same figure read at close) ÷ the figure read at close × 100 Shrinking each week, then flat once the return window has passed Treating the figure read at close as the month's last word. Refunds on its orders are still being processed, and in the example they took five weeks to stop.
Refunds by order monthRefunds processed in a month, split by the month the original order was placed Each order month's refunds tailing off as its return window closes Reading refunds processed as refunds caused. A heavy refund week in January can belong to December's orders.
Cost coverageProduct sales with a cost recorded ÷ all product sales × 100 Every product carries a cost, so any margin figure covers the whole range Reading a margin figure without checking coverage. Products with no cost recorded drop out of it.

Shopify reporting with ShopifyQL

A ShopifyQL query names a dataset with FROM and the figures to return with SHOW. Net sales by channel for last month reads:

FROM sales SHOW net_sales, orders GROUP BY sales_channel DURING last_month

The same query runs in two places. In the ShopifyQL editor in the Shopify admin it returns a table you can chart, save and share as a report. In an app it goes through the shopifyqlQuery field of the GraphQL Admin API, which needs the read_reports access scope, Level 2 access to protected customer data and API version 2025-10 or later. Shopify notes that protected customer data approval can take time, so ask for it before the build starts.

If your returns export carries the order ID for each returned item, that ID builds the order-dated line in the example: each refund is matched to its order and dated by the order.

How to build a Shopify dashboard

  • Data sources

    ShopifyQL's sales and returns datasets for the channel, discount and refund figures, and the orders behind them for each order's date. Keeping weekly snapshots needs a table outside Shopify, in a warehouse or a sheet, which is data infrastructure work once more than one shop or source is involved.

  • Grain

    One row per order line and one per refund line, each carrying the order date and the processed date. On top of that, a snapshot table: one row per month per read date, holding the month's net sales on both datings. The revision lines are drawn from it.

  • Refresh cadence

    Daily for sales by channel. The snapshot is taken weekly, on Thursdays in the example, and never overwritten.

  • Which date leads

    Decide which dating the headline figure uses. Processing date matches Shopify's sales reports and is fixed at close. Order date says what the month's trading was really worth, once it has settled. The example shows both, labelled, and names the dating under every figure.

  • When a month is final

    Set the read date after which a month's order-dated figure is treated as settled, from your own return window and how long refunds take to process. In the example September stopped moving by 5 November, five weeks after close.

Questions a Shopify dashboard should answer

“How did each channel do last month?”Net sales by sales channel, with channel share beside it.
“Are we discounting more than we planned?”Discount rate, week by week, with promotion weeks marked.
“Is last month's figure final yet?”Close revision, read from the snapshot table.
“Why did refunds jump this week?”Refunds by order month, to see which month's orders they came from.
“Can we trust the margin figure?”Cost coverage, checked before any margin is shown.

Tracking and measurement answers a separate question, which advert or campaign brought an order. A shop with stores too will want retail KPIs for its buying and stock.

Shopify dashboard examples by tool

  • Power BI

    Every sale and refund carries two dates, so the date table needs two relationships to the sales table: order date active, processed date inactive. A measure switches to the processed date with USERELATIONSHIP when a page needs Shopify's own dating. Both lines in the example then come from one model.

  • Data Studio (formerly Looker Studio)

    Point the revision chart at the snapshot table, with read date across and one series per dating. The snapshot has to be written somewhere first, in BigQuery or a sheet, because every read of a live source shows only today's figure.

  • Excel

    For one shop, a log tab is enough: once a week, add a row with the read date and last month's net sales on both datings. Six or seven rows after close show whether the month has settled.

  • Google Sheets

    To work in a spreadsheet instead, our Fresh Sheets add-on pulls Shopify orders, totals, refunds and units ordered into Google Sheets on the schedule you choose. Add a log tab beside it, as in Excel, and record last month's total each week so the revision lines have something to draw from.

Two datings gave the example's September two different figures, so before anything is built on your shop's data through our dashboards and BI service, we agree with you which date each Shopify figure carries.

Questions about Shopify data

Can I build a Shopify dashboard without an app?

Yes, for one shop and a handful of views. The ShopifyQL editor in the Shopify admin runs a query, charts the result and saves or shares it as a report. You need an app, or a pipeline into a warehouse, once the dashboard joins Shopify to data held elsewhere, or keeps weekly snapshots like this page's example.

What access does an app need to run ShopifyQL?

Shopify's documentation lists three things for the shopifyqlQuery field: the read_reports access scope, Level 2 access to protected customer data, and GraphQL Admin API version 2025-10 or later. Shopify also says protected customer data approval can take time and should be requested early, so ask for it before the dashboard build starts.

Is Shopify analytics enough, or do we need a warehouse?

It's enough for questions about Shopify's own data. On this page the first reason to add a warehouse is the weekly snapshot, because the revision lines need last month's figure stored every Thursday in a table of your own. The second is bringing in stock or payment data held outside Shopify.

Why doesn't our Shopify reporting match the finance figures?

The dates are the first thing to check. In Shopify's sales reports a refund counts on the day it went through, so an August order refunded in September reduces September. Finance may book it differently. Put both figures side by side for one month, list the refunds that land in different months, and agree which date each report uses.

Can ShopifyQL split sales by sales channel?

Yes. The sales dataset has a sales_channel dimension, so one query returns net sales and orders for each channel the shop sells through. Shopify's own example ranks channels by total sales over 30 days. Group by the channel field Shopify gives you, and keep each channel as its own line on the dashboard.

When is last month really final?

A Shopify export of three months' orders and refunds shows how far each month moved after it closed.

Book a call

Free 30 min call