— Surface 10 · Broader Google footprint + cross-cloud bridges

One grocer deal.
Six Google P&Ls.

Cloud Sales is the headline P&L. But the Delectable platform consumes — and lights up monetization in — six other Google product surfaces simultaneously. Ads, Workspace, Maps, YouTube, CCAI, Programmable Search, Trends. Plus the cross-cloud bridges that pull workloads out of Azure / AWS / SAP / VTEX / Salesforce and into the Google stack — that's how Giant Eagle's Azure + Databricks workload becomes Vertex + BigQuery consumption. This page is the multi-team map for the field motions that activate on the same grocer deal.

— Six Google P&Ls · all activated by one grocer deal

The map of who else wins.

P&L 01 · Cloud Sales

Vertex · BigQuery · Cloud Run

The deck's headline. CUD activation, $1.6M+ ARR per Tier-1 grocer in pure consumption.

P&L 02 · Google Ads

Ad Manager + Ads API

$69B retail-media TAM. Grocer's first-party shopper signals → Google Ad Manager → CPG closed-loop attribution.

P&L 03 · Workspace

Gmail + Calendar + Drive

Communication module sends transactional + marketing email via Gmail API. Scheduling on Google Calendar. Asset libraries on Drive.

P&L 04 · Maps Platform

Maps API + Places API

Store locator · delivery routing · fulfillment ETA · cultural-DMA targeting. Every shopper session calls Maps.

P&L 05 · YouTube

YouTube Data API

Social Commerce module ingests creator content. Recipe videos. Product-demonstration extraction. Future: YouTube Shopping integration.

P&L 06 · CCAI ROADMAP

CCAI + Dialogflow

2026 H2. Customer-service intents, order status, returns, dietary advisory. Dialogflow CX for IVR. CCAI Insights for analytics.

The field-team line: Every Tier-1 grocer Delectable lands consumes services from all six P&Ls. Bring the Ads field rep, the Workspace AE, and the Maps platform PM to the discovery workshop — the deal lights up their quota too. That's the multi-team co-sell motion this surface enables.
— The Google APIs Delectable integrates today (and 2026 roadmap)

Twelve API surfaces. One sales motion.

Below is every Google API the Delectable platform either consumes today or has on the 2026 roadmap. Each maps to a specific module + capability, so the relevant Google team can see how their product surface lights up in a grocer deployment.

