Restaurant Produce Ordering: How Much to Order, How to Spec It, and How to Keep It Fresh

To order produce for a restaurant, count what you have in the units you actually use (bunches, heads, each, pounds), figure out how much you'll go through between now and the truck after this one, and order the difference in the vendor's pack sizes. Then adjust for two things that matter more with produce than with anything else: how long each item really lasts in your walk in, and what the price is doing this week.

Produce is the hardest category to order well. It spoils in days, the price can move between one order and the next, it comes in a mix of bunches, counts, and pounds, and two cases of the same item can look nothing alike. A par that works for canned tomatoes will either run you out of cilantro on Saturday or leave you throwing it away on Tuesday.

This guide covers what's different about ordering produce, with a full worked example of a weekend order.

In this guide

• Why produce needs its own ordering routine
• Order to the next truck, not the week
• Set pars by delivery day
• Count in the unit you use, order in the unit they sell
• Write specs your vendor can't misread
• Market prices and price swings
• Worked example: a Friday produce order
• Waste or 86: decide which way to lean, item by item
• Check quality at the door
• Storage and rotation
• What line cooks can do
• Common mistakes
• FAQ

Why produce needs its own ordering routine

Most of the ordering basics apply to produce: count, compare to par, order the gap, check the delivery. What changes is how much room for error you have.

• Short shelf life. A case of fryer oil can sit for weeks. A case of cilantro can't. Extra produce isn't "stock," it's a countdown.
• Price swings. Many produce items are priced on the market, so last week's invoice price isn't a promise.
• Mixed units. You might count romaine by the head, buy it by the 24 count case, count onions by the pound, and buy them in 50 lb sacks.
• Quality varies. Size, ripeness, and condition change from case to case and week to week. A spec that's clear to you might mean something else to the person packing your order.
• Frequent deliveries. Many kitchens get produce two or three times a week, often from a specialty produce vendor rather than the broadline. More deliveries means more orders, and each one has to be sized for a different stretch of days.

That last point is where most produce ordering goes wrong, so start there.

Order to the next truck, not the week

A produce order only has to last until the next produce truck arrives. Ordering "for the week" on a vendor that comes three times a week means carrying days of extra product that's aging the whole time.

Here's the rule I'd use: the amount you have after this delivery should cover everything you'll use until the next delivery lands, plus a small buffer. And because you count before this delivery arrives, the count also has to get you to the truck.

Say your produce vendor delivers Monday, Wednesday, and Friday mornings, the cutoff is the afternoon before, and you're open seven days. If you count on the morning of the cutoff day, each order covers:

The two weekday gaps are two days apart. The weekend gap is three. That one extra day, and the fact that it's usually your busiest stretch, is why the Friday produce order is so much bigger than the others.

If you haven't mapped your cutoffs and delivery days yet, our guide to building a vendor ordering schedule walks through it.

Set pars by delivery day

Because each order covers a different stretch, one par per item doesn't work for produce. Each order day needs its own par, built from what you actually use on the days that order covers.

Our guide to setting par levels covers the formula in detail. For produce, the important change is to use usage by day of the week, not an average day. Saturday cilantro and Tuesday cilantro aren't the same number.

Illustrative example with made up numbers. A kitchen tracks cilantro usage over a few weeks and gets this typical pattern, in bunches:

Using the coverage windows from the table above:

Sunday count (Monday truck):     Sun + Mon + Tue        = 8 + 5 + 5        = 18 bunches
Tuesday count (Wednesday truck): Tue + Wed + Thu        = 5 + 6 + 7        = 18 bunches
Thursday count (Friday truck):   Thu + Fri + Sat + Sun  = 7 + 10 + 12 + 8  = 37 bunches

Add a small buffer (here, 3 bunches midweek and 4 for the weekend, a judgment call based on how much busy days swing):

Now compare that with a single par of 30 bunches for every order:

Thursday: needs 37 to get to Monday, par of 30 leaves it 7 short  →  cilantro is 86'd Sunday night
Tuesday:  needs 18 to get to Friday, par of 30 carries 12 extra    →  12 bunches aging into the next order

