User-Submitted Entry

A user-submitted entry is a food in your app's database that another user (not the app's team and not a manufacturer) created. User submissions are why MyFitnessPal can find your local bakery's scone and why Cronometer has thousands of restaurant dishes — but they're also the single biggest source of accuracy variance in calorie tracking.

How they happen

You're logging lunch, the app can't find a match, and there's a prompt to "add this food." You type in the name, calorie count, macros, and serving size. Save. That entry now lives in the database, available to every other user who searches for something similar. At scale, this builds a huge library — and also 400 slightly-different entries for "greek yogurt."

Where they go wrong

A few common failure modes:

• Serving-size drift. Someone entered "1 slice" for a pizza, but the "slice" in their photo is half of what you're eating.
• Brand collisions. "Chocolate chip cookie" — there are dozens of brands with different calorie counts under the same generic name.
• Typos. 120 kcal accidentally entered as 12 kcal. Usually caught by review systems, sometimes not.
• Stale entries. A product was reformulated in 2022, but the 2019 entry never got updated.

How apps try to help

MyFitnessPal shows a confirmation count — the more users who confirmed an entry, the further up search results it ranks. Cronometer badges entries by source. Lose It! marks entries as "Verified" separately from community submissions. None of these systems are perfect; you still have to read the nutrition numbers and sanity-check that a "slice of pizza" at 180 kcal is not being confused with a 520-kcal slice.

When user-submitted is fine

For casual tracking — rough awareness, weekly average, long-term habit — user-submitted entries are usually fine. The errors average out over weeks. You don't need laboratory accuracy to know your lunches are bigger than you thought.

When to upgrade

When you're in a focused cutting or bulking phase, or you're troubleshooting why the scale isn't moving, tighter entries matter more. In that phase: scan barcodes, pick verified entries, build custom entries from packaging labels for foods you eat weekly. The 10-minute investment in a solid custom-entry library pays back for months.

A practical filter

When you look at user-submitted options and three of them are within 15% of each other, any of them is fine. When the spread is 400 to 900 calories, something is wrong — check the serving size, pick the one with the most confirmations, or create a custom entry from the actual label in front of you.