Charlie's Coffee data landscape

Live operations sit in AlloyDB. Historical performance, market demand, locations, and reviews sit in BigQuery. Broker documents sit in Cloud Storage.

Show a relationship

stores.store_id = historical_sales.store_id One store maps to many weekly sales rows.

AlloyDB

Operational data

What is happening now

BigQuery

Analytical data

History and growth

Cloud Storage

Broker documents

Proposed terms for each site

market_demand

Weekly coffee-category demand for every ZIP in the scenario, including ZIPs where Charlie's does not yet operate.

Grain
one ZIP × ISO week
Join with
zip_code
Useful for
Forecasting market demand and deriving Charlie's capture rate.