Staff analytics is not about chasing employees — it is about helping everyone perform better. The difference between a mediocre server and a top seller can be 20-30 % in check average, and that difference usually comes from specific habits that can be taught.
Where to find the reports
Two reports:
KPI cards in the Staff report (3)
| KPI | Description |
|---|---|
| Active registers | Number of registers used in the period |
| Total tips | Sum of tips collected |
| Average tip per order | Tips/number of orders with tip |
Sales per register (table + bar chart)
Each server who logs in to their own register appears in the table:
| Register/Server | Orders | Sales | Avg order | Tips | Share |
|---|---|---|---|---|---|
| Anna | 180 | 72,000 | 400 | 6,800 | 24 % |
| Bengt | 165 | 58,000 | 352 | 4,200 | 19 % |
| Cecilia | 155 | 62,000 | 400 | 7,200 | 20 % |
| David | 210 | 67,000 | 319 | 3,800 | 22 % |
How to read the table:
Top sellers (avg order): Anna and Cecilia at 400 SEK avg order. They sell more per guest than the others.
Lowest avg order: David at 319 SEK. He has the most orders (210) but the lowest average. That means he is fast but not selling upsells (drinks, desserts, coffee).
Action: Let David shadow Anna and Cecilia one evening. Measurable target: Raise avg order from 319 to 380 SEK in 4 weeks.
Tip analysis (table + bar chart)
| Server | Orders w/ tip | Share % | Avg tip | Highest tip |
|---|---|---|---|---|
| Anna | 145 (of 180) | 80.6 % | 47 SEK | 300 SEK |
| Bengt | 98 (of 165) | 59.4 % | 43 SEK | 180 SEK |
| Cecilia | 128 (of 155) | 82.6 % | 56 SEK | 400 SEK |
| David | 102 (of 210) | 48.6 % | 37 SEK | 150 SEK |
How to read the table:
Tip stars: Cecilia has 82.6 % tip frequency and 56 SEK average tip. She builds a relationship with the guest that they want to reward.
Tip laggards: David has 48.6 % tip frequency. So few guests leaving tips is a signal — either his service is too fast and doesn't build a relationship, or he is not asking the tip question at payment time.
Productivity measurement per hour
Divide sales per server by hours worked to get revenue per labor hour:
| Server | Hours | Sales | Revenue/hour |
|---|---|---|---|
| Anna | 32 | 72,000 | 2,250 SEK |
| Bengt | 40 | 58,000 | 1,450 SEK |
| Cecilia | 30 | 62,000 | 2,067 SEK |
| David | 45 | 67,000 | 1,489 SEK |
Benchmarks:
If a server is below benchmark, it may be because of:
Upsell index
Although Vendion does not have a specific "upsell KPI", you can measure it via:
(Avg order − menu price for 1 main) / menu price × 100 = upsell index
Example: Avg order 400 SEK, average main course 220 SEK.
That means on top of the main, the server sells on average 82 % more per guest in appetizers, desserts, drinks.
Benchmarks:
100 %: Server performing well
Action plan to raise avg order
Avoid pitfalls
How to present staff results
Use the numbers constructively, not punitively. The most effective approach:
Integration with the Staff module
When you roll out Vendion Staff (launching in 2026), you can connect servers' scheduled hours directly to sales data:
Incentive program – a concrete model
Common in the restaurant industry: give 5-10 % bonus on upsell above the baseline.
Example: Baseline avg order 320 SEK. Anna delivers 400 SEK on average over 180 orders. Added value = (400−320) × 180 = 14,400 SEK. 5 % bonus = 720 SEK to Anna that month.
This:
AI Boss staff questions
This feature is part of Vendion Analytics++.
Curious how it looks in practice? Read more about the product or book a short demo.
Was this article helpful?