Foleil lets your recipe library evolve without treating an earlier meal as if you cooked the new version. A recipe is something you can change; a saved food entry describes a particular logged portion. Keeping those roles separate makes repeat cooking more useful, especially when ingredients, serving yield or preparation change over time.
How it works
Edit a recipe for later use and review the updated ingredients and nutrient calculations. Saved food entries retain their recorded portion and nutrition information instead of being reinterpreted solely from the current recipe card. Foleil checks calculated ingredient information against the recipe it describes, so changed ingredients need a matching calculation before those figures are reused.
Why it matters
Food information depends on what an item actually contains. The USDA FoodData Central documentation, reviewed 19 October 2026, describes differing food-data sources; a historical log has an additional question, which recipe version the portion represented. Foleil preserves the account of the logged meal rather than using a later library edit to imply the past changed. That is a record-keeping advantage, not a laboratory validation of either recipe version.
Compared with other approaches
MacroFactor's recipe guide, reviewed 19 October 2026, documents recipe ingredients, servings, steps and saved recipes. Foleil does not infer a competitor's historical editing behaviour from that guide. Its reason here is its own separation between recipe preparation and saved consumption records, connected to the meal week and shopping workflow. The comparison remains about a behaviour you can check in Foleil rather than an unsupported claim about what another app overwrites.
The evidence
A saved portion carries its own amount and available figures. The recipe library can describe what you cook next time without becoming the sole authority for what a past entry contained. A changed ingredient can also invalidate preparation time, equipment or calculated labels that no longer describe the new dish. Reviewing those fields together keeps the updated recipe coherent instead of attaching old detail to new ingredients.
Put it into your day
Imagine changing a curry from one protein source to another. Edit the recipe, review ingredient amounts and inspect the available nutrition basis again. Check the cooking instructions and time as well, because substitutions can affect preparation. Keep yesterday's logged portion as the account you recorded then. When you cook the new version, choose its serving amount for the new entry. This makes later comparison more meaningful: two meals can share a familiar recipe name while containing different ingredients. You keep the convenience of a reusable library and a historical food record that does not silently rewrite itself around your latest kitchen experiment.
Frequently asked questions
Does editing a recipe mean I ate the new version last week?
No. Earlier saved food entries retain their recorded portion and available nutrition information.
Should I review figures after an ingredient change?
Yes. Calculations and practical preparation details need to match the updated ingredients and yield.
Does this prove past nutrient values were exact?
No. Preserving a historical estimate preserves its original basis and uncertainty; it does not independently validate it.
Can two entries share a name but differ in nutrition?
Yes. Different versions or portions can have different recorded ingredients and figures. Use the saved entry’s details rather than assuming a familiar recipe name establishes identical food.
