A Telegram Mini App with pre-ordering and payment
The morning peak queue was running to 12 minutes. We moved ordering and payment into Telegram so the guest collects a cup that is already made.
- Client
- Coffee shop chain, 6 locations
- Industry
- HoReCa
- Year
- 2026
- Duration
- 6 working days
A queue built up at the counter every morning: one barista was taking the order, ringing up the receipt and making the drink at the same time. Guests walked out rather than wait. What was needed was an ordering channel that does not ask anyone to install yet another app.
What we did
and why we did it that way.
A storefront inside the messenger
A Mini App with the menu, modifiers and a choice of location. The guest sees the pick-up time before paying.
Payment and fiscal receipts
YooKassa and SBP, with the receipt issued automatically. The money goes straight to the chain’s account and never passes through us.
The barista screen
A separate page on a tablet: the order queue, timers, and a “done” button that pushes a notification to the guest.
Reporting and export
A nightly export of sales by location into the manager’s spreadsheet. This used to be a manual reconciliation every morning.
What changed
and what we measured it with.
How it went
day by day and week by week.
- Day 1
Brief and flow map
We walked through the guest journey and the bottleneck at the counter.
- Days 2–3
Mini App and menu
Storefront, basket, choice of location and time.
- Day 4
Payments and receipts
Acquiring connected, refunds tested.
- Day 5
Barista screen
Order queue and notifications to the guest.
- Day 6
Pilot at one location
We launched, listened to the baristas and reworded what confused them.
How it looks
in schematics.
These are screen schematics. We do not publish client interfaces without permission
A similar problem
on your side?
Describe it in the brief. In working hours we come back with an estimate of time and cost within two hours.