Business Value
- Classifies recipes by type of dish.
- Narrows a long recipe listing to one category.
- Shows the recipe code next to the name.
- Replaces search boxes that never filtered anything.
- Exports recipes in the shape the import reads.
Use Cases
- Chef filters the listing to desserts before costing a menu.
- Cost controller sets up categories once for the whole recipe file.
- Kitchen manager exports recipes, edits them in a spreadsheet and re-imports.
How It Works
Recipes had no classification, and only one of the nine search boxes worked. Recipes now have a category, and the listing is rebuilt.
Setting up categories
Open Point of Sale → Settings → Recipe Category. The listing shows Code and Name, and searches on either.
The screen has its own add / change / view permission. Every role that can already edit a recipe has it. No other role has it until you grant it.
Category on the recipe
The Recipe screen gains an optional Category field, a single-select autocomplete.The rebuilt recipe listing
The listing now shows Recipe code, Recipe name and Category. Category is empty where the recipe has none. The search panel now has six fields that work:
Fill several boxes to narrow on all of them. Fill none to get every recipe.
Preparation time, Total cost, Cost per portion and Suggested selling price are gone. None ever filtered. Store is now a multiselect.
The recipe import
The recipe row gains an optional Category code, matched by code. It goes first, before the store code, so every other column moves one to the right:- Leave Category code empty to import with no category.
- A code that does not exist gives “Category code in line 4 does not exist.” and nothing is imported.
- The import now updates the existing recipe by recipe code instead of creating a duplicate.
- A recipe code repeated inside one file is now rejected.
- Non-stock item code is now optional, so a recipe without one can be exported and re-imported.