Every household with a dietary restriction — an allergy, an intolerance, a strong personal preference, or a picky eater who's decided mushrooms are unacceptable — knows the specific tax this adds to meal planning. It's not just finding suitable meals once; it's having to keep re-checking every suggestion, every week, because most tools don't remember what you told them last time.
For families in 2026, the stakes are higher than convenience alone. Allergen mistakes are serious. Picky-eating phases are exhausting enough without re-filtering the same preferences every Sunday. A planner that stores your household's rules once — and applies them everywhere — turns dietary planning from a weekly chore into background infrastructure.
The re-explaining problem
Generic recipe search lets you filter by tag — "vegetarian," "gluten-free," "nut-free" — but tags are attached to the recipe, not remembered about you. Every search starts from zero. If your household has a combination of restrictions (dairy-free and low-carb, say, or nut allergy plus a toddler who won't eat anything green), you're stacking filters manually every time instead of the app already knowing your defaults.
The re-explaining problem shows up in three places:
- Weekly planning — you reject suggestions that violate a rule you've stated before.
- Recipe import — a newly imported dish might include an excluded ingredient unless the filter runs automatically.
- AI-generated meals — without hard exclusions, a model might "forget" an allergen between sessions.
A persistent profile fixes all three at once.
Allergies, intolerances, and preferences: not the same thing
Setting up dietary rules works better when you separate how strict each rule is.
Hard exclusions (allergens and medical needs)
Shellfish, peanuts, sesame, gluten for coeliac disease — these need hard filters checked against titles, ingredients, components, and notes. No soft matching. No "the AI probably remembered." If an ingredient is on the exclusion list, the meal shouldn't surface — period.
Anyone with a diagnosed allergy should still read labels and consult healthcare professionals. A meal planner reduces planning friction; it doesn't replace medical vigilance.
Diet patterns (how you usually eat)
Vegetarian, high-protein, low-carb, Mediterranean-leaning — these shape ranking and suggestions rather than absolute blocks. You might flex for a guest or a special occasion, but the default should match how your household eats most weeks.
Priorities (what makes a meal suitable)
Tags like toddler-friendly, meal-prep-friendly, quick-meals, and one-pot shape which meals rise to the top without excluding everything else. A meal that's technically allergen-safe but takes ninety minutes isn't suitable for your Tuesday even if it passes the hard filter.
Personal dislikes (strong preferences)
Mushrooms, olives, coriander — often not medical, but still non-negotiable for someone at your table. A free-text excluded-ingredient list handles these alongside allergens, so one person's "absolutely not" doesn't require a separate workflow.
What a persistent profile should cover
A meal planner that actually respects restrictions long-term needs a few distinct pieces of information, set once:
- Diet preferences — vegetarian, high-protein, low-carb, or whatever pattern your household follows most weeks.
- Restrictions and priorities — toddler-friendly, meal-prep-friendly, quick-meals, and similar tags that shape which meals get suggested, not just what's excluded.
- Excluded ingredients, specifically — a free-text list (mushrooms, shellfish, a specific allergen) that acts as a hard filter, checked against titles, ingredients, and components rather than just recipe tags.
- Preferred cooking methods — stovetop, oven, air-fryer, a specific appliance like Thermomix — which matters more than it sounds, since a technically-suitable recipe that needs equipment you don't have isn't actually suitable.
Once this is set, it should apply everywhere: to free suggestions, to AI-generated meals, and to anything imported from a URL — not just to a one-time search filter.
Step-by-step: setting up your household profile
1. List hard exclusions first
Write every allergen and absolute no-go ingredient. Be specific — "nuts" might need to distinguish tree nuts from peanuts depending on your household. This list is the foundation; everything else is preference.
2. Add diet pattern defaults
Choose the pattern that describes most weeks, not the ideal you'd like someday. A mostly-vegetarian household that eats fish occasionally might use pescatarian tags or manual overrides — the profile should reflect reality.
3. Set priorities for your life stage
Families with young children often need toddler-friendly and quick-meals prioritised. Households that batch-cook on Sundays need meal-prep-friendly. Pick two or three priorities, not ten — over-tagging dilutes ranking.
4. Note cooking equipment
If you cook primarily on a Thermomix, air-fryer, or stovetop only, say so. Imported recipes that need a slow cooker you don't own shouldn't clutter suggestions.
5. Test with one planning week
Plan seven days and scan every suggestion against your mental checklist. If something wrong slips through, check whether it's an import tagging issue, a missing exclusion, or a priority that needs tightening.
Planning for picky eaters without separate meals every night
Picky eating — especially in toddlers — responds better to structure than to nightly negotiation.
Component-based serving — rice, protein, and veg offered separately lets a child eat the parts they accept while adults add sauce or seasoning. See toddler-friendly meal prep for rotation patterns that work.
Rotation over novelty — familiar meals reduce rejection. A meal rotation built from cook history surfaces what actually got eaten, not what a stock photo suggests kids like.
One safe side — plan every meal with at least one component you know will be accepted (bread, plain pasta, fruit). It lowers the stakes when the main is new.
Rate with notes — "ate the chicken, ignored the sauce" is gold for next week's suggestions. Star ratings alone don't capture picky-eater nuance.
Trust, but verify
Even with a well-configured profile, a good planner should show its work. A visible summary of "this suggestion matched your diet and excluded your allergens because of these settings" does two things: it builds trust that the filter is actually being applied, and it makes it obvious when a setting needs adjusting (excluded ingredient list too narrow, restriction not ticked). That transparency matters especially for anything AI-generated — a hard allergen exclusion should never depend solely on an AI model reliably remembering a prompt.
What the transparency panel should tell you
- Which diet tags matched
- Which exclusions were checked (and none found, or flagged)
- Which priorities boosted the ranking
- Whether the meal came from your library, an import, or AI generation
If a suggestion looks wrong, the panel should make the fix obvious: add an exclusion, toggle a priority, or edit an imported ingredient list.
Common mistakes with dietary meal planning
Relying on recipe tags alone. A blog tagged "gluten-free" might still list soy sauce in the ingredients. Hard filters on ingredient text catch what tags miss.
Mixing up preference and allergy workflows. Treating a mushroom dislike with the same urgency as a nut allergy is fine for filtering — but only allergy-level rules should be described as safety-critical in how you verify at the table.
Never updating the profile. Kids outgrow phases. New diagnoses appear. A profile set two years ago may not match today's table.
Planning only allergen-safe mains and forgetting sides. Cross-contamination and hidden ingredients in sauces, stocks, and dressings matter. Component-level ingredient lists help the shopping pass catch what titles miss.
Assuming AI is allergen-safe by default. Use AI for ideas and variety; rely on hard exclusions and your own review for safety.
Frequently asked questions
Can one profile handle multiple people's restrictions?
Most household planners use a combined profile — the strictest common denominator for allergens, plus priorities that reflect the whole family. Some meals may need a simple base with add-ons (sauce on the side, protein swap) rather than one dish that satisfies everyone identically.
Do imported Cookidoo and Samsung Food recipes respect my exclusions?
They should, if the planner checks imported ingredient lists against your profile automatically. Always verify the transparency panel on the first few imports from a new source.
What about eating out or takeaway nights?
Leave a flex slot unplanned, or tag a "takeaway" placeholder. Dietary profiles mainly govern home cooking; they don't need to model every restaurant menu.
How does this connect to nutrition estimates?
Dietary planning and nutrition estimates are separate layers. Exclusions keep unsafe or unwanted ingredients off the board; nutrition estimates give a rough sense of balance across the week — useful, but not a substitute for medical nutrition advice.
How this works in SpendScan
SpendScan's meal planner stores diet, restrictions, excluded ingredients, and cooking methods once in your planning profile, and every suggestion — free ranking or AI-generated — respects them automatically. A transparency panel shows exactly which settings shaped a given recommendation, so restrictions don't need re-explaining every week, and excluded ingredients are checked as a hard filter across titles, ingredients, components, and notes.
Meal planner, meal library, AI features, and recipe import are Pro (7-day free trial). The shopping list is free forever — including when you're planning around allergen-free substitutes and need one merged list for the whole week. Shop the Week and receipt-aware prices help you shop once with confidence, rather than making emergency runs for forgotten free-from items.
Set it up once. Trust it every week. Spend your planning energy on what to cook, not on re-stating what your household can't eat.