Most recipe recommendation engines work the same way: they show you what’s popular, what was clicked most, or what matches a category filter you set once during onboarding. They have no idea that one person in your household can’t eat gluten, another has a genuine hatred of slimy textures, and a third wants everything spicy enough to notice.
The result is a list of “recommended” recipes that you still have to manually filter before they’re actually useful.
Pantryfy’s Taste Profile is built to fix this. Instead of giving everyone the same suggestions, it builds a profile for each member of your household — spice tolerance, allergens, dietary labels, texture aversions, skill level, and time constraints — and uses all of it when generating recommendations and planning meals.
What goes into a Taste Profile
Each household member gets their own profile. The fields cover the things that actually determine whether a recipe will work for your household:
Spice tolerance — a five-point scale from “none” to “extra hot.” If most of your household sits at “mild,” a recipe calling for a tablespoon of gochujang won’t surface near the top of your recommendations.
Allergens — the standard set (peanuts, tree nuts, milk, eggs, soy, wheat/gluten, fish, shellfish, sesame, mustard, celery, sulphites). Checked allergens are enforced as hard filters: recipes containing them are excluded from household suggestions, and ingredient-swap suggestions that conflict with them are filtered out too. In a household where one person has a food allergy, that one profile entry protects every suggestion the whole household sees.
Dietary labels — vegetarian, vegan, gluten-free, dairy-free, nut-free, kosher, halal, pescatarian, paleo, keto. Set any that apply to a member and they’re used when generating suggestions.
Texture aversions — things like slimy textures, mushy dishes, fatty or gristly cuts, or gritty foods. These are the aversions that often go unspoken but reliably cause meals to get pushed around a plate.
Cooking skill — beginner, home cook, or confident chef. This affects which recipes surface when time or technique complexity is a factor. Recipes with complex knife work or multi-stage sauce reductions rank differently for a beginner than for someone who cooks five nights a week.
Time available — a soft cap (15, 30, 45, or 60 minutes) that the planner uses when generating recommendations. Weeknight dinners and Sunday afternoon cooking are different problems.
How the profile affects recommendations
When Pantryfy generates recipe recommendations — either through the “what can I cook” feature or when Autopilot is drafting your week — it runs the household’s combined profile against candidate recipes before surfacing them.
This means the starting pool of suggestions is already filtered for what your household can eat. You’re not scanning through recipes with ingredients someone is allergic to, looking for the few that might work. The shortlist you see reflects your household’s actual constraints.
Autopilot uses the taste profile alongside pantry state when drafting a weekly plan. If you’re on Pro or Family tier, the Autopilot draft accounts for who’s eating, what they can eat, how long you generally want to spend cooking on a weekday, and what’s already in your pantry. The profile makes the “remembers your household” promise actually mean something.
Recipe search learns your taste too
Taste also shapes recipe search. When Pantryfy searches the web for recipes — or generates candidates for you — the results are re-ranked toward your household’s taste, built from three signals: what you’ve told it (ingredient loves and dislikes), what you favourite, and what you actually cook. Search relevance stays primary — a result that matches what you asked for still comes first — with taste-fit as a secondary boost within it. And the ranking is honest about its data: it only kicks in when Pantryfy has flavor data for the ingredients involved, so the more you favourite and cook, the more results lean toward your taste. There’s no fake personalization on day one.
Household members versus household defaults
The profile system is designed for households where different people have different needs — not just for a single person’s preferences. Each member has their own profile because a household with a nut allergy in one person and no restrictions in another needs different handling than one where everyone eats the same way.
When generating recommendations for the household as a whole, Pantryfy takes the union of every member’s hard constraints and enforces all of them: if one member has a peanut allergy, recipes with peanuts won’t appear in the shared recommendation list. The same is true of diets — if one member is vegetarian, recipes that conflict with a vegetarian diet are excluded from household suggestions outright, not just ranked lower. That’s deliberate. A “recommendation” the table can’t actually share isn’t a recommendation, and a diet or allergy isn’t a preference to be traded off against how tasty something looks. Set it once, and every suggestion respects it.
You can view and edit each member’s profile from the Settings page, and you can adjust profiles anytime — they’re not locked after setup.
What the taste profile doesn’t do
The soft parts of the profile — spice tolerance, texture aversions, skill, time — shape ranking, not access. You can always search or browse recipes outside your usual parameters; if you want to cook something spicier than your usual household preference, nothing stops you. Allergens and diets are the exception: those are enforced as hard filters on suggestions, because a recipe that violates them was never really an option. Your saved recipe library itself stays fully browsable either way.
It also doesn’t replace the pantry matching. The best recommendation is still the recipe that fits your pantry today, not the one that technically matches your preferences but requires a full shopping trip. Taste profile and pantry matching both run — a recipe with high pantry overlap and good household fit ranks higher than one that does well on just one dimension.
If your household’s tastes have shifted — someone’s expanded their palate, a dietary restriction has changed — update the profile and the next round of recommendations reflects it immediately.
For households where AI planning does most of the heavy lifting, getting the taste profiles set up accurately is the fastest way to make Autopilot’s drafts feel like they were written for your specific household rather than a generic family of four. The setup takes about two minutes per member, and the effect on weekly plan relevance is immediate.
If you’re evaluating Pantryfy alongside other meal planning apps, the best AI meal planning apps comparison covers how the taste layer compares to what other tools offer.