Vertex AI Gemini Pro The reasoning engine LIVE
How we use it. The 20% of grocery queries that require deep inference — meal planning, dietary substitution reasoning, occasion-aware basket building. Delectable's HyperGraphs ground the prompt first, Gemini reasons on the qualified subset.
Used by · Agentic Chat · PIM enrichment · Workflow · Search agent
Vertex Retail Search + Discovery Engine Search relevance + agentic discovery LIVE
How we use it. Live in our staging project today — retail.googleapis.com/Catalog: default_catalog + 3 Discovery Engine collections (us, eu, global). On Delectable-enriched catalogs, Vertex Retail Search out-ranks Algolia / Constructor / Bloomreach measurably.
Used by · Grocer.com on-site search · UCP find_products intent
Google Ad Manager + Google Ads API Retail media closed-loop LIVE
How we use it. The Ads module routes CPG retail-media dollars through grocer's first-party shopper signals into Google Ad Manager. Closed-loop attribution back to grocer purchase. The $69B retail-media TAM lands here — and it's the Google Ads team's quota, not Cloud's.
Used by · Ads / RMN module · Social Commerce attribution · CPG advertiser console
Gmail API (Google Workspace) Communication module · transactional + marketing email LIVE
How we use it. Outbound shopper notifications, FSR co-sell emails, partner-portal invites. Through the grocer's own Workspace tenant when they have one (better deliverability than third-party ESPs). SendGrid fallback for grocer's without Workspace.
Used by · Communication module · Co-sell automation
Google Calendar API (Google Workspace) Scheduling + delivery windows LIVE
How we use it. The Scheduling + Calendar module booking flows. Shopper selects delivery window → event written to grocer's fulfillment calendar. Coming next: native shopper-side Calendar integration for meal-plan event creation ("Friday family dinner" lands on the shopper's calendar with the basket attached).
Used by · Scheduling module · Calendar module · Workflow templates
Google Drive API (Google Workspace) Asset libraries · catalog media · creator content LIVE
How we use it. Grocer asset libraries (product photography, packaging, brand guidelines). Creator commerce attachments (recipe PDFs, photo galleries). Files-on-Drive integration in the merchandiser console. Future: Workspace + Vertex AI grounded answers over the grocer's Drive corpus.
Used by · CMS module · Social commerce · Merchandiser console
Google Maps Platform · Maps + Places + Routes APIs Store locator · delivery routing · cultural DMA LIVE
How we use it. Store locator on every shopper surface — Maps API per page view. Delivery routing for fulfillment (Routes API). Geographic cultural-DMA targeting for IA (e.g. Asian-American neighborhoods → boost Asian-cuisine SKUs in default sort). High-frequency consumption.
Used by · Storefront · Fulfillment · IA cultural-DMA model
YouTube Data API Creator commerce · recipe content · social discovery LIVE
How we use it. Social Commerce module ingests YouTube creator content (cooking, recipe, product reviews) and threads it into the shopping feed. Catalog-aware deep links — "shop this recipe" button. 2026 roadmap: YouTube Shopping API integration when the surface becomes available for retailers.
Used by · Social Commerce module · Creator partner pipeline
Programmable Search Engine + Custom Search JSON API Fallback discovery · merchant intelligence LIVE
How we use it. Catalog-quality signals during sourcing (find canonical product detail pages across vendor sites for ingredient validation). Fallback discovery layer when Vertex Retail Search lacks coverage for new SKUs. Competitive intelligence signal collection for the Ads module.
Used by · Sourcing module · IA validation · Ads competitive signals
Google Trends (via Trends API tier) Demand-signal layer for Ads + merchandising LIVE
How we use it. Trend signals feed the Ads module's bid optimization (rising trends get boosted CPC) and the merchandiser console's "what to feature this week" recommendations. Calibrated against grocer's actual basket data via the Analytics module.
Used by · Ads / RMN · Merchandiser console · Analytics
CCAI · Customer Conversation AI Customer-service AI · order status · dietary advisory ROADMAP
Plan. 2026 H2. Customer-service flows for the grocer's call center and chat support. CCAI Agent Assist gives reps real-time grounded answers from Delectable's Food + Shopper HyperGraphs. CCAI Insights for call analytics + intent classification. Reduces grocer support cost while consuming CCAI minutes.
Used by · Customer service flows · Support analytics · QA
Dialogflow CX IVR + scripted chat fallback ROADMAP
Plan. 2026 H2. Voice IVR for grocer call centers (order status, store hours, simple FAQ). Scripted-chat fallback when shoppers are outside the Gemini-Pro-confident reasoning band. Cheap, deterministic intents that don't need Vertex inference but still drive Google Cloud consumption.
Used by · IVR · Chat fallback · Long-tail intents
— Cross-cloud bridges · the migration motion

Pulling workloads into the Google stack.

Most Tier-2 grocers run hybrid clouds — some AWS, some Azure, some on-prem SAP. Delectable is the bridge that pulls catalog, transaction, loyalty, and content data out of those systems and into BigQuery / GCS / Pub-Sub — where Vertex AI and Gemini can reason over it. Every bridge we build is a workload Google didn't have last quarter.

— From · Foreign cloud

AWS-resident grocer data

  • S3 buckets · catalog images, transaction logs, media
  • Redshift / Snowflake · transaction warehouse
  • DynamoDB · session state, cart state
  • Personalize / Bedrock · displaced by Delectable + Vertex
