Home / Guides / Article
Data & dashboards

Sales Dashboard for Small Business: What to Track and How to Build It

One screen that tells you how sales are going, what is selling and where it comes from. Here are the numbers to include, how to define them so they match your books, and when a free tool is enough.

Updated: 2026-11-09 · TinyBuild

The holiday peak is the busiest stretch of the year for many small shops, and the weeks after it are when owners finally ask the questions that matter: did the promotion actually pay off, which products carried the season, and which channel is worth more attention next year? The data to answer them usually exists. It is just spread across a shop admin, a payment provider, a marketplace account, and a spreadsheet someone updates on Mondays.

A sales dashboard for a small business brings those answers onto one screen. This guide covers which numbers to put on it, how to define them so they match your accounting, four ways to build one from free to custom, and how to use it for a year-end review.

If you want to see your own numbers first, drop a sales export into our free CSV sales dashboard. It runs in your browser and reads exports from Shopify, WooCommerce, Etsy, Stripe, Square and spreadsheets. For a simplified example of a custom version, try the sales dashboard demo.

What a small business sales dashboard should answer

Start from the questions, not the charts. Most small teams check the same five things, and each one maps to one or two numbers:

QuestionNumber that answers itUsual source
Are we selling more or less than before?Net sales vs the previous period and the same period last yearShop or POS orders
Is each customer spending more?Average order valueOrders
What is selling?Net sales and units by productOrder line items
Where are sales coming from?Net sales by channel (web shop, marketplace, retail, B2B)Order source or sales channel field
Are customers coming back?Repeat customer rateOrders with a customer ID or email

If a chart doesn't help answer one of these questions, or a question specific to your business, leave it off the first version.

The sales KPIs worth tracking first

  1. Net sales. Product sales after discounts and returns, before tax and shipping. This is the headline number. See the next section for why "revenue" is not precise enough.
  2. Orders. Count of orders, excluding test and cancelled orders.
  3. Average order value (AOV). Net sales divided by orders. Watch it during promotions: a busy week with a falling AOV may mean the discount was deeper than it needed to be.
  4. Units and net sales by product. A ranked table is more useful than a pie chart. Add stock on hand if you can, so a best-seller that is about to run out stands out.
  5. Net sales by channel. Web shop, marketplace, retail, wholesale. Channels often differ in fees and margin, so the mix matters as much as the total.
  6. Repeat customer rate. The share of customers in the period who had ordered before. It is the clearest sign of whether the business is building loyalty or renting traffic.
  7. Return or refund rate. Refunded value divided by gross sales. It often rises a few weeks after a promotion, so look at it again in January.
  8. Gross margin, if you have product costs. Net sales minus cost of goods. Without reliable costs, leave it out rather than guessing; a precise-looking wrong margin does more harm than no margin.

Leave these out at first: website traffic totals, social follower counts, and revenue as reported by ad platforms. Ad platforms count conversions with their own attribution rules, and their totals often exceed what the shop actually took. If you need ad performance, show ad spend next to the shop's own sales by channel rather than the platform's revenue figure.

Agree on definitions before building charts

The most common reason a dashboard gets ignored is that its numbers don't match the accountant's, the shop admin's, or last month's spreadsheet. Usually nothing is broken; the numbers are just defined differently. Write the definitions down once.

Shopify's own reports are a good reference. In its sales report definitions:

TermShopify definition (simplified)Use it for
Gross salesProduct price × quantity, before discounts, returns, tax and shippingDemand before discounts
Net salesGross sales − discounts − sales reversals (returns, cancellations, edits)The headline sales number
Total salesNet sales + taxes + duties + shipping charges + feesCash collected from customers, not income

Other systems use different words for similar ideas. Stripe exports show charged amounts and fees per payment, and payouts arrive days later as one lump sum. Marketplaces deduct their fees before paying out. Decide these points for your business:

  • Which date counts. Order date, payment date, or payout date. Use order date for sales trends and payout date only for cash flow.
  • Which time zone. A late-night order on the last day of the month can land in a different month depending on the time zone.
  • What is excluded. Test orders, cancelled orders, internal orders, and staff discounts.
  • Currency. If you sell in several currencies, convert at a fixed, documented rate, or report each currency separately.
  • When returns count. On the date of the return, as Shopify does, or against the original order. The first matches accounting; the second shows the true return rate of a promotion.

Then run a reconciliation check: pick one week and compare the dashboard with the shop admin and with what arrived in the bank account. Explain every difference before anyone makes a decision from the dashboard.

A one-screen layout people actually open

The best small business dashboards fit on one screen and read top to bottom:

  1. Headline row: net sales, orders, AOV and repeat customer rate, each with the change against the previous period. For seasonal businesses, add the same period last year, because comparing December with November says little.
  2. Trend chart: net sales per day for short ranges, per week or month for long ones. Mark promotions so a spike has an explanation.
  3. Products: top products by net sales, with units and stock if available.
  4. Channels: net sales by channel as a simple bar or stacked bar.
  5. Exceptions: unusually large refunds, orders stuck in a status, or products that stopped selling. A short list here is often more useful than another chart.

Add two small but important details: a date range and channel filter, and a line saying when the data was last updated. A stale dashboard looks exactly like a fresh one unless it says otherwise.

Four ways to build a sales dashboard, from free to custom

