💡 Vendor Compliance & Market Rules Acknowledgment Workflow

[github-actions[bot]]

Summary

Structured digital workflow where market managers define rules, insurance requirements, and compliance checklists that vendors must acknowledge before joining a market roster. Replaces paper-based compliance tracking that managers currently do via email and spreadsheets. Directly extends FR10c (market rules acknowledgment) with document upload, expiration tracking, and automated renewal reminders — turning a simple text acknowledgment into a full compliance management system.

Market Signal

FDA food traceability rules took effect January 20, 2026, requiring full supply-chain tracing capability for covered foods. Market manager pain points research identifies compliance management as a top operational challenge — manual tracking of insurance certificates, health permits, and organic certifications across dozens of vendors. ManageMyMarket and Marketspread offer basic vendor application management but lack ongoing compliance tracking with expiration alerts. The farmers market management software category is now positioned as a "necessity, not a futuristic concept" — compliance is a primary driver of adoption. Sources: FDA Traceability Rules, Market Management Software Trends.

User Signal

The PRD includes FR10c: "Market Manager can define market rules/expectations that vendors must acknowledge before joining." The current specification is a text-based acknowledgment — a checkbox. Research shows managers need document management (insurance certificates with specific coverage amounts, health department permits with expiration dates, organic certifications from accredited bodies) with automated expiration tracking. Maria (manager persona) currently tracks this across spreadsheets and email attachments — the exact manual coordination the platform aims to eliminate. 25 issues closed in the last 30 days are all compliance/infrastructure related, showing the project has strong compliance DNA.

Technical Opportunity

The planned architecture already includes audit logging via PostgreSQL triggers on all domain tables (FR35) and role-based visibility (FR42). Compliance documents can be stored as references in Cloud Storage with metadata in Cloud SQL — the Go backend's existing file handling patterns apply. The vendor join request flow (FR13) is the natural integration point — adding a compliance checklist step before roster approval. The internal/auth/ middleware already enforces market-scoped permissions, ensuring managers only see compliance for their markets. The audit subsystem (Epic 8) provides the immutable record trail required for compliance documentation.

Assessment

Dimension	Score	Rationale
Feasibility	high	Extends existing FR10c and FR13 flows; no new infrastructure needed beyond Cloud Storage
Impact	med	Critical for manager adoption but doesn't directly touch customer or vendor core loops
Urgency	high	FDA traceability rules already in effect; managers need this before onboarding at scale

Adversarial Review

Strongest objection: This is operational tooling for managers, not coordination infrastructure. It doesn't help Rachel find her vendor or help Brad check in faster. It risks turning Markets into ManageMyMarket — a back-office tool — when the competitive advantage is the multi-actor coordination flywheel.

Rebuttal: Manager adoption is the supply-side enabler — without managers, there are no organized markets for vendors and customers. The PRD explicitly positions the manager as "secondary but critical enabler." Compliance tracking directly reduces the coordination overhead that makes managers reluctant to adopt new tools. The feature strengthens the flywheel: managers adopt because compliance is easier → more markets onboard → more vendors join → more customers discover. ManageMyMarket charges $150+/mo for this as a standalone tool; Markets includes it as part of the unified coordination platform, making the switching cost argument stronger.

Suggested Next Step

Extend FR10c specification in the PRD to include document upload, expiration tracking, and automated renewal notifications. Design the compliance checklist schema as part of the market profile domain model. Prioritize for Epic 2 (Market Administration) as an enhancement to the vendor roster management flow.