Component pooling
This article covers pooling component demand across multiple Plan rows so you don't over- or under-prep a shared component.
Before you start
Have at least one recipe that uses a component, with multiple active Plan rows needing it.
Steps
- MakrPrep sums every active plan row's component demand into a pool per component, found by opening the component in Recipes in Production.
- Use per-row include/exclude toggles in the "Show breakdown" section to control whether a given row's demand counts toward the pool.
- The pool shows a computed batch count (a scale factor against the component's batch yield) based on total demand.
Marking a pooled batch prepped deducts its ingredient stock once. This is tracked separately from any individual recipe's own completion, so the same component never gets deducted twice even if several recipes using it are completed afterward.
A component's pool card in Recipes in Production, showing pooled total, 'Mark prepped,' and the breakdown of contributing rows with their own checkboxes
What to expect
Prepping a pooled component ahead of time and then completing several recipes that use it won't double-deduct that component's ingredients. MakrPrep checks whether it's already been pooled-prepped before deducting again through a recipe's own completion.
Common issues
- A recipe's completion deducted component ingredients I thought were already covered: check whether that component was actually marked prepped in the pool first. If it wasn't, completion deducts its ingredients directly as a fallback.
- Component pool total looks too high or low: check each contributing row's include/exclude toggle. A row left included that shouldn't be (or vice versa) skews the pooled total.