Rett fra Bonden doesn't just scrape a website and publish whatever it finds. Every important field is cross-checked against independent sources, tracked with where it came from and when — this page explains exactly how, in plain language.
Behind every produsent profile is a record of, for each individual field, which source supplied that value and when it was last confirmed — not just a single "verified: yes/no" flag for the whole profile. We call this field-level provenance.
This matters because a producer's address might be confirmed while their phone number is still awaiting a second source, or vice versa. Verification happens field by field, not all-or-nothing.
Norway's official business register — legal name, organisation number, registered address and business status.
Norway's organic-certification registry (finnoko.debio.no) — checked for producers associated with an organic certification claim.
Public listing data — address, phone and opening hours as reported to Google.
A producer's own homepage or official Facebook page — the preferred source for product and description text.
A producer can also confirm a field directly (we call this owner-attested); that counts on its own, without needing a second source.
For the fields customers rely on most to actually find and contact a produsent — address and phone number — we require at least two independent, higher-quality sources to agree on the same value (for example, the business register and the producer's own homepage, or Google Places and an official Facebook page) before we treat it as confirmed. Minor formatting differences (like "+47 911 22 333" vs. "91122333") don't count as a disagreement.
A value reported by only one source is not treated as unconfirmed data-quality risk-free — it's flagged for a human to check, rather than silently marked as verified.
AI guesses are never enough on their own. Values inferred by heuristics — a guessed product category, a seasonal assumption, a generic web-search snippet — are explicitly excluded from counting as evidence. They can surface as a starting point during data collection, but they can never by themselves make a field "confirmed".
Two different companies sometimes share a building, or one enrichment pass accidentally pulls in details from a neighbouring business. We run a domain-coherence check that compares a producer's listed website and email against their profile URL, so that data belonging to one company doesn't end up attached to a different one's profile.
Producers whose key fields have cleared cross-source agreement show a ✓ Verified badge and are prioritised in search results. Producers whose data is still awaiting a second confirming source remain fully listed — they are not hidden — just without that badge, while the field in question sits in a review queue for a human to check rather than being presented as confirmed.
As expectations around AI transparency and data provenance keep growing in Europe, we think showing our actual verification work — rather than a marketing claim — is good practice. This page describes what our verification pipeline genuinely does today; it is not a claim that we meet any particular law or regulatory standard.
Curious about the rest of the platform? See how it works technically or why we're building this.