Insights and Revenue
Insights gives managers a read-only view of business performance for the current workspace. It combines revenue, transactions, bookings, top services and products, payment distribution, comparisons, and activity timing into one operating dashboard.
Payments is the money operations surface. Insights explains what happened; Payments is where operators review the payment ledger, connected-account status, payouts, and payment actions.
Surface Map
Insights
Console surface: Insights
Primary job: Read business performance, trends, top services and products, payment methods, comparisons, and heatmaps.
Payments
Console surface: Shop > Payments
Primary job: Manage payment visibility, Stripe Connect status, transactions, payouts, refunds, and manual payment workflows.
Legacy revenue route
Console surface: Shop > Revenue
Primary job: Redirects to Shop > Payments. Do not link new docs or UI to the legacy route.
Backend analytics
Console surface: Shop analytics APIs
Primary job: Provides workspace-scoped performance, trends, comparisons, distributions, heatmap data, and CSV export.
Use Insights for analysis. Use Payments when the operator needs to act on money movement.
Visibility
Insights is a manager-level console surface. Owners, admins, and managers can open the page for the cookie-selected workspace.
Manager visibility rules:
- Manager-level operators see workspace performance rather than customer-facing payment credentials.
- Insights should not expose payment setup secrets or connected-account administration.
- Staff who are not in the manager tier should use the task-specific surfaces they are allowed to access.
- Payments remains the authoritative route for payment operations and payment status checks.
If an operator can open Payments but not Insights, verify workspace membership and role before checking analytics data.
Periods
The Insights page has one selector for most analytic windows.
7 days
Used by: Trends, top services and products, payment methods, heatmap, CSV export, and weekly comparison.
14 days
Used by: Trends, top services and products, payment methods, heatmap, CSV export, and monthly comparison.
30 days
Used by: Trends, top services and products, payment methods, heatmap, CSV export, and monthly comparison.
90 days
Used by: Trends, top services and products, payment methods, heatmap, CSV export, and monthly comparison.
The performance summary at the top of the page uses a fixed this-month window. It is a current snapshot, not a reflection of the selected trend period.
All money values are formatted in the workspace currency. Backend values travel as integer cents before display.
Overview Tab
The Overview tab answers whether revenue and demand are moving in the right direction.
Revenue this month
What it shows: Current-month revenue with period label and delta when available.
Operator use: Quick check for month-to-date performance.
Sales and bookings or transactions
What it shows: Count of completed sales and booking activity.
Operator use: Understand demand volume without reading the ledger.
Average ticket
What it shows: Average revenue per sale or booking.
Operator use: Spot pricing, product mix, or booking mix changes.
Cash and manual collected
What it shows: In-person manual tender recorded this month, when present.
Operator use: Confirm manual collection is being captured without double-counting revenue.
Trends
What it shows: Revenue time series for the selected period.
Operator use: See daily movement and identify spikes or gaps.
Top services and products
What it shows: Ranked revenue and quantity list.
Operator use: Identify what is carrying the business in the selected window.
Empty states are expected for new workspaces or periods with no activity.
Distribution Tab
The Distribution tab explains how revenue and activity are distributed.
Period over period
What it shows: Revenue, transaction count, and average ticket compared with the previous window.
Operator use: See whether the current period is up or down without exporting data.
Payment methods
What it shows: Succeeded POS transaction revenue and count by payment method.
Operator use: Understand tender mix, card/manual usage, and operational habits.
Activity heatmap
What it shows: Day-of-week by hour activity intensity.
Operator use: Plan staffing, service availability, and operating hours around real demand.
For comparison cards, the 7-day selector compares against the previous 7 days. Wider selectors use the backend monthly comparison window.
The hourly heatmap combines POS transaction timing with booking appointment timing. POS sales are bucketed by when the transaction was created; bookings are bucketed by when the appointment is scheduled to happen. That makes the heatmap useful for staffing, not just accounting.
Exports
Use Export CSV on the Insights page to download the selected period.
Export behavior:
- The export follows the active period selector.
- The browser receives a CSV attachment from the backend.
- Rows include transaction date, transaction ID, amount, fees, net amount, payment method, employee, and status.
- The export is workspace-scoped and should be treated as operational financial data.
- Large or custom reporting needs should use a narrower date range or a dedicated finance workflow rather than screenshots.
The Insights export is for analysis. It does not replace the Payments surface for transaction actions, refunds, account requirements, or payout review.
Payments Relocation
Revenue operations moved to Shop > Payments. The old Shop > Revenue route permanently redirects to Shop > Payments so bookmarks keep working, but new operator guidance should point to Payments.
Use Payments for:
- Connected payment account state.
- Payment ledger review.
- Recent transactions.
- Payout and requirement checks.
- Refund or payment action workflows.
- Manual payment recording.
Use Insights for:
- Revenue trend analysis.
- Period comparison.
- Top services and products.
- Payment-method distribution.
- Hourly activity planning.
- CSV analysis exports.
Troubleshooting
Insights is unavailable
Confirm the operator is owner, admin, or manager for the selected workspace
Totals do not match a payout
Compare against Payments. Insights is an analytics view and may group by analytic period rather than payout timing
Payment methods are empty
Confirm there are succeeded POS transactions in the selected period
Heatmap is empty
Confirm the selected period has POS activity or scheduled booking activity
Export fails
Retry with the selected preset period, then narrow the range if the dataset is too large
A link to Shop > Revenue appears
Replace it with Shop > Payments; the old route only exists as a redirect
Update internal notes, launch packets, and support references so operators do not keep following the retired route.