Skip to content
feed.love Analyze food
Feed Love methodology

How Feed Love matches foods

Why “milk,” “oatmeal,” and branded foods sometimes need a second look.

Practical guideSource-aware3 sections
01

Descriptions can map to different foods

A typed ingredient must be matched to a structured food record before nutrient values can be calculated. Similar food names can represent different products, preparations or fat levels.

Feed Love shows the selected database record, a confidence indicator and alternative matches for ambiguous inputs. Changing the match recalculates the analysis.

The chosen food record matters. Preparation, brand, fat level, and quantity can change the result, so Feed Love surfaces the match instead of hiding it.
02

Specific inputs improve the match

The most accurate analyses combine a specific food description with a quantity, such as “1 cup 2% milk” or “180 g cooked brown rice.”

Preparation matters too: raw oats, cooked oatmeal, roasted potatoes and boiled potatoes can map to different food records and different water content.

03

Correct assumptions instead of hiding them

When the match is ambiguous, Feed Love exposes alternatives so you can correct the database record instead of accepting a hidden assumption.

Use this on a real meal

Open Meal studio, add measured foods, then review the exact source matches and serving basis described in this guide.

Open Meal studio →

Search Feed Love