YoTummy App

YoTummy launched into a category - cottage-kitchen food sales - that lives or dies on trust, permit compliance, and the math of perishable inventory.

• Per-region cottage-food rules: What a home cook can legally sell varies by jurisdiction - hot meals in some markets, baked-goods-only in others, vacuum-sealed jams elsewhere; the listing flow had to enforce permit limits at upload time.
• Allergen disclosure that holds up: Diners with peanut, gluten, or dairy intolerances need allergen tags that surface in search, not buried in description fields.
• Batch-size economics: Home cooks make 8 portions of biryani, not 80; the marketplace had to prevent overselling without making the listing flow feel like a spreadsheet.
• Pickup, not delivery: Routing couriers around a home kitchen was off the table; the product needed an appointment-style pickup-window flow with neighbour-friendly arrival nudges.
• Zero-commission revenue model: The platform pledged zero cut on the food itself, so monetisation had to come from optional add-ons cooks would actually opt into.

We built YoTummy on Angular with a PHP back-end tuned around perishable inventory and a permit-aware listing builder.

• Permit-gated listing builder: Cooks pick their cottage-food permit type on onboarding; the listing form only allows categories that permit covers, with state-specific labelling baked in.
• Allergen schema in search: Every dish carries a structured allergen vector (peanut, tree-nut, gluten, dairy, egg, shellfish, soy, sesame); search filters resolve against the vector, not free text.
• Portion-cap inventory: Cooks set today's portion ceiling per dish; the listing automatically pulls itself when the last portion is reserved, no manual unpublish.
• Pickup-window slots: Diners reserve a 15-minute pickup window; the cook sees their afternoon as a Calendly-style schedule with arrival nudges 10 minutes out.
• Walking-distance feed: Default search radius is half a mile expanding outward; cuisine, dietary, and permit-type filters layer on top.
• Revenue add-ons: SMS reminder packs, printable pickup labels, and a featured-listing boost are paid extras cooks opt into - the food transaction itself is fee-free.

The app shipped to both stores, found product-market fit fastest in three high-density cottage-kitchen pockets, and gave cooks a measurable economic step-up.

• Live in three permit-friendly states at launch with a roadmap to add jurisdictions as permit-mapping is added.
• Median cook gross weekly take: $147 within 90 days of joining, up from zero (most cooks had never sold publicly before).
• Over-promise incidents (cancelled portions) under 2 % thanks to portion-cap inventory and automatic unpublish.
• Allergen-related complaints: zero across the first 4,000 transactions, attributed to the structured-tag enforcement.
• Pickup-window adherence: 91 % of diners arrived within their booked 15-minute slot.
• Add-on attach rate: 34 % of active cooks opt in to at least one paid extra, validating the zero-commission revenue model.