Network → Network Sales uses the Receipt icon. This screen has different visibility tiers, and its headline metrics do not use the same filter set as its transaction list. Network KPI cards and charts currently respond only to Date; Store, Customer, receipt/note/product search, and Status filter only the transaction query. The exact Amelia Grant Harbor & Hearth /network/sales capture was rejected because it remained loading and the surface can expose customer and receipt data. No fabricated or mismatched screenshot 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 → Network Sales using the Receipt icon. Confirm the current operating tenant and whether it is an Enterprise HQ, child organization, Agency/Platform context, or proxied storefront before interpreting anything. A child organization queries its parent HQ network identity.
  2. Understand the access tier. A non-agency user can access permitted network transactions. HQ Owners and platform super admins in a non-agency HQ context can also see network KPI cards and charts. Agency/Platform owners see anonymized Platform Metrics and no individual transaction rows; a platform super admin can see the permitted platform metrics and transaction surface.
  3. Do not infer broader access from a hidden card or missing row. Role, tenant type, parent relationship, and server policies determine visibility. Agency users are told that individual transactions are not accessible at platform level and to proxy into a specific store for transaction details.
  4. Set Date first. Presets are Today, 7 days, 30 days, 90 days, and 1 year; the custom picker provides separate From and To calendars plus Clear dates and Apply. With no dates, the query passes no explicit date boundary. Verify the displayed dates and reporting timezone before comparison.
  5. For HQ KPI access, read Total Revenue, Total Sales, Avg Ticket, and Active Stores. These values come from the network-stats query for the HQ identity and current Date only. They do not recalculate for Store, Customer, receipt/note/product, or Status filters below.
  6. Read Payment Types as date-scoped tender amount, or No payment data yet when empty. Read Top Stores by Revenue as the first five returned store rows in its date-scoped chart, or No store data yet. The display formats KPI currency as USD with no cents; reconcile exact amounts from source receipts/reports before financial use.
  7. For Agency/Platform metrics, read the Anonymized badge and the visible Platform Revenue, Platform Sales, Avg Ticket, Active Stores, Total Storefronts, Unique Customers, CentriPay Volume, and CentriPay Txns cards when returned. Payment Methods (Platform-wide), Revenue Trend, and Sales by Status are aggregate-only. The period buttons apply only the date range and clear selected stores.
  8. Treat KPI and transaction evidence as separate scopes. A transaction Store filter can narrow the rows while KPI cards remain unchanged because the KPI request receives only Date. Never claim the filtered rows reconcile to a card unless you independently run a matching report with the same exact scope.
  9. Under Transactions on desktop, choose one or more permitted Stores, one Customer, optional Receipt, note or product text, and Status. Status choices are All statuses, Completed, Returned, Exchanged, Layaway, On Account, Saved, and Voided.
  10. Transaction filters update the URL and refetch as each value changes. The visible desktop Search button currently has no click handler and does not perform a separate submission. Do not tell users they must click it, and do not use the button as evidence a fresh query ran.
  11. On mobile, type in Search receipt, product, customer and open the Sliders Horizontal filter sheet for Date, Customer, Store, and Status. Apply Filters only closes the sheet; the selections already update the query as they change.
  12. Use Clear all filters to restore Status to All and Stores to none while also dropping Customer, search text, and dates from the filter object. Confirm the visible result afterward; clearing filters broadens the request only within the user’s permitted network.
  13. Read Displaying <n> sales on desktop or <n> sales on mobile as the number currently loaded, not necessarily the total matching the server. Results load in pages of 50. Choose Load more until the required result appears; realtime sale changes can invalidate and refresh the query.
  14. On desktop, each row shows Receipt and date/time, Store, Customer, Sold by, Total, Status, optional note, expand chevron, and a return icon. A missing customer, seller, or store displays a dash rather than proving the source record never had that relationship.
  15. Choose a customer name to open the customer profile panel. This exposes customer data and is not a harmless navigation preview; verify the correct network/store customer before editing or communicating.
  16. Choose a row to open Sale Detail. Desktop writes the sale ID into /network/sales/<saleId>, retains current query parameters, and scrolls the row into view. Mobile opens the detail in a bottom sheet without changing to that sale-detail route.
  17. Review the full sale detail before any action: tenant/store, location/register/session, receipt, customer, seller, line items, payments, totals, status, note, fulfillment, returns, integrations, and other evidence available to the role. Network context does not make every receipt action appropriate.
  18. Use the return icon, Process Return, or Edit only when the receipt is eligible and the effective user has authority. These launch the same operational return/edit workflows used by receipt detail; verify tenant, location, register, quantities, payment/refund path, and post-action audit evidence.
  19. Treat No sales found across the network as a result for the current filters and permissions. Clear the likely filter, confirm the network identity/date, and load the appropriate storefront context before reporting missing data.
  20. Do not use Export. The desktop Export button is presently rendered without a click handler, so it does not download the filtered result. Use an approved working report/export surface instead and recheck this guide after the product implements an export action.
  21. Protect customer and financial data. Do not place transaction rows, customer profiles, receipt details, returns, or exported network data in public screenshots. The approved manifest intentionally contains no exact Network Sales image.

