Richer and better structured data in Open Food Facts

BE INFORMED 📢 Announcements
1

Hi everyone! :waving_hand:

We’ve just published a new blog post that details a major step forward for the project: we’re upgrading our nutrition data scheme!

:link: Read the full post here: https://blog.openfoodfacts.org/en/news/data-in-open-food-facts

Why does this matter, especially if you’re reusing Open Food Facts?

  • If you are building an app, conducting research, or using our API/exports, this is a game-changer. Here are the 3 key informations you need to know about this revamp:Open Food Facts can now store nutritional facts from separated sources: from the packaging, from manufacturers, from open databases (e.g., USDA), from ingredient-based estimates; you will know precisely where the data is from, and we’ll have the possibility to store multiple nutritional tables for 1 product.

  • The nutritional table will be a “smart aggregation” of values, prioritizing the most reliable sources and clearly indicating the source of each nutrient.

  • The API remains compatible for existing reusers, allowing reading and writing of nutritional data like before.

We’d love to hear your feedback!

Open Food Facts

New tags data model and API features
2

I hope crowdsourced data will be priorized over manufacturer data because in my experience manufacturers load their product data once and do not update them when anything changes. Their data becomes unreliable over time.

Problem updating ingredients in the Android app