Farm to Table Directory

Home › Guides › Sourcing & Farm Partnerships › Planning Crop Yields for Restaurant Demand

Sourcing & Farm Partnerships

Planning Crop Yields for Restaurant Demand

The most common conversation between a chef and a farmer goes something like this: "How much arugula can you give me in June?" The honest answer is, "It depends," and the work of turning that into a plan is the heart of crop planning for restaurants. Matching what a farm grows to what a kitchen actually uses prevents shortages, gluts, and wasted effort. This article explains how to estimate demand, translate it into plantings, build in buffers for weather and loss, and use communication to keep both sides on track.

Start with demand, not seed

Crop planning for restaurants begins with the menu. What dishes use the crop, how often do they sell, and how much is used per serving? A chef who knows that the restaurant sells about forty salads a day and uses a defined weight of greens in each can estimate weekly demand.

Gather data from past purchase records, menu mix reports, and prep sheets. If you are new, start with rough estimates and refine them. Account for seasonality in covers, since summer patio season or holiday periods can double or halve volume. Note which items are fixed on the menu and which rotate.

Distinguish between must-have and nice-to-have items. A restaurant that cannot function without basil needs a reliable supply, while one that treats radish microgreens as a garnish can be flexible. Sharing this priority list helps the farmer plan. See Planning a Farm to Table Menu Year Round for the menu planning side.

Converting servings into pounds

The math is straightforward, but needs care. Here is a hypothetical example, clearly labeled as an illustration.

  • A restaurant sells 40 side salads per day, 6 days a week, in summer: 240 per week.
  • Each salad uses 3 ounces of cleaned greens: 720 ounces, or 45 pounds of cleaned greens per week.
  • Trimming loss: cleaned weight is often a fraction of harvested weight, so the farm might need to harvest noticeably more than 45 pounds, depending on the crop and quality standards.

Always work from usable yield: the weight after trimming, washing, and discarding damaged product. The ratio varies by crop. A crop like carrots may lose little in trimming, while artichokes and fresh peas lose a lot in waste. Ask the chef for the usable yield they need, and ask the farmer for the usual loss factor.

Put the numbers in a simple spreadsheet: crop, weekly use, start and end dates, price, and notes. Review with the farmer in winter and update regularly. For the farm-side picture, read Seasonal Sourcing How Farms Plan for Your Menu.

From demand to plantings

Farmers convert weekly demand into plant counts or row feet using their own yield data. Yield per row foot depends on variety, soil, spacing, season, and skill. Records from previous years are the best guide. For new crops, farmers use extension guides or trial plantings.

Succession planting, sowing small amounts at intervals, spreads harvest over weeks. A restaurant needing consistent lettuce each week might have plantings every one to two weeks. Single-harvest crops, such as sweet corn or bulb onions, need careful timing to hit a window.

Include time from seed to harvest, which varies with temperature. A crop sown in cool spring may take much longer than one sown in warm summer. Farmers also account for germination failure, pest damage, and weather by planting extra. For crops grown under cover, see From Greenhouse to Table Growing Year Round.

Buffers, risk, and sharing the loss

Weather, pests, and disease make exact predictions impossible. Good plans build buffers. Farmers often plant ten to thirty percent more than the target for crops with high risk, though the right margin depends on the crop and the farm's experience. The extra product needs a home, such as other customers, a market, a CSA, processing, or donation.

Chefs can reduce the risk by staying flexible, accepting substitutes, and committing to a base volume. Some restaurants pay a modest premium or agree to buy a minimum quantity in exchange for guaranteed supply. Others agree to take the entire crop, using surpluses in specials, preserves, or staff meals.

Discuss what happens when things go wrong. If a crop fails, who bears the cost? Common approaches include crop failure with no penalty, partial shortfalls with substitution, and share-the-risk pricing. Writing it down avoids conflicts. See How Restaurants Choose Their Farm Partners.

Pricing and commitments

Pre-season conversations can include price agreements, deposits, and purchase commitments. Some restaurants pay in advance for a share of a farm's production, similar to a CSA. This helps farm cash flow in spring when expenses are high.

Price should reflect the cost of growing, harvest, packing, and delivery, plus a fair profit. Clarify whether prices are fixed for the season or change weekly with the market. Fixed pricing helps planning but exposes one side to market swings.

Here is another hypothetical example: if a farm's cost to grow, harvest, and pack a pound of mixed greens is $4.50 and the farm wants a margin, the price must exceed that. A chef uses the price per usable pound to calculate dish cost. See How to Price Farm to Table Menus Profitably and Pricing Strategies for Small Farms. All numbers here are illustrative, and real costs vary widely.

Communication rhythm

A planning system works only if both sides talk. A rough rhythm:

  1. Winter: share menu ideas, volumes, and priority crops; farm shares seed orders and plan.
  2. Early spring: confirm plantings and first harvest dates.
  3. Weekly in season: farm sends availability; chef sends orders.
  4. Mid-season: review what is working; adjust plantings for later succession.
  5. Fall: plan storage crops and winter supply.
  6. End of year: review sales, waste, and lessons; set goals for next year.

Share data. If a chef sees that salads have stopped selling in cool weather, telling the farm early can prevent over-planting. If a farmer sees a crop is coming early, a quick call lets the kitchen plan a feature.

Apps and spreadsheets help but are not required. See How to Use Data to Grow Local Food Sales for ways to use data.

Food safety and handling in planning

Planning should consider post-harvest handling. Harvest timing should match delivery to preserve quality, and cooling capacity limits how much can be harvested at once. A farm without a walk-in cooler cannot harvest a large amount of greens ahead of a delivery.

Document traceability. Keep records of harvest dates, fields, and customers for each lot. Follow produce safety rules and ask your state department of agriculture about requirements for your farm size. See the FDA for general produce safety information. Also consider how product will be stored in the restaurant, since overbuying leads to spoilage.

Learning from each season

At season's end, compare plan with reality. Where were you short, and where did you have too much? Why? Was it weather, planting errors, menu change, or poor communication? Record lessons.

Over time, estimates improve. A farm that has supplied a restaurant for several years often knows its needs better than the restaurant does. These relationships produce the best food and the least waste. Keep an eye on the wider picture too; see The Challenge of Scaling Local Food Production for what happens when demand grows beyond a farm's capacity.

For more from the farm side, FARM.fm's roadside farm stand story is a light look at keeping customers coming back, and FARM.fm's farm stand self-checkout satire is a good laugh about technology at the farm gate.

FAQ

How far ahead should a restaurant tell a farm what it needs?

Ideally in winter, before the farmer orders seed and plans plantings. For long-lead crops, earlier is better.

How much extra should a farm plant?

It varies by crop and risk. Many farms plant a margin above target and plan an outlet for surplus.

What if a crop fails?

Agree in advance on substitutions, shared risk, or credits. Communicate early so the kitchen can adjust.

Keep learning

Browse all 259 guides →