Selected work / Meal prep company

Meal prep company · Operations automation

A grocery list that builds itself from weekly orders.

3-4 hrs → 30 min weekly order processing, zero missed items

The problem

The company offers 40-plus weekly menu items. Every week the owner exported Wix orders and manually translated 90-plus order lines into a menu tally and grocery list: counting items, unpacking combos, tracking dietary modifications, looking up recipes, multiplying quantities, checking inventory. Three to four hours of error-prone work, every single week.

What we built

A full-stack web app with a deterministic ten-step pipeline. Upload the weekly CSV and it parses every order, explodes combos into individual items, classifies dietary modifications, maps products to a 566-row recipe database, computes exact ingredient quantities, deducts inventory, and prints a menu tally that matches her existing kitchen template. Anything ambiguous gets flagged, never silently skipped.

Before: 3-4 hours a week, by hand

Read
  • Open the CSV in Excel
  • Note variants and mods by row
Count
  • Tally each product by hand
  • Unpack combo orders mentally
Look up
  • Find each recipe in a spreadsheet
  • Multiply by order count
Shop
  • Check pantry, calculate packages
  • Hope nothing was missed

After: under 30 minutes a week

Upload
  • Export the Wix CSV
  • Drop it in the app
Print
  • Menu tally generated
  • Grocery list by store aisle
Review
  • Scan flagged exceptions
  • Adjust if needed
Shop
  • Package counts calculated
  • Grouped by store section

How it was built

The work, step by step.

  • Next.js
  • Custom web app
  • Claude Code
  1. 01

    Parse the weekly export

    Filters non-food and unpaid orders; extracts the date range for the run.

  2. 02

    Explode combos and variants

    Starter kits become individual items; size, flavour, and base variants parsed from raw order strings.

  3. 03

    Classify dietary modifications

    Customer notes mapped to dietary buckets (gluten-free, dairy-free, no onion) with priority-ranked rules.

  4. 04

    Compute the ingredients

    A 566-row recipe database multiplied against order counts, with dynamic grain substitution for skillets.

  5. 05

    Build the outputs

    Inventory deducted, store package counts calculated, menu tally formatted to match the owner’s printed kitchen template exactly.

In the wild

Order upload: drag and drop the weekly Wix export.
Order upload: drag and drop the weekly Wix export.
Grocery list output: grouped by aisle, package counts calculated, anomalies flagged for review.
Grocery list output: grouped by aisle, package counts calculated, anomalies flagged for review.

Have a workflow like this? Let's look at it.

A free, 20-minute readiness call. We'll tell you honestly whether it's a two-week build or a bigger one.