Change the seasonality metric and scope
Use the Tu restaurante performance report to compare seasonality by metric and account scope. The card lets operators switch between Precio total, Cuentas and Promedio por cuenta, then compare Total de cuentas del restaurante, Reservas and Sin reserva without saving preferences or changing restaurant data.
In this article
The seasonality heatmap helps a location manager compare when account value and account volume concentrate across the week. It is useful when reviewing service peaks before adjusting staffing, reservations handling or floor planning.
The controls work inside the existing restaurant report. Antylogic uses the datasets already returned by GET /reports, so changing the view updates the chart only; it does not create new metrics, edit tickets or call a write endpoint.
Before you start
- The user is signed in with an organisation and location selected, such as Harbor Demo Group and Harbor Soho for the GB documentation runtime.
- The user has at least one accepted location permission for report access: reports:view, tpv:view, tpv:use, catalog:view, reservation:view or staff:view.
- The restaurant performance report is available at /:orgId/:locationId/reporting/performance/restaurant and includes the seasonality heatmap-comparison block.
- For a useful heatmap, the selected report period should include active, non-void TPV tickets, ideally including both tickets linked to reservations and tickets without a reservation reference.
Instructions
- 1.
Open the restaurant performance report
Open Reporting and choose Tu restaurante for the active location. For capture work, the direct route is /:orgId/:locationId/reporting/performance/restaurant with a period that contains real ticket activity.
- 2.
Find the seasonality card
Scroll to Perspectivas sobre la estacionalidad. The default view uses Precio total with Total de cuentas del restaurante and draws the day-and-hour heatmap for the selected period.
- 3.
Change the metric
Use the segmented tabs to switch between Precio total, Cuentas and Promedio por cuenta. Precio total compares ticket totals, Cuentas compares ticket count, and Promedio por cuenta compares average ticket value in each populated cell.
- 4.
Change the account scope
Open the scope dropdown and choose Total de cuentas del restaurante, Reservas or Sin reserva. Total includes all active tickets, Reservas includes tickets with a reservation reference, and Sin reserva includes tickets without one.
- 5.
Read the heatmap
Compare Monday to Sunday and 00 to 23 hours. Each period has its own maximum value, so stronger colour indicates the busiest cells relative to that period. On web, hovering a cell shows the period, day, hour and formatted value.
- 6.
Leave without saving
No save action is required. The metric and scope are temporary report controls, and reopening the screen returns to the backend default metric and scope.
Validations and limits
- If no organisation or location is selected, the screen asks the user to select a location before consulting reports.
- If the user lacks every accepted report permission, the report query is not enabled and the screen shows a permissions message.
- The default metric is total and the default scope is Total de cuentas del restaurante.
- Only metric options with both key and label are shown, and scope options come from SeasonalityPayload.scope_options.
- The Reservas scope counts tickets linked to reservations, not reservations themselves.
- Changing metric or scope does not change the URL, does not persist a user preference and does not call a write endpoint.
- If a scoped dataset such as metric::scope is missing, the frontend falls back to the base metric dataset; if there are no matching tickets, the heatmap can render with little or no colour intensity.
Expected result
The operator sees the same seasonality report through a different metric and account scope, making revenue, account count and average account value easier to compare without modifying operational data.