Planning the week's dinners and building the grocery list are usually treated as two separate chores. They shouldn't be. Once you know what you're cooking, the ingredient list already exists — it's just spread across four or five recipes instead of one list. The only real task left is consolidating it, and that's exactly the part worth automating.

Why writing the list by hand doesn't scale

Building a grocery list from memory means re-reading every recipe for the week, cross-checking what's already in the pantry, and manually merging duplicates — two recipes both call for an onion, three both need garlic. It's tedious enough that a lot of households skip planning ahead entirely and just decide what to cook at the grocery store, which is slower and more expensive than shopping from a list.

How this works once meals are planned first

In Fam to Table, once at least two recipe-based meals are on the current or coming week, a Build list button shows up right in the plan's header — no separate screen, no re-entering anything. Tapping it pulls every ingredient from every planned recipe into one shopping list.

From there:

One thing worth knowing: quick-add meals — the ones where you just type "Taco night" without attaching an actual recipe — don't carry structured ingredients, so they won't contribute anything to the generated list. If a meal needs to show up in the grocery list, it needs to be a real recipe on the calendar, not a text placeholder.

The actual order of operations

Plan the meals first, generate the list second. Trying to build a grocery list before the week is planned means guessing at what you'll cook, which defeats the purpose. The list should be the last step — a byproduct of a decision you've already made, not a separate decision of its own.