A guest opens the menu from your bot menu button — nothing to install, nothing to register. They add dishes to the cart, give an address and pay; the order arrives in your Telegram as it is sent.
The screens are already wired together: buttons lead where they should, forms send, lists are drawn from a table.
A layout of the screens rather than a screenshot of a finished app: how it looks depends on your colours, type and content.
🍕
Menu
Search, section chips and dish cards with an Add to cart button. Dishes live in a table: removing one or changing a price is a row edit, and a chip narrows the menu by the Section column.
Search
Sections
Dishes
Add to cart
🛒
Cart
What was chosen, the delivery address, name and phone, and a Pay button for the cart sum. The total is counted from the cart; the promo code field is a sample with no calculation and is not sent with the order. Payment goes to your own till; without one, the payment action is removed from the button and the order goes out as a request.
Dishes
Address
Total
Pay
🛵
Order status
Order stages from “Accepted” to “Delivered”, a delivery time, the courier, the kitchen address with directions and a Write button. Stages, time and courier are sample text, not a live status.
Stages
Courier
Directions
Write
👤
Profile
The name from Telegram, bonuses, order history and links to My order and Support — the latter opens the kitchen’s bot. The history is a private table: a paid order appears in it at once, and only the guest sees it. The bonuses are a sample.
Bonuses
History
My order
Support
What gets changed first
Menu sections and dishes are set for your kitchen; photographs go into the app’s storage.
Delivery fields are yours to shape: zone, entrance, time.
Table booking — the Booking screen from the screen library; the template has none.
How to start from this template
1Open the builder and pick the template — it opens assembled and working.
2Replace the content with your own: table rows, text, photographs and prices.
3Connect your bot and press Publish — the app becomes a button in its menu.
Questions about this template
How does an order reach the kitchen?
As a Telegram message to the app owner at the moment it is placed — with the dishes and the total. No separate software; every order also collects in the submissions archive in the editor.
Can payment be taken up front?
Yes, by card through your own till — YooKassa or T-Bank. The money reaches you directly and the till issues the receipt. For payment on delivery, payment is removed from the cart button and only the form submission is kept.
What if a dish runs out?
The dish row is removed or edited. Inside the published app from a phone the change shows at once; in the editor, after publishing. The template has no separate sold-out switch.
How it looks in the trade
The industry page shows what the app is made of in this trade, what it costs to run and where to start.