Single-basis indicator
Ticket, margin, and productivity calculated the same way across the entire chain.
Platform · Data layer
Analytics
The same indicator, the same calculation basis, across the entire chain.
The challenge
Each manager arrives at the meeting with their own spreadsheet and their own number. The same indicator — average ticket, margin, productivity — means one thing at one store and something else next door, because each one calculates it its own way. Comparing turns into arguing about methodology before arguing about results.
What this costs
The results meeting starts by reconciling numbers, not by making decisions. The location ranking doesn't hold up, because the basis keeps changing. And the decision that depended on the data arrives after the month it was meant to correct.
Indicators are calculated on the Data Lake, with the same definition across the entire chain. One store's number becomes comparable with another's without reconciliation, and the discussion goes back to being about the result — not about where the number came from.
Layer 03
Ecosystem and data
It sits on top of the Data Lake, in the data layer: it draws from the single repository and returns a comparable indicator, both in the EPOC dashboard and exported to the client's corporate BI.
What this delivers
Comparison across locations
A store ranking that holds up, because the methodology is the same for all of them.
Margin by item and by store
Recipe card cost meets sale price, by product and by location.
Operational and management dashboard
The daily view for those who operate, and the period view for those who decide — from the same source.
Calculated on the Data Lake
The metric comes from the single repository, not from a manual export from each system.
Looker license for the client's BI
The chain's BI team gets a Looker Enterprise license over the operation's data — and whatever is already analyzed in Power BI, Tableau, or Qlik stays there.
Conversation with
- BI
- Corporate ERP
Where it applies
In operation
Fine dining
Nino Cucina
Floor service and margin control on the same platform.
The challenge
Keep the service sequence flawless without losing sight of the cost of each dish.
30tables
POS · KDS · Analyticsdeployed
Frequently asked questions
Do I need a separate BI tool to use Analytics?
Not for the essentials: there's an operational and management dashboard within the platform itself. For advanced analysis, the data is exported to the corporate BI the chain already uses.
Why do the numbers reconcile across stores here, when they didn't before?
Because the calculation is unified and comes from the Data Lake. Before, each store exported and built the metric its own way; here the definition is the same for all of them.
Does the margin factor in the dish's actual cost?
It factors in the recipe card cost matched against the sale price. The quality of the margin depends on the recipe card being kept up to date — which is what the inventory and recipe cards page covers.
Talk to a specialist
Your operation has grown. Is your technology ready?
How many locations, what stack is already running, what needs to be integrated, and what the rollout would look like.