One flat par is wrong in both directions. It's too low for the weekend and too high midweek.

Check the par against shelf life

Before you trust a produce par, compare the days it covers with how long that item really lasts in your kitchen. In this example the kitchen's own rule is that cilantro is good for about 5 days after delivery. Friday's delivery has to last until Monday morning, which is 3 days, so the par works.

If a par covers more days than the product lasts, don't raise it. Order more often, ask whether the vendor can deliver an extra day, or plan for the item to run out and have a backup ready. "Usable life" here means how long it stays good enough to serve in your walk in. Keep track of it from what you see, since it varies by item, season, and how it's stored.

Count in the unit you use, order in the unit they sell

Produce is where the gap between count units and order units is widest. A typical produce section of an order guide looks something like this:

Do the math in the count unit, then convert to cases at the end. Our guide to restaurant inventory units explains the conversion step by step.

Counting partial cases

Nobody counts a full produce cooler in whole cases. Some practical rules:

• Count items, not boxes, for anything you use by the piece: heads, bunches, each.
• Estimate pounds from the case weight for bulk items. A 25 lb case of Romas that's about a third full is roughly 8 lb. For expensive items, put it on a scale.
• Count only what you'd serve. If 3 of 12 romaine heads are browning, the count is 9. The other 3 go on your waste log, not your count. Counting product you're about to throw away is a fast way to run out.
• Count the oldest product first and note it. If half your avocados are already soft, that changes what you need Friday.

For prepped produce (diced onion, picked herbs, sliced tomato), decide whether you'll count it and convert it back to raw, or keep it on a separate prep count. Converting back to raw takes the item's yield, and our guide to running a restaurant yield test shows how to measure it. Our inventory count guide covers counting prepped food.

Write specs your vendor can't misread

"Avocados, 1 case" leaves a lot to the person packing your order. A clear spec line names the item, variety, pack, size or count, and anything else that changes how it cooks or plates.

A few terms worth knowing:

• Count. On citrus, avocados, and some other fruit, the count is how many pieces fit in the standard box. In the same box, a higher count means smaller fruit. That's why a 165 count case of lemons isn't a better deal than a 115 count case if you're juicing. Our guide to comparing vendor prices has more on count sizes.
• Grade. USDA publishes voluntary grade standards for many fresh fruits and vegetables. Tomatoes, for example, have a U.S. No. 1 grade with requirements around maturity, shape, and freedom from decay and damage (USDA AMS). Many vendor catalogs use their own quality labels instead. If your vendor lists "choice" and "premium," ask what the difference is and get a sample.
• Ripeness. For avocados, tomatoes, bananas, and stone fruit, tell the vendor when you plan to use them. Many produce vendors will take a ripeness note. Ask yours.
• Substitutions. Say what's acceptable before it happens: "Roma or vine OK," "no subs on Hass." Our guide to shorted items and substitutions covers setting sub rules with your vendor.

Put these specs in your order guide so they go out the same way no matter who orders.

Market prices and price swings

On many produce price lists, some items show a fixed price and others say "market" or "MKT." Market means the price isn't set ahead of time. It follows what the vendor is paying, which can change from one order to the next.

Weather in growing regions is one of the big drivers. USDA's Economic Research Service attributed a 3.8 percent rise in fresh vegetable prices in 2019 mainly to bad weather in several growing areas, and noted that regional weather can move one crop's price without touching others (USDA ERS). Its December 2024 vegetable outlook described losses from extreme heat in California and hurricanes in Florida, with grower prices up for lettuce, onions, carrots, and tomatoes (USDA ERS, VGS-374).

You can't control the market, but you can avoid surprises:

