The meal plan is a calendar of breakfast, lunch, and dinner slots for your household. Click a slot to search recipes — results already filtered by everyone's restrictions — or leave slots empty and let the shuffle do the thinking.
Weekly rules (“fish at most once”, “meatless Mondays”) live on the plan itself, and curated starter plans give you a base to riff on.
Shuffle fills every empty future slot with recipes that fit your rules and restrictions. If some slots already have meals you've shopped for, NOM asks before touching them — fill only the empty slots, or replace the week and start fresh.
One tap turns the coming days into a shopping list. NOM merges quantities across recipes (three recipes' worth of onions becomes one line), converts recipe units into the units stores sell — pounds, fluid ounces, cans — and groups everything by department in the order you walk the store: produce first, frozen last.
Already have it? Items in your pantry are subtracted before the list is built.
Completing a shopping trip moves items into the household pantry with expiration estimates by category — days for fresh produce, months for the spice rack. The pantry feeds back into shopping lists so you never buy a fourth jar of cumin.
Invite family with a code. Every member gets their own profile and restrictions; the plan, pantry, and shopping lists are shared. In-app messaging keeps the “grab milk on your way home” coordination next to the list itself.
The public recipe wall you may have seen on this site is a feature flag each NOM instance sets for itself. Hosting private diet setups for your family, or a client list as a coach or dietitian? Leave it off: your instance shows nothing to the world, and every recipe, restriction, and plan stays behind login.
Import recipes from a URL, write your own, or start from the built-in library. Collect them into cookbooks, rate them, and the ones your household actually likes float to the top of search and shuffle.
Where we focus
Most nutrition tools assume one person logging meals at a desk. NOM designs around the opposite: a household planning together, and somebody standing in aisle six wondering how many cans three recipes add up to.
A calendar of the household's breakfasts, lunches, and dinners. Tap a slot to pick a recipe — already filtered by everyone's restrictions — or hit shuffle and let NOM fill the gaps by the plan's rules.
The coming days become one consolidated list: quantities merged across recipes, recipe units converted to what stores actually sell, grouped by department in walking order. What's already in the pantry gets subtracted first.