OptionSetupOngoing effort and costWorks well whenLimits
Built-in reports (Shopify Analytics, WooCommerce Analytics, Square reports)NoneIncluded with the platformYou sell through one platform and one person checks the numbersOne system only; other channels and costs are missing
CSV export + a dashboard tool such as our free CSV sales dashboardMinutesA manual export each timeA monthly or seasonal review, or checking what your data can show before investingNot live; one file at a time
Spreadsheet or Looker Studio, fed by a connector or a maintained sheetHours to daysLooker Studio is free; Pro is $9 per user per project per month. Shopify needs a third-party connector or a sheet in between, and most connectors are paid per monthA marketing-led team that already lives in Google toolsConnector limits, unclear definitions, and someone has to keep the sheet current
Custom dashboardDays to a few weeksHosting and occasional maintenanceSeveral data sources, margin after fees, several roles, or alertsNeeds a clear scope and an owner

There is no shame in staying with the first two options. A small shop with one sales channel and one decision-maker rarely needs more than the platform's reports and a monthly look at an export. Move up only when a specific question can't be answered.

When a custom sales dashboard is worth it

A custom dashboard pays off when the work of producing the numbers becomes a job of its own. Typical signs:

  • Sales come from several systems: a web shop, a marketplace, a POS and B2B invoices from the accounting tool.
  • The figure you care about, such as margin after payment fees, marketplace commission and shipping, isn't in any one export.
  • Someone spends an hour or more each week assembling a report by hand.
  • Different people need different views: the owner wants totals, the warehouse wants stock risk, sales staff want their accounts.
  • You want to be told when something unusual happens, such as a sudden drop in orders from one channel, instead of noticing a week later.
  • Meetings start with an argument about whose numbers are right.

If none of these apply, a custom build is probably premature. If two or three apply, the time saved and the decisions it unlocks usually justify a small first version.

What a first custom version includes

A first version should prove that the numbers are right and that people use the dashboard. It does not need every metric. A focused scope looks like this:

  • One or two data sources, for example Shopify orders and Stripe payouts, or a POS export and the accounting tool.
  • Five to eight metrics with written definitions, matched against the shop admin for one test week.
  • A date range filter, a channel filter, and comparison with the previous period.
  • Top products, a channel split, and a short exceptions list.
  • A "last updated" label and a CSV export so figures can be checked.

At TinyBuild, a working demo of that scope on sample or exported data usually takes about 3 days. Moving to production adds scheduled data syncs, API rate limits, backfilling history, access control and hosting, which we scope and quote separately. Later additions might include margin after fees, cohort views, stock alerts or a weekly email summary. The sales dashboard demo shows the kind of screen a first version starts from.

Use it for a year-end and peak-season review

December and January are a good time to look back at the busiest weeks while the details are still fresh. Use the dashboard, or an export in the CSV tool, to work through these points:

  1. Peak week against a normal week. Compare net sales, orders and AOV in the promotion week with an average week in October, and with the same week last year.
  2. Discount depth against AOV. If orders rose but AOV fell sharply, test a smaller discount or a threshold offer next year.
  3. Products. Which products sold out, and when? Which promoted products barely moved?
  4. Channels. Did the mix shift? A channel that grew in the peak but carries high fees may look better than it is.
  5. New and returning customers. How many peak-season buyers were new, and how many of them ordered again by the end of January?
  6. Returns. Check the return rate for peak-season orders in late January, when most returns have arrived.

Write the findings down with three changes for next year. If the review was hard because the data was missing or scattered, that is useful too: it tells you exactly what a better dashboard needs. If the problems were technical, such as orders that failed to sync, our Black Friday technical checklist covers what to test before the next peak.

Common sales dashboard mistakes

  • Calling total sales "revenue". Tax and shipping inflate it, and tax isn't yours to keep.
  • Mixing order dates and payout dates in the same chart.
  • Counting test, cancelled or duplicate orders, especially after a promotion when tests were run on the live shop.
  • Trusting platform-reported ad revenue as if it were sales.
  • Thirty metrics on one screen. Nobody reads them, and the important change gets lost.
  • No owner. Someone has to notice when a sync breaks or a definition changes.
  • No freshness label, so a dashboard that stopped updating three weeks ago still gets used.

FAQ

What should a small business sales dashboard include?

Net sales, orders and average order value with a comparison to the previous period, a sales trend chart, top products, sales by channel, and the repeat customer rate. Add gross margin only when product costs are reliable. Keep it to one screen.

Is Shopify's built-in analytics enough?

For a store that sells only through Shopify and is reviewed by one person, usually yes. It becomes limiting when sales also come from marketplaces, a POS or B2B invoices, or when you need margin after fees and shipping, because those figures sit in other systems.

What is the difference between gross sales, net sales and total sales?

In Shopify's definitions, gross sales is product price times quantity, net sales subtracts discounts and sales reversals such as returns, and total sales adds taxes, duties, shipping charges and fees to net sales. Use net sales as the headline number on a dashboard.

Can I build a sales dashboard for free?

Yes. Platform reports, a spreadsheet, Looker Studio's free tier, or our free CSV sales dashboard cost nothing. The cost appears when you need live data from several systems: connectors are usually paid, and someone has to maintain the setup.

How often should the data refresh?

Daily is enough for most small businesses. Hourly or real-time data is worth the extra work only when someone acts on it within the day, for example during a flash sale or for stock that sells out quickly.

How long does a custom sales dashboard take to build?

A focused first version with one or two data sources and five to eight metrics can be shown as a working demo in about 3 days. A production version with scheduled syncs, history and access control takes longer and depends on the data sources involved.

Sources and scope

Metric definitions follow Shopify's sales report documentation. Looker Studio pricing is from Google Cloud's Looker Studio page, checked in November 2026; connector prices vary by vendor and change often, so check current pricing before choosing one. This guide is general information for small businesses, not accounting advice; agree on revenue definitions with your accountant.

Where does your sales data live?

Tell us which systems you sell through and which numbers you check every week. TinyBuild offers a free assessment and a fixed quote. A focused dashboard demo usually takes about 3 days; live syncs and production hosting are scoped separately.

Share your idea →