What if every food had a climate score? Here's the first 100,000.
Phase 1 of the EOS-Ayce Eurostars research project is complete: a public, peer-reviewable LCA baseline calculated by Eaternity from public data.



Look up any product in the Flit app to see the estimated climate score.
Flit enables you to search and scan products to view the results. We've made it easy for you to review the scores and provide us feedback.
Search
Look up any of the 100,000 products by barcode or name. Inputs come from Open Food Facts plus public LCA references (Agribalyse, BAFU/UVEK, the Eaternity Database, scientific literature).
See the score
For each product, you'll see an A–E rating, a CO₂ value, and a per-product confidence score. Products whose inputs introduce too much uncertainty are held back rather than published.
Review and feedback
Contact us to flag a methodology question, an input error, or a score that looks off. The release is open precisely so it can be challenged — that's what it's for.
How the scores are calculated
Every score uses lifecycle assessment, drawing on Open Food Facts product data and public LCA references. The EOS engine runs the rest: a gap-filling pipeline that solves for ingredient masses from declared nutrients, infers origin where labels are silent, geo-locates suppliers, models agricultural emissions, attaches transport and processing, and assembles a life-cycle inventory product by product.
ISO 14040/14044
Lifecycle assessment methodology
Open Food Facts
Public product data inputs
IPCC Tier 1
Agricultural emissions modelling
FAO climate zones
Supplier geo-location
Methodology decisions, data sources, and assumptions are documented and public. No registration, no paywall.
Eurostars Project Milestones
The EOS-Ayce Eurostars Project contains two distinct phases with the goal of developing the infrastructure for end-to-end environmental footprinting of food.
Phase 1 — Public-data baseline
Calculated by Eaternity from public inputs only: Open Food Facts product data plus public LCA references (Agribalyse, BAFU/UVEK, the Eaternity Database, scientific literature). It establishes a public, peer-reviewable starting line at scale.
- ✓ 100,000 European supermarket products
- ✓ A–E rating + CO₂ value per product
- ✓ Per-product confidence score
- ✓ Open dataset, open methodology, open engine
Phase 2 — Primary-data layer
Verified primary data flows into the same engine on a per-product basis, with explicit brand-client consent. Phase 2 is also where the methodology integrates into commercial and non-commercial applications.
- → Verified farm-level inputs
- → Per-product, explicit consent
- → Supply-chain-specific, auditable
- → Commercial & non-commercial applications
An EU-funded research consortium.
EOS-Ayce holds three partners with three complementary roles, each developing a different piece of the larger capability.

LCA methodology & calculation engine
Since 2008, building the scientific foundation for food climate scores. Methodology aligned with ISO 14040/44 and the EU Product Environmental Footprint standard. Owner of the EOS calculation engine.

Retail-facing platform
Builds the platform that translates farm-level and LCA data produced by Klim and Eaternity into actionable sustainability insights for retailers, while enabling suppliers to easily share primary data at scale through an intuitive supply chain engagement layer.
The May 2026 open release is issued by Eaternity on the basis of that joint work. EOS is open source at gitlab.com/eaternity/eos.
National funding bodies
EOS-Ayce (E!7949) is co-funded by Eurostars under the European Partnership on Innovative SMEs, with national funding from Innosuisse (CH), BMBF (DE) and FFG (AT).
For methodology review, collaboration or feedback: hello@eaternity.ch
Frequently Asked Questions
What this research release is, and what it isn't.
Are my products in the 100,000?
The score is calculated from public inputs only. It's an estimate, not a calculation based on data the client has shared with us under their contract.
If you want to know whether a specific product is in the dataset, go to flit.eaternity.org and search by barcode or name.
Is my company's private data in this release?
- Open Food Facts product data (public, user-contributed)
- Public LCA reference databases (Eaternity Database, Agribalyse, BAFU/UVEK, scientific literature)
No client confidential data provided to Eaternity, inoqo or Klim will be used or communicated at this stage. Anything a client has shared with Eaternity, Klim or inoqo under contract is governed by that contract and used only for the work that contract covers. It is completely separate from this research release.
Phase 2 is where primary data flows into the engine, on a per-product basis but only with your explicit consent.
The score for our product looks wrong. What do we do?
We recommend you first check your product on Open Food Facts, if the ingredient list and origin fields are correct and the score still seems off, please contact our team to let them know: hello@eaternity.ch
Can we use this score on our packaging, website, or claims?
If you would like a fully verified score that you can publish on your packaging and website, please contact:
- Eaternity: hello@eaternity.ch
- inoqo: hello@inoqo.com
I'm a Klim/inoqo client / a Klim farmer / asking on behalf of one. Is my data in this?
Klim's primary data flows only into the engine in phase 2, on specific products a brand client has explicitly authorised, with Klim running the consent, the collection and the verification. Phase 2 is the layer where verified farm-level data brings the score from a public-data estimate to something supply-chain-specific and auditable.
Why are you publishing our data without our permission?
The scores are Eaternity's calculations of public information, using an open methodology. No client data, no supplier data, and no permission-gated data flows in.
A brand can absolutely engage so that the public-data estimate for their product is replaced with a primary-data calculation under their control, that's phase 2.
The overall goal of the Eurostars EOS-Ayce project is developing the infrastructure for end-to-end environmental footprinting of food.
Are CodeCheck / Open Food Facts / Yuka going to show our product's score?
The Flit app at flit.eaternity.org is the demonstrator for how this data could be incorporated into one of these platforms.
How does this affect our ongoing engagement / contract with Eaternity?
There is no impact on our ongoing engagement. Existing contracts, confidentiality and roadmaps are unchanged. The public release is a research-track output of the Eurostars consortium.
We'd rather not be in the public dataset. Can we be removed?
I've reviewed your methodology and would like to discuss some aspects
Calculated using Eaternity's EU-aligned methodology (ISO 14040/14044). Product data enriched with Open Food Facts (Open Database License). EOS calculation engine open-source at gitlab.com/eaternity/eos.


