Building a truck menu

A truck menu is written against constraints a restaurant does not have: the prep you can do before service, the holding you can manage in a small space, and how fast a queue moves when everyone is standing outside in the weather. Cooking ability is rarely the binding one.

Length costs more in a truck

Every additional item consumes prep time, storage, holding capacity and mental load in a space where all four are scarce. It also slows the queue, because a longer menu takes longer to read and produces more questions at the window.

• ✓Build around a small core that shares ingredients, so prep and waste both stay controlled.
• ✓Use modifiers rather than separate items where you can. One item with three variations is easier to prep and hold than three items.
• ✓Watch holding, not just cooking. An item that must be cooked to order sets the pace of the entire queue behind it.
• ✓Have one thing you are known for. A truck with an identity outsells a truck with options.

Price for the setting

Truck pricing has to absorb costs a restaurant spreads differently — pitch fees, generator fuel, travel, and a trading calendar interrupted by weather. It also faces a customer who is comparing you to the truck twenty feet away rather than to a restaurant.

Contribution margin per item matters more than percentage here, because your number of transactions per day is capped by queue speed rather than by demand. Selling a thin-margin item faster does not help if the line was the constraint.

Events change the answer

A festival with a captive crowd and a two-hour peak wants a shorter menu than a lunchtime pitch with steady flow. Many trucks run a reduced event menu for exactly this reason, and decide it in advance rather than discovering mid-service that the full menu cannot keep up.

Worth knowing how that works in your system: Opero does not switch menus automatically by time or by day, so a reduced event menu is a deliberate change to what is available rather than something that flips on a schedule.

How this works in Opero

Modifier groups with per-option pricing let one item carry its variations rather than becoming three items, which keeps both the menu and the prep list short. Availability is per location, so a truck can 86 an item at the window the moment it runs out and it disappears from the ordering screen immediately.

If you run more than one truck, each is its own location with its own menu and prices, so an event truck and a lunchtime truck do not have to carry the same list.