Home / Industries / Restaurants and food service
What's specific to restaurants is still ahead.
Straight answer: tables, kitchen tickets, recipes and tips aren't in Zarvela yet. We'll build them with the first restaurant that wants to build them with us.
Coming soon
What happens every day.
The problems we hear most in restaurants and food service.
The ticket that gets lost between the floor and the kitchen
A handwritten order arrives late or wrong.
Ingredients that don't add up
If a plate doesn't use up what it takes, kitchen inventory isn't telling the truth.
Split checks and tips
Splitting a check and recording the tip takes time at the register.
The cost of every plate
Without the recipe and its cost, you don't know what each plate makes you.
Here's how the dining room will look.
A preview of what we want to build: the table orders, the ticket reaches the kitchen and the recipe uses up its ingredients.
Coming soon
| Ingredient the recipe uses | Per plate | Left |
|---|---|---|
| Brioche bun | 1 ea | 46 ea |
| Ground beef | 5 oz | 15.8 lb |
| Cheddar | 1.4 oz | 4.2 lb |
Preview of what's next · not in Zarvela yet
What solves it in Zarvela.
Every capability with where it stands, checked against the code.
Inventory, purchasing, sales tax and the books are the same for every industry.
| Capability | Status |
|---|---|
| Tables and kitchen tickets | Coming soon |
| Recipes that use up ingredients as you sell | Coming soon |
| Cost of every plate from its recipe | Coming soon |
| Split checks and tips on the receipt | Coming soon |