Skip to content

Main content

Food Label Serving Weight Crosswalk

Scale an explicitly supplied food-label amount by measured consumed weight without selecting a dietary target.

Loading tool…

Description

Scale a label's per-serving amount to supplied consumed grams.

Dietary arithmetic depends on as-purchased versus edible mass, per-serving versus per-100-gram bases, measured versus trace states and recall periods. A recorded allergen list is not a verified allergen-free declaration. Portion counts, label intervals and mass differences use supplied assumptions rather than establishing actual intake or nutritional suitability.

Scale a label's per-serving amount to supplied consumed grams.

When to use this tool

Use Food Label Serving Weight Crosswalk when you already have labelServingGrams, consumedGrams, amountPerLabelServing and need to scale a label's per-serving amount to supplied consumed grams.

How to use the tool and how it works

  1. Enter labelServingGrams, consumedGrams, amountPerLabelServing. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read labelServings, consumedAmount. Use the output convention below.

Require serving grams>0 and consumed grams/amount>=0; servings=consumed/serving, amount=amountPerLabelServing*consumed/serving.1

Input fieldMeaning and unitsAccepted input
labelServingGramsLabel Serving GramsRequired. Finite number; strictly above 0.
consumedGramsConsumed GramsRequired. Finite number; minimum 0.
amountPerLabelServingNonnegative amount in the stated nutrient/quantity unit per labeled serving, not per 100 g.Required. Finite number; minimum 0.
Output fieldInterpretationReturned shape
labelServingsLabel ServingsRequired. Finite number.
consumedAmountConsumed AmountRequired. Finite number.
json
{
  "input": {
    "labelServingGrams": 40,
    "consumedGrams": 60,
    "amountPerLabelServing": 8
  },
  "output": {
    "labelServings": 1.5,
    "consumedAmount": 12
  }
}

Limitations and assumptions

  • Units and food basis must match. No actual composition, consumption, nutrient adequacy or recommended intake is established.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Check original food labels, composition sources, ingredient/allergen information and dietary records before combining amounts. Use a complete appropriately interpreted dietary assessment when requirements or suitable intake matter; local scaling and source labels do not make those judgments.

References

  1. Calculation and input contract: dietetics/food-label-serving-weight-crosswalk — tool.io

Similar or alternative tools