Skip to main content
The Overview dashboard brings the selected shop’s operational summary into one page. Use it for a quick read, then open History or Analytics when you need order-level or deeper reporting detail.

​
Who can do this?

The complete dashboard data set is for Owners and Managers. Several underlying summary and staff endpoints enforce those roles. Staff may see an Overview navigation link, but link visibility does not override API authorization.

​
Where to do it

Choose Overview in the Management Admin App and confirm the correct shop in the shop picker.

​
What the dashboard shows

  • Sales and an area chart for the selected reporting window.
  • Orders, including a comparison trend where previous-period data exists.
  • Average order value, calculated from revenue and order count.
  • Average rating, based on available order rating data.
  • Team information, including role labels and ratings when present.
  • Upcoming or relevant booking information for the shop.
The page formats currency, dates and numbers from the active shop context. Empty cards or charts can mean there are no qualifying records in the selected period; they do not automatically indicate an error.

​
Use the dashboard safely

  1. Select the shop first.
  2. Select a reporting period.
  3. Read the headline value and its comparison together.
  4. Use History to inspect the orders behind a total.
  5. Use Analytics for domain-specific breakdowns available to Owners and Managers.

​
Platform notes

This dashboard is the management-web summary. POS and guest apps create operational records but do not show this same dashboard. A payment or booking may take a short data refresh before it appears in an aggregated card.

​
Market notes

GB shops use their configured currency and tax terminology; German shops use their own locale, currency and tax terminology. The meaning of the operational metrics is shared.

​
Troubleshooting

If one card is empty while others loaded, check that card’s own loading or empty state and the selected period. If multiple protected sections fail for Staff, treat it as the documented role boundary rather than zero business activity.