The problem
Meal prep commerce is two jobs: help a customer choose the right food, then help the kitchen make the right amount of it. A catalog alone doesn't handle customization, nutrition, recurring meal plans, event ordering, or the handoff to the kitchen.
What I built
The original store is a Next.js and Payload CMS application with Supabase accounts, customizable meal components, nutrition data, meal plans, cart and order flows, and email and SMS notifications.
The second phase, Sprezza Sports, is a Shopify app for tournament meals: a reusable meal library, event menus, team and recipient allocations, handoff details, paid meal totals, and kitchen prep.
From an order to a cooking plan
Shopify owns payment and order truth. My app adds the event context and turns confirmed, paid quantities into kitchen totals. Unpaid, cancelled, refunded, or ambiguous orders are held back for review instead of becoming kitchen work.
Meal variants map to reviewed recipes and ingredients. Batch yields, shared components, stock on hand, and purchasing units all shape the grocery and prep plan. If a recipe mapping hasn't been reviewed, the plan says so instead of producing a confident wrong number.