A recipe may use the same ingredient in several places: flour in a dough and on the work surface, or butter in a filling and a topping. A shopping total can collect those amounts so you know what to gather.
The difficult part is deciding which rows really match. Similar names are not enough. Ingredient identity, preparation, and compatible units all need to agree before quantities are added.
Match the ingredient, not a fragment of its name
Cream and cream cheese are different ingredients. Their names share a word, but that is not a reason to combine them. Likewise, an unknown row should not be attached to the first public ingredient that happens to contain a similar phrase.
BatchLadle uses a stable ingredient identity for confirmed matches. When you recognize a custom or alternative name, review and assign the intended ingredient explicitly. This makes the decision visible and prevents an accidental text match from changing the list.
Keep preparation differences visible
Packed and loose quantities do not necessarily share a volume-to-mass relationship. Whole and chopped nuts also describe different preparations. A list should preserve those distinctions instead of treating the state as a label that can be discarded after conversion.
If two rows intentionally use the same ingredient in different forms, keep them separate until you decide how to buy and prepare it. The tool is organizing the quantities you supplied; it cannot know whether one purchase will satisfy both uses without your choice.
Add compatible quantities
Two gram quantities with the same identity, state, and preparation can be added directly. For example, 270 g of flour plus another 30 g of the same flour gives a total of 300 g. A mass in kilograms is normalized to grams before being added.
BatchLadle keeps mass and volume in separate shopping totals. It does not automatically use a density to merge a cup quantity into grams. If you decide to use one mass total, establish the conversion separately and enter reviewed original amounts in compatible mass units before rebuilding the list.
| Rows | Shopping treatment |
|---|---|
| 270 g flour + 30 g of the same flour and state | 300 g flour |
| 135 g butter + 45 g of the same butter and state | 180 g butter |
| Cream + cream cheese | Keep separate |
| Known mass + a cup measure | Keep separate, or convert and review the original row amounts first |
Do not turn a note into a total
“To taste” has no numeric amount to add. A range such as “1–2 tablespoons, if needed” also carries information that a single total cannot express unless you make a choice. Preserve these entries visibly with their original wording.
Notes about use can remain useful even when the quantities combine. A shopping total of 180 g of butter does not tell you that 135 g belongs in one part of the recipe and 45 g in another. Keep the recipe rows as the preparation guide and use the shopping list for gathering ingredients.
Decide what to include before exporting
Checking off an item records progress on the list. Before printing or downloading, decide whether the output should include checked items. A list for the shop may omit what you already have; a complete preparation record may include it.
Also check whether notes and unresolved items are included. Omitting them can make a list look complete while leaving out something you still need to decide. The export options should make those choices visible rather than relying on an unexpected default.
Read the grouped list once
Scan each group for a surprising ingredient, an unexpected unit, or a missing note. If a total looks wrong, return to its contributing rows and check the identity and state rather than editing the total without understanding the cause.
The result should be a compact list you can explain: which rows contributed, which conversions were used, and which items remain separate. That is more useful than a shorter list created by merging everything that looks similar.