Guides
Food truck price changes: a test-and-review protocol
How to price food truck services as a protocol: write the reason, expectation and failure line before changing a number, test one change, then review it.
What to take away
- This is how to price food truck services as a protocol, not a formula or a price list. The point is to make each price a decision with a stated reason, a stated expectation and a review date.
- Write down what you expect a price change to do before you make it. Without that sentence, any outcome gets explained as a success.
- Change one variable at a time. A price move and a menu move made together tell you nothing about either.
- Fair means the price covers the whole block, including the unpaid hours, and is defensible to the customer paying it. Those are two separate tests.
- Keep every price decision in one running log. That log is the only thing that makes the next decision better than the last.
What the protocol is for
Most price changes on a truck happen as a reaction: a supplier invoice rises, a slow month lands, or somebody notices the truck opposite charges more. The change gets made, sales move for a dozen reasons at once, and nothing is learned.
A protocol fixes that by forcing three things: a written reason, a written expectation, and a date to check. It costs about ten minutes per decision and it is the difference between a pricing history and a pricing habit.
Step one: define the block you are recovering
Before any price is set, establish what a service actually costs you end to end. That means the whole block, from leaving the support kitchen to returning to it, including the drive, setup, breakdown and waste disposal.
What each order must carry
- Labor for the full block
- Fuel, pitch fee, packaging, disposal
- Share of monthly commitments
- Divide by orders actually completed
Total the block cost: labor for the full block, fuel, the pitch fee, packaging, disposal and a share of your monthly commitments. Then divide by the orders you actually complete. That figure is what each order has to carry before a single ingredient is counted.
The full construction of this, and why the service minute rather than the plate is the right unit, is in pricing built from the block rather than the plate.
Step two: write the decision down
For each price you are about to set or change, record five fields.
Five fields to record
- Item and price before and after
- Reason in one sentence
- Expectation for volume, contribution, queue
- Failure line that triggers reversal
- Review date
- Item and changethe item, its current price and the new price.
- Reasonwhy you are changing it, in one sentence, such as a supplier increase or a block cost that the current price does not clear.
- Expectationwhat you expect to happen to orders and contribution per service.
- Failure linethe result that would make you reverse the change.
- Review datethe service on which you will compare the result with fields three and four.
Field four is the one people omit and the one that does the work. A price change with no stated failure condition never gets reversed, because there is always a reason the disappointing result was somebody else's fault.
Step three: change one thing
Run the change with everything else held still. Same pitch, same hours, same board, same crew if you can manage it.
This is harder than it sounds on a truck, where weather and pitch conditions move constantly. The practical compromise is to run the change for long enough that ordinary variation averages out, and to log the weather alongside the sales so an obvious confound is visible later.
Step four: review against what you wrote
At the review date, compare the result to field three, not to your memory of what you hoped. Three outcomes, three responses.
Review outcomes and responses
Volume held, contribution up?
Keep it, check neighboring items
Volume fell more than expected?
| Outcome | What it usually means | What to do |
|---|---|---|
| Volume held, contribution up | Price was below what the pitch bears | Keep it, and look at neighboring items |
| Volume fell more than expected | Price crossed a threshold for this crowd | Reverse it or restructure the offer |
| Volume held, contribution flat | Something else absorbed the change | Check waste, portion drift and comps before concluding |
The third row catches a common failure. A price rise that produces no contribution gain is usually being eaten by portion creep or unrecorded waste, and neither is fixed by another price rise.
The two tests for fair
The word is doing real work here, so separate it into two questions.
The first is whether the price covers the block, including the hours nobody pays for. A price that only covers the trading window borrows from the owner's unpaid time, and it fails the moment that time has to be bought.
The Bureau of Labor Statistics gives a usable yardstick for that time. Its Occupational Outlook Handbook entry for food service managers puts the 2025 median pay at $69,390 per year, or $33.36 per hour, and notes that these managers often work evenings, weekends and holidays.
On a truck, one or two people carry that management work on top of cooking. Put the owner's unpaid block hours into the block cost at a rate you could defend, and the median hourly figure for the job you are doing is a fair floor. Pricing that treats that time as free is a subsidy, not a margin.
The second is whether the price is defensible at the window. The board price must be what the customer pays. Any unavoidable charge must be shown upfront, not added later. The description must match the food.
The Federal Trade Commission's Advertising FAQ's: A Guide for Small Business states that under the Federal Trade Commission Act, advertising must be truthful and non-deceptive, and advertisers must have evidence to back up their claims. A board price that is not the price paid is the same kind of problem as an inaccurate description.
Pricing a booking rather than a service
Bookings need the protocol run differently, because the demand risk moves. You are selling a block of your calendar to someone who knows their headcount, so the terms matter more than the rate.
Booking terms to agree
- When the headcount locks
- What is payable if it drops
- Who decides weather cancellation
- Compare fee to best pitch block
Three of them decide most outcomes: when the count locks, what is payable if it drops afterward, and who decides that weather has canceled the day. Agree all three in writing before quoting, and treat a booking with none of them as an unpriced risk rather than a cheap job.
Bookings also compete with retail services for the same block, so the comparison is not the fee against the food cost. It is the fee against what that block would have earned at your best pitch, the same comparison that later decides whether a second pitch or a second unit makes sense.
The log, and where it lives
Keep every decision in one place, in date order. Item, before, after, reason, expectation, failure line, review date, outcome. After a season it is the most valuable document the business has, because it turns pricing from instinct into evidence.
What the pricing log holds
- Item, before, after
- Reason and expectation
- Failure line and review date
- Outcome after review
- Kept in date order
It sits next to the sales and cost records, which you are keeping anyway. IRS Publication 583, Starting a Business and Keeping Records, says you can choose any recordkeeping system suited to your business that clearly shows your income and expenses, and purchases, sales, payroll and other transactions generate the supporting documents behind those records. A pricing log alongside that data is what lets you answer why a price is what it is.
What has to be true before a price can hold
Two things outside pricing will defeat it if they are wrong. The line must be fast enough to spread the block cost over a reasonable number of orders. That is a staffing and menu question: who owns which station at the peak, and how many steps each item takes.
And your permitted hours at the pitch have to match the block you priced, which is recorded in the compliance register and its conditions.
The third is demand, and the honest way to influence it is not discounting. It is being findable and predictable: posting where the truck will be, and then being there.
Common questions
How long should a price trial run?
Long enough that weather and day of week average out, and short enough that you act on it. Decide the length before you start, in services rather than in weeks, so you are not tempted to stop on a result you liked.
Should I discount to fill a quiet service?
Rarely, and never as a habit. A discount trains the crowd to wait for it and rarely brings people who become regulars at full price. If a service is consistently quiet, the question is whether the pitch or the hours are wrong, which is a survey question rather than a pricing one.
What if my costs rise mid-season?
Run the protocol rather than absorbing it silently. Record the cost change as the reason, decide whether to move price, portion or the item itself, and set a review date. Absorbing a rise quietly is a decision too; it is just one nobody wrote down and nobody reviews.
Can I price differently at different pitches?
Yes, and often you should. Block cost truly differs: a longer round trip, a higher pitch fee, or a shorter sellable window all change what an order must carry.
Trouble comes when customers see a difference with no explanation. Make the reason visible, or limit the difference to service types, not adjacent corners.
