How to turn recipes into one shared grocery list

Why is the grocery list always a step behind?

A grocery list falls behind the week because writing it down is a separate step from deciding what to cook. A missing feature is almost never the reason. That gap is where “we’re out of milk” gets discovered after the shop has already closed. Which nights to cook and how many dinners to plan is its own decision, covered in the weekly meal planning guide; this guide covers the step after that decision: turning whatever’s going to be cooked into items on a list someone can shop from.

How does a recipe link turn into items on the list?

By reading the page instead of asking anyone to retype it. Paste a recipe URL, from a blog, a recipe site, wherever it was found, into Plannie’s meal planner, and Plannie pulls in the title, a photo if the page has one, and the ingredient list, then adds it as a planned meal for whichever day it’s needed. From there, one tap sends those ingredients on to Groceries. The same import also handles a shared photo or PDF of a recipe, which helps with the recipe torn out of a magazine or forwarded as a scan.

Why do some recipe links import cleanly and others don’t?

Because not every recipe page is built the same way underneath. Most recipe blogs and dedicated recipe sites publish their ingredients and steps as structured data, tagged with schema.org’s Recipe type, or on older sites with the h-recipe microformat, so each ingredient is marked in a machine-readable way rather than buried in a paragraph. A page built that way hands its ingredients to any tool that asks, Plannie included, cleanly and predictably. A page that writes “2 cups flour, 1 tsp salt” as plain prose in the middle of a life story about grandma’s kitchen has to be parsed the hard way, and that’s where an import occasionally grabs the wrong line or misses a quantity.

What happens to ingredients you already have at home?

Nothing gets added to the grocery list without a chance to remove it first. Every ingredient pulled in from a recipe shows up as a reviewable line before it reaches the shopping list, so pantry staples like flour, salt, or olive oil can be dropped from that batch before anything is sent to Groceries. Without that review step, a household that cooks the same six recipes on rotation would re-buy the same spice rack every week.

What happens when the import doesn’t parse cleanly?

It depends on what was shared in the first place. A link, a photo, and a PDF each go through the same recipe-reading pipeline but leave different amounts of tidying behind; plain typed text skips the pipeline entirely and lands exactly as written.

What you paste or share	What Plannie extracts	Where it lands	What still needs a human
Recipe URL	Title, photo, and ingredients read from the page’s own structured data	A planned meal with ingredients ready to send to Groceries	Check any ingredient the source page didn’t tag cleanly
Photo of a recipe	Ingredient text and title read from the image	A planned meal with an ingredient list, no cooking steps	Confirm ingredient names and amounts the scan misread
PDF	Ingredient list read from the document text	A planned meal with an ingredient list	Re-check quantities split awkwardly across lines
Plain typed text	Nothing, it’s typed exactly as written	Straight onto the grocery list as its own item, no meal card	Nothing, this is the fallback that always works

Whatever doesn’t come through clean stays editable afterward. Ingredients can be renamed, split, or removed directly on the list, so a shaky import costs a few seconds of tidying.

How do two people shop off the same list at the same time?

By opening the same list on two phones and watching it update as it happens, so nobody compares notes afterward. Once ingredients land on the grocery list, anyone in the household can open it in their own browser or app and check items off in real time, so a parent standing at the shelf and a partner doing something else at home both see the same, current state of what’s left to buy. That’s what kills the classic “did you get milk?” text sent mid-aisle: the answer is already checked off before the question gets typed.

How do sub-lists handle shopping that isn’t groceries?

By giving anything that isn’t groceries its own list, rather than mixing it into the grocery view. A cabin-packing list, a school-supplies list, or a birthday-party shopping list each get their own cover, icon, and colour, so a household can tell them apart at a glance while groceries stay the one list everyone reaches for by default. The full range of what a list can hold, from covers to reminders on individual items, is in the lists help article; the shared grocery list feature page covers the grocery-specific view on its own.

Who can edit the list, and who can just check things off?

Everyone in the household can do both by default; there isn’t a separate view-only tier for a shared grocery list. Anyone can add an item, rename one, delete one, or check one off, from any device signed into the household. Day to day, where a list lives matters more than who’s allowed to touch it: a shared list on a kitchen kiosk is visible to the whole family, while a personal list stays private to whoever created it and syncs only across their own devices.

What carries over from one week to the next?

The list itself. Nobody starts a fresh one every Monday. Grocery items don’t disappear until they’re checked off, so anything left unbought from this week’s shop is still sitting on the list when next week’s recipes get imported on top of it, rather than being silently dropped. That’s also why the review-before-adding step for pantry staples matters: without it, a staple that’s already sitting in the cupboard from two weeks ago would get piled back onto the list every time a recipe calls for it again.