You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we first implemented the Nutri-Score, we didn't have ingredients analysis, so we used the product category to get an estimate of the % of fruits and vegetables for some products (e.g. fruit juices, jams).
We now also compute an estimated % of fruits/vegetables from the list of ingredients.
In some cases, the categories are not accurate (e.g. "fruit juice" when the product is a fruit nectar with water), which causes the % of fruits / vegetables to be overestimated.
We probably should reverse the priority: if we have a fruit % from ingredients, use that, and use the category as a last resort.
To Reproduce
currently on the producers platform for lea nature:
Describe the bug
When we first implemented the Nutri-Score, we didn't have ingredients analysis, so we used the product category to get an estimate of the % of fruits and vegetables for some products (e.g. fruit juices, jams).
We now also compute an estimated % of fruits/vegetables from the list of ingredients.
In some cases, the categories are not accurate (e.g. "fruit juice" when the product is a fruit nectar with water), which causes the % of fruits / vegetables to be overestimated.
We probably should reverse the priority: if we have a fruit % from ingredients, use that, and use the category as a last resort.
To Reproduce
currently on the producers platform for lea nature:
https://fr.pro.openfoodfacts.org/produit/3289196100467/nectar-de-poire-biologique-jardin-bio
(nectar listed in fruit juices)
Expected behavior
More precise Nutri-Score computation.
Screenshots
No response
Additional context
No response
Type of device
Other
Browser version
No response
Number of products impacted
No response
Time per product
No response
The text was updated successfully, but these errors were encountered: