How to Build a Marketplace Sales Dashboard in Google Sheets
Design a reliable Shopee, Lazada, or TikTok Shop dashboard with clean source tabs, defined KPIs, refresh checks, and a layout people can actually use.
A useful marketplace dashboard is not a collection of colourful charts. It is a small reporting system with clear metric definitions, trustworthy source tabs, a repeatable refresh process, and enough context for someone to make a decision.
This guide shows how to build that system in Google Sheets. The same structure works whether you start with manual exports or keep supported data current with Spyliner.
Start with decisions
Define who uses the dashboard and what they decide
A store operator may need yesterday's orders, cancellations, fulfilment backlog, and low-stock products. A manager may need weekly GMV, net sales, order volume, average order value, advertising spend, and comparison with the previous period. Finance may care more about payouts, fees, refunds, and unsettled orders.
Write down the audience, refresh frequency, and three decisions the dashboard should support. This prevents the common mistake of importing every field and creating charts that nobody acts on.
Use clear layers
Separate raw data, reference tables, calculations, and dashboard tabs
- 1
Raw tabs
Create one tab per marketplace, store, and dataset. Do not place manual notes or presentation formulas inside imported ranges.
- 2
Reference tabs
Maintain mappings for store names, SKU aliases, category groups, targets, currency rates, or product costs.
- 3
Model tabs
Standardize columns, combine sources, deduplicate records, and calculate reporting fields here.
- 4
Dashboard tabs
Present only the KPIs, trends, filters, and exception lists the audience needs.
- 5
Control tab
Show data owner, source date range, last refresh time, metric definitions, and known limitations.
Keep the first version small
Start with eight marketplace KPIs
- ✓Gross merchandise value or gross sales, using one documented status and date definition.
- ✓Net sales after cancellations, refunds, and seller-funded discounts when those fields are available.
- ✓Orders and units sold, kept separate because one order may contain several items.
- ✓Average order value: the chosen sales measure divided by distinct valid orders.
- ✓Cancellation and return rates, with the numerator and eligible denominator documented.
- ✓Advertising spend and attributed sales using a consistent attribution window.
- ✓Top and declining products based on comparable periods rather than lifetime totals.
- ✓Data freshness: the latest source timestamp and latest successful workbook refresh.
Before combining stores
Standardize identifiers, dates, currencies, and statuses
Create canonical fields such as marketplace, region, store, order_id, order_item_id, sku, order_created_at, reporting_date, status_group, currency, gross_sales, discount, fee, refund, and net_amount. Map each source into those fields without deleting the original source values.
Keep identifiers as text so leading zeros are not removed. Convert timestamps using a documented timezone. If stores use different currencies, preserve local values and add converted reporting values with the exchange-rate date and source recorded.
Presentation layer
Build the dashboard from overview to exceptions
- 1
Add controls
Use date, marketplace, store, and category selectors only when they change a decision.
- 2
Add KPI cards
Show the current value, comparison period, absolute change, and percentage change where meaningful.
- 3
Add one trend chart
Plot sales and orders over time with consistent granularity and clearly marked incomplete periods.
- 4
Add contribution tables
Rank stores, products, categories, and channels by both value and change.
- 5
Add an exception queue
Surface cancelled orders, delayed fulfilment, missing mappings, unmapped SKUs, or unusual fee differences.
Operational discipline
Create a refresh and quality-assurance routine
For manual exports, record the exact report filters and archive each source file. For Spyliner tasks, keep source datasets in dedicated tabs, use clear task names, and schedule updates early enough that they finish before the dashboard is reviewed.
After each refresh, test row counts, duplicate keys, blank identifiers, maximum source date, currency values, and totals against the marketplace dashboard. Display a warning when data is stale or a check fails.
Quick answers
Questions people usually ask
How many charts should a marketplace dashboard have?+
Start with one trend, a few KPI cards, contribution tables, and an exception list. Add a chart only when it answers a recurring question better than a table.
Should multiple stores share one raw tab?+
Usually keep raw outputs separate, then combine them in a model tab. This makes source problems easier to isolate and prevents one refresh from disturbing another store.
Can Spyliner build the formulas and charts?+
Spyliner brings supported marketplace data into Google Sheets. Your workbook still owns business definitions, private costs, mappings, formulas, and dashboard design.
