💡 Cross-Market Vendor Week-at-a-Glance

[github-actions[bot]]

Summary

A weekly calendar view showing all markets a vendor attends, visible to both the vendor (for schedule management) and their followers (for trip planning). Customers following a vendor who attends multiple markets see a "Where to find [vendor] this week" card with market names, days, times, distances, and check-in status. Vendors see their own multi-market commitment overview.

Market Signal

No competitor shows a vendor's multi-market schedule from the customer perspective. Farmish shows vendor profiles but not market-specific schedules. Seen Markets and Marketspread are manager-centric and don't surface vendor schedules to consumers. The multi-market vendor (Brad persona) is a primary user — research shows vendors commonly attend 2-4 markets per week and struggle to communicate their schedule to customers.

User Signal

The PRD's Brad persona is explicitly a "multi-market organic produce vendor." FR13 supports vendors joining multiple markets. FR24 allows customers to view vendor market participation status. But no requirement currently surfaces a consolidated week view. Customer journey 1 (Rachel) describes following vendors — knowing WHEN and WHERE they'll be next directly supports the "confident trip" use case.

Technical Opportunity

Built on existing vendor-market associations (FR13) and the vendor profile/schedule data model. The calendar view is a read-only aggregation of vendor_market_day records. No new backend endpoints needed — a GraphQL query joining vendor → market_roster → market_schedule provides the data. Frontend: a simple calendar component in both the vendor profile (customer view) and vendor dashboard. Leverages Gluestack UI calendar/date components.

Assessment

Dimension	Score	Rationale
Feasibility	high	Read-only aggregation of existing data model. No new infrastructure. Simple calendar UI.
Impact	high	Directly serves both primary personas (Brad's schedule management, Rachel's trip planning).
Urgency	high	Core vendor and customer need from day 1. Multi-market vendors are a primary adoption target.

Adversarial Review

Strongest objection: Most customers only visit one market weekly. Multi-market customers are a small niche — is this worth building?

Rebuttal: While the CUSTOMER benefit initially serves power users, the feature primarily serves VENDORS by giving them a unified schedule view and making their multi-market presence discoverable. It helps new customers discover additional market days for their favorite vendor, increasing vendor reach. Implementation cost is very low — it's a read-only aggregation of existing data with a calendar UI component.

Suggested Next Step

Design the GraphQL query for vendor weekly schedule aggregation and mock up the customer-facing "Where to find [vendor] this week" card component using Gluestack UI.

[b4631119-oss]

cool