Skip to main content

HospitalityFrom our projects

From menu plan to order.

Every week the same question comes up in every kitchen: what do we need to order? The kitchen uploads the menu plan, the AI proposes quantities within the budget, and the kitchen manager approves twice.

Anonymised data

Starting point.

There is little time between two services, and that is exactly when next week's order has to go out. Until now each kitchen kept its own Excel list for it. The ERP where the order ends up in purchasing needs too many clicks for a single order.

Purchasing, in turn, wants to know whether the week fits the budget and who approved what. And the kitchen would like to choose items instead of working out each time whom to order from.

How does each kitchen get to a sensible order quickly, without purchasing losing track?

What we built.

A web app: the kitchen works on the phone, the kitchen manager on the laptop.

  1. Setting the limits calculatedThe week's budget comes from guests, days and the daily rate that purchasing sets. The supplier is in the delivery schedule; the kitchen just chooses items.
  2. Counting, also by voice AIThe cook types in the stock or says something like "six kilos of basmati rice, two crates of lemons". Fixed rules recognise most of it, and the AI only helps with the rest. The cook confirms every line heard.
  3. From menu plan to proposal AIThe kitchen uploads the week's menu plan. From it the AI proposes quantities and writes why for each line. If the proposal does not fit the budget, the software trims it by fixed rules.
  4. Approving twice calculatedThe kitchen manager sees all kitchens at a glance, checks every line and changes where needed. Then the supplier says what it can deliver, and the kitchen manager decides a second time.

What the AI does not do.

  • It sets no prices. The AI proposes quantities. Prices come from the catalogue; the software calculates totals and budget.
  • It does not order. Nothing goes to the supplier without the kitchen manager's approval.
  • It does not overrule a rule. What the fixed rules recognised in the spoken words stays as it is. And the kitchen accepts the goods itself, line by line.

What we learned.

Rules first, AI only for gaps.Once the rules had correctly recognised "bacon, sliced" and the AI turned it into a bratwurst. Since then what the rules found stands. The AI only helps where the rules find nothing.
No sensible proposal without a budget.With no budget in the brief, the AI proposed far more than the week allowed. Now that it knows guests, days and budget, it comes close, and a calculated step trims the rest.
Reality beats assumption.We had assumed the supplier had an interface. In conversation with them it turned out that orders and replies still go as Excel by email. So we first rewrote the process and will only change the code once that is settled.

How do your kitchens order today?

Excel lists, phone or an ERP nobody likes using: tell us about it. In a conversation we will see where fixed rules are enough and where an AI can make suggestions. No obligation, of course.

Send a project enquiry

reCAPTCHA *
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Lettenweg 40
4123 Allschwil

Tel: +41 (0)61 544 05 00
Support Tel: +41 (0)61 539 10 80

Email: This email address is being protected from spambots. You need JavaScript enabled to view it.

© Kallysoft Informatik AG All rights reserved.

Made with in Switzerland

Swiss Made Software logo
Swiss digital services logo
Swiss Hosting logo
Consent to cookies & data processing
We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this website and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies. Please note that if you reject them, you may not be able to use all the functionalities of the site.