• Ask for the price before cutoff on any market item that's a big part of the order. A quick text to your rep is enough.
• Set a "call me if over" note on items like avocados or berries: "Hass 48 ct, call if over $65."
• Compare against your last invoice, not your memory. If you keep an order history, the last price is easy to find.
• Check the wholesale market if a jump looks big. USDA's Agricultural Marketing Service publishes terminal market reports, issued daily from major U.S. wholesale markets, covering hundreds of fruits and vegetables (USDA Market News). Those are wholesale prices, not what your distributor will charge, but they can tell you whether a jump is happening everywhere or just on your invoice.
• Decide your move ahead of time. When a key item spikes, your options are usually to pay it, adjust the portion or the dish, run a special that uses a cheaper item, or buy a different size or grade. Pick one before cutoff, not at the back door.

If a vendor consistently comes in higher than another on the same spec, that's a price comparison question, not a market one.

Worked example: a Friday produce order

This is an illustrative example. The restaurant, vendor, usage, prices, and shelf life rules are made up to show the method. They don't describe any real vendor or restaurant.

Setup:

• Open seven days. Specialty produce vendor delivers Monday, Wednesday, and Friday mornings, with a cutoff the afternoon before.
• The kitchen counts produce Thursday morning. Friday's delivery has to carry it until Monday's truck, so the count plus this order must cover Thursday through Sunday.
• The vendor will break a case of cilantro and sell loose bunches at $1.10 each. A full 30 bunch case is $24.00, or $24.00 ÷ 30 = $0.80 a bunch.
• Avocados are market priced. The last invoice was $56.00 a case. Thursday's quote is $68.00.

Here are five lines from the order:

"Left Monday morning" is count plus order minus usage. For cilantro: 9 + 30 + 2 = 41, and 41 − 37 = 4.

Every line needs the same quick check first: does what's on hand get you to Friday's truck? Cilantro is tight. The kitchen has 9 bunches and uses about 7 on Thursday, so it starts Friday with 2. That's fine as long as the truck is on time. If this vendor runs late often, Thursday's count is the moment to plan a backup.

Now the rounding decisions, which are where produce ordering actually happens.

Cilantro: don't round up to a second case

Short of par:                41 − 9 = 32 bunches
One case:                    30 bunches  →  2 short of par
Two cases:                   60 bunches  →  9 + 60 = 69, leaving 69 − 37 = 32 bunches Monday morning

Thirty two bunches on Monday morning is far more than the 10 the kitchen uses Monday and Tuesday (5 + 5). That would leave 22 bunches on Wednesday morning, 5 days after delivery and at the end of this kitchen's usable life rule. Most of them get thrown away:

22 bunches × $0.80 = $17.60 of cilantro in the trash

Instead, the kitchen orders one case plus 2 loose bunches:

1 case + 2 loose:            $24.00 + (2 × $1.10) = $26.20  →  exactly at par (41)

Loose bunches cost more each, but the kitchen only buys what it will use. If your vendor won't break cases, ordering one case and accepting a 2 bunch gap against a 4 bunch buffer is usually a safer bet than a second case.

Romaine: round up

One case gets the kitchen to 36 heads, 2 over par, with 6 left Monday morning. Romaine lasts a few days in this kitchen, and Monday's truck brings fresh product, so rounding up is easy.

Avocados: order to par, watch the price, spec the ripeness

Last price per avocado:      $56.00 ÷ 48 = $1.17 (rounded)
This week per avocado:       $68.00 ÷ 48 = $1.42 (rounded)
Increase:                    $12.00 ÷ 48 = $0.25 per avocado

Extra cost on 44 avocados used Thursday to Sunday:   44 × $0.25 = $11.00

Eleven dollars over the weekend isn't worth pulling guacamole off the menu. It might be worth not running the avocado toast special this week, or it might not. The point is that the chef sees the number before cutoff instead of finding it on the invoice.

The order also includes a ripeness note: "half ripe for Friday, half firm for Sunday." With 18 avocados left Monday morning, firmer fruit is less likely to go past ripe before it's used.

Lemons and onions: rounding up is fine

Both need far less than a full case, but the kitchen's on hand won't cover the weekend, so the choice is one case or none. Both last well in this kitchen (lemons in the walk in, onions in dry storage), so the extra rolls into next week's orders. The cost is cash sitting on the shelf, not waste. Just remember Sunday's count will show plenty of both, and Monday's order shouldn't include them.

