Step one
The guest scans the code
One printed code per table, each tied to its own table number. The menu opens in the browser. Nothing to download, no account to make.
QR menu and AI ordering — pilot opening in Doha
FlitInfo puts a QR code on every table. Guests open a live menu in their browser, ask an assistant whatever they need to know, and send the order straight to your kitchen. Nothing to download.
From the seat to the pass
Step one
One printed code per table, each tied to its own table number. The menu opens in the browser. Nothing to download, no account to make.
Step two
Change a price, mark the hammour sold out, push a Friday special. It reaches every table at once, with allergens listed on each item.
Step three
It knows your ingredients, your spice levels, what is vegetarian and what is halal. It replies in the guest's own language and never gets too busy.
Step four
Orders arrive itemised, with the table number and any allergy note attached, on your kitchen screen or your printer. No re-typing, no misheard modifiers.
The product
01
Edit an item, change a price, or flip something to sold out from your phone. Every table sees it on the next tap.
02
A guest asks in Malayalam and gets an answer in Malayalam. The ticket still reaches the kitchen in English.
العربية · English · हिन्दी · اردو · മലയാളം · Filipino
03
Tag ingredients once. The assistant screens every dish against them and flags the ticket so the kitchen sees it too.
04
Run it on a tablet by the pass, or send it to the thermal printer you already own. Both, if you want.
05
See which dishes draw questions, which get left in the cart, and what the assistant could not answer.
06
A second round of drinks is two taps. A request for the bill pings staff instead of a raised hand.
For the people running the floor
The point is not to replace your staff. It is to stop them spending the shift walking back and forth for things a screen can handle.
The rest of what we do
Mobile
Native and cross-platform apps for iOS and Android, from a first release to a product already in people's hands. We handle the build, the store submission, and what comes after it.
iOS · Android · React Native · Flutter · APIs
Web
Marketing sites, dashboards, booking systems and online stores. Fast, searchable, and easy for your own team to update once we hand it over.
Next.js · WordPress · E-commerce · SEO · Hosting
Before you ask
No. The QR code opens the menu in whichever browser is already on the phone. There is no app to install and no account to create.
For pilot restaurants we do the setup ourselves. You send us your menu in whatever form you have it — a PDF, a spreadsheet, photographs — and we load the items, allergens and prices, then print the table codes. Most kitchens are live within a week.
At launch: Arabic, English, Hindi, Urdu, Malayalam and Filipino. The guest is answered in their own language, while the kitchen ticket always arrives in English so nothing has to be translated at the pass.
No. It removes the trips that exist only to fetch information or repeat an order back to the kitchen. Your team keeps doing the parts of service that actually need a person.
Usually not. Tickets run on any tablet or screen with a browser, or print to a thermal printer you already own. The only thing you physically add are the printed table codes.
You are, exactly as you are today. You tag the ingredients once; the assistant screens dishes against those tags and flags the ticket for the kitchen. It surfaces what you told it — it does not guess, and it does not replace your own allergen checks.
Pilot programme
We are onboarding a small group of restaurants in Doha before the wider launch. Setup is done for you, your menu is loaded, and you get a direct line to the team while we tune the assistant to your kitchen.