💡 Seasonal Produce Discovery Overlay

[github-actions[bot]]

Summary

Integrate seasonal produce availability data with the customer discovery flow. When customers search or browse, surface "What's in season near you" prompts that connect to vendors listing those products. Combines the Seasonal Food Guide's 170+ item database with vendor product catalogs to bridge general food literacy with specific vendor discovery — "Peaches are in season → 3 vendors sell peaches → 2 are checked in today."

Market Signal

The Seasonal Food Guide app (170+ items, zip-code localized) proves demand for seasonal awareness. No farmers market app connects seasonal data to specific vendor catalogs. Research shows customers segment into health-conscious shoppers and culinary enthusiasts who actively seek seasonal produce. CSA subscription models validate the concept of seasonal-awareness driving purchase behavior. Local food demand continues growing with USDA promotion programs.

User Signal

Rachel persona is a "health-conscious weekly market shopper" who plans Saturday shopping. FR23 supports product-intent discovery. Adding seasonal context enriches this: "organic eggs + it's peach season, here are peach vendors too." Seasonal discovery directly supports the search-to-follow conversion metric identified as the primary success signal in the PRD.

Technical Opportunity

Seasonal produce data is publicly available and can be stored as a static dataset keyed by USDA zone and half-month period. Vendor product categories already planned (FR12: vendor product catalog). A simple join between seasonal data and vendor product tags enables the overlay. Implementation: seed database with seasonal data, add a "seasonal picks" section to the Discover screen, filter vendors by seasonally-relevant products. No new infrastructure needed.

Assessment

Dimension	Score	Rationale
Feasibility	high	Public seasonal data, static dataset, simple join with existing vendor product categories.
Impact	med	Enhances discovery and browsing, drives search→follow conversion, but doesn't solve a critical pain point.
Urgency	low	Nice-to-have enhancement for the discovery flow. Can be added post-MVP without architectural changes.

Adversarial Review

Strongest objection: Seasonal data is generic — it doesn't tell you what a specific vendor actually has today. This is informational, not transactional.

Rebuttal: The value is in the DISCOVERY phase, not confirmation. Seasonal data drives browsing and following behavior: "What should I look for at the market this week?" Combined with real-time check-in status, it becomes actionable: "Peaches are in season → 3 vendors sell peaches at your market → 2 are checked in today." It bridges the gap between general food curiosity and specific vendor engagement, supporting the search-to-follow conversion metric.

Suggested Next Step

Research the Seasonal Food Guide data format and licensing. Prototype a "What's in Season" card component for the Discover screen that maps seasonal items to vendor product categories.