Recipe Platform Gap Analysis

Gap Analysis

Comparison Basis

Current state is the existing corporate recipe collection/menu builder environment as described by the user. Future state is the recipe_collection prototype web app and its documented roadmap.

Capability Area	Corporate Current State	Future-State Prototype Target	Gap	Evidence Quality
Mass-to-volume conversion	Proper conversion is missing or insufficient.	Recipes/base foods support measurement authority and bridge conversions across unit families.	Corporate tools cannot reliably scale between mass and volume; prototype must prove authority-field workflow and conversion warnings.	User-provided/Observed
Hotel-pan and unconventional units	Hotel-pan-style production units are not adequately supported.	Hotel-pan units are available in live scaling and Forecasting.	Operators lack familiar production units in current tools; prototype must validate where advanced units are allowed.	User-provided/Observed
Sub-recipe ingredient rollups	Lack of recipe roll-up prevents scaling from sub-recipe ingredients.	Hierarchical and flattened recipe rollups support nested ingredient demand.	Current tools understate or obscure ingredient needs from nested recipes.	User-provided/Observed
Menu-to-production flow	Forecasting and production records are not sufficiently connected.	Forecast summaries snapshot into production records with actuals, variance, implied demand, and posted facts.	Current workflow lacks a durable handoff from plan to production truth.	User-provided/Observed
Ordering forecast	Automated ordering forecast is missing or incomplete.	Inventory planning uses menu/recipe demand, on hand, preferences, catalog, and invoice staging direction.	Current tools require manual demand-to-order translation.	User-provided/Observed
Forecast accuracy analysis	Forecast-to-production accuracy analysis is missing or incomplete.	Production records calculate accuracy and history/item trends; future Analytics consumes posted facts.	Current tools do not close the learning loop between forecast and actual production.	User-provided/Observed
Vendor/source specificity	Not specified in current corporate examples.	Vendor/category preferences exist; item/catalog-line vendor resolution is roadmap.	Prototype still needs finer vendor sourcing before strong purchase suggestions.	Observed/Inferred
Receiving/accounting	Not specified in current corporate examples.	Invoice placement is explicitly not accounting; receiving/accounting are future design areas.	Future accounting boundary remains undefined.	Observed/Unknown
Production deployment	Not specified.	Prototype uses mock auth and local-first architecture.	Enterprise deployment, auth, migration, and integration needs remain open.	Observed/Unknown

Priority Gaps

1. User-provided: Mass-to-volume and hotel-pan conversion gaps block trustworthy production scaling.
2. User-provided: Missing sub-recipe rollups block accurate ingredient demand.
3. User-provided: Forecasting and production records need a connected actual-vs-plan workflow.
4. User-provided: Ordering forecast should derive from menu/recipe demand instead of manual translation.
5. User-provided: Forecast-to-production accuracy analysis should create a feedback loop for future planning.
6. Observed: Prototype vendor-source mapping and receiving/accounting boundaries still need refinement before automated ordering is production-ready.

BA Alignment

• Activity areas: Analyze strategy; evaluate solution; analyze requirements and define design options.
• Techniques used: Gap analysis, future-state modeling, data modeling, process analysis, risk analysis.