Your menu, without retyping it
Photograph your menu, drop in the file or give your website address: FestFlow pulls out the dishes, the prices and the categories, and you check them over before publishing. Nothing goes live without your approval — products arrive as “unavailable” and allergens always as “not declared”, because that declaration is yours to make, not a machine’s.
Say what you feel like, in plain words
Your customer types “a really cold beer” or “gluten-free within a kilometre”, and the app turns it into real filters: food or drink, the 14 allergens, diet, terrace, distance, waiting time. Every result shows its own wait — the counter and the kitchen do not move at the same speed. What they type is read on the phone itself first: an allergy never leaves the device. The rest goes to a model hosted in Geneva, which does not train on your data.
Thumbs up or down, dish by dish
Once they have picked up their order, your customer gives each dish a thumbs up or down. Only someone who has eaten the dish can vote — order paid for and picked up — so the numbers cannot be inflated. The votes sit next to the dish name and feed “what people like most”. The ranking therefore says exactly what it is: what people like, not what sells.
The 14 allergens, in the customer’s language
The mandatory declaration (OIDAl art. 5) is made once, on the dish’s own record, and appears translated in all five languages. Until something is declared, the customer reads “ask the staff” — never an empty list that would suggest there are no allergens at all. And the allergy warning stands out in red in the kitchen and on the printed ticket.
One account, every stop
Your business exists once; each festival gets its own version of it. You apply to open festivals and the organiser approves — your whole season from a single dashboard. On site, your stall appears on the map with its wait time: visitors find you without looking for you.
Menu and prices per festival
Adapt your menu and your prices to each event without touching your base account. A sold-out product is removed in one tap.
Solo between festivals
At your regular spot, your customers see your food truck — not festival wording. Same POS, same mobile orders, same payment account.
The POS holds when the network gives out
Selling carries on offline and syncs when the network comes back. The sale in progress survives a tablet reload.
Every way of paying
In the app: card or TWINT.
At your place: cash, card or TWINT — the customer pays by QR from their phone, or on your own terminal, contactless if they like.
Whichever way they pay, it all lands in the same till and the same daily journal. No double charge is possible on QR payments.
Your customers order without queueing
Menu with photos and extras, a pickup time announced from your real workload, a notification when it is ready and handover verified by QR.
Screen, ticket, or both
The kitchen board on screen, automatic printing on a USB thermal printer, or both — kitchen and counter each with their own. Printing works even offline.
The money, straight to you
Every online payment lands in your payment account, opened in your name, and is then paid out to your bank account: card and TWINT. At a festival, the organiser’s share is calculated and traceable order by order: it can be deducted at the moment of each payment, or invoiced periodically against the statement — that is agreed up front.
You know what sells, and when
Your sales and your activity, by day and by location. Enough to decide your menu and your next stops on figures, not on guesswork.