A marketplace dashboard that puts exception queues first and reconciles before showing money

A marketplace seller software reporting dashboard should begin as a blank data dictionary and exception queue. Populate it only after the seller can reproduce the event, population and evidence path. This prevents a polished chart from concealing unmatched orders, late corrections or incompatible state meanings.

The specification was researched on 6 September 2026 for one fictional England seller. It contains no counts, rates, target lines or trends.

Write the decision header

Name the legal seller, authorised marketplace account, approved product population, source-system version, reporting period and Europe/London timezone. Add the decision owner and the actions permitted by the page: investigate, correct, pause, roll back or release within a stated boundary.

Do not import an official statistic as a local target. The ONS internet-sales dataset describes retail activity within its own published scope, not marketplace-software records or this seller's conversion.

Complete the blank dictionary

Create one row per measure. Do not merge product, stock, order, payment, fulfilment and settlement events.

Field	Required entry
Decision and owner	[blank]
Exact event and state transition	[blank]
Eligible population and denominator	[blank]
Numerator or other unit	[blank]
Clock, timezone and maturity cutoff	[blank]
Source, query, schema and definition version	[blank]
Identity and deduplication rule	[blank]
Late, missing and excluded records	[blank]
Correction status and uncertainty	[blank]
Access, retention and evidence owner	[blank]
Threshold source and response	[blank]

The Government Data Quality Framework stresses fitness for purpose, metadata and communication of quality issues for government data. Treat it as a methodological reference only. The merchant must define its own evidence and authority.

Put exception queues first

The first panel should show unresolved records, not an aggregate score. Separate queues for a product change lacking rendered-offer verification, conflicting stock, an order without a matching payment state, a captured payment without later settlement, a return without a resolved refund, and a dispute without an owner.

Add independent queues for a safety instruction, a privacy choice that conflicts with recorded device access, a privileged-account change without authorisation and a financial mismatch. NCSC secure online-service guidance treats logging, security monitoring, transaction monitoring and incident management as distinct concerns. Its guidance does not certify this dashboard.

Each queue needs source freshness, oldest eligible event, correction version, accountable owner, next action and restart evidence. Suppress the summary when an underlying definition or reconciliation is unresolved.

Reconcile before displaying money

Keep order placed, accepted, authorised, captured, fulfilled, cancelled, returned, refunded, disputed and settled apart. A money panel must state currency, gross or net basis, refunds and disputes, accounting period and VAT treatment. HMRC's VAT record guidance describes records required of VAT-registered businesses but does not decide this seller's transaction treatment. Obtain accountant and VAT review.

Show provenance beside every value

Display query and definition versions, extraction time, latest eligible event time, missing-record status and correction note. Keep a link to the stored evidence ID, not a mutable screenshot alone. A supplier-reported field must retain that label; a rendered-state inspection must identify who inspected what version.

Privacy permission and analytic validity remain separate. The ICO's storage and access technologies guidance provides the PECR context for user-equipment operations. It does not make a dashboard event complete or representative.

Finish with a controlled decision

The decision panel records GO, INVESTIGATE, CORRECT, HOLD or ROLLBACK, the exact evidence version and unresolved limitations. Leave all buyer thresholds blank until authorised. Re-open the definition after schema changes, marketplace updates, accounting changes, safety action, privacy configuration changes or evidence expiry.