What these five lines cost

Cilantro:       $26.20
Romaine:        $38.50
Avocados:       $68.00
Lemons:         $42.00
Onions:         $29.50
Total:          $204.20

If a midweek produce order regularly falls under your vendor's minimum, our guide to order minimums and delivery fees works through whether to pay the fee or add items.

Waste or 86: decide which way to lean, item by item

With produce you'll rarely land exactly on par. When you have to round, the question is which mistake costs less for that item: a little extra that might go bad, or running out.

Write the lean next to each item on your order guide so whoever orders makes the same call. If something keeps running out anyway, an 86 log will show whether it's the par, the count, or the vendor.

Check quality at the door

Produce is where checking the truck matters most, because problems hide in the bottom of the case. The receiving section of our purchasing guide covers the full process. For produce specifically:

• Open at least one case of each item. Look at the bottom layer, not just the top.
• Check the count on count items. If the invoice says 48 avocados, a quick count tells you if it's 44.
• Weigh pound items that matter for cost, like tomatoes or a case of mushrooms, against the invoice weight.
• Check ripeness and size against your spec, not just "is it the right item."
• Check temperature on cut produce. The FDA Food Code treats cut leafy greens, cut tomatoes, and cut melons as foods that need time and temperature control for safety, which generally means holding them at 41°F or below (Oregon Department of Agriculture, Navy and Marine Corps Public Health Center). States adopt different versions of the Food Code, so confirm the rules with your local health department.
• Refuse what you won't serve, and get it on the invoice before the driver leaves. Our guide to shorts and substitutions covers getting the credit.

Storage and rotation

Good ordering doesn't help if the product dies in the walk in. A few habits that protect your produce:

• First in, first out. Put new product behind or under old product. Date every case when it comes in so nobody has to guess.
• Keep ethylene producers away from sensitive items. Some produce gives off ethylene gas as it ripens, which speeds up aging in produce nearby. Extension guidance lists apples, avocados, bananas, melons, peaches, pears, and tomatoes as ethylene producers, and broccoli, cabbage, cauliflower, leafy greens, and lettuce as sensitive (Ask Extension). In the example above, that means the avocados shouldn't sit on the shelf right above the romaine.
• Don't store basil in the coldest spot. Most herbs keep best very cold, but basil is chilling sensitive. Postharvest guidance from UC Davis and Rutgers puts basil's storage temperature at about 50°F or above, warmer than most walk ins run (UC Davis research, Rutgers NJAES). In practice, that often means keeping the walk in supply small, using it fast, and ordering it more often.
• Track what gets thrown out. A quick waste log (item, amount, reason) tells you which pars are too high. If you're throwing out the same item every Tuesday, the Monday par is wrong.

What line cooks can do

The person placing the produce order is usually working from a count and a par sheet. The line sees things neither of those shows:

• Tell whoever orders when quality drops. "The parsley from Wednesday is already yellowing" is useful information for the next spec or the next vendor conversation.
• Use the oldest first, even when the new case is easier to reach.
• Don't stash product on your station for tomorrow. Hidden produce doesn't get counted, so it gets ordered again.
• Speak up about specials and big parties early. A Saturday special that uses 6 extra bunches of basil needs to be on Thursday's order, not mentioned Friday night.

Common mistakes

• One par for every order day. It runs you out on the weekend and buries you midweek.
• Ordering "for the week" on a vendor that comes three times a week.
• Counting product you're about to throw out.
• Rounding up to full cases on herbs and other fragile items when the vendor sells loose bunches or half cases.
• Vague specs that leave size, ripeness, and substitutions up to the packer.
• Finding market prices on the invoice instead of asking before cutoff.
• Checking the top layer only at the back door.
• Not recording usable life. If nobody writes down that the cilantro is done by day five, the next par will ignore it.

FAQ

How much produce should a restaurant order?

