💡 Restaurant & Chef Bulk Pre-Order Channel for Market-Day Pickup

[github-actions[bot]]

Summary

Enable restaurants, cafes, and catering businesses to browse vendor catalogs, place bulk pre-orders for market-day pickup, and build recurring supply relationships through the platform. Creates a high-value B2B revenue channel for vendors alongside the existing B2C market experience, without requiring a separate role — implemented as a "business account" flag on customer accounts.

Market Signal

Farm-to-table restaurant sourcing is a growing market segment with strong tailwinds. Local Line and Barn2Door focus on farm-to-buyer ecommerce but don't integrate with market-day operations — they require separate logistics. The USDA Farmers Market Promotion Program (FMPP) actively funds projects connecting institutional buyers (restaurants, schools, hospitals) to market vendors. Flashfood's May 2026 launch of "Flashfood For Partners" — a dedicated B2B app for retail partners — signals growing industry appetite for structured B2B channels in the local food space. The gap: no platform connects restaurants to market vendors within the market-day coordination workflow.

User Signal

No existing idea discussion addresses B2B/wholesale buyer needs — this is a blind spot in the current 47-idea backlog. The PRD's vendor persona Brad explicitly wants "increased discoverability and repeat customer flow" — a single restaurant ordering $500/week provides more revenue stability and discoverability than 50 individual $10 purchases. Market managers (FR10a) already have vendor search and invitation workflows that conceptually extend to buyer-vendor matching. Discussion #372 (Reserve-at-Market Intent Signaling) covers individual customer pre-orders; this scales the concept to wholesale quantities with recurring relationships.

Technical Opportunity

The customer account model (FR1) can accommodate a "business" flag without a full 4th role — keeping the three-role architecture clean. GraphQL schema already supports product catalogs (FR12) and vendor profiles (FR11) that bulk buyers would browse. Pre-orders are structurally similar to the reserve-at-market intent signaling in Discussion #372 but for larger quantities. The vendor notification infrastructure (FR29-31) supports order notifications. The manager governance system (FR10c: market rules) provides the control mechanism — managers can enable/disable bulk ordering per market. Key constraint: this should be positioned as post-MVP growth since the core 3-role coordination loop must work first.

Assessment

Dimension	Score	Rationale
Feasibility	low	Requires new order management flow, pricing tiers (wholesale vs retail), recurring relationship tracking, and pickup coordination. Not architecturally complex but feature-rich. Explicitly post-MVP.
Impact	high	Opens an entirely new revenue channel for vendors. One restaurant relationship can match dozens of individual customer transactions. Creates strong vendor retention (vendors stay on the platform because of B2B revenue). Potential FMPP grant alignment.
Urgency	low	No competitor does this within a market-day coordination app. The opportunity is real but can wait until after MVP proves the core coordination loop. Establishing the idea now ensures it's on the roadmap when the time is right.

Adversarial Review

Strongest objection: This is premature scope expansion for a project that hasn't shipped MVP. Adding wholesale/B2B capabilities before the core 3-role coordination loop works risks diluting focus. Additionally, many farmers market rules restrict or prohibit wholesale transactions to protect consumer access to products.

Rebuttal: This is explicitly positioned as a post-MVP growth feature, not an MVP addition. The infrastructure foundation — vendor catalogs, product listings, notification system, follow relationships — is being built for MVP anyway. B2B pre-orders layer on top without architectural changes. On market rules: the feature respects market governance by letting managers enable/disable bulk ordering per market, aligning with FR10c (market rules that vendors must acknowledge). Vendors independently set their own wholesale availability, minimum quantities, and pricing. The strongest argument for planning this now: one restaurant buying $500/week from a vendor provides more revenue stability than 50 individual customers, directly supporting vendor retention on the platform — which is critical for the multi-actor flywheel the PRD describes.

Suggested Next Step

Interview 3-5 farm-to-table restaurant owners/chefs about their current sourcing workflow from farmers markets — how do they currently order, what's frustrating, what would they pay for convenience. Research market governance rules around wholesale transactions at target pilot markets. Design a lightweight "business account" profile extension on the customer model that doesn't require a 4th role in the auth system.