Google Cloud Consumer Goods Belgium

Foodpairing

Application Refactoring · IT Operations Automation · Real-time Analytics

In the food and beverage industry, launching new products successfully is a challenge. More than 80% of product launches fail, due in large part to the sector’s traditional reliance on slow, expensive consumer testing.

Achieves more than 75% correlation with real consumer panels
Automates flavor analysis of 100 products daily with Cloud Run
Foodpairing uses Google Cloud to predict consumer tastes with 75% accuracy, cutting development time to days.
Manages 70TB+ of molecular and consumer data in BigQuery

Reported impact

Business outcome

Reduces food briefing-to-formulation cycle from 18 months to days; Manages 70TB+ of molecular and consumer data in BigQuery; Automates flavor analysis of 100 products daily with Cloud Run; Achieves more than 75% correlation with real consumer panels.

  • Cost Reduction
  • Productivity Improvement
  • Risk Reduction
  • Scalability

Solution

“With Google Cloud we have built a closed loop,” explains Jan Stout, senior data scientist at Foodpairing. “We analyze products in the lab, build a molecular map in BigQuery, and predict consumer responses with Gemini Enterprise Agent Platform and Gemini with over 75% accuracy, enabling new products to be launched with confidence. It all runs on Google Cloud.” With Google Cloud we have built a closed loop. We analyze products in the lab, build a molecular map in BigQuery, and predict consumer responses with Gemini Enterprise Agent Platform and Gemini with over 75% accuracy, enabling new products to be launched with confidence. It all runs on Google Cloud. This data is combined with extensive consumer research to fuel a platform of 200,000 digital twins—virtual consumers built from real-world preferences and behaviors. Using Gemini Enterprise Agent Platform , Foodpairing models how these virtual individuals will react to new flavors or packaging.

Data flow

stored or unified in BigQuery, Cloud Storage, Cloud SQL, orchestrated via Gemini Enterprise Agent Platform, Google Kubernetes Engine, and surfaced through Gemini Enterprise, Gemini, Cloud Run

Solution architecture

8 components · 3 layers
  1. Storage
    • BigQuery Stores and queries the analytics and AI-ready datasets that power the workload.
    • Cloud Storage Stores large files, lake data, or static assets that feed downstream analytics and applications.
    • Cloud SQL Provides the managed relational data layer for operational application data.
  2. Serving
    • Gemini Enterprise Provides a secure enterprise environment for teams to use Gemini with governed data access.
    • Gemini Powers natural-language reasoning, summarization, generation, or assistance inside the workflow.
    • Cloud Run Runs application services and proprietary code in a managed container environment.
  3. Orchestration
    • Gemini Enterprise Agent Platform Provides governed enterprise access to Gemini models, agents, and regional controls.
    • Google Kubernetes Engine Orchestrates the platform's containerized services and high-concurrency workloads.

Architecture clues

  • # Foodpairing cuts food briefing-to-formulation cycle from 18 months to days with Gemini
  • Automates flavor analysis of 100 products daily with Cloud Run
  • Foodpairing uses Google Cloud to predict consumer tastes with 75% accuracy, cutting development time to days.
  • From supermarket shelf to BigQuery—and back again
  • Manages 70TB+ of molecular and consumer data in BigQuery
  • The next phase for Foodpairing is the self-driving lab—a 24/7 autonomous facility where Gemini-powered agents decide which experiments will be most useful to run next.

Evidence from the source

Achieves more than 75% correlation with real consumer panels
Automates flavor analysis of 100 products daily with Cloud Run
Foodpairing uses Google Cloud to predict consumer tastes with 75% accuracy, cutting development time to days.
Manages 70TB+ of molecular and consumer data in BigQuery
Reduces food briefing-to-formulation cycle from 18 months to days
Transparency Evidence & methodology 95/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    5 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    Foodpairing customer story

    First-party
    https://cloud.google.com/customers/foodpairing
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jun 6, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jul 30, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.