💡 Vendor Farming Practices Discovery Filters

[github-actions[bot]]

Summary

Enable vendors to declare their farming and production practices (organic, no-spray, regenerative, pasture-raised, etc.) as structured profile attributes, and let customers filter and discover vendors by practice. Unlike certifications, these are vendor-stated practices with optional manager verification, creating a searchable trust layer that differentiates Markets from directory-style competitors.

Market Signal

Localize generates $100K/month revenue from 200K installs by targeting specific dietary communities (raw dairy, grass-fed, pasture-raised) with 218K products across 30+ categories — validating that practice-based food discovery is a viable and monetizable market. However, Localize surfaces product categories, not farming practices. A customer searching for "no-spray apples" cannot distinguish between conventional and sustainable growers on any existing platform. Farmish offers no practice filtering. The farm-to-table transparency movement continues to accelerate, with 73% of consumers saying they want more information about how their food is produced (2025 FMI Power of Produce survey). Source: screensdesign.com Localize analysis, FMI survey (Aug 2026).

User Signal

The PRD defines Rachel as a "health-conscious weekly market shopper" — exactly the persona who cares deeply about farming practices. The product's existing product catalog (FR12, vendor_products table) captures what is sold but not how it is produced. The UX spec's Category Filter pattern (filter chips with flex-wrap) already provides the interaction model for practice-based filtering. Multiple existing ideas focus on product discovery (#362 Seasonal Produce, #370 What's Fresh Today, #394 Product-Level Following) but none address practice-based discovery — a significant gap for the health-conscious target demographic.

Technical Opportunity

The architecture defines vendor profiles (vendors table) and product catalogs (vendor_products table). Adding a vendor_practices junction table (vendor_id, practice_type ENUM, self_declared BOOLEAN, manager_verified BOOLEAN, verified_at TIMESTAMP) extends the data model cleanly. The GraphQL vendor.graphqls schema can expose practices as a filterable field on vendor queries. NativeWind filter chips (per UX-DR pattern) render the practice filters in the customer discovery view. The manager verification workflow reuses the existing market_vendors approval pattern (FR10), keeping the implementation DRY.

Assessment

Dimension	Score	Rationale
Feasibility	high	Junction table + enum + filter chips. Reuses existing approval workflow pattern. No new services needed.
Impact	med	Differentiates from Localize's category-only approach. Directly serves the health-conscious Rachel persona. Validated by $100K/mo Localize revenue.
Urgency	low	Most valuable when vendor profiles and customer search are live (post-Epic 3 and Epic 6). Can be added incrementally.

Adversarial Review

Strongest objection: Self-declared badges without verification are meaningless — any vendor can claim "organic" without USDA certification. This creates false trust signals that could damage platform credibility when customers discover discrepancies.

Rebuttal: The framing is critical: these are "vendor-stated practices," NOT certifications. The UI clearly labels them as "Vendor states: no-spray" with an optional "Verified by [Market Name]" badge when a manager confirms. This mirrors how farmers markets work today — managers know their vendors' practices and vouch for them informally. Digitalizing this existing trust chain (vendor declares → manager optionally verifies) adds a layer of accountability that doesn't exist anywhere else. For USDA-certified organic vendors, the certification can be noted separately as a distinct, verified attribute. The platform does not create the risk of false claims — it creates accountability by making claims visible, searchable, and trackable.

Suggested Next Step

Define the practice taxonomy (8-12 common farming practices: organic, no-spray, regenerative, pasture-raised, grass-fed, free-range, non-GMO, biodynamic, permaculture, integrated pest management, hydroponic, wild-caught) and create a quick spec for the vendor_practices data model, vendor profile practice declaration UX, manager verification flow, and customer discovery filter integration.