Solutions · Food Trucks

Food truck ordering software for a kitchen with no fixed address

No floor plan, no dining room — just a window, a line, and inventory that has to last the day without a walk-in to restock from.

Built for how a food truck runs

A truck has none of the things hospitality software assumes. There is no floor plan, no dining room, no back office and frequently no reliable power for anything you would call a terminal. There is a window, a line in front of it, and a fixed amount of food that has to last until it doesn't.

What it does have is the tightest feedback loop in the business. You know within an hour whether a pitch was worth turning up to, and you find out you are out of the thing everybody wants while forty people are still queueing. Running out is not a failure — it is the model. Not knowing you are about to is the problem.

So everything here is a web address rather than a machine. The menu, the kiosk and the screen on the hatch all open in a browser on hardware you already own, which means the whole setup fits in a tablet and a phone and survives being packed away every night.

What changes when the kitchen moves

01

Sold out, everywhere, immediately

Recipes are built from ingredients, so what you have left is arithmetic rather than a guess. When something goes, it goes from the QR menu, the screen on the hatch and any kiosk at the same moment — not when somebody remembers to cross it off.

02

A menu that changes by pitch

A festival menu and a Tuesday lunch menu are two menus, and switching which one a code opens takes a moment. The sticker carries the location, not the list, so nothing gets reprinted.

03

The queue in the street

A code on the truck opens the menu on the guest's phone while they are still in the line. They arrive at the window having already decided, or having already ordered.

04

A screen on the hatch

Any tablet or monitor with a browser becomes the board — the menu, today's specials, the thing you want to shift before it goes. Outside service hours it flips to a closed screen with your hours on it.

05

No terminal to buy or carry

There is nothing to install and nothing licensed per device. Everything opens on the hardware you already have, and a second screen is the same address opened again.

06

Which pitch was worth it

Revenue by day and by hour, and what actually sold. The difference between a good site and a bad one is usually two hundred euro and nobody writes it down.

A wall screen showing featured dishes with their photographs and prices, rotating through the menu
A tablet on the hatch is the board. No signage box, no player, no fee per screen.

Relevant modules

Digital Menu

A code on the truck, a menu on the phone, in the languages your queue reads.

Learn more →

TV Display Board

Any screen with a browser becomes the board on the hatch.

Learn more →

Mobile Ordering

Ordering from the line rather than at the window.

Learn more →

Self-Order Kiosk

A tablet on a stand takes the deciding off the window.

Learn more →

Inventory

What is left, in ingredients, before it runs out mid-service.

Learn more →

Reporting

Which pitch, which hour, which dish.

Learn more →

Common questions

Does any of this need a fixed internet connection?

It runs in a browser, so a phone hotspot is enough. Guests are opening a web page, not installing anything.

Can we run different menus at different events?

Yes. Each code opens the menu you have pointed it at, and changing that takes effect against the sticker already on the truck.

What happens when we sell out of something?

It stops being orderable on every surface at once, because they all read the same menu.

Do we need a floor plan if we have no tables?

No. A truck can run on the menu, the board and orders alone — the floor plan is there for venues with a room to draw.

Is there anything to install?

No. Every surface is a web address opened on hardware you already own.

See it in action

See Gueridon running from a window.

Book a demo