oppiOS / Performance
Takings, labour, and the work.
From your own trade.
Nothing to export on a Friday.
Track revenue performance, trends, and key metrics
9.0% from previous
4.1% from previous
Insights will appear when data is available
Breakdown of revenue by source category
This section will be populated when data is available
Insights will appear when data is available
Analysis of highest revenue periods
This section will be populated when data is available
Revenue
The revenue view charts the venue's trading from its aggregated data: a line over the range you choose, bars by day of week, so a slow Tuesday is a pattern you can see rather than a feeling you have.
Labour
The labour view reads the same aggregated record from the roster side. Hours and cost over the range, alongside the revenue they were rostered for.
The record
OPPI aggregates POS transactions and shifts into a clean, analysable record on the sync cadence. Performance reads it. So does the forecast, the Immune System and oppiGPT. When you ask a question here and there, it is the same numbers answering.
Operations
The operations view brings the operational side of the record into the same frame, over the same date ranges. Some sections of these views are still being built and say so on the screen; what is drawn is drawn from real data.
What it does
Trading over a date range and by day of the week.
Hours and cost from the roster side of the record.
The operational record over the same ranges.
The same filters across every view.
Per-person performance and intelligence tabs on each staff profile, in Human Resources.
Last week's revenue by day beside the labour that served it.
Ask oppiGPT and get an answer drawn from the same record these charts read.
Is it this Tuesday or every Tuesday? The day-of-week view answers.
The numbers, without the export.
Revenue, labour and operations from the record the whole system shares.