The chef who ordered your carrots may not be there when you deliver them.
Someone else opens the back door. They have a prep list, another supplier waiting and no particular reason to know about the conversation you had on Monday. They need to know what you brought, whether the kitchen ordered it, where it goes and who can answer a question.
Your carrots can be excellent while that moment is awkward.
I admire the care growers put into producing something a chef wants to serve. There is judgment in the variety, the harvest and the decision about what is good enough to leave the farm. A restaurant relationship asks that care to travel a little farther: onto the order confirmation, through the receiving door and into the next purchasing decision.
The first paid order gives the kitchen a chance to discover what working with the farm actually feels like. Flavor matters. So do a usable pack size, a delivery that fits the day and an invoice that reaches the right person.
That is the part of farm marketing I want to examine here: helping an interested restaurant become a customer that can comfortably buy again.
Give the trial a specific job
Consider an illustrative order, not a client case study. A neighborhood restaurant wants to try a grower’s carrots for a roasted vegetable side. The chef asks for 20 pounds on Thursday, ahead of the weekend.
“Twenty pounds of carrots” sounds settled. It leaves several useful questions unanswered.
Does the chef want small whole carrots for a composed plate, or larger roots that the kitchen will cut? Tops on or off? Two ten-pound cases, or four five-pound packs? Is the trial for one special, or a possible regular menu item? Who receives deliveries on Thursday morning?
The answers change what a successful order looks like. Mixed sizes may be perfectly useful for a purée and frustrating for a dish designed around three matching whole carrots. A generous case can become an expensive purchase if the kitchen cannot use it.
Ask what the ingredient needs to do. Then agree on the product specification and a quantity the restaurant can meaningfully test. A first order should be large enough to teach both businesses something, without requiring either one to make a commitment it does not yet understand.
University of Minnesota Extension similarly advises direct-market growers to discuss buyers’ product requirements, pack sizes, pricing and purchasing processes. Its guidance is a useful foundation for that first conversation.1
In our example, the chef chooses topped carrots in an agreed size range, packed as two ten-pound cases. The grower confirms Thursday between 9 and 10 a.m. The chef names the sous-chef as the receiving contact and identifies who can approve a change.
Now the farm has an order it can fulfill and the restaurant has an order it can recognize.
Make the promise small enough to keep and clear enough to use
The order confirmation should separate what is confirmed for this delivery from what might be available later.
“Twenty pounds confirmed for Thursday” is different from “we expect a similar quantity next week.” Both statements can be helpful. Combining them into a vague promise of ongoing supply invites a menu decision the farm may not be able to support.
Substitutions need the same care. A different variety, maturity or size can change preparation and presentation. Record who may approve a substitution, how to reach them and what happens if they do not respond. Unless an alternative was agreed in advance, silence should not become permission to send something else.
Price needs a unit attached. State the price per pound or pack, the expected total, any delivery charge and how a variable-weight order will be billed. Agree on the payment method, due date and invoice recipient before unloading the truck.
Also ask whether the restaurant needs supplier setup completed before purchasing. Getting the chef’s approval and getting the business ready to receive and pay a new vendor may involve different people.
These details can live in a short email. What matters is that the farm, buyer, receiver and invoice recipient are working from the same agreement.
The first-order information sheet
This completed example uses fictional order details and illustrative pricing. Replace the terms with what both businesses actually agree. Keep contact details available to the people handling the order.
- Order reference
- Trial 001 · Thursday delivery · Restaurant name and delivery address recorded here.
- Product and purpose
- Topped carrots, agreed size range; trial for a roasted vegetable side. Confirm the written specification with the buyer.
- Quantity and pack
- Two cases × 10 lb net weight = 20 lb total. Label each case with farm, product, net weight and the farm’s applicable lot identification.
- Price and total
- Illustrative agreed price: $2.50/lb; product total $50. Delivery $10; order total $60, before any applicable tax. No additional product without approval.
- Availability
- This order confirmed. Next Thursday’s quantity remains subject to the next availability confirmation; no standing order established.
- Substitutions
- No substitutions without the chef’s written approval. Farm contacts buyer about a shortfall before dispatch and confirms the revised quantity and invoice.
- Delivery and access
- Thursday, 9–10 a.m., rear receiving entrance. Record access instructions and call the receiving contact if delayed or unable to enter.
- People to contact
- Buyer: chef’s name and number. Receiving: sous-chef’s name and number. Backup: manager’s name and number. Farm: primary and backup contacts. Identify who may authorize changes.
- Receiving and handling
- Check quantity, specification and condition with the receiver. Supply crop-specific handling information consistent with the farm’s procedures and restaurant requirements. Do not leave unattended without an agreed, suitable handoff arrangement.
- Invoice and payment
- Invoice Trial 001 emailed to the agreed accounts contact and copied to the buyer. Example agreed terms: payment by bank transfer seven calendar days after delivery. Show the actual due date on the invoice.
- Problems and resolution
- Report visible discrepancies at receiving and other concerns promptly to the farm contact, with order reference and relevant details. Agree on credit, replacement or another remedy; confirm the outcome in writing.
- Next order
- Availability update Monday; order request due Tuesday at noon for Thursday delivery. Reply through the agreed ordering channel. Farm confirms quantity, price and delivery before the order is considered booked.
This is a commercial handoff sheet, not a substitute for required labeling, traceability records, food-safety procedures or buyer documentation.
The order should make sense without the original conversation
When the driver arrives, the chef is away. The sous-chef has the confirmation, recognizes the order reference and checks two labeled cases against the delivery record.
That is a successful handoff. Nobody has to reconstruct Monday’s enthusiasm to decide whether the kitchen should accept Thursday’s vegetables.
Give the restaurant a copy it can share internally before delivery. Bring the matching delivery record. Use consistent product names and units across the confirmation, case labels and invoice. If the chef ordered pounds and the invoice says only “two boxes,” somebody still has to solve the order.
The receiver should be able to record a shortage or condition concern while the driver is present. The farm should keep the receiving contact and delivery outcome with the order. A signature can document the handoff, but it does not make a later quality concern disappear.
If nobody is available, follow the agreed backup procedure. An unattended box by a kitchen door is not automatically a completed delivery. A late arrival also needs a message early enough for the restaurant to respond, rather than an explanation after its receiving window has closed.
The goal is a routine another member of staff can perform correctly. That helps the restaurant on a busy morning and helps the farm when someone other than the owner drives the route.
The ingredient has to earn its place during service
The first tasting told the chef the carrots were worth trying. Weekend service will answer different questions.
Did the agreed size range make preparation predictable? How much trimming was required? Did the kitchen use the amount it expected? Was the pack convenient to store and handle? Did the ingredient work in the dish the chef intended?
A grower does not need to teach a professional kitchen how to cook. It can provide accurate product information and invite specific feedback about fit. If the harvest differs meaningfully from the sample, say so before the kitchen discovers the difference halfway through prep.
In our example, the carrots perform well. The kitchen uses 12 of the 20 pounds during the planned trial. The remaining eight pounds are a purchasing clue, even if the chef finds another use for them.
Perhaps the next trial should be smaller. Perhaps the side sold more slowly than expected. Perhaps another dish could create regular demand, but only if the chef wants it. None of those possibilities is resolved by asking whether the chef “liked everything.”
I would rather understand why 12 pounds worked than celebrate a 20-pound sale that leaves the buyer hesitant to repeat it.
A follow-up that helps the next order
Agree on a suitable time to follow up after the ingredient has been used and before the next order deadline. A short conversation outside service can uncover more than repeated messages asking whether the restaurant needs anything.
Here is how that conversation might sound. The dialogue is illustrative.
Grower: “Did the carrots work for the side you were testing?”
Chef: “Yes. The size was good, and they roasted well. We used about 12 pounds.”
Grower: “Would ten pounds be a better next order, or do you expect more covers this week?”
Chef: “Ten is better. My sous-chef received them, but the invoice didn’t get to our office.”
Grower: “I’ll send it to the accounts address you give me and copy you. Was anything unclear for your sous-chef?”
Chef: “No. Same delivery window works. Can you send availability to both of us?”
Grower: “Yes. I’ll send Monday’s update to you both. If you request ten pounds by Tuesday noon, I’ll confirm the order and the delivery charge. We’ll keep it as a weekly decision for now.”
There are three useful discoveries here: a better quantity, an invoice-routing problem and a second person who needs the availability message.
Write them into the customer record. Otherwise, the farm has had a good conversation without improving the next delivery.
If the chef reports a problem, settle the remedy before asking for another sale. Identify the affected product and order, understand the impact, and confirm what the farm will do. A credit for an unusable item should not depend on the buyer placing a replacement order.
If the trial was simply a poor fit, accept that answer. Finding out that a restaurant needs a specification or delivery frequency the farm cannot sustain is valuable information for both businesses.
Make the second order easier to place
The restaurant should not have to remember how to buy again.
Send the current availability, prices, pack sizes, ordering deadline and next delivery window through the agreed channel. Make the action plain: reply with the product and quantity, or use the order link. Confirm receipt and then confirm what the farm can supply.
A text message can work for a small operation. So can email or a simple form. The weakness is having different versions scattered across the owner’s phone, a driver’s notes and an inbox nobody else checks.
Keep one current order record and a customer record with contacts, receiving instructions, payment terms and agreed preferences. Give the farm’s backup person access to the information needed to fulfill the order. Ask the restaurant to identify an authorized alternate buyer so an absent chef does not halt purchasing.
Only move to a standing order when the restaurant explicitly agrees to the quantity, cadence, price arrangements, availability limits and change or cancellation deadline. Regular ordering is useful. An unwanted box delivered because last week went well is not.
Repeat business has to work for the farm, too
A smaller order may be the right answer for the kitchen and a difficult answer for the delivery route. Discuss that openly.
Use this deliberately simple example. An order brings in $120 in product revenue. Its assigned growing, harvest and packing costs are $65. Order handling costs $8, and delivery labor and vehicle costs allocated to the stop are $22. That leaves $25 before any costs not included in those categories.
A special return trip costing another $30 would turn that remaining contribution into a $5 shortfall. The sale still appears in the revenue total. The extra trip explains why the account feels less worthwhile than it looks.
These are illustrative figures, not industry benchmarks. Use the farm’s own costs, including the owner’s time, and avoid counting the same expense twice. Distinguish the extra cost of adding a nearby stop to an existing route from the fully allocated cost of running that route over time.
The practical answer might be a minimum order, a transparent delivery fee, a fixed route day or a pickup option. For our carrot buyer, ten pounds may work if the restaurant fits the Thursday route and accepts the agreed charge. A dedicated trip for the same order may not.
Explain the ongoing terms before the trial. If a first-delivery concession is temporary, label it that way. Both businesses should know what the relationship will cost once the introduction is over.
Measure what happens after the first yes
A compact record of new restaurant accounts can show whether the handoff is improving. These are proposed operating measures, not universal performance targets.
| Measure | How to track it | What it helps explain |
|---|---|---|
| Second-order rate | Accounts placing a second paid order ÷ first-order accounts that have completed the chosen observation window. | Whether trials become repeat purchases. Record planned one-time buyers and supply interruptions separately. |
| Time to second order | Days between first and second paid orders, alongside the intended buying cadence. | Whether weekly prospects are returning weekly, or whether the expected rhythm was wrong. |
| Ordering consistency | For ongoing accounts, track orders across expected buying opportunities, quantities and known pauses. | Whether the relationship is becoming dependable without treating seasonal closures as customer loss. |
| Delivery economics | Revenue, product costs, handling time, route time, vehicle costs, credits and extra trips, using a consistent allocation method. | Which accounts and routes support the business after the work of serving them is included. |
| Preventable problems | Record wrong packs, missing information, missed windows, unapproved substitutions and invoice corrections per delivery. | Which repeated problem deserves a change to the process. |
| Payment experience | Compare actual payment dates with agreed due dates and record invoice disputes or routing errors. | Whether the account pays as agreed and whether the farm is creating avoidable collection work. |
Suppose eight of 12 restaurants reorder within a chosen 30-day window, and all 12 have had the full 30 days to do so. The second-order rate is about 67%. That describes this group; it does not establish whether the rate is good.
Investigate the four that did not return. One may have bought for a single event. Another may have missed the next ordering deadline. A third may want the product but need a different pack. Those are different situations with different responses.
Likewise, a higher second-order rate is not an improvement if it depends on repeated discounts and expensive emergency deliveries. Read purchasing behavior, service problems and economics together.
Give good food a relationship it can grow in
Before the next first delivery, make sure somebody who never met the chef can answer five questions: What was ordered? What exactly will arrive? Who will receive it? How will the farm get paid? How does the restaurant order again?
Then follow the ingredient far enough to learn whether it worked in the kitchen.
That is a manageable place to begin. One clear confirmation. One receiving handoff. One useful conversation after service. A record that makes the next order easier for both businesses.
In my agricultural consulting work, this is the kind of commercial process I can help a farm examine: how the wholesale customer experience connects the product, the people doing the work and the economics of serving the account.
The chef’s enthusiasm deserves a good first delivery. The farm’s work deserves a fair chance at the second order.