💰 Yield & Costing
Indicative yield, validated yield, ingredient cost, portion cost, food cost % — how the numbers connect.
7 sections · ~6 min read
The costing chain
Ingredient cost → adjusted by yield → split into portion cost → expressed as food cost %. Each step pulls from a single source so the numbers can't drift.
Ingredient cost — auto from Oracle
Ingredients pull prices from Oracle EBS via itemCode. The Ingredients page lets Purchasing override manually if needed (e.g. promo pricing). Recipe cost is the sum of (ingredient % × ingredient cost).
📍 In RecipeHub: Ingredients DB page
Role-specific notes
PURCHASING: You're the only role that can override ingredient prices. Prices sync from Oracle EBS automatically.
Indicative yield (Production Trial)
At Production Trial, Factory records the indicative yield — the first real reading from a controlled batch (e.g. 100 kg input → 92 kg output = 92% yield). Tentative — refined later from regular production.
Validated yield (regular Production)
Once the recipe is Approved and runs in regular production, Factory captures the validated yield from real runs. This replaces the indicative for costing — once you have real production data, you trust it. Both fields live on the recipe; the system uses the validated one if present.
Build component cost — auto-derived
On a Product Build, each component is linked to a recipe (composite / SFG) or an Oracle ingredient code. Cost is derived automatically from the linked item's /kg or /piece price × the component weight. Components without a link still accept a manual cost. Total build cost shown in the header is the sum of all components.
📍 In RecipeHub: Product Builds page
Role-specific notes
PURCHASING: When an ingredient is missing /kg or /piece, the components using it show as no cost. Add the Oracle UOM conversion to unblock.
FACTORY: You don't maintain prices, but if a build cost looks wrong it usually traces back to a missing ingredient conversion in Oracle.
NPD: Linking the right SFG recipe is what makes a composite build cost itself — manual costs are the fallback, not the default.
Portion cost — from Builds
A Product Build defines portion size (e.g. 200g cup). Portion cost = (yield-adjusted recipe cost) × (portion weight / batch weight). Builds inherit the recipe's validated yield automatically.
📍 In RecipeHub: Product Builds page
Food cost % — the headline KPI
Food cost % = portion cost ÷ retail price. Targets vary by brand and channel. Goals are set in KPI & Goals and tracked in Build Analytics.
📍 In RecipeHub: Cost Control page
Role-specific notes
ADMIN: You and Subhanshu are the only editors of KPI & Goals.
NPD: You see the targets and design recipes to hit them.
QA: Watch FC% drift across runs — sudden moves usually mean yield or ingredient-cost changes.
FACTORY: Validated yield is the lever you control. Higher yield → lower FC%.
PURCHASING: Ingredient prices flow straight into FC%. Focus negotiations on the heavy hitters.