The Busy Trap: How to Run a Food Truck Without Bleeding Your Profits

It’s 12:40 on a Saturday, the line is eight deep, and the register hasn’t stopped chiming for twenty minutes. By every visible signal, this is a good day. Then Tuesday comes, the numbers finally get tallied, and the good day turns out to have made twelve dollars.

That gap — between how a day feels and what it actually earned — is the single biggest thing separating food trucks that survive their first two years from the ones that don’t. It’s rarely the food. It’s almost always the numbers underneath it: what each dish actually costs to make, what’s about to run out, whether last weekend’s festival was worth the tank of gas, and whether the crew scheduled for Thursday actually matches what Thursday needs.

None of that requires an accounting degree. It requires five specific habits, done consistently, instead of once a year when the taxes are due.

Price your menu around real food cost, not guesswork

Most new owners price their menu the way they’d price a garage sale: look at what the truck next door charges, land somewhere close, and hope the math works out. It’s an understandable instinct — and it’s also how a truck can do steady business all summer and still come up short at tax time.

The reliable way to price a dish starts with knowing exactly what it costs to make. Take every ingredient — protein, bun, cheese, sauce, the paper wrapper it goes in — and cost each one at what you actually paid per unit. A burger built from four ounces of ground beef, a bun, and two slices of cheese isn’t “about three dollars.” It’s $2.50 for the beef, $0.50 for the bun, $0.50 for the cheese: a batch cost of $3.50. That number is the floor everything else gets built from.

From there, the formula is simple: selling price equals cost per serving divided by your target food cost percentage. Trucks generally aim tighter than a sit-down restaurant does. Most brick-and-mortar kitchens run 28 to 35 percent, but a truck’s fuel, commissary rent, and event fees eat margin a restaurant’s overhead structure doesn’t carry, so the smarter target sits closer to 25 to 32 percent. At a 30 percent target, that $3.50 burger needs to sell for $11.67 — round it to $12, and ingredients are covered with room left for everything else the truck has to pay for.

Here’s the part most pricing guides skip: not every item needs to hit that percentage individually. A menu blends. Drinks, chips, and simple sides can run a much lower food cost and pull the blended average down, while the signature dish sits closer to 30 on its own. Force every item to the same target and the popular dish gets overpriced while the throwaway sides get underpriced — margin lost on both ends.

ItemCostTarget food cost %PriceBurger$3.5030%$12Side of chips$0.4015%$3Burger + chips combo$3.90~20% blended$15

The burger alone never moved. Attaching a low-cost side dragged the blended percentage down and made the whole plate more profitable without touching the recipe that customers actually care about.

Prices aren’t a one-time decision, either. Ingredient costs drift, and a menu priced correctly in spring is often underwater by fall. The fix isn’t a once-a-year panic increase — it’s revisiting the math whenever a key ingredient’s cost moves more than about 10 percent, and making small, regular adjustments instead of one jarring jump a regular customer will actually notice and resent.

This is also where a connected system earns its keep. Some owners track this in a spreadsheet with formulas linking ingredient cost to recipe cost to menu price. Others set it up in something like a Notion-based recipe database, where updating one ingredient’s price automatically recalculates every recipe that uses it and flags which items have drifted out of their target range. The mechanism matters less than doing it. Owners who reprice on a schedule keep their margin. The ones who price once and never look again are the ones surprised by a bad year.

Stop running out of ingredients mid-shift

There’s a specific kind of dread that sets in when the lunch line is ten deep and someone in the back just found the last handful of shredded cheese. Running out mid-shift doesn’t just cost the sale in front of you. It costs the next twenty people who see the sign go up and walk to the truck next door instead.

The fix isn’t stocking more of everything. Over-ordering just trades one problem — running out — for another: spoilage, and perishables don’t forgive a bad guess. The real fix is knowing, for each ingredient, the point at which you need to reorder, and checking against it before the week gets away from you, not during Saturday’s rush when it’s too late to do anything but apologize.

Set that reorder point based on how fast the ingredient actually moves and how long your supplier takes to deliver. If a supplier needs two days’ lead time and the truck goes through eight pounds of ground beef on its busiest day, the minimum stock needs enough cushion to survive a busy weekend without a same-day emergency run to the wholesale club.

Rotation matters as much as the threshold. First in, first out — using the oldest stock before the newest, every time, without exception — is the cheapest thing a truck can do to cut spoilage, and it costs nothing but the discipline to label prep dates and actually check them. Trucks that rotate consistently waste noticeably less than ones that don’t. The ingredients pushed to the back of the cooler are the ones that quietly become next month’s write-off.

Weather is worth building into the plan, too. A rained-out Saturday can cut foot traffic dramatically compared to a clear one, and a truck that preps the same quantity regardless of forecast ends up either scrambling to restock on a surprise busy day or throwing out a full prep list on a slow one. A rough weather-adjusted prep guide — smaller batches on days the forecast looks bad — protects margin on both ends.

None of this needs to live in your head. A simple inventory list with a current-stock number, a minimum-stock number, and a flag that changes when one dips below the other does the job — whether that’s a whiteboard, a spreadsheet, or a Notion inventory database where a formula marks anything below minimum and surfaces it on a dashboard before the truck even opens. The tool is optional. Knowing the number before the rush starts is not.

Choose events and locations worth the drive

A packed festival can still be the worst booking of the month, and the math is almost always the same story: a vendor fee, a full tank of gas, and a slow afternoon that brings in barely enough to cover both. From the truck window, it looked busy. On the ledger, it was a loss.

The fix is running the break-even math before saying yes to a booking, not after. Add up what the spot will actually cost — the vendor or parking fee, fuel there and back, any commissary time lost prepping for it — and compare that total against a realistic sales estimate based on expected attendance and what similar past events actually brought in, not what the organizer promises over the phone.

