Features
What Bitehint does, in order of what matters
Bitehint generates weekly menus from real recipes, checks them against your personal nutrition targets, and maps ingredients to source-backed catalog context you can inspect.
1 · Weekly planning
Menus generated from real recipes
The core of Bitehint is not recipe browsing — it is generating day and week plans from a real recipe catalog. A constraint solver fills your meal pattern with recipes that fit your settings, avoids repeats within the week, and lets you regenerate a single meal or day without losing the rest.
2 · Nutrition targets
The plan is checked, not estimated
Targets come from your own profile and measurements — calories, macros, micronutrients, and custom targets. Drag the sliders: the same day passes or fails depending on your numbers.
Your targets
In the app, defaults are derived from your profile and measurements — and every target stays yours to adjust.
Tuesday’s plan, re-checked live
within range
target met
2 g below target
target met
Drag the sliders — the same day passes or fails depending on your numbers. That is the point.
3 · Ingredient mapping
Recipe ingredients keep their source context
Ingredient lines stay connected to package facts, allergen declarations, certifications, and source records. This is the link between recipe planning, nutrition checks, and the catalog data behind each fact. Try the mapping demo.
Chana masala
390 kcal / serving · nutrition derived from 9 ingredients
Source record on file — inspect the original
Ingredient facts from package source records
4 · Source-backed catalog
Every fact has a receipt
Recipes, catalog entries, ingredients, nutrients, allergens, traits, certifications, sources, and brands each have detailed pages in the app, and every fact links to the source record it was derived from. Traceability is the claim: you can inspect where a number came from.
Chana masala
390 kcal / serving · nutrition derived from 9 ingredients
Source record on file — inspect the original
Ingredient facts from package source records
5 · Personalized controls
Settings that shape the plan
Meal patterns, recipe and catalog lenses, nutrition targets, allergens, avoided ingredients, kitchen equipment, saved recipes, profile facts, and measurements — these are planning inputs, not preferences. Hard constraints are never violated; the rest steers what the solver generates.
Your planner settings
Meal pattern
Quick dinners Mon–Fri · batch cook Sunday
Hard constraints
No peanuts · no cilantro · vegetarian weekdays
Saved recipes
18 favorites steering generation
Supporting tools
Also in the app
Barcode scanning
Camera scanning with GTIN lookup for catalog fact checks.
Nutrient pages
Every tracked nutrient has its own page: what it is and where to get it across catalog entries and recipes.
Curated tags
Cuisine, effort, and occasion tags — curated, not crowdsourced — that filter predictably.
Chana masala
390 kcal / serving · nutrition derived from 9 ingredients
Source record on file — inspect the original
Ingredient facts from package source records
Roadmap
Planned next
Nothing below is live yet. Order and scope may change as the beta evolves.
Next up
Catalog-aware planning
Use catalog facts as planning context without changing the solver contract.
Exploring
Pantry and leftovers
Plan around what is already in the house.
Household profiles
Individual targets, one shared menu.
Further out
More stores and regions
Coverage beyond the current Dutch selection.
Mobile companion
Scanning, quick checks, and tonight's plan on the go.
Go deeper
Keep reading
Beta
Good food is a solvable problem.
Bitehint is in beta while the catalog and planner mature. Already have an account? Your week is waiting.