Enough to cover what you'll use from your count until the delivery after this one arrives, plus a small buffer, minus what you have on hand. Use usage for the specific days the order covers, not an average day, and check that the amount doesn't outlast the item's usable life. Then round to the vendor's pack sizes, leaning up for items that keep and down for items that don't.

How often should a restaurant order produce?

It depends on your volume, storage space, and what your vendors offer. The tradeoff is simple: more frequent deliveries mean smaller orders, fresher product, and less waste, but more orders to place and more trucks to check. If your pars for fragile items keep running longer than those items last, that's a sign you need more frequent deliveries for that category.

What does "market price" mean on a produce invoice?

It means the price isn't fixed ahead of time and follows what the vendor is paying. It can change from one order to the next. Ask your rep for the current price before cutoff on any market item that's a big part of your order, and add a "call me if over" note for items that swing a lot.

Should I buy produce from my broadline or a specialty produce vendor?

Compare them on the same spec, by cost per usable unit, and include delivery fees and minimums. Specialty produce vendors often deliver more frequently and may break cases, which can matter more than a lower case price for short shelf life items. Our vendor price comparison guide walks through it, and our guide to choosing between broadline and specialty distributors has a worked example of splitting produce off the broadline, including the minimums and ordering time.

How do I count a partial case of produce?

Count in the unit you use: bunches, heads, each, or pounds. Estimate pounds from the full case weight, or weigh expensive items. Only count product you'd actually serve. Anything past its prime goes on the waste log.

What should I do when a produce delivery arrives in bad condition?

Refuse what you won't serve and have the driver note it on the invoice, or contact your rep right away if you find it after the truck leaves. Then cover the gap and adjust the next order. Our guide to shorted items and substitutions covers credits and backup sources.

Keeping produce orders consistent with Proteus Kitchen

A clipboard and a well built order guide can handle everything in this article. What's hard is keeping it consistent when different people order on different days. Proteus Kitchen keeps your produce items and vendors in one place. Each item can be counted in one unit (like bunches) and ordered in another (like cases), with the conversion saved, so the daily count and the order don't get mixed up. Each vendor has its delivery days, order deadlines, ordering method, and a notes field. Each item has its own notes field too, which is a good place for specs and ripeness notes.

When you build a purchase order, Proteus shows each item's current amount, its target, a suggested quantity, and an estimated total based on the last vendor price, so you can compare this week's market quote with what you paid last time. Proteus keeps one target per item, so if you run different pars for different order days, write them in the item's notes. It generates the order as text to send through the vendor's portal, a text, or an email. It doesn't place orders with vendors for you, and it doesn't need a POS integration. Past orders stay in your history, so last week's price and quantity are easy to find.

If your produce order guide is already in a spreadsheet, Free Restaurant Setup covers bringing it into Proteus, and there's a 30 day free trial below.

Sources

• USDA Economic Research Service, Charts of Note: fresh vegetable prices and weather (2019 fresh vegetable price rise attributed mainly to weather)
• USDA Economic Research Service, Vegetables and Pulses Outlook, VGS-374, December 2024 (2024 weather losses and higher grower prices)
• USDA Agricultural Marketing Service, Market News: Types of Reports (terminal market reports)
• USDA Agricultural Marketing Service, Tomato Grades and Standards (voluntary U.S. grade standards)
• Ask Extension, Ethylene producing and ethylene sensitive produce
• UC Davis, Basil Postharvest Chilling Sensitivity and the Impact of Storage Temperature and Atmosphere on Sensory Quality
• Rutgers NJAES, Fact Sheet FS1283 (basil storage temperature)
• Oregon Department of Agriculture, Food Code fact sheet: cut leafy greens
• Navy and Marine Corps Public Health Center, Cut Tomatoes fact sheet

Next step: fix your Friday produce order

1. Pull two to four weeks of usage for your top 10 produce items, by day of the week.
2. Write down which days each produce order covers, from count to the following truck.
3. Set a separate par for each order day, and check each one against how long the item really lasts in your walk in.
4. Add clear specs and a "lean up" or "lean down" note to each item on your order guide.
5. On your next order, ask for prices on market items before cutoff and compare them to your last invoice.