Describe it. Get a list. Done.

You know you need "stuff for a stir fry" or "the usual vegetables" — but turning that into an actual list means sitting there naming every single item one at a time. Broccoli. Garlic. Ginger. Soy sauce. Spring onions. By item six you're not sure if you already wrote down rice.

The blank list is the hard part

The hardest part of a shopping list is often the blank page, not the typing. Deciding what to buy takes effort, and that effort is harder on some days than others. Describing what you need in plain words gives the list a starting point, and Shopolit turns that description into a real list you can edit.

This isn't just a typing problem — it's decision fatigue, and there's real research behind why it feels harder some days than others. A narrative review of the research on food-related decision fatigue found that as the mental effort of deciding piles up, people shift toward automatic, low-effort choices — the same pattern researchers have traced back to earlier lab studies, like Vohs and Heatherton's finding that people who'd already used up their self-control ate significantly more ice cream than those who hadn't. Separate research on the time of day and food choice found the effect gets worse later in the day: choices made in the afternoon and evening consistently trend toward whatever's simplest, not necessarily what's intended. None of this is really about willpower — it's that naming twelve individual grocery items from scratch is a real cognitive cost, and it's one most shopping list apps quietly ignore.

How it works

Describe what you need in plain language, such as my vegetables, a dinner party for eight, or healthy lunches for the week. Shopolit turns the description into an editable list, which you review before it is added to the shared list. The description is part of the Plus plan.

Describe what you need in plain language — "my vegetables," "dinner party for 8," "healthy lunches for the week" — and Shopolit turns it into a real, editable list. Nothing is added silently: you see the full list before it lands on your shared list, and you can edit or remove anything first.

It isn't limited to groceries either. "Camping trip for 4" or "home office supplies" work the same way — the AI reasons about what a request like that actually needs, rather than matching against a fixed list of grocery items.

Hosting flips the usual shopping-list problem around. It's not "what does my household need this week" — it's "what does an entire event need," which is a much bigger blank page than a Tuesday grocery run, and one most people only face a few times a year. Buying for a crowd also carries waste: USDA's Economic Research Service estimated that 31% of the U.S. food supply was lost at the retail and consumer levels in 2010.

Same feature, bigger scale

The same plain-language description that works for a dinner for two also works for a larger event. Describe the occasion and Shopolit works out what it needs, such as proteins, sides, drinks, and dessert, sized to the number of people you give. The result is a list built for the event, not a fixed template.

The same plain-language description that turns "dinner party for 8" into a real list already works at hosting scale. Describe the event and Shopolit reasons about what it actually needs — proteins, sides, drinks, something for dessert — sized to however many people you tell it, not a fixed template.

Describe "Thanksgiving for 12, plus 2 vegetarians" and the generated list accounts for the vegetarian substitution specifically — not just a bigger version of a meat-centric list. You review the full list before anything lands on your shared list, so you can adjust anything that doesn't match what you're actually planning to cook.

Describing a list is part of Shopolit Plus, alongside recipe import. See what's in Plus.

What does this look like in practice?

Suppose it is Sunday, you are hosting a dinner for eight, and the menu is not planned yet. Instead of building the list backwards from a meal you have not decided, you describe the dinner and review the list it produces. You can then change anything that does not match the menu you settle on.

Say it's Sunday and you're hosting a dinner party for 8 people, but haven't planned the menu yet. Instead of trying to reverse-engineer a shopping list from a meal you haven't decided on, you type "dinner party for 8" into Shopolit. You get back a real list — proteins, sides, drinks, something for dessert — sized for 8 people, which you can then edit: swap an item, remove what you already have, add anything specific to what you're actually cooking. The list existing in the first place is what removes the blank-page problem; you're editing from then on, not starting from nothing.

A dinner party for 8 is one scale of this problem — hosting an entire event is the same idea sized all the way up.

Describing a list is part of Shopolit Plus, alongside recipe import and smart suggestions. See what's in Plus.

Common questions

What if it gets something wrong or adds too much?

Nothing is added to your shared list automatically. You review and edit the generated list first. Nothing lands on the shared list until you're satisfied with it. If the AI adds something you don't need, you can remove it. If it misses a quantity, you can fix it. You can add anything extra too, before it's final. This review step exists for one reason: a slightly-off description should never turn into the wrong items showing up on a list everyone else in the household relies on. You're always the last check before anything goes onto the real, shared list.

Does it know what I already have?

It checks against what's already on your list to avoid obvious duplicates. But it has no way to see your actual pantry or fridge. It's working entirely from your description, not a scan of your kitchen. Say you already have garlic at home, but don't mention that. The generated list may still include it, since nothing told it otherwise. That's exactly why the review step matters. You're the one who actually knows what's in the house. Removing anything you already have is a normal, expected part of using the feature, not a workaround.