Event fees also quietly change the food cost math. If a truck’s street-side food cost runs a comfortable 27 percent and an event charges a 20 percent vendor fee on gross sales, the effective food cost at that event climbs toward the low 30s — closer to restaurant territory, but without a restaurant’s fixed seating and steady walk-in traffic to support it. At a premium curated festival charging closer to 30 percent, that effective number can push past 35, the point where the math stops working no matter how good the line looks.

Some trucks handle this with a separate event menu, priced a dollar or two above the street version. Customers at a festival generally expect to pay a bit more than they would at a weekday lunch spot, and they rarely push back on it, especially once they’ve already paid to get in the gate.

The larger discipline is treating every location as a data point instead of a gut feeling. A spot that “always does well” deserves a second look if nobody’s actually tracked whether the sales there cover the parking, the fuel, and the vendor fee it costs to show up. Track it a handful of times — sales, parking, fuel, event fee, and what’s left over — and a pattern emerges fast. Some regular bookings are quietly subsidizing others, and some “reliable” spots aren’t reliable at all once the costs are subtracted.

This is where owners often build a simple locations log. Even four columns — sales, parking, fuel, and what’s left — tracked in a spreadsheet, or in something like a Notion events database that calculates the difference automatically, turns “that market feels good” into “that market nets a few hundred dollars a week after costs, and it’s worth the drive.” The second version is the one that actually helps decide where to park next month.

Build a staffing schedule that doesn’t eat your week

Every Friday afternoon has a version of the same scene: a notebook, a calculator, and an owner trying to remember whether the closer worked the full shift at the farmers market or left early to cover someone else’s shift across town. Staffing a truck is simple in concept — match people to shifts — and surprisingly easy to lose an hour of the week to in practice.

The first fix is building the schedule around bookings, not a fixed template. A Tuesday lunch spot that reliably does forty orders doesn’t need the same crew as a Saturday festival expecting four hundred. Building shifts off the events calendar, rather than repeating the same weekly pattern regardless of what’s actually booked, keeps labor cost roughly proportional to expected volume instead of overstaffing the slow days and scrambling on the big ones.

The second is tracking hours against results, not just against a time clock. Noticing that one cashier’s shifts consistently bring in more per hour than another’s isn’t about ranking people unfairly — locations and days differ, and one person’s Tuesday isn’t another’s Saturday. But over a few weeks, real patterns show up: who to schedule for the high-volume festival shifts, and who’s a better fit for a steady, lower-pressure weekday lunch spot.

The third, and the one that quietly causes the most Friday-afternoon headaches, is making sure payroll only counts hours actually worked, not hours scheduled. It’s an easy mistake to build into a spreadsheet or template without noticing: a formula that sums every shift tied to an employee — including next weekend’s shift, which hasn’t happened yet — will show payroll owed that’s larger than what’s actually due. Building this yourself means filtering for completed shifts only. Using a template that does it automatically means checking the total against one real pay period before trusting it.

None of this requires new software. A shared calendar and a notebook tracking hours will get a two-person truck through its first year. But as the crew grows past two or three people, the spreadsheet-and-notebook version starts costing real time every week — which is exactly the gap a connected system is built to close: one place where the schedule, the hours, and the payroll are the same data, instead of three versions that all have to agree with each other by Friday.

Close out every day so you know if you made money

There’s a specific kind of exhaustion at the end of a good shift — feet sore, the fryer still cooling, the truck smelling like a win. It’s also the moment most owners are least equipped to answer the only question that actually matters: did today make money?

“Felt busy” and “was profitable” are not the same measurement, and the gap between them is exactly why a five-minute closing routine matters more than almost anything else on this list. Done at the end of every operating day, it turns twelve hours of transactions into one honest number instead of a guess reconstructed from receipts three weeks later.

The routine itself is short. Count the drawer and reconcile it against what the card terminal and any mobile payment app say came in — a mismatch here, even a small one, is worth noticing the same day, while anyone involved still remembers what happened. Tally the food cost of what actually sold against the revenue it brought in, and there’s a real food cost percentage for the day, not the theoretical one from the menu-pricing spreadsheet. Log any waste and any refunds. What’s left, after subtracting the day’s other expenses — fuel, a supply run, anything paid out of the till — is net profit. Not revenue. Profit.

Do this daily, and two things happen. First, a bad day gets caught immediately. A spike in food cost percentage on a Tuesday is worth investigating while it’s still fresh — was the walk-in running warm, did someone over-portion all afternoon — rather than at month’s end, when that Tuesday is indistinguishable from thirty other days. Second, a real pattern builds: which days of the week are actually worth opening for, which menu items need a second look, whether last month’s price increase protected margin or just annoyed regulars without moving the number that matters.

The honest version of this habit doesn’t need to be complicated. A notebook with five columns — revenue, food cost, expenses, waste, net profit — filled in at every close will tell you more about the business than a fancier system nobody actually updates. Whether that’s a paper ledger, a spreadsheet, or a Notion daily report that pulls the day’s sales and expenses together automatically so the number appears without a calculator, the tool matters less than the habit.

The five numbers in this piece aren’t complicated math. They’re the difference between running a truck and actually knowing how it’s doing. Most owners who fail at this business didn’t lose to bad tacos. They lost to not knowing, until it was too late, that the tacos were the only thing going right.

None of this requires a subscription to anything. A notebook and the discipline to use it every day will get most trucks further than expensive software nobody opens. But if piecing together five separate spreadsheets sounds like its own part-time job, that’s the specific gap Food Truck Business OS was built to close — the same recipe costing, inventory alerts, location profit, staffing hours, and daily closing routine described above, already connected to each other in one Notion workspace, so the numbers update themselves instead of waiting for you to remember to check them.