Recipe costing software that keeps every plate cost live
Static recipe spreadsheets are out of date the moment a supplier price changes. tSpoonLab turns every recipe into a live cost model, so plate cost, menu cost and margin stay accurate across every location, automatically.
Why static recipe costing fails at scale
The cost of disconnected recipe data
When recipe costs are calculated in isolation, they become unreliable almost immediately. The problems compound as the operation grows:
- Recipe costs are calculated once and never updated as supplier prices move
- Each location keeps its own version, so plate cost differs site to site
- Sub-recipes and yields are ignored, so the costed number is not the real number
- Menu pricing decisions are made on cost data that is already wrong
Outcome:
A recipe cost that is not connected to live purchasing data is a guess with decimals.
Every recipe as a live cost model
From static spreadsheet to connected cost infrastructure
tSpoonLab structures every recipe as an escandallo, a detailed cost model that includes ingredients, quantities, yields, waste factors and nested sub-recipes. Because it connects directly to purchasing data, the cost model stays current without manual updates:
- Recipes structured as escandallos with ingredients, quantities, yields and waste factors
- Cost per portion recalculated automatically when supplier prices change
- Sub-recipes nested with full cost inheritance through every layer
- Plate cost, menu cost and margin visible per location in real time
The recipe cost model reflects real contracted prices, not estimates, not last quarter's averages.
Plate cost and menu costing
Visibility from individual plate to full menu margin
Knowing the cost of one recipe is not enough. Operators need to see how every plate contributes to the overall menu margin, and where pricing should be adjusted:
- Cost per plate and per menu calculated from live recipe data
- Target margin vs real margin tracked by location and period
- Menu engineering inputs: popularity vs profitability on every dish
- Pricing decisions based on current cost, not last year's figures
Recipe costing across every location
Consistent cost models from central kitchen to every unit
Multi-site operations cannot afford recipe cost variance between locations. tSpoonLab applies the same cost model everywhere, so margin visibility is consolidated and comparable:
- Standardised recipe cost models applied group-wide from a single source
- Supplier price changes reflected across all recipes and locations at once
- Consolidated margin visibility by brand, country and operational unit
- New locations inherit the full costed recipe library on day one
Outcome:
Recipe costing becomes continuous, consistent and actionable across the entire group.
Recipe costing vs recipe management
Recipe costing focuses on the cost model and margin of each recipe. Recipe management focuses on standardisation, versioning and operational rollout of recipes. Many tools do one or the other. tSpoonLab does both, connected, so the cost model and the operational standard share the same recipe structure.
Frequently asked questions
If your operation is growing, opening new locations or struggling to maintain control, this conversation will clarify your path.