Know what your recipes contribute before you eat them

Homemade food is where tracking breaks

Logging a wrapped snack is a scan. Logging a pot of soup is a research project: whose recipe, what went in, how much of it did you eat, and what do you do tomorrow when you eat the rest.

The usual workarounds are all lossy. People search for a stranger’s “vegetable soup” and accept its numbers, or log the raw ingredients one by one every single time, or give up on cooked meals entirely and track only what has a label. A recipe you enter once removes the choice.

Ingredients in, per-serving numbers out

A recipe in Pantensa is a list of products from your own catalog with quantities, plus how many servings it makes. From those two things, the per-serving nutrition follows — calories, macros and the wider nutrient set, computed rather than estimated.

Because the ingredients are your catalog entries, the numbers are the ones you already reviewed. A recipe is not a second place where nutrition data can be wrong; it inherits whatever you confirmed when you added the product.

Flexible ingredients, for how people actually cook

Real recipes have slots, not fixed lists. A smoothie takes whatever berry is in the freezer. A soup takes the stock you happen to have. Forcing one canonical version means either editing the recipe every time or logging something you did not eat.

Pantensa lets an ingredient be a choice made at cooking time, so one recipe covers the family of meals it really is — and the day gets the version you actually made, not the version you first wrote down.

• One recipe, several interchangeable ingredients.
• Serving sizes that match how the dish is served.
• Adjust quantities for the batch you actually cooked.
• The choice you made is what lands in the day.

Servings, portions and the rest of the pot

A recipe that makes six servings is not one meal. Two people eating one serving each is a fact about a day; the other four servings are a fact about the days after it.

Pantensa treats a serving as the unit you log, so eating the same dish across three days is three ordinary entries rather than three separate acts of arithmetic. Nobody should have to divide a pot of soup by hand to know what they ate.

Unknown is not zero

Some things about a home-cooked meal are genuinely unknown — the oil left in the pan, what the café put in the dressing. A tracker that stores unknown as zero produces a day that looks complete and reads low.

Pantensa marks a day incomplete instead of understating it. That is a small rule with a large effect on whether the weekly numbers mean anything: a total you trust is worth more than a total that is merely full.

The same recipes, later, against your stock

Not in the first release

Pantry mode is not in the first release. When it arrives, a recipe’s ingredient list becomes something that can be checked against what is in the kitchen — what you can cook tonight, and what is missing from what you planned.

The recipes do not need rewriting for that. A recipe that already names real products in real quantities is already the input that answers the question.