→
Delectable bridge
+ BigQuery DTS
— To · Google Cloud

BigQuery + GCS + Vertex

  • BigQuery Data Transfer Service · Redshift / S3 → BQ scheduled
  • Storage Transfer Service · S3 → GCS sync, immutable lineage
  • Pub/Sub Lite + Eventarc · DynamoDB stream → BQ via Delectable adapter
  • Vertex AI · the new reasoning + retrieval layer
— From · Azure

Azure-resident grocer data

  • Azure Blob Storage · media, catalog files
  • Synapse / SQL Database · transaction warehouse
  • Azure OpenAI · displaced when grocer trials Gemini Pro
  • Azure Communication Services · displaced by Gmail / SendGrid
→
Delectable bridge
+ BigQuery Omni
— To · Google Cloud

BigQuery + GCS + Vertex

  • BigQuery Omni · query Azure SQL in place, materialize to BQ-native
  • Storage Transfer Service · Azure Blob → GCS
  • Vertex AI · Gemini Pro replaces Azure OpenAI in evals
  • Gmail / SendGrid · replace ACS for transactional
— From · ECom + ERP systems

SAP · VTEX · Salesforce · Shopify · BigCommerce

  • SAP S/4 + SAP Commerce Cloud · 30%+ of regional grocer ERP base
  • VTEX · LATAM + Tier-2 grocer ecommerce platform
  • Salesforce Commerce Cloud + Marketing Cloud · Tier-1 grocer common
  • Shopify Plus + BigCommerce · independent + DTC brand operators
→
Delectable
Sourcing module
— To · Google Cloud

BigQuery + Vertex + Workspace

  • Sourcing module · normalizes catalog → BQ enrichment_warehouse
  • PIM enrichment · 8 → 42 attrs, fed back to source OR to Merchant Center
  • Vertex Retail Search · the new on-site search layer
  • Google Ads · retail-media activation against the new attribute graph
— From · Loyalty + retail-media SaaS

Eagle Eye · Inmar · Stuzo · mParticle

  • Eagle Eye Loyalty · used at Giant Eagle (live Q1 2026), Loblaws, Tesco
  • Inmar · promo + circular networks, audience segments
  • Stuzo · convenience-store loyalty (7-Eleven, Circle K)
  • mParticle · CDP layer at most Tier-2+ grocers
→
Loyalty
connector pack
— To · Google Cloud

Shopper HyperGraph in BigQuery

  • BigQuery federated source · live join, no double-warehousing
  • Shopper HyperGraph · 847 signals per household derived
  • Google Ad Manager · first-party audiences activated
  • Vertex AI · household-level reasoning over loyalty data

Every bridge above is built or in active development. The full connector matrix lives at commerce/src/commerce/sourcing/connectors/ in the Delectable repo. Adding a new connector typically takes 1-2 weeks; we have 14 in production today.

— Implication for John's team

Tomorrow's meeting should expand.

The deck is structured for John's Food, Drug & CPG team — Cloud Sales. But the consumption picture above means a single Delectable deal threads quota for at least three other teams. Best move: bring them into the room.

Bring · Google Ads field

RMN + Ad Manager AE

$69B retail-media TAM. Demonstrate Ad Manager → Delectable Shopper-HyperGraph attribution loop. Field-level deal: CPG dollar flow.

Bring · Workspace + Maps

Workspace AE + Maps Platform PM

Gmail + Calendar + Drive integrations. Maps high-volume usage. Both surfaces light up monetization on the same grocer deal.

Bring · CCAI BD

CCAI partner lead

2026 H2 roadmap. Pre-positioning. Customer-service flows are the natural next workstream after shopper-facing agentic basket builds.

A single co-sell motion. Six Google P&Ls.

The same workstream that lights up Cloud Sales also lights up Ads, Workspace, Maps, YouTube, and CCAI. Multiplied quota attainment across six teams.

→ Co-sell playbook ↗ Architecture