Screen and contract reference

Control or areaWhat it means
Receipt iconExact CentriPOS navigation icon for Network → Network Sales.
Network identityHQ tenant used for stats and permitted transaction search; a child organization resolves through its parent HQ.
Permission tierControls whether the user sees network KPIs, anonymized platform aggregates, individual transactions, or a combination.
AnonymizedAgency/Platform aggregate label; individual transactions remain unavailable to non-super-admin agency users.
DateOnly filter shared by the KPI/stat query and transaction query.
Today / 7 days / 30 days / 90 days / 1 yearPreset date ranges applied immediately and stored in the URL.
Custom From / ToSeparate calendar boundaries for the query; verify displayed dates and timezone.
Total RevenueDate-scoped network aggregate formatted as whole-dollar USD in this view.
Total SalesDate-scoped sale count returned by network stats.
Avg TicketDate-scoped network average formatted as whole-dollar USD.
Active StoresDate-scoped contributing-store count returned by network stats.
Payment TypesDate-scoped payment-amount chart; it does not follow transaction-only filters.
Top Stores by RevenueDate-scoped chart showing up to the first five returned store aggregates.
Platform MetricsAgency/Platform aggregate cards for revenue, sales, stores, customers, and CentriPay activity when authorized.
Payment Methods (Platform-wide)Aggregate platform tender amounts without transaction disclosure.
Revenue TrendDate-scoped platform daily revenue bars.
Sales by StatusPlatform aggregate counts for Completed, Returned, Voided, Layaway, and Account Sales.
StoreMulti-store transaction filter only; it does not recalculate KPI cards.
CustomerOne customer-ID transaction filter and profile-panel entry point.
Receipt, note or productTransaction search sent to the network-sales search routine.
StatusAll, Completed, Returned, Exchanged, Layaway, On Account, Saved, or Voided transaction filter.
Desktop Search buttonCurrently inert; filters already update and refetch on change.
Mobile Apply FiltersCloses the filter sheet; selections already applied while changing.
Clear all filtersResets the transaction and date filter object to All statuses with no stores.
Displaying / sales countCurrently loaded rows, not guaranteed full match count.
Load moreFetches the next page of up to 50 permitted sales.
Sale rowReceipt/time, store, customer, seller, total, status, note, detail toggle, and return entry point.
Desktop sale route/network/sales/<saleId> with current query parameters preserved.
Mobile sale sheetBottom-sheet detail without the desktop expanded-sale route.
Customer profileSensitive customer detail panel opened from the linked name.
Process Return / EditPermission- and lifecycle-sensitive receipt actions from Sale Detail.
Export buttonCurrently rendered without a download handler; do not rely on it.
No exact screenshotThe Amelia Grant Harbor & Hearth /network/sales capture was rejected for an unresolved loading state and sensitive transaction exposure; no invented replacement is used.

Expected result

The network totals and storefront rows match the selected organization, date, timezone, locations, channels, and statuses, and drill-down sales explain the aggregate.

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.