MealPrep.exe is a local-first meal-prep ERP for small-batch, home-based meal-prep businesses. It replaces the spreadsheets, WhatsApp groups, and notebooks that most chefs juggle with one purpose-built web app.

The problem it solves: a chef has to plan menus each week, let clients order online, track who ordered what, calculate exact batch counts, generate shopping lists, optimise delivery routes, and keep on top of allergen safety. Most chefs run three or more tools to do it. MealPrep.exe replaces all of them.

For the chef

Recipe builder: build meals from 818 real USDA ingredients with live cost and margin as you add them, plus auto-inherited allergens.
Weekly menu planner: pick meals and publish when ready; unpublished meals stay hidden from clients.
Order management: cards on a status workflow (pending → confirmed → prep → delivered), filterable by status.
Batch counts: total portions per meal across all confirmed orders for the week.
Shopping list: aggregated ingredients grouped by category, tickable while shopping, printable.
Delivery route: an OR-Tools TSP solver turns client addresses into the optimal stop order with total miles and Google Maps links.
Ingredient archive: 818 real USDA ingredients with full nutrition, plus custom ingredients and USDA lookup.

For the client

Public menu: browse published meals with prices, calories, and macros. No login needed.
PIN login: a simple four-digit PIN per client; no passwords or email verification.
Allergen warnings: a red border and warning icon on any meal containing a client's allergens.
Order placement: select portions, submit; the order starts as pending until the chef confirms.
Order history: track past orders with colour-coded status badges.

How an order moves

The chef creates meals, plans the week, and clicks publish.
A client browses the menu, logs in with their PIN, and submits an order.
The chef sees the order as pending and confirms it.
The batch and shopping pages plan production.
The chef cooks, then marks the order delivered.
The client checks their history for live status updates.

Under the hood

FastAPI and SQLite on the backend, a dependency-free vanilla JS frontend, a mobile-first dark theme built for the kitchen, and OR-Tools routing for deliveries. No cloud required: it runs on a laptop in the kitchen at localhost:8000, and the whole database is a single portable file.