Shopping lists are automatically generated from meal plans, aggregating ingredients based on the recipes included. The system scales ingredient quantities according to the yield specified in the meal plan. For example, if a recipe produces 500g and the meal plan uses 250g, the ingredient amounts are halved.

When using yield-based recipes, the shopping list correctly reflects the scaled amounts based on the total batch yield. This means that if a recipe is designed to produce a certain weight or volume, the shopping list will adjust ingredient quantities accordingly.

Ingredients from different recipes are combined into a single line on the shopping list when they share the same ingredient and aisle. For instance, if one recipe calls for 200g of chicken and another calls for 1 whole chicken, the system will merge these into one line if the ingredient has portion data available.

Items are organized by grocery store aisle, making it easier for members to navigate their shopping experience. If an ingredient does not have a specified aisle, it will default to the "Other" aisle.

Both admins and members can add manual items to the shopping list. This can include free-text entries like "paper towels" without selecting a library ingredient. When adding a manual item, you can specify an optional amount and unit, and the aisle selector defaults to "Other."

Members can use the "Add Extra" button in the meal plan shopping list block to add these items. However, any manual additions made by members will only affect their personal shopping list and will not alter the shared meal plan shopping list.

The pantry feature allows members to maintain a list of ingredients they always have on hand. Items marked as "in pantry" can be hidden from the shopping list, streamlining the shopping experience.

Admins can enable or disable the pantry feature for their users through the App Station settings. When enabled, users can access their pantry from the "My Stuff" page and manage their pantry items easily.

When the same ingredient appears with different unit types across recipes, the shopping list combines them into a single line if the recipe-side count unit matches a portion entry on the ingredient. For example, if one recipe lists "200g chicken" and another lists "1 chicken" (with no unit), the system will merge these if the ingredient has a portion that defines "1 piece = 60g."

If the necessary portion or density data is missing, the shopping list will display these ingredients as separate lines. Admins will see a small warning badge next to unmerged lines, indicating why merging could not occur (e.g., "Add a clove portion"). Members will not see these warnings; their shopping list view remains unaffected.

Shopping lists allow users to manage the state of items. Members can mark items as "in pantry," "removed," or "scratched off" when purchased. Scratched-off items can be moved to a "Purchased" section at the bottom of the list, which can be toggled on or off.

When the shopping list is regenerated, user item states are preserved, ensuring that scratched-off items remain marked as such. However, removed items reset to unchecked so they can be reviewed again.