Web app example · a store owner reviewing performance
This dashboard is for a store owner who wants a readable view of manually entered sales figures. Summary cards and a 30-day revenue chart put revenue, orders, average order value and refunds in one place.
Because the figures are entered by hand, consistent definitions matter. Decide when each day is recorded, how refunds are counted, and who checks entries before using the dashboard to discuss business performance.
Cleo is opening to founders in small batches. Join the waitlist and we'll save your spot.
Updated
A manual store analytics dashboard records daily figures and summarizes revenue, orders, average order value and refunds over 30 days. Use the sample to name the audience, the main action, and the smallest useful first version. Cleo HQ then helps turn your own brief into a product plan and a working build.
Choose whether the calculation uses gross or net sales and which orders count in the period, then apply that rule every day. A number is hard to compare if its meaning shifts between entries. The example includes average order value among its KPI cards; document the formula in ordinary language so anyone entering or reviewing figures can interpret it.
It can show whether recorded revenue rises, falls, or varies across recent days, which may help the owner ask better follow-up questions. A chart alone cannot explain the cause of a change or establish a trend across a whole year. The sample focuses on a 30-day window; compare it with known promotions, holidays, or stock changes before drawing conclusions.
Manual entry can provide a simple starting point when a shop wants to review a small set of figures without building a broader reporting system. It also creates a responsibility to enter complete, consistent data. The example includes daily entry and store settings; assign an owner and a routine for checking missing days or correcting an accidental value.