Work / MenuBot
One order, four screens, one system.
MenuBot is the product we run every day. Here is what happens when a single order goes through it, from the customer's phone to the door.
The journey
Scroll down the ticket: each stamp is one screen.
-
1The order lands on the restaurant panel.
-
2The restaurant follows its courier on the map.
-
3The courier has the address and the order.
-
4The customer watches it arrive.
Demo restaurant, staged demo order.
What this shows
- One order record flows from the customer app to the restaurant panel and on to the courier app.
- The customer, restaurant and courier apps are written as web apps and shipped as native iOS apps.
- Each restaurant's data is kept separate from every other restaurant's, table by table.
- The same flow runs in Turkish, English, Russian and Ukrainian.
What is not in this story
- Ordering by WhatsApp: the channel exists, but its end-to-end run is not verified yet, so it is not shown.
- Real customers: the restaurant is our demo restaurant and every screen shows demo data.
- Real timings: the clock on the ticket is a simulation, not a measurement.
The three apps in this story
- MenuBot Orderfor customers · iOS 1.19 App Store ↗ — MenuBot Order (opens in a new tab)
- MenuBot Partnerfor the restaurant · iOS 1.3.0 App Store ↗ — MenuBot Partner (opens in a new tab)
- MenuBot Courierfor couriers · iOS 1.2.6 · unlisted App Store ↗ — MenuBot Courier (opens in a new tab)
Want the same kind of system for your business?
Tell us about it