A modern workspace featuring financial charts and multiple clocks on a white table, ideal for trading.
Photo by AlphaTradeZone on Pexels

Measurement Planning

Ecommerce dashboard design

An ecommerce dashboard should help a team decide what to do today and explain what happened after the numbers settle. Start with decisions, definitions and data …

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Measurement.

undefined

An ecommerce dashboard should make key store measures easy to scan, compare and investigate. Start with the decisions it must support, then set clear definitions, a visual hierarchy and useful drill-downs. A screen of impressive charts is less useful if nobody knows which figure to trust or who will act on it.

Choose the reporting layer to fit the sources and users. For a Shopify example, Vidi describes a Shopify connector for Looker Studio and combining Shopify data with GA4, Meta Ads and Google Ads; Microsoft documentation explains data refresh in Power BI (Vidi; Microsoft).

Separate operating signals from outcomes

Separate operating signals from confirmed outcomes. Use early signals to prompt investigation and reconciled results to assess performance; label provisional same-day figures so they are not mistaken for final finance results.

Trading view: orders, sales and payment or checkout incidents, with same-day figures marked as subject to change. Merchandising view: demand, stock and fulfilment capacity by product; traffic alone does not confirm a sale. Marketing view: channel and traffic-source results, compared over relevant periods. Finance view: reconciled sales, returns and finance measures, with each report basis stated.

Set a refresh cadence to suit the decisions the dashboard supports and the timing of its sources. Assign an owner to check refresh failures, and show the last successful refresh and expected delay so users can judge how current each view is.

Shopify notes that sales reports can differ across reports, exports or dashboards because of timing or reporting logic. Treat a difference as a reason to check each measure’s basis, rather than assume one dashboard is wrong. Shopify says sales report data is up to date, give or take about 1 minute; you can reopen or refresh the report to display newer data (Shopify).

Power BI refresh can query underlying data sources, load source data into a semantic model and update dependent report or dashboard visuals. Microsoft notes that renaming or removing a source column or table can cause refresh to fail, so assign an owner to check schema changes and refresh failures (Microsoft).

Design for differences between reports

Shopify separates returns and refunds: sales reports include returns, while the Payments finance report includes refunds. If both appear in a dashboard, label them separately and state each report basis. Otherwise, readers may treat two different measures as competing versions of the same number.

The timing of a refund can also affect how a figure appears. Shopify says a pending refund can leave a positive amount in the Sales by channel report; when the refund is complete, the amount appears as negative. A visual treatment that identifies refund status and report helps readers interpret that change without mistaking it for an unexplained sales movement.

Comparisons between Shopify Analytics and another tracking service can differ for reasons beyond a dashboard calculation. Shopify identifies differences in how page reloads, unique visitors and sessions are counted, as well as reporting time zones; Google Analytics may not count visitors without JavaScript and cookies or those using blocking extensions. Name the system behind each view, and avoid combining unlike counts into one unlabelled total. Reconcile unexpected movements to source reports using matching dates, time zones and filters before treating them as trading changes.

For an Australian store, label whether reported sales, discounts and profit are GST-inclusive or GST-exclusive, and apply the chosen basis consistently across cards, charts and exports. State the tax basis beside each finance measure rather than leaving readers to infer what a figure includes.

Shopify Sales Report vs. Finance Reports: Key Differences in Returns and Refunds

  • Sales Report (Shopify)Includes returns as a positive adjustment; reflects pending or completed return events.
  • Payments Report (Shopify)Includes refunds as negative adjustments; only records actual refund payments made.
  • Impact on DashboardWithout clear labelling, users may misinterpret a refund as a sales increase if not aligned with the correct report basis.

Top 5 Reasons for Sales Discrepancies Across Shopify Reports

  1. GST Inclusion Not Consistently AppliedSome reports show GST-exclusive values; others include GST — label clearly to avoid confusion.
  2. Refund Status MisinterpretationPending refunds appear as positive amounts; completed refunds show as negative — label status explicitly.
  3. Channel Attribution Models DifferMeta Ads may assign credit to last click; Shopify may use first-click or multi-touch models.

