Pantry mode: what it will add after the first release

Why it comes second

A pantry app that does not know your recipes can tell you that you have 400 g of rice. It cannot tell you whether that is enough for the week, because “enough” is a question about a plan.

So the order is forced. Products, then recipes, then a plan, then nutrition — and only then does a number on a shelf become an answer instead of a fact. Pantensa’s first release is that foundation, and it is designed to be worth using on its own, because a foundation you abandon before the second floor arrives has helped nobody.

Everything below is what the second floor is meant to be.

Stock and batches

A product in your catalog would gain a quantity: how much of it you currently have, in the unit the product already uses.

Batches are the reason this is not a single number. Two bags of flour bought three weeks apart are the same product and different stock — different purchase dates, different expiration, possibly different prices. Tracking them as batches is what makes “use the older one first” expressible at all.

Expiration, before it becomes waste

Each batch would carry a date, and the dates would surface where they are actionable — while you are planning the week, not in a notification the morning after.

The useful version of this feature is not a list of expiring items. It is a plan that quietly prefers the yogurt that expires on Thursday over the one that expires next month.

Missing products, before you start cooking

With stock known and a plan in place, the comparison is arithmetic: a planned meal needs certain products in certain amounts, and either they are there or they are not.

The result is a flag on the plan rather than a discovery in the kitchen — a day marked as not currently cookable, and the specific line that makes it so.

A shopping list counted from the gap

This is the feature the rest of it exists for. A shopping list should not be everything the week needs; it should be everything the week needs minus everything you already have.

• Your meal plan needs 500 g rice.
• Your pantry has 120 g rice.
• Pantensa suggests buy 380 g.

Three lines, and they are only computable if the plan, the recipes and the stock live in one catalog. That is the whole argument for building the catalog first.

Cooked dishes are inventory too

Cooking a recipe consumes ingredients and produces servings, and those servings are stock in their own right — four portions of soup in the fridge is a fact about the kitchen exactly like a bag of rice is.

Treating a cooked dish as inventory is what closes the loop between the plan and the leftovers, and it is the difference between a planner that assumes every meal is cooked from scratch and one that knows Wednesday’s dinner already exists.

Grocery prices, batch by batch

Because a batch records what was bought, it can also record what it cost. Accumulated over time that gives a per-product price history — what you actually paid, in the shops you actually use, rather than a national average.

This is intentionally part of Pantry mode and not a separate feature: a price without a batch is a number you typed into a spreadsheet, and it would go stale the same way.

What you can do today instead

The first release is not a waiting room. It runs in nutrition-only mode, which is a complete way to use Pantensa, and everything you build in it is what Pantry mode is designed to read later.

The three things worth doing now, in the order they pay off:

• Fill the catalog fast with the barcode scanner and food database search.
• Turn the meals you actually cook into recipes with real per-serving nutrition.
• Put them on a week with the meal planner with nutrition tracking.

None of that is throwaway work, and none of it depends on a feature that does not exist yet.