Ingredients demand analysis
Stage 2 · Analysis
The operator jobs behind Ingredients searches
Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.
- 1
Maintain one usable Ingredient identity
Define the Kitchen Ingredient, its working units, category and links to supplied products without duplicating each supplier SKU.
Ingredient is the stable Kitchen concept. Supplier offers and purchased products reference it but keep their commercial identity.
Evidence: restaurant ingredient management software · ingredient database restaurant
- 2
Keep food facts traceable
Maintain source-identified allergen, dietary, nutrition or handling facts that Recipes and Dishes can resolve.
A fact must identify its source, scope and review state. AI inference or a generic database match is a proposal, not approved Kitchen truth.
Evidence: restaurant allergen ingredient database · ingredient nutrition database restaurant
- 3
Count and replenish Ingredient stock
Record observed quantities and define replenishment policy using compatible units and lead-time evidence.
Inventory owns quantities, movements and reorder policy. Ingredients supplies identity and conversions for that work.
Evidence: restaurant ingredient stock count · ingredient reorder level restaurant
- 4
Record Ingredient loss
Capture discarded Ingredient quantity, reason, source and accountable evidence.
Waste owns the loss event. Ingredient provides the subject identity; the event must not be stored twice.
Evidence: ingredient waste tracker · ingredient usage analysis restaurant
- 5
Understand every dependency
Find which Recipes, Dishes and Drinks use an Ingredient and what changes would be affected.
Usage is a graph traversal over canonical references. It must expose unresolved or stale links rather than infer dependencies from names.
Evidence: where used ingredient report restaurant · restaurant ingredient cost history
Record map
Evidence the capability owns, references, or derives
kitchen.ingredients.ingredient
Kitchen Ingredient
Owner: Ingredients
Ingredient owns the Kitchen-local material identity and its supported units and descriptive facts.
- stable Ingredient identity
- name and units
- reviewed handling or classification facts
- audit stamps
kitchen.ingredients.operational-evidence
Ingredient operational evidence
Owner: Suppliers, Receiving, Inventory, Recipes and Waste
Ingredient analysis reads supply, stock, usage and Waste evidence from their owners.
- Supplier offers and mappings
- received acquisition evidence
- Inventory observations
- Recipe usage
- Waste events
Required record questions
What must Ingredients make knowable?
- Which Kitchen Ingredient is this and what stable identity distinguishes it from a supplier product?
- Which purchase, storage, usage and Recipe units are valid and which conversions are evidenced?
- Which Supplier offers or received products map to it without becoming Ingredient-owned?
- Which allergen, dietary, nutrition, origin or handling facts exist, from which source and review state?
- Which Recipes, Dishes and Drinks reference it?
- Which effective purchase or receipt evidence supports current price?
- Which Inventory location and observation supports quantity on hand?
- Which demand, lead time and safety-stock evidence supports reorder policy?
- Which Waste events reference the Ingredient?
- What downstream records would a proposed Ingredient change affect?