Data foundations
The operational food data your organization already maintains — unified, structured, and ready for emissions modeling.
Data we handle
Menus & recipes
Ingredient lists, portions, and preparation methods mapped to emissions factors.
Meal sales
Transaction and volume data from meal sales, meal plans, and service records.
Purchasing
Vendor invoices and procurement records to validate sourcing and categories.
Site structure
Location, client, and reporting hierarchy for multi-site rollups.
Structured for emissions modeling
Menus, recipes, purchasing records, meal sales, and site metadata are normalized into a consistent data foundation — validated and structured before reports are generated.
Sample data view
GreenEats validates coverage across each site — how many locations have menus, sales, and purchasing connected — so reports are based on complete operational data.
Sample data for Westbridge University Dining, 12 dining locations.
Menus & recipes
11 of 12 dining locations1,240 items
Across all dining locations
Ingredients, portions, and preparation methods by location.
Meal sales
12 of 12 dining locations2.1M transactions
FY2025 · all locations
Meal sales and transaction data by site, station, and period.
Purchasing
11 of 12 dining locations18,400 line items
FY2025 invoices
Vendor invoices and procurement records by category.
Site metadata
12 of 12 dining locations12 dining locations
Campus dining network
Property and reporting identifiers for multi-site rollups.
Data coverage by site
12 dining locations
| Location | Menus | Sales | Purchasing |
|---|---|---|---|
| North Campus Dining | ✓ | ✓ | ✓ |
| Medical Center Café | ✓ | ✓ | ✓ |
| Union Food Court | ✓ | ✓ | — |
| Athletics Concessions | — | ✓ | ✓ |
Gaps at Union Food Court (purchasing) and Athletics Concessions (menus) explain why some data types show 11 of 12 dining locations connected.
See this with your data.
Generate a first sample report from existing dining data.