Meal Prep SoftwareFree GuidesOur StoryBook a demo

Flambia

Meal Prep Menu Planning in 2026: How Many Dishes, How Often to Rotate, and Who Decides

Size the menu from arithmetic, not from the chef’s imagination. A 5-meal day with no dish repeated within 7 days needs 35 distinct dish slots a week, and every dish beyond that adds a cooking line to the morning. Rotate on a weekly cycle, swap ingredients with the seasons, and let customer ratings plus a price cap decide what stays.

Menu planning is where meal prep businesses quietly win or quietly bleed. The menu decides your food cost, your morning, and whether customers stay past month two. Here is how I planned menus across my brands, Black Monkey Cooks, Cebulka and Primate, and the rules I would hand any operator drawing up their first weekly cycle.

How many dishes does a meal prep menu need?

Start with the promise you make to the customer, because the promise sets the floor. A prepaid daily meal-set carries 5 meals, breakfast through dinner. If you promise that no dish repeats within 7 days, one week of one plan needs 35 distinct dish slots. That is the floor: enough variety that a customer eating you every day never sees the same plate twice in a week. The ceiling is set by your kitchen, not by your ambition. Each plan you add shares most of its dishes with the others, so the real number to watch is the count of distinct dishes cooked on any single morning, not the length of the dish library. My rule: the menu is big enough when customers stop mentioning repeats, and small enough that the morning still ends in the morning. If you are still designing the operation itself, begin with how to start a meal prep business.

Why does every extra dish multiply the morning?

Because a dish is not a line on a menu; a dish is a production line in your kitchen. Each needs its own chopping board, oven slot, portioning tray, and printed label run. Cooking 20 distinct dishes on a morning means 20 small factories running in parallel before the couriers arrive. Add a 21st and you have not added a sliver more work, you have added one more setup, one more cleanup, one more place a cook can grab the wrong tray. At peak my kitchen packed about two thousand prepaid meal-sets, roughly ten thousand individual meals, in one morning, and the only way that fits into hours is a menu where every dish earns its production line. The cost side of the same discipline lives in what is a good food cost percentage for meal prep.

How often should you rotate the menu?

Weekly. The weekly cycle matches how customers order, how you buy, and how you plan production, so any other cadence fights the rhythm of the business. Publish next week’s lineup before the order deadline, cook against paid orders, then repeat. Rotation does not mean invention. A rotating menu draws from a stable dish library; the cycle reshuffles proven dishes so a Tuesday in March does not look like a Tuesday in February. Resist the urge to rotate faster to seem creative. New dishes carry risk in 3 places at once: an untested recipe cost, an unproven cooking time, and an unknown customer reaction. Introduce 1 or 2 new dishes per cycle at most, and retire something when you do. A menu that only ever grows is a menu nobody is managing.

Who decides which dishes stay: the chef or the customers?

The customers, with the food cost holding the second pen. Chefs defend dishes they enjoy cooking; customers defend dishes they enjoy eating; only one of those groups pays you. In my kitchens, customers were prompted by email and in-app after delivery to rate each dish, and those ratings drove what stayed in the rotation. The mechanism matters: better-rated dishes get chosen more, balanced against food cost by a weight the operator sets. A beloved dish that costs half its price cannot dominate the menu, and a cheap dish nobody rates well should not survive on margin alone. Without a rating loop you are guessing from complaint emails, which only surface the angriest tenth of your customers. Ratings also protect retention, because the dish a customer hates twice is the dish that cancels the plan; more on that in meal prep customer retention.

When should you swap dishes for the season?

Twice a year at minimum, and by ingredient before by recipe. The cheapest seasonal move is swapping components inside a proven dish: the same chicken dish carries roasted root vegetables in January and a tomato salad in July, keeping the recipe’s tested cooking time and customer rating while the ingredient price follows the harvest. Whole-dish swaps come second: pumpkin soup and beef stew earn their spot in November and fight for survival in June. Watch your supplier invoices as the calendar turns, because seasonality shows up there before it shows up on any food blog. The operator habit worth copying: when a key ingredient’s price climbs for the season, swap it out of the recipe rather than swallowing the cost or raising the dish price mid-cycle. Customers forgive a vegetable change; they remember a price change.

What does the bloated-menu death spiral look like?

It starts with kindness. A customer asks for a baked salmon option, the chef adds it. Another wants a vegan dessert, in it goes. Nothing is ever retired, because every dish has at least one fan. A year later the library is enormous, the morning runs long, and cooks are context-switching between dishes they cook once a fortnight and never get fast at. Quality slips first on the rare dishes, complaints rise, and the instinct is to add more options to please the complainers, which stretches the shift again. The spiral only breaks one way: cut. Rank the library by rating and by food cost, keep the winners on both counts, and force every addition to name the dish it replaces. A short menu cooked brilliantly beats a long menu cooked adequately, every week of the year.

What keeps a planned menu profitable?

Constraints set before taste gets a vote. Two did the heavy lifting in my kitchens. First, macro bounds: every day’s menu had to land inside hard protein, fat, and carbohydrate ranges for each plan, so a week could never drift indulgent because the chef felt inspired. Second, a price cap: a ceiling on ingredient cost per dish slot, checked at planning time rather than discovered on the invoice. In my own operation an optimiser composed the rotating menu under hard macro bounds, a price cap, and a no-repeat-within-7-days rule, which meant the discipline was enforced before a single pan was heated. You can run the same three constraints on paper; what matters is that they run before cooking, not after. Set the cap from your target ratio and your dish prices, and revisit both when you revisit how to price meal prep meals.

Take the cost sheet that keeps a menu disciplined

A price cap is only as good as the target numbers behind it, so here are mine.

Get the food-cost benchmark sheet, free.
The target ratios I watched weekly across my brands: ingredients, packing, courier share, contribution per bag. One page to lay beside your own numbers every week. Straight to your inbox.

Frequently asked questions

Should customers pick their own meals?

Offer swaps within the planned menu, not free choice across the library. Full choice destroys the production math, because you lose the certainty of knowing what to cook before you buy. A swap between two planned dishes keeps the morning predictable while giving the customer a sense of control.

Can a dish repeat two weeks in a row?

Yes, and your best dishes should. The no-repeat discipline lives inside the week, protecting the daily eater from seeing the same plate twice in seven days. Across weeks, repetition is how a dish earns its keep; a top-rated dish appearing every cycle is a feature, not laziness.

How do you retire a low-rated dish without losing its fans?

Announce the change inside the menu, replace it with something from the same category, and watch the scores on the replacement. Fans of one dish rarely cancel over its retirement; customers cancel over slipping quality across the whole week, which is what a bloated library causes.

Do different diet plans need separate menus?

No. Plans should share one dish library, with each dish portioned differently to hit each plan’s macro ranges. Separate menus per plan multiply the workload for no customer benefit; shared dishes with adjusted portions keep variety high and the number of distinct dishes cooked per day low.

Where to go from here

Run your dish costs and prices through the operator profit calculator to see what your current menu does to weekly contribution. The pricing side lives in how to price meal prep meals, and the wider operator guides in the operator playbook. When you want the whole sequence with the scripts in hand, the founder’s starter kit is here.

Book a demo with the founder