💡 Vendor Attendance Track Record for Customer Confidence

[github-actions[bot]]

Summary

Display a vendor's historical attendance reliability on their profile — showing how consistently they show up on committed market days (e.g., "Attended 47 of 48 market days"). This directly serves the platform's confidence-first positioning by giving customers evidence-backed trust signals before deciding to visit a market.

Market Signal

Uber, Lyft, and Airbnb all use reliability signals to build trust in two-sided marketplaces. No farmers market app surfaces vendor reliability data to customers. Seen Markets and Marketspread track vendor applications and booth assignments but don't expose attendance consistency to customers. The broader "trust economy" trend shows consumers increasingly expect transparency about service provider reliability before committing their time and money.

User Signal

The PRD's primary KPI is "failed-trip reduction" and the core metric is "customer confidence that translates into trips taken and completed." Customer Journey #1 explicitly describes Rachel being "burned twice" by unreliable vendor information. This feature directly instruments the confidence-first positioning by giving customers evidence to make go/no-go decisions. Distinct from idea #389 (Manager Market Health Analytics) which is manager-facing market trends, not customer-facing vendor trust signals.

Technical Opportunity

Check-in data is already captured by the system (FR14). The architecture includes an append-only audit log (FR35, internal/audit/) that records all check-in/checkout events with timestamps. Computing attendance percentage is a straightforward aggregate query against existing data. The vendor profile component (VendorCard) already supports badges and metadata display. The freshness timestamp component (UX-DR6, FreshnessTimestamp) provides the UI pattern for time-contextual data display.

Assessment

Dimension	Score	Rationale
Feasibility	high	All required data is already captured by the check-in system and audit log. Implementation is a read-only aggregate query + a profile badge component. No new infrastructure needed.
Impact	high	Directly serves the platform's core differentiator (confidence-first positioning). Gives customers a reason to trust the app over social media or word-of-mouth. Creates positive reinforcement for reliable vendors.
Urgency	med	Requires sufficient check-in history data to be meaningful (minimum ~4-6 weeks of market days). Design now, activate after initial vendor adoption stabilizes.

Adversarial Review

Strongest objection: Vendors might resist a public reliability metric, seeing it as punitive — especially when absences happen for legitimate reasons (illness, weather cancellations, family emergencies). This could hurt vendor adoption, which is the critical supply-side constraint.

Rebuttal: Frame it positively as a "track record" rather than a "score." Show the positive stat ("Attended 47 of 48 market days") rather than a penalty rating. Managers can excuse legitimate absences (weather cancellations, approved leave) so they don't count against the record. Vendors who show up consistently will embrace this as differentiation against unreliable competitors — it rewards exactly the behavior the platform wants to encourage.

Suggested Next Step

Design the attendance calculation logic: define what counts as a "committed market day" (roster commitment vs. calendar-based), how manager-excused absences are handled, and the minimum number of market days before a track record is displayed. Mock up the VendorCard treatment showing the track record badge.

---

Generated by the weekly feature ideation workflow on 2026-08-07.