Repository navigation
💡 Manager-verified SNAP/EBT acceptance badge & Discover filter #69
Replies: 2 comments
Weekly UpdateWhat ChangedNew competitive intelligence on digital SNAP/EBT infrastructure at farmers markets:
Updated Assessment
RecommendationAdvance. The discovery layer (badge + filter) is clearly the right scope — don't build payment infrastructure. MarketLink already handles the payment side. Markets' value-add is surfacing SNAP acceptance in the discovery flow so Rachel can filter for "SNAP-accepted" when searching. Consider partnership positioning with MarketLink rather than competing. |
Weekly UpdateWhat Changed
Updated Assessment
RecommendationAdvance. The USDA's FY2026 cooperative agreement signals strong federal interest in mobile SNAP at farmers markets. The urgency increases because the SNAP ecosystem is actively being modernized, creating a window to integrate with emerging tools (MarketLink/TotilPay) rather than building from scratch. Consider whether the SNAP badge feature should also surface nutrition incentive program availability (Double Up Food Bucks) alongside EBT acceptance — this would make the feature significantly more valuable to SNAP customers. Weekly feature ideation update — 2026-08-07. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Add a SNAP/EBT acceptance attribute on markets and vendors, expose it as a search/filter in customer Discover, and badge it on listing and detail screens. Make the platform the most reliable place for low-income shoppers to find SNAP-eligible vendors before they travel.
Market Signal
User Signal
_bmad-output/planning-artifacts/research/feature-priority-matrix-market-app-2026-03-15.md).epics.mdimplements SNAP/EBT as a market or vendor attribute, search filter, or badge — onlyNFR14mentions not storing payment credentials. There is a planning-to-implementation gap here.Technical Opportunity
accepts_snap_ebtboolean (and optionalsnap_match_programenum: none / Double Up / market-token) to the existing market and vendor profile tables shipped in Epic 2 / Epic 3.lucide-react-nativehas a wallet icon).Assessment
Adversarial Review
Strongest objection: "Self-attested SNAP acceptance becomes a trust hazard — vendors will mark themselves as accepting and customers will arrive to find they don't, which is exactly the failed-trip the product is supposed to prevent."
Rebuttal: Gate the badge on manager confirmation, not vendor self-attestation. Markets are already a manager-curated roster (Epic 2/4), and the manager dashboard can require an "I have verified this vendor's SNAP authorization" checkbox before the badge becomes visible to customers. This converts a trust risk into a market-manager trust signal — exactly the platform's differentiator.
Suggested Next Step
Spike a one-page tech spec covering: (1) schema migration, (2) manager-confirmation workflow, (3) Discover filter UX, (4) vendor-profile badge, (5) analytics events to measure SNAP-filtered search → follow conversion. Use the bmad-quick-spec workflow.
Proposed by the BMAD Analyst (Mary) on 2026-04-07.
Workflow run
All reactions