Network → Reports uses the Bar Chart 3 icon but mounts the same SalesReportView used by the main Reports area, with its default Sales report title and “Analyze your sales with personal or company-wide report views” subtitle. No network-mode or parent-HQ identifier is passed. Every report, breakdown, receipt drill-down, saved view, column layout, export, print, and email operation uses the current active tenant ID. A parent/child relationship or the Network tab itself does not aggregate child businesses. The exact Harbor & Hearth capture was rejected because multiple report metrics remained loading; no fabricated replacement is published.

Before you beginConfirm the organization and participating locations. Network actions may affect more than one storefront.

Step by step

  1. Go to Network → Reports using the Bar Chart 3 icon. Confirm the active CentriPOS business in the operating-context bar before interpreting the page. The route location does not change the data tenant.
  2. Read the heading carefully. The component displays Sales report—not Network report—and the same subtitle used by the ordinary Sales Reports workspace. This is the clearest visible indication that the shared report builder is mounted unchanged.
  3. Understand the tenant boundary. The report hooks send the active tenantId to the sales-report RPC. An Enterprise HQ sees that HQ tenant’s own sales rows; a child organization sees its own tenant rows; a proxied context uses the proxied tenant. Related child storefronts are not automatically unioned.
  4. Do not treat a Location filter as a storefront/network selector. Location IDs belong to the active tenant’s report scope. They narrow that tenant’s locations and cannot add another child business.
  5. For an actual cross-business question, use a verified network-aware screen/report or run the same saved configuration separately in each authorized storefront and reconcile the exports with explicit tenant labels. Never sum overlapping or differently scoped totals without confirming definitions.
  6. Choose Report type from Sales summary, Receipt status, User, Location, Register, Customer, Customer group, Product, SKU name, Brand, Supplier, Product category, or Tag. These are the same choices and computations as the main Sales report.
  7. Choose one or more supported Measures. Available values depend on the report type and include revenue variants, counts, averages, discounts, returns, customer attachment, tax, tips, cost/gross profit/margin, first/last sale, items, and supported e-cart measures. Cost-sensitive values remain subject to role visibility.
  8. Set the exact Date preset or custom range and confirm the time boundaries. Choose a comparison only when the selected report and period support it; a comparison is not a second tenant/network scope.
  9. Use Include and Exclude chips for the supported active-tenant dimensions. Location is handled as report location IDs; other chips are passed as include/exclude filter maps. An exclusion can materially change receipt and line visibility, so read every chip before sharing a result.
  10. Use Advanced report controls to arrange period columns, rows, nested rows, selected receipt/detail columns, gift-card inclusion, and required row details as supported. Month breakout is offered when the range spans months. Sort rules affect presentation, not tenant scope.
  11. Switch between Table and Chart only for supported chartable measures. Read selected range, comparison, row groups, time buckets, totals, and empty/unassigned groups together; a chart is a rendering of the same active-tenant result.
  12. Open a total/row receipt drill-down to inspect the underlying permitted sales. It reuses the report’s date, location, include/exclude, time bucket, period, parent group, and group filters and returns only a limited receipt set. Use receipt detail to validate a representative amount without assuming it proves an entire network.
  13. Use Saved Views to store the current report query for this tenant and route. Personal views belong to their creator; Shared view management requires authority. A saved view re-runs against current data and is not a frozen result or cross-store template by itself.
  14. Use saved Column layouts only for the active tenant/profile and compatible report type. A column layout changes selected detail columns, not measures, filters, ownership, or tenant scope.
  15. Use Export CSV only after verifying business, report type, measures, dates, comparison, include/exclude chips, location scope, arrangement, gift-card setting, and data columns. The generated export represents the current report model, not an automatic network consolidation.
  16. Use Print to review orientation, margins, optional chart, business label, selected range, view status, measures, columns, prepared-by identity, table, and totals before the system print dialog.
  17. Use Email only with approved recipients and current tenant data. The workflow sends a branded https://pos.getcentri.com report link and supports immediate or scheduled delivery where configured. Review saved schedules separately; do not send one storefront’s private report as if it were an anonymized network report.
  18. If the report remains loading or errors, do not substitute data from Network Sales, a local report, or an invented screenshot. Preserve the active tenant, route, report type, date range, filters, and safe error state for support.
  19. To compare the shared component itself, open Reports → Sales Reports with the same active tenant and query. The results should match because both routes use the same report implementation; any difference should be investigated as URL/saved-view/context state, not presumed network aggregation.

Screen and contract reference

Control or areaWhat it means
Bar Chart 3 iconExact Network navigation icon for Reports.
Sales report headingDefault heading of the shared SalesReportView mounted at /network/reports.
Active tenant boundaryEvery report RPC receives the current tenantId; no parent-HQ or network-union argument is supplied.
Network tab boundaryNavigation placement only; it does not change the report’s data plane.
LocationActive-tenant location IDs only, not child-storefront selection.
Report typeSales summary, Receipt status, User, Location, Register, Customer, Customer group, Product, SKU name, Brand, Supplier, Product category, or Tag.
MeasuresReport-type-dependent calculations such as revenue, counts, averages, discounts, returns, customer, tax, tips, costs, profit, margin, items, dates, and supported e-cart metrics.
Date / comparisonCurrent and optional comparison periods within the same active tenant.
Include / ExcludeSupported active-tenant receipt and line filters; no relationship-based network expansion.
Advanced report controlsPeriod columns, row/nested-row grouping, detail columns, gift-card inclusion, and row-detail requirements.
Table / ChartTwo presentations of the same scoped report result.
Receipt drill-downLimited underlying sale set using the current report’s date, location, filter, period, and grouping state.
Saved ViewReusable current-tenant report query with Personal/Shared ownership and fresh data.
Column layoutReusable active-tenant/profile detail-column selection for a compatible report type.
Export CSVWorking export of the current report model; not a network consolidation.
PrintPrintable branded report model with reviewed chart, layout, metadata, table, and totals.
Email / scheduleBranded report-link delivery for the active tenant; recipients and schedules remain sensitive.
Cross-business methodUse a verified network-aware surface or separately labeled per-store reports and reconcile deliberately.
No exact screenshotThe Harbor & Hearth /network/reports capture was rejected because revenue, payment, customer-balance, and lead metrics remained loading; no invented image is used.

Expected result

The route is correctly treated as the ordinary Sales report for the active tenant—not a network union—and its report type, measures, dates, comparison, active-tenant locations, include/exclude filters, arrangements, receipt drill-down, saved view, export, print, and email evidence reconcile with the equivalent main Reports route.

Troubleshooting

  • Confirm the organization and participating locations before comparing, publishing, or transferring.
  • Keep local and network-level records distinct when reviewing inventory or catalog values.
  • Check whether your network role allows the action shown in the guide.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.