Ntoed Sub-Recipe
Ntoed Sub-Recipe
-reason for having cost details is because we have a small accounts payable
management
-supplier field should be supplier type?
-supplier field- the only purpose for this is to give an option to automatically
select the last supplier or preferred supplier of an specific ingredient
-ingredient code should be a required field
-not necessary to have inventory fields (inventory date and inventory count)
-place ingredient code and usable percentage/yield field at ingredient details
section (first set)
-additional fields; default purchase UM, default recipe UM, default stock UM
-will talk about UOM conversion (with sir AC)
-where to place purchase unit cost?
-ideally creation of ingredient should start in purchasing
-tab style for add ingredients (basic details, costing etc.) refer to analytics-
adding ingredients
--------------------------------------
*SUBRECIPE
-filter for adding ingredient in sub-recipe/may add a category
-supplier field is not necessary on this stage
-recipe creation should tag into a brand upon creating a recipe (rather than going
to mapping)
------------------------------------------
*NEW DESIGN
-remove purchase unit cost
-remove cost details fields
-add yield uom and yield quantity
-updated mockup for adding ingredient/recipe/subrecipe
--------------------
hiearachy navigation:
item cheeseburger
recipe consist of
subrecipes consist of
ingredients
---------------------------------
recipe need to map to an item
---------------------------------
menu items
non food items