Abstract

BackgroundServing sizes on the Nutrition Facts table (NFt) on Canadian packaged foods have traditionally been unregulated and non-standardized. The federal government recently passed legislation to regulate the serving sizes listed on the NFt. The objective of this study was to compare the serving sizes on food product NFts to the recommendations in the 2003 Nutrition Labelling regulation (Schedule M) reference amounts, the Canadian Food Inspection Agency (CFIA) ranges, and Canada’s Food Guide recommendations. An additional objective was to determine if food and beverage products that report smaller serving sizes have a higher calorie density, compared to similar products with a larger serving size.MethodsData for 10,487 products were retrieved from the 2010 Food Label Information Program (FLIP) database and categorized according to Schedule M categories. Correlations between calorie density and manufacturer stated serving size were tested and the proportion of products meeting recommendations were tabulated.Results35% of products had serving sizes on the NFt that were smaller than the Schedule M reference amount and 23% exceeded the reference amount. 86% of products fell within the CFIA’s recommended serving size ranges; however, 70% were within the lower-half of the range. Several bread and juice categories exceeded CFG’s recommendations, while several dairy product categories were smaller than the recommendations. Of the 50 Schedule M sub-categories analyzed, 31 (62%) exhibited a negative correlation between serving size and calorie density.ConclusionWhile most products fell within the CFIA’s recommended serving size ranges, there was a tendency for products with a higher calorie density to list smaller serving sizes.

Highlights

  • Serving sizes on the Nutrition Facts table (NFt) on Canadian packaged foods have traditionally been unregulated and non-standardized

  • The serving size stated on the Nutrition Facts table determine the nutrient levels that will be reported on that label

  • Comparison of serving sizes in relation to schedule M reference amounts Table 1 compares the manufacturer stated serving sizes reported on the NFt with the Schedule M reference amount and Canadian Food Inspection Agency (CFIA) recommended serving size ranges. 35% of products had serving sizes that were lower than the reference amount in schedule M, 42% of products had serving sizes that were consistent with the reference amount, and 23% exceeded the reference amount

Read more

Summary

Introduction

Serving sizes on the Nutrition Facts table (NFt) on Canadian packaged foods have traditionally been unregulated and non-standardized. The serving size stated on the Nutrition Facts table determine the nutrient levels that will be reported on that label Research has demonstrated that the reported serving sizes on NFts are often smaller than the portions typically consumed [7]. This suggests that food companies may be intentionally trying to reduce the reported calories on the nutrition label by using smaller serving sizes [8]. Research has demonstrated that using different serving sizes on the NFts of similar products, confuses consumers and makes comparisons among similar foods difficult. Anticipated guilt from consumption, purchase intentions, and choice behaviour, can be influenced by serving size manipulations, and may disproportionately influence weight-conscious consumers who are concerned about calories, but not serving size [8]

Objectives
Methods
Results
Discussion
Conclusion

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.