Reports → Dashboard uses the Gauge icon. It is an RPC-backed current-data summary for the active tenant, the signed-in user’s visible locations, the selected Day/Week/Month/Year, and URL-backed product filters. It is not scoped to the operating-context register: excludedRegisterIds is null. Most KPI cards display an “Open … report” button that currently has no navigation handler; only the explicit Open status report, Open center, customer-account collection rows, product quick view, customer profile, and recent-receipt links are working drill paths on this screen. The approved Harbor & Hearth Dashboard capture was rejected because it remained in a missing-report/location loading state.
Step by step
- Go to Reports → Dashboard, identified by the Gauge icon. Confirm the active business in the app context. Do not assume the selected operating register limits the dashboard; the dashboard sends the permitted location IDs but no register exclusion/filter.
- Wait for the initial dashboard response. A full-page spinner means the first retail-dashboard RPC is loading. Dashboard data did not load prints the request error and offers Retry dashboard. Dashboard is loading means no normalized response exists yet and offers Load dashboard. Dashboard needs a retry is a render-error boundary, not a data conclusion.
- Set View to Day, Week, Month, or Year. Day covers the selected local day; Week starts Monday; Month covers the selected calendar month; Year covers a prior full year or the current year through today. Comparisons use Previous day, Previous week, Previous month, or Previous year respectively.
- Use the left/right arrows to move one period. Next is disabled for the current period. Choose the date label to pick a day inside the desired period, jump by month/year from 2000 through the current month, or choose Today to return the anchor to now without changing Day/Week/Month/Year mode.
- Use Location to select among locations visible to the signed-in user. With no selection, the RPC receives null and represents all visible locations. Invalid or unauthorized location IDs from a shared URL are removed after the location list loads. Confirm the displayed location count/name before comparing totals.
- Understand the URL state. View, anchor date, selected locations, Product movement sort/direction, and product Brand/Category/Supplier/Tag filters are written into the dashboard URL. Clear filters resets to Day, today, all visible locations, Product Revenue descending, and no product attributes. It does not change tenant or register context.
- Wait for Updating to finish after a filter change. The query can temporarily retain the previous response as placeholder data while fetching the new scope. Never copy a number mid-update without rechecking the final date/location label. Desktop prefetches adjacent periods; mobile does not.
- Review Interaction reports to finish before using interaction conversion metrics. The queue selects up to 40 newest tenant sales with no primary interaction, excludes only voided and refunded statuses at the query level, applies location scope and configured receipt-prompt rules, then shows at most 20. It is a work queue, not a complete exception report.
- For each missing-report row, confirm receipt number, customer/no customer, location, register, updated time, status, and total. Choose Log to open the sale-linked interaction form. Save one accurate interaction, close the dialog, and verify the queue/sales data refresh. Do not log a made-up interaction merely to clear the badge.
- Choose Refresh in the missing-report panel to refetch both prompt settings and queued sales. No missing interaction reports means none survived this limited/configured query; it does not prove every historical receipt has interaction context.
- Read Interactions for the selected period and location scope: Logged, Won, Lost or left without buying, Sale / save, No sale/save, and recent visible activity with owner/location and Won/Lost/Saved/Open classification. Choose Open center for the working detailed route. An interaction-summary error is isolated and does not invalidate the retail RPC totals.
- Read Revenue status first. Billed revenue is Completed + completed layaway revenue plus open Customer Account/on-account and layaway balances. Completed / collected is closed new-sale revenue plus Customer Accounts payments collected by payment date; it can therefore differ from billed revenue.
- Open customer balances is revenue from on-account and layaway receipts still open. Excluded is calculated as the nonnegative remainder of the maximum of current KPI revenue or summed receipt-status revenue, less billed and collected-account components; it is labeled saved, voided, cancelled, or incomplete activity. Reconcile unusual residuals in Sales Reports rather than treating the label as exact row-level proof.
- Choose Open status report for the working status/revenue Report Center route. When Customer Accounts payments collected is positive, expand it to see linked receipts with customer, location, payment methods/count, and collected amount; choose a row to open that receipt. If collection detail is unavailable, the aggregate can still be included above.
- Review primary KPIs: Revenue, Sales, Customers, and Gross profit. Each shows current, previous-period value, absolute movement, and percentage change when calculable. A zero previous value with positive current displays +100%; two zeros display No change. This is a display convention, not an infinite-growth calculation.
- On desktop, Revenue can show up to six location contributions and a sparkline. Switch its two-dot panel to Receipt status to view status breakdown; on mobile use the bottom dots or swipe horizontally at least 36 pixels. The headline Revenue value remains the current KPI while the panel changes.
- Treat each KPI’s Open revenue/sales/customers/gross profit/discount/average report text carefully: these are plain buttons with no click handler in the current component. They do not open Report Center. Use the explicit Open status report or go to Reports → Report Center manually with the same date/location scope.
- Review Discounts given, Discount rate, Average ticket, and Avg. items / sale against the previous period. Gross profit depends on the cost basis returned by the dashboard RPC; missing/zero product cost can distort it. Validate finance decisions in the detailed report and source product costs.
- Use Product movement only when products_sold is returned. Summary tiles show filtered Units sold, Product revenue, Avg item revenue, and Discounts. Sort by Revenue, Qty Sold, or Discounted; choosing the active sort reverses direction. Results are paged ten at a time.
- Filter Product movement by Brand, Category, Supplier, and Tag. The dashboard matches the RPC product row to the current catalog by SKU for filtering; rows lacking a matching catalog SKU can disappear when any attribute filter is active. Product quick view resolves by product ID, then SKU, then normalized name. Verify the exact product/variant before editing elsewhere.
- Read each product row as Qty Sold, Revenue, Revenue lost/discount, and average discount percent derived from discount divided by revenue plus discount. Product filters affect Product movement totals/list only; they do not refetch or narrow the top Revenue/Sales/Customer KPIs.
- On desktop only, Revenue by day renders when trend rows exist. Mobile intentionally suppresses the daily chart and KPI sparklines. A chart render failure can leave an empty bounded area while other dashboard sections continue; do not infer zero revenue from a missing chart.
- Payment methods appears only when rows exist and shows transaction/use count by method; although the RPC also returns amount, this dashboard section displays count only. Do not reconcile tender dollars from these tiles. Use payment/register reports.
- Top salespeople appears only when rows exist and shows user, revenue, sale count, items sold, and average sale value. It reflects the returned selected period/location scope and is not commission/payroll authority. Confirm effective user attribution, returns, account collections, and report rules before compensation decisions.
- Recent transactions appears only when rows exist, ten per page. Choose the receipt number to open /sales/receipts/<sale ID>. Choose a named non-walk-in customer to open the customer profile. Walk-in, item count, transaction time, total, and cashier are summary evidence; opening a receipt must not change the surrounding receipt list’s scope.
- Use Clear filters and reconstruct the intended scope when totals look wrong. Then compare Revenue status with the explicit status report, Customer Accounts collection receipts, source receipts, register reports, payment reports, product costs, and interaction center. Record tenant, date mode/anchor, location IDs, URL filters, update state, and receipt IDs when escalating.
- No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth Dashboard inspection remained in a missing-interaction/location loading state, so the invalid capture was removed rather than shown as a completed dashboard or replaced with another screen.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Gauge icon | Exact CentriPOS Reports navigation and mobile-header icon for Dashboard. |
| Day / Week / Month / Year | Calendar scope; weeks begin Monday and current year runs through today. |
| Previous period comparison | Previous day, Monday-based week, month, or year aligned to the selected mode. |
| Date picker | Choose an anchor date and jump from 2000 through the current month; future dates are unavailable. |
| Location | Signed-in user’s visible locations; no selection means all visible locations. |
| No register filter | Dashboard RPC receives no excluded-register IDs and is not limited by the operating-context register. |
| URL filters | View, date, locations, product sort/direction, brands, categories, suppliers, and tags. |
| Updating | New scope is fetching while prior placeholder data may remain visible. |
| Clear filters | Day/today/all visible locations/product revenue descending/no product attributes. |
| Interaction reports to finish | Limited prompt-configured queue of missing primary interactions, at most 20 from 40 queried sales. |
| Log | Opens the sale-linked interaction capture dialog and refreshes queue/sales after close. |
| Interactions | Logged, won, lost, sale/save, no sale/save, and recent classified activity. |
| Open center | Working link to Communications interaction overview. |
| Billed revenue | Completed and completed-layaway revenue plus open on-account/layaway revenue. |
| Completed / collected | Closed new-sale revenue plus Customer Accounts collections by payment date. |
| Open customer balances | Open on-account and layaway revenue. |
| Excluded | Nonnegative residual labeled saved/voided/cancelled/incomplete; validate in status report. |
| Open status report | Working Report Center link for status measured by revenue. |
| Customer Accounts payments collected | Expandable receipt-level collection rows when available. |
| Revenue / Sales / Customers / Gross profit | Current and previous-period KPI cards. |
| Revenue card panels | Location contribution or receipt-status detail selected with dots/swipe. |
| Open … report KPI buttons | Currently inert plain buttons with no navigation handler. |
| Discounts given / Discount rate / Average ticket / Avg. items per sale | Secondary period KPIs and comparisons. |
| Product movement | RPC products_sold summary, sorting, catalog-SKU attribute filtering, ten-row pagination, and quick view. |
| Product filters boundary | Narrows Product movement only, not headline dashboard KPIs. |
| Revenue by day | Desktop-only bar chart. |
| Payment methods | Count only on this screen even though amount exists in returned data. |
| Top salespeople | Revenue, sale count, items, and average sale; not payroll authority. |
| Recent transactions | Ten-row pages with working receipt and eligible customer-profile links. |
| Dashboard data did not load | RPC error with Retry dashboard. |
| Dashboard is loading | No successful normalized response yet with Load dashboard. |
| Dashboard needs a retry | Render-error boundary with retry that remounts the view. |
| No public screenshot | Rejected real Harbor & Hearth loading-state capture; no substitute or fabrication. |
Expected result
The dashboard has finished updating and its tenant, Day/Week/Month/Year, anchor date, and visible-location scope are confirmed; billed, collected, open, excluded, KPI, interaction, product, payment-count, staff, and recent-receipt summaries reconcile to the working detailed routes and source records, while product-only filters and inert KPI report buttons are not mistaken for global filters or drilldowns.
Troubleshooting
- Check the date range, timezone, locations, registers, statuses, and saved-view filters first.
- Refresh after the underlying transaction has finished posting.
- Open the source sale, payment, movement, or closure when a total needs transaction-level proof.
CentriPOS API explorer · API Center administration