Nutrition Label to Food Log: A Step-by-Step Guide
Log packaged food by matching the label basis, amount eaten, serving multiplier, calories, macros, and supported Appediet entry fields.

To log packaged food from a nutrition label, identify the label’s nutrition basis first, measure or estimate the amount actually eaten, calculate a quantity multiplier, and then verify the saved food identity, serving unit, calories, protein, carbohydrate, and fat against the label.
Do not begin with the calorie number alone. A correct number attached to the wrong serving basis still creates the wrong record.
Start with the label basis
Read the top of the Nutrition Facts panel before entering any nutrient value:
- serving size;
- servings per container;
- whether nutrition is shown per serving, per package, or in two columns;
- the household measure and metric amount;
- calories and nutrients for that stated basis.
FDA guidance explains that nutrition information is usually listed for one serving. It also states that serving size reflects the amount people typically consume; it is not a recommendation for how much a person should eat.
A single package can contain more than one serving. The package size and the label serving size are therefore not interchangeable.
Per serving, per package, and per 100g
Use the basis printed on the package.
| Label basis | Quantity calculation | What to record |
|---|---|---|
| Per serving | amount eaten ÷ labeled serving amount | The resulting number of servings |
| Per package | amount eaten ÷ total package amount | The resulting fraction or number of packages |
| Per 100g | grams eaten ÷ 100 | The resulting 100g multiplier |
| Dual column | choose the column that matches the amount eaten | Do not add the columns together |
For a per-serving label, keep the household measure and grams connected. If one serving is “1 cup (227g),” the household measure and weight describe the same labeled serving.
For a per-100g label, the multiplier is the measured grams divided by 100. A 75g amount uses a multiplier of 0.75.
Check one calculation before logging
FDA’s sample lasagna label lists one serving as 1 cup (227g) and 280 calories. FDA’s example states that eating 2 cups equals two servings and 560 calories.
The arithmetic is:
| Field | Calculation | Result |
|---|---|---|
| Servings eaten | 2 cups ÷ 1 cup per serving | 2 servings |
| Calories | 280 × 2 | 560 calories |
| Protein | 15g × 2 | 30g |
| Total carbohydrate | 34g × 2 | 68g |
| Total fat | 9g × 2 | 18g |
These values come from the FDA sample, not from an Appediet scan or a commercial food package used in this article.
For a per-100g calculation example, if a label states 240 calories per 100g and the measured amount is 75g, the calculation is 240 × 0.75 = 180 calories. This is an arithmetic demonstration, not a real product label.

Match the package before entering the amount
A barcode or food search result should still be checked against the package in front of you. Confirm:
- brand and product name;
- flavor or variety;
- package version;
- serving size and metric amount;
- calories per stated basis;
- protein, carbohydrate, and fat;
- another nutrient required for the user’s purpose, such as sodium or fiber.
A matching barcode does not guarantee that the database entry reflects a reformulated product or a label from the same country. Use the current package label for that exact product as the comparison source.
Map the label to the food record
Build the record in this order:
- Food identity: choose the exact branded food or create a clearly named custom entry.
- Serving basis: use grams, milliliters, pieces, a household measure, or the package-defined serving.
- Default quantity: set the amount that corresponds to one unit of the chosen basis.
- Calories and macros: enter values for that same basis.
- Additional fields: copy only fields shown on the label and supported by the record.
- Amount eaten: log the multiplier calculated from the actual portion.
Do not mix calories per package with protein per serving. Every nutrient in a single entry needs the same basis.
Use the Appediet route that matches the package
Start with barcode scanning or food search, then compare the result with the product name, serving unit, and Nutrition Facts label on the package.
If the scanned item is the wrong food, choose a closer match. If the food is correct but its protein, carbohydrate, or fat values do not match the label, edit those values before saving.
If no search or barcode result matches the product in your hand, create a My Food entry from the package label. Match the serving size first, enter the nutrition values on that same basis, then compare the saved entry with the package before you reuse it.
Avoid four common basis errors
Logging the whole package as one serving
First compare servings per container with the amount eaten. A package with multiple servings is not automatically one serving.
Using the serving count without the serving amount
“Two servings” is incomplete unless the label’s serving definition is known. Record whether one serving is a cup, piece, packet, or stated weight.
Combining per-100g nutrients with a per-serving quantity
Choose one basis and keep all values on it. Convert the whole set when a conversion is required.
Correcting calories without checking macros
A record can remain internally inconsistent when only calories are changed. Recheck protein, carbohydrate, and fat against the same label basis.
A final verification pass
Before saving, read the record back as a sentence:
This entry represents [product] at [unit and amount]. One recorded unit equals [label basis]. I ate [quantity]. The calories and nutrients come from [label date or package version].
Then verify:
- the product identity matches;
- the label basis is written once and used consistently;
- the amount eaten is represented by the quantity;
- the calculation multiplier is correct;
- calories, protein, carbohydrate, and fat use the same basis;
- the generated image in this guide was not used as label evidence.
What the label cannot establish
A Nutrition Facts panel describes the packaged product under its stated serving basis. It does not determine how much a person should eat, diagnose a nutrition condition, or prove a health outcome. It also does not describe ingredients added after opening, such as milk, oil, sauce, or toppings.
Log added ingredients separately when they are not included in the packaged product’s label.
Frequently asked questions
Should I log one package or one serving?
Use the amount actually eaten. If the package contains multiple servings, calculate the fraction or number of servings from the label basis.
What if the label lists values per 100g?
Divide the grams eaten by 100, then multiply every per-100g calorie and nutrient value by that multiplier.
What if the barcode result does not match the current label?
Choose a closer match or create a My Food entry from the package. Match the serving size and nutrition values to the same label basis before saving.
Sources
- FDA: Serving Size on the Nutrition Facts Label
- FDA: How to Understand and Use the Nutrition Facts Label
- FDA: Calories on the Nutrition Facts Label
- Appediet official website
- Appediet on Google Play
- Appediet on the App Store
- Appediet: How AI Estimates Food Calories
- Appediet: How to Track Calories Without Weighing Food
Check one current package label
Use the label in front of you, calculate the amount eaten on one consistent basis, and verify the food identity, quantity, calories, protein, carbohydrate, and fat before saving.
Download Appediet