How to price meal prep when some meals go unsold

The batch has to be paid for by the meals you sell

Dividing a meal-prep batch by the number of containers filled gives you a production cost per meal. It does not tell you how much each paid order must recover if some containers are left over.

Keep two numbers: meals produced and meals expected to sell. The difference is especially useful when you cook before orders close, offer several menu choices or make extra portions to avoid selling out. More choice may be useful to customers, but it can leave money sitting in unsold stock.

Start with the entire batch’s cost, including work that is easy to overlook: purchasing, preparation, portioning, packing, cleanup and delivery. Use a consistent boundary. If delivery is charged separately, compare its revenue and costs separately rather than treating delivery revenue as meal revenue while ignoring the route cost.

Worked example: 50 meals cost USD 280 to prepare and deliver

This example assumes all 50 meals are prepared and packed, with no recovery value for unsold meals. Labor, delivery and overhead stay at the amounts shown even if fewer meals sell. The USD figures are invented for the calculation; they are not current supplier prices or a recommended selling price.

The production cost is $280 ÷ 50 = $5.60 per meal made. At an $8 price, selling the whole batch brings in $400 and leaves $120 after the costs entered here: a 30% margin before payment fees, taxes or other omitted costs.

Now keep the same prepared batch but change the number sold. This is not a forecast; it is a way to see how sensitive the result is to unsold meals.

At 45 sales, each paid meal has to recover about $6.22 of batch costs, and the margin falls to 22.2%. At 40 sales, it falls to 12.5%. Neither result is visible if you keep dividing by 50 after the week’s orders come in.

Match raw purchase weights to the portions you serve

Before relying on the ingredient total, check cooking yield. In a separate illustration, 2 kg of raw chicken costing $20 produces 1.5 kg of cooked chicken. Ten cooked portions of 150 g each therefore carry $2 of chicken cost per portion. Multiplying the raw cost per gram by 150 cooked grams would give $1.50 and understate the cost.

Record the raw amount purchased, the usable cooked amount and the portion you actually pack. Keep the weight basis next to each number. Rice is another place where raw purchase weight and cooked serving weight can be mixed accidentally; use a measured batch yield rather than swapping the two.

The BC Cook Articulation Committee’s yield-testing method provides the underlying distinction between purchased and usable quantities. Cooking loss is different from an unsold finished meal. Include both when they occur, but count each loss once.

Calculate a target price using expected paid orders

If you expect to sell 45 of the 50 meals and choose a 30% margin on the entered batch costs, the arithmetic is ($280 ÷ 45) ÷ (1 − 0.30). That gives $8.888…; rounding up gives $8.89 per paid meal. Thirty percent is a chosen scenario here, not a universal meal-prep benchmark.

If fees are a percentage of sales, adding them as a fixed amount before you know the price can miss their effect. For a fee rate f and target margin m, use: (batch cost per paid meal + fixed fee per meal) ÷ (1 − m − f). Enter rates as decimals. The denominator must be positive.

For example, with an illustrative 3% processing fee and a $0.30 transaction fee spread across an average order of five meals, the fixed fee is $0.06 per meal. Using the same batch and target, ($280 ÷ 45 + $0.06) ÷ (1 − 0.30 − 0.03) rounds up to $9.38. These are example fee assumptions, not a provider’s quoted rates.

This calculation gives you a cost-based candidate price. It does not prove demand at that price. Compare the portion, menu and delivery offer with what your customers value, and test a realistic order count before committing to a larger batch.

Check bundle discounts against the costs they actually save

A five-meal order might save delivery time or spread a fixed transaction fee. It does not automatically make the chicken, containers or preparation five times cheaper. Before offering a bundle discount, write down which costs fall and by how much.

In the example above, ten five-meal orders would spread a $0.30 transaction fee to $0.06 per meal; fifty separate one-meal orders would cost $0.30 per meal in fixed transaction fees. The difference is $0.24 per meal before any delivery saving. That is a more useful starting point for a discount than an arbitrary percentage.

Likewise, a delivery minimum should reflect the actual route and order size. Allocating a $30 route across 50 paid meals adds $0.60 each. Across 30 paid meals it adds $1.00, if the route cost stays the same. Changing the delivery promise may change the route itself, so revisit the assumption rather than treating it as permanent.

Review the batch after sales close

Keep a short record of meals made, full-price sales, discounted sales and unsold meals. Use actual revenue when some meals sell at a discount; multiplying every meal by the headline price will overstate it. Record what happened to leftovers rather than automatically treating them as a full-price sale.

Then update next week’s quantity or ordering deadline. The worksheet below helps you compare expected and actual figures. The free calculator can also cost a batch using your sellable portion count. Inventory Boss can keep recipe ingredients, manually recorded sales and waste together; it does not forecast demand, manage meal subscriptions or calculate nutrition labels.