From one truck to a fleet

The second truck is a management problem, not a cooking one. What changes when you can no longer be at the window, and how to compare trucks fairly.

The first truck works because you are in it. You know what sold, what ran out, what the queue looked like at one o'clock and whether the pitch was worth the fee, because you were standing there. The second truck removes all of that at once.

What actually changes

  • You stop seeing the service. Everything you knew by being present now has to arrive as information.
  • Cash becomes a control problem. One person handling cash they also counted is a different situation from someone doing it unobserved at a field forty miles away.
  • Prep splits. Shared prep across trucks needs a plan; separate prep in each truck duplicates cost and drifts in quality.
  • Pitch selection becomes a decision with evidence rather than a memory, because you were not at either one.

Compare trucks, not just totals

Ranking two trucks by takings mostly ranks the pitches they were given. A truck at a festival will out-take a truck at a business park regardless of who is running it, and concluding anything about the operators from that is a mistake.

  • Takings per trading hour, which removes the length of the day.
  • Average ticket, which reflects selling and menu rather than footfall.
  • Cash variance per service — the number most worth watching once you are not present.
  • Return on the pitch fee, which is the decision you actually control for next season.
The comparison that matters most

Same truck, same pitch, different day or different operator. It is the only comparison where the location is held constant, and it is the one that tells you something about how the truck is being run.

The people problem

A second truck needs someone who can run a service alone: cook, take money, handle a queue, decide when to 86 something, and cope when the signal drops. That is a rarer person than a second vehicle is a purchase, and most fleets are constrained by them rather than by capital.

Which means the honest sequence is usually: find and train the person, then buy the truck. The reverse produces a truck you have to staff yourself, which is the situation you were trying to leave.

How this works in Opero

Each truck is its own location in Opero, so it carries its own menu, prices and availability, and reporting breaks down per location — which is what lets you compare trucks and pitches on the numbers rather than on impressions. Pricing is per location, so a second truck is one more line rather than a renegotiation.

Cash and card sit on the same records at each truck, so a variance is traceable to a service rather than assembled from a pouch of receipts at the end of a week.

One limit worth knowing as you grow: access in Opero is account-wide, so anyone you give a login sees every truck's numbers. There is no way to restrict an operator to their own truck today.

See per-location reporting across trucks.

Explore multi-location

Frequently asked questions

Can I give a truck operator access to only their truck?
Not today. Access in Opero is account-wide, so any login sees every location's figures. If restricting an operator to their own truck matters to you, that is a genuine gap to weigh.
How should I compare two trucks?
Not by takings, which mostly reflects the pitch. Use takings per trading hour, average ticket and cash variance — and where possible compare the same truck at the same pitch across days or operators, which is the only clean comparison available.
What limits growing a food truck fleet?
People, almost always. A second truck needs someone who can run a whole service alone, and that person is harder to find than the vehicle. Train them before you buy, not after.

Run your whole restaurant on one platform

POS, kiosk, QR ordering, kitchen display, and payments on one spine — you bring the tablets, and the card reader is the one piece you buy from us. Unlimited devices, no per-device fees.

Explore the platform

Keep reading

Opero™ is a product of TackOn LLC. · The Restaurant Operating System