Glossary
Food Database
Updated February 28, 2026
A food database stores nutrition entries for quick search and logging. For photo-based workflows, see Food Logging.
Entries and accuracy
| Entry type | Source | Tip |
|---|---|---|
| Packaged foods | Label data | Match serving size and brand |
| Restaurant items | Brand or chain data | Portions vary; sanity check calories |
| Generic foods | Standard references | Use for simple single-ingredient items |
| Custom recipes | User-built from ingredients | Log once, reuse often |
User correction workflow
When values look wrong, use a controlled correction step.
| Error type | User action |
|---|---|
| Missing serving data | add serving context before saving |
| Suspicious calorie mismatch | compare alternate entries and annotate context |
| Portion ambiguity | save a custom corrected version |
When to override automatically
Manual overrides are most useful when:
- Serving sizes don’t match across brands or entries.
- Label data is missing or inconsistent, creating repeated logging friction.
- You’re in a tightly constrained meal planning phase and need repeatable numbers.
Prefer a corrected custom food saved once over repeated guesswork when source quality is uncertain.