Source: The WISEcode Standard v1.0, Sections 3.1.3, 5.4 and 7.1.
If your product picked up a sugar penalty you were not expecting, one of the following is almost always the cause.
1. Sugar is entering through a compound ingredient
A compound ingredient such as a chocolate coating, a seasoning blend or a sauce base is broken into its sub-ingredients before scoring. Any sweetener inside that blend counts as added sugar even though the word sugar never appears on its own line of your label.
2. A concentrate is acting as a sweetener
Fruit juice concentrates and similar reductions are treated as added sugars when they are functioning as sweeteners rather than as the characterising fruit of the product.
3. The panel data is incomplete and a value was estimated
Where added sugars are not declared, the figure is estimated from ingredient logic, category averages or reference databases. An estimate can be higher than your true value. Supplying the declared grams per serving replaces the estimate.
4. The panel shows a percent Daily Value for Total Sugar
Records displaying a percent Daily Value for Total Sugar or Trans Fat are flagged during data sanitation as invalid declarations. Fix the panel so added sugars are given in grams per serving.
5. Serving size or calorie figures are inconsistent
The penalty is a ratio of sugar calories to total calories per serving. If the declared serving size and calorie count do not correspond, the ratio will be wrong even when the sugar figure is right.
How to get it corrected
Correct the Nutrition Facts Panel and ingredient declaration at source, resubmit through your Portfolio, and the product will be rescored. If the penalty persists after the data is confirmed accurate, raise a support request with the UPC so the record can be reviewed.
Comments
0 comments
Please sign in to leave a comment.