Make the definition visible

Every headline metric needs a source, time zone and calculation. Decide whether “sales” means orders placed, paid revenue, net sales after returns or another finance measure. Display the chosen definition near the number. Do not place two similar figures side by side without explaining their different jobs.

A glossary entry can read: “Orders — number of orders placed on a given date; source: Shopify sales report; date basis: order date.” Shopify defines orders as the number placed on a given date, so make the date basis visible beside the metric (Shopify).

Use a drill-down from a red signal to the product, channel or checkout step that can be investigated. Add an owner and an action threshold where a decision is expected.

Review the dashboard after a trading incident. Did its labels and drill-downs help the team investigate the issue? Refine them where needed.

Limit dashboard editing to people responsible for the model, and give other users viewer access suited to their work. Keep a change log for definition, source, filter and tax-basis changes, with the effective date and owner; retest affected cards, charts and drill-downs after a change.

Key Ecommerce Metrics with Clear Definitions for Australian Stores

Orders
Number of orders placed on a given date
Gross Sales
Product price × quantity before taxes, shipping, discounts or reversals
Net Sales
Gross sales minus discounts, returns and sales reversals
Gross Profit
Net sales minus product cost (as defined by Shopify)
GST Basis
All financial figures are GST-inclusive unless otherwise stated

Match each view to its comparison

Shopify sales reports include views of sales over time, by product and by channel. Use these as distinct ways to inspect a result: a time-based view shows movement across periods, while product and channel views reveal how the total is distributed. Label the grouping clearly so readers know what each chart compares.

Use a three-zone layout: headline KPI cards across the top, a line chart of sales over time beneath them, then bar charts for product and channel breakdowns side by side. Keep the selected period and grouping visible in each chart title or control, so readers can see what they are comparing without guessing.

Shopify also provides average order value over time; show it as a separate trend rather than mixing it into a sales total (Shopify).

Give headline figures a usable glossary

Use the report’s own terminology in labels and supporting text. Shopify defines orders as the number placed on a given date; gross sales are product price multiplied by quantity before taxes, shipping, discounts and sales reversals. Gross sales include pending, cancelled and unpaid orders, but not test or deleted orders, so the label should not imply that it means paid revenue.

For each glossary entry, record the metric name, definition, calculation, source, date basis, GST basis and refresh owner. Keep the glossary available beside the dashboard so readers can check what a headline figure includes before comparing it with another view.

If the dashboard includes average order value, show how it is calculated rather than treating it as self-explanatory. Shopify’s definition uses gross sales, excluding adjustments, minus discounts, excluding adjustments, divided by the number of orders. This helps readers distinguish it from a sales total and understand which parts of the calculation affect it.

A profit measure also needs a clear name and basis. Shopify defines gross profit as the total profit made on the product during the report period, calculated by subtracting product cost from net sales. If readers see both sales and profit figures, keep their labels distinct and make the calculation available beside the figure or in a glossary.

Explain adjustments that can change a reported amount. Shopify defines discounts as line-item discounts plus the order-level discount share; discounts applied to an entire order are proportionally applied across their sales. Sales reversals are order adjustments that result in a negative monetary value, so a negative figure should not be presented without a label that clarifies what it represents.

Further reading: Helpful definitions (amplitude.com).

In this guide

  1. Building a daily trading dashboard from Shopify reportsA daily trading dashboard should answer whether the store is operating as expected and where someone needs to investigate. Keep the first screen small enough to …
  2. Separating leading indicators from confirmed outcomesProduct-page visits, add-to-cart events and checkout starts can warn of a change before sales settle. They are signals to investigate, not sales in another name.
  3. Showing data freshness in a store reportA report without an update time can make yesterday’s incomplete data look final. Show when each source was last processed and whether the current period may still change.
  4. Removing metrics that do not inform a trading decisionEvery daily dashboard metric should answer a question or trigger an action. If it only fills space, move it to a detailed report or retire it.

More from Measurement Planning

Measurement Planning

Basket and merchandising analytics

Use product pairings, recommendation results, category routes and onsite search evidence to guide merchandising decisions.