Why a personal price list is more useful than a generic estimate
Two households can pay very different prices for the same ingredient. Pack size, brand, store, location, dietary needs, and shopping habits all affect the real number.
A personal price list starts with what you buy. Record a price and unit that can be used across recipes, such as dollars per kilogram, litre, item, or pack. The aim is a useful estimate, not accounting precision.
Start with the ingredients that drive cost
You do not need to price every spice before the budget becomes useful. Begin with the ingredients that make the largest difference: proteins, dairy alternatives, fresh produce, specialty products, and regularly purchased staples.
When a recipe contains an ingredient without a price, show the estimate as partial. This makes the missing information visible and gives you a clear next item to add.
- Use the unit that matches how the ingredient is sold
- Update prices when your usual pack changes
- Keep a note of the store or brand only when it helps
- Do not present a partial estimate as a complete recipe cost
Use cost per serve to compare meals fairly
Total recipe cost can make a six-serve meal look expensive beside a two-serve meal. Cost per serve creates a fairer comparison and changes when the planned serving size changes.
Budget Friendly, Mid-Range, and Treat labels can help with quick filtering, but the thresholds should suit your household. A fixed category set is less useful when it ignores dietary needs or local prices.
Set the budget before the list is full
Choose a weekly amount based on recent real spending, not an arbitrary target. A budget that is too low becomes a permanent warning and stops helping with decisions.
As recipes enter the plan, compare the estimated list total with the weekly amount. If the plan runs high, change one expensive meal, adjust serves, use an ingredient already at home, or accept that the week has a reason to cost more.
Separate estimates from actual spend
An estimate is useful before shopping. The actual price is useful after the item is bought. Keep both concepts clear so a completed shop can teach the next estimate.
Enter actual prices for the items that changed most, then complete the list. Over several weeks, the history can show whether the budget is realistic and where variation usually occurs.
Be clear about what the budget does not know
Kyura v1 does not connect to live supermarket catalogues. It cannot promise the current price at Coles, Woolworths, ALDI, or a local market. Values come from the user and can become out of date.
That limitation is also a form of control. The estimate can reflect the products you actually buy and remain retailer-neutral. Future integrations can add optional retailer data without replacing the personal list.
Common questions
Keep the limits clear
How often should I update ingredient prices?
Update the items that materially change your estimates when you notice a new usual price or pack size. There is little value in maintaining every minor pantry item every week.
What if only some ingredients have prices?
Kyura can show a partial estimate and identify missing prices. Do not treat that number as the complete recipe cost.
Does Kyura find the cheapest supermarket?
No. The v1 budget uses prices you enter and stays retailer-neutral. Live retailer comparison is not a launch feature.