Data Sources
CalorieMetrica combines nutrition reference data, common serving assumptions and local-food estimates to make practical calculator pages.
Food database approach
Core items are stored in the site food database and scaled by portion. Local foods use representative recipes, so results should be treated as a close estimate.
Formula approach
Calculator pages use widely accepted BMR/TDEE, macro, protein and hydration logic. Formula notes are shown on relevant pages to improve trust and transparency.
Corrections
When users report better label data or verified recipe values, CalorieMetrica can update the database and note changes in the update log.
How CalorieMetrica builds nutrition estimates
CalorieMetrica uses a transparent estimate-first approach. Food values are based on common serving sizes, typical macro ranges and practical South Asian, Middle Eastern and global recipe patterns. Homemade meals can vary because oil, rice quantity, meat cut, sauces, flour type and cooking method change the final nutrition value.
Data quality levels
| Level | Meaning | Best use |
|---|---|---|
| High confidence | Simple foods with relatively stable values, such as eggs, milk, rice, oats or plain chicken. | Daily tracking and macro planning. |
| Medium confidence | Common cooked meals where recipe variation exists, such as daal, roti, paratha or grilled chicken meals. | Useful estimate with portion awareness. |
| Recipe-dependent | Mixed dishes such as biryani, kabsa, mandi, shawarma, nihari, kheer and fried snacks. | Use as a guide; adjust for oil, sauce and serving size. |
Why values may vary
A plate of biryani cooked with more oil, larger rice portion or fattier meat will not match a lighter homemade version. The same applies to shawarma sauces, kabsa rice, paratha oil, dal tempering and dessert sugar. For this reason, CalorieMetrica shows estimates and encourages users to track portions consistently.
Correction policy
If a food value appears inaccurate, it should be reviewed against serving size, recipe type and ingredient assumptions before changing the database. CalorieMetrica prioritizes realistic user guidance over false precision.
How a food page is built, step by step
1) We identify the dish and its common regional preparations (home, street and restaurant versions). 2) We break the recipe into its main calorie drivers — rice or bread, meat, oil or ghee, sugar or syrup, sauces. 3) We estimate a per-100g range and typical serving weights from standard food-composition references and representative recipes. 4) We express the result as a range rather than a single number, because oil quantity and portion size vary more in South Asian and Gulf cooking than in packaged food. 5) The page is reviewed for internal consistency — the serving table, the examples and the FAQ must all agree — and dated with a "Last reviewed" badge.
What we do not claim
CalorieMetrica does not perform laboratory analysis of foods, and our pages are not reviewed by doctors or registered dietitians. Values are careful editorial estimates, suitable for everyday tracking and planning, not for clinical use. Where a packaged product has a label, the label is the better source. We state this plainly because an honest range is more useful than false precision.
Reporting a data error
If a value looks wrong, tell us through the Contact page with the food name, serving size and, if available, your source. Verified corrections are applied to the page and recorded in the Update Log.