Trust is a label, not a promise
Anyone can claim their data is good. We attach a quality level to every record and show it to you on every answer, including when the honest label is beta.
The three quality levels
Every supplier record, dataset row and capability output carries one of these. They are machine-readable, so your agent can filter on them.
data_quality: beta
Machine-collected, not yet human-verified.
Sourced automatically with a source_url and a scraped_at timestamp. Useful for shortlisting, not for a decision you cannot reverse.
Today: All 60 supplier records are currently beta.
data_quality: reviewed
Checked by a human against the cited source.
A person confirmed the record matches its source. Fields that could not be confirmed are removed rather than left hopeful.
Today: Target for the current milestone.
data_quality: gold
Verified with the counterparty or an authoritative register.
Confirmed directly with the supplier, or drawn from an official register such as the EU Novel Food catalogue.
Today: Reserved. Nothing is labelled gold today.
How we handle being wrong
An honest "unknown" beats a confident guess
Every capability has a confidence threshold. Results below it are flagged review_required and the uncertain items go to a review queue. A capability that does not know says so, and that gap becomes the next thing we fix.
Beta is never dressed up as verified
Quality labels travel with the data into your chat window. We do not aggregate a beta record into a confident-sounding summary, and we do not hide the label behind a footnote.
Every rule cites its source
A regulatory answer names the regulation and the entry it came from: Regulation (EU) 2015/2283 and the Union list, not "according to EU law".
One concept, one term
A shared glossary maps Co-Packer, Co-Filler, Contract Manufacturer and Lohnhersteller onto a single canonical Supplier object. Synonyms are mapped, never maintained in parallel.
What happens to your data
The gateway proxies your request to the capability and logs metadata about the call, never its contents.
- What we log
- Duration, capability ID, status code, user ID, language.
- What we do not log
- Question and answer payloads. Your ingredient lists and briefs are not retained.
- Authentication
- OAuth 2.1 with PKCE and Dynamic Client Registration. No API keys emailed around.
- Transport
- TLS 1.3, strict header sanitation.
- Third parties
- Self-hosted fonts, no advertising or social embeds. Google Analytics is loaded consent-denied by default and only measures if you accept.
Standards, stated plainly
We classify capabilities and products using the GS1 Global Product Classification standard at segment level. That is a statement about our taxonomy, not a certification. fmcg.network is not affiliated with, endorsed by, or certified by GS1, and you will not find a GS1 logo used as a trust badge anywhere on this site.
The same applies everywhere else: we name the regulation, the register or the protocol we build on, and we link to it so you can check.