How to Cater With a Food Truck (And Get Paid Before You Show Up)
Catering is the best off-season revenue a truck has, but the money is decided by your deposit terms and minimums — not your menu.
Food Truck or Restaurant Owner? Sign up for the Culinary Entrepreneur Newsletter!
If you want to cater with a food truck, the thing that decides whether it's profitable isn't your menu or your pricing — it's whether money changes hands before you drive there. Catering gigs pay a guaranteed number for a known headcount at a known time. Service days pay whatever walks up. That's why catering is the best off-season revenue a truck has, and why the operators who do it badly are the ones who treat a catering booking like a really good service day.
Here's the part nobody writes down: the contract terms, not the cooking.
Why catering pays better than a service day
A service day is a bet. You buy product, you drive somewhere, and you find out what you made when you close. A catering gig removes almost every variable that makes that bet bad:
Known headcount. You prep for 80, you sell 80. Waste goes close to zero, and waste is where truck margin quietly dies.
Known time window. Two hours of service instead of eight hours of hoping.
No weather risk. A corporate lunch happens in the rain. Your Saturday spot does not.
No line-speed ceiling. On a service day your revenue is capped by how fast the window moves. A catering invoice is agreed in advance.
One decision-maker. You sell once, to an office manager, instead of 200 times to strangers.
That last one is the real unlock. Catering is a sales job, not a marketing job. You aren't trying to be discovered — you're trying to be remembered by about forty people in your city who book food for other people.
How do you get paid before you show up?
This is the whole post. A catering booking that isn't paid for in advance is a reservation, and reservations get cancelled the morning of, after you've already bought the product.
The structure that works:
Set a minimum, in dollars, not headcount. "My catering minimum is X" is a sentence you say out loud early in the conversation. Headcount minimums get negotiated down. Dollar minimums don't, because the number is the number whether twelve people show up or ninety.
Take a non-refundable deposit to hold the date. Half is standard. The deposit is not a payment toward the food — it's what you charge for turning down other work on that date. Say it that way, because that's what it actually is.
Collect the balance before service, not after. Before you leave the commissary is better than on arrival. On arrival is much better than invoicing afterward.
Lock the final headcount 72 hours out, in writing. After that number is confirmed, it can go up but not down. You're buying product against it.
Put the overtime rate in the agreement. Events run long. If you don't have a per-half-hour number written down, you'll eat an extra ninety minutes for free and call it customer service.
If a client won't put a deposit down, you've learned something useful for free. Serious bookers expect to pay a deposit — they do it for the venue, the photographer, and the rental chairs. An event planner who balks at a deposit is telling you they're still shopping.
What should you actually charge?
I'm not going to hand you a per-head number, because anyone who does is guessing about your food cost, your market, and your drive time. Build it instead. Price a catering gig from the bottom up, every time:
Line | What goes in it | What people get wrong |
|---|---|---|
Food cost | Your real cost for the confirmed headcount, plus a small buffer | Pricing off menu prices instead of actual plate cost |
Labor | Every paid hour: prep, drive, setup, service, breakdown, cleaning | Counting only the service hours |
Travel | Fuel both directions, mileage, generator fuel, tolls, parking | Forgetting the trip home |
Commissary time | Extra prep hours this gig forced you to buy | Treating it as free because it's prepaid monthly |
Compliance | Event permits, insurance riders, certificates the venue demands | Discovering the rider requirement a week out |
Opportunity cost | What you'd have made at your normal spot that day | Leaving it out entirely — this is the big one |
Margin | Your actual profit, added on top of all of the above | Hoping it shows up after the fact |
Add the first six, then add your margin. That's your price. If the number is higher than what the client wants to pay, the answer is a smaller menu, not a smaller margin.
Opportunity cost is the row that flips decisions. A weekday corporate lunch costs you nothing in lost service revenue. A Saturday wedding costs you your best day of the week, and it has to clear that bar before it's worth saying yes to. I wrote out the full break-even math for events separately — the same arithmetic applies here.
Where do catering clients actually come from?
Not from a catering page nobody visits. Search demand for "food truck catering" is dominated by booking marketplaces and local results — you're not going to out-rank those, and the leads they sell you come with a cut attached.
The bookings that repeat come from a shorter list:
Offices within 15 minutes of where you already park. They've eaten your food. Someone in that building books lunch for 40 people once a month and is tired of sandwich trays.
Property managers of office parks. One relationship, many tenants, recurring slots.
Breweries and taprooms without kitchens. They need food to keep people drinking. This is the single most underworked channel for a truck.
Event planners and venue coordinators. Forty people in your city book most of the private events. Get on their list once and you're on it for years.
Your own line. The person ordering tacos on Tuesday is also the person planning their company's summer party.
The last one is the cheapest and the most ignored. A small card at the window that says "we cater — text this number" converts better than any ad I've ever run, because it reaches people who already know the food is good. I learned the expensive version of this lesson wasting money on Facebook ads trying to reach strangers instead.
The honest caveat
Catering is not free money and it is not for every truck.
It's a different business with a different failure mode. Service days fail slowly — a bad Saturday costs you a bad Saturday. Catering fails loudly. If you're late, or you run out of food at minute forty of a two-hour window, you didn't have a slow day; you ruined someone's wedding, and they will tell everyone who asks.
Specifically, don't take catering work if:
You can't produce the confirmed headcount at your line speed inside the service window. Do that math before you quote.
Your menu doesn't hold. Some items are great to order and terrible to serve 120 of in ninety minutes.
You're the only person who can run the truck and the gig conflicts with your best service day.
You haven't checked whether the venue requires an insurance rider or a specific permit. That's a week of lead time you may not have.
Also: catering revenue is lumpy and it's seasonal in the opposite direction from your service days, which is exactly why it works as an off-season engine — and exactly why it won't smooth out your cash flow month to month the way people expect.
Where doing this by hand breaks down
One or two gigs a month, a notes app is fine.
The wall shows up around the fifth or sixth simultaneous booking. Deposits collected in four different ways. A headcount confirmed in a text thread you can't find. An invoice you're pretty sure got paid. Catering revenue sitting outside your sales reporting entirely, so when you try to work out whether catering is actually beating your service days, you can't — the numbers live in two different places.
That's the point where it needs to be one system: the deposit, the balance, the order, and the sales data in the same place your service-day revenue already is. Otherwise you're running two businesses and only measuring one of them.
Avocado handles catering orders and deposits through the same system that runs your window, so a catering gig shows up in your sales reporting next to everything else instead of in a separate spreadsheet.
Avocado is a POS built for independent restaurants and food trucks. We're operators first, and we'd rather tell you the honest version than the version that closes faster.
This is operator experience, not legal advice. Deposit terms, cancellation policies, and contract language vary by state — have a local attorney look at your catering agreement before you rely on it.