💡 CSA Share Integration & Market-Day Pickup Coordination

[github-actions[bot]]

Summary

Let vendors who run Community Supported Agriculture (CSA) programs coordinate share pickups at their market stalls. CSA members get notified when their share is ready, bridging two local food ecosystems that currently operate in separate silos and driving high-value vendor acquisition.

Market Signal

CSA programs are rapidly going mobile — Local Line and GrownBy are expanding CSA management features in 2026. USDA reports 7,000+ CSA farms in the US. The cross-pollination between CSA sales and farmers market sales is well-documented (many CSA farmers also sell retail at markets), but no platform bridges the two operationally. The MarketLink/TotilPay ecosystem includes GrownBy eCommerce but doesn't integrate with market-day coordination. This is a structural gap in the local food technology landscape.

User Signal

The PRD identifies Brad (multi-market organic produce vendor) as the primary vendor persona — Brad-type vendors are the most likely to also run CSA programs. The existing vendor check-in workflow (FR14) creates a natural extension point: when a vendor checks in, they can also flag "CSA pickups available today." No existing idea discussions cover CSA integration, despite CSA being one of the most established local food distribution models.

Technical Opportunity

The architecture already supports vendor-to-market associations and check-in events (Epic 4). CSA pickup coordination is a natural extension of the domain event bus — a vendor CSA check-in triggers notifications to CSA member followers via the existing FCM/Firebase Realtime infrastructure. Apollo Client cache can store CSA membership state. The exception-first UX principle applies beautifully: vendors only flag CSA availability when pickup is ready, not manage the full CSA lifecycle. The lightweight approach means minimal schema additions (a csa_pickup_available boolean on the vendor market-day status, plus a csa_member follow relationship type).

Assessment

Dimension	Score	Rationale
Feasibility	med	Requires new CSA-specific data model (share types, member relationships) but builds on existing check-in and notification infrastructure. MVP can be very lightweight.
Impact	high	Each CSA vendor brings 20-100 dedicated members into the app ecosystem. Bridges two previously siloed local food communities. Strong vendor acquisition magnet.
Urgency	med	CSA management tools are evolving fast (Local Line, GrownBy). Establishing market-day pickup coordination before competitors adds it creates positioning advantage.

Adversarial Review

Strongest objection: Only 10-20% of market vendors run CSA programs — the addressable user base may be too small to justify development cost.

Rebuttal: CSA vendors are high-value anchor tenants who bring their dedicated customer base into the app. Each CSA vendor acquisition effectively onboards 20-100 CSA members as new market customers who then discover other vendors and markets. The feature serves as a vendor acquisition magnet with outsized network effects even if the CSA-specific functionality is only used by a subset. Additionally, CSA pickup at markets reduces the vendor's separate distribution overhead, making market participation more attractive.

Suggested Next Step

Research the Local Line and GrownBy APIs/data models to understand CSA share structures. Design a lightweight "CSA pickup available" toggle on the vendor check-in screen. Interview 3-5 CSA vendors who also sell at markets to validate the coordination pain point and understand current workarounds.