What drives the price
The price on this page starts at the Ordering and delivery level: guests order through your website or a Telegram Mini App, pay with local providers, follow the courier on the map, collect loyalty points and get notifications. A native app in the App Store and Google Play is not included in this price; it is estimated additionally, at mobile development rates. Chain adds a kitchen display, a courier app with routes and payouts, and analytics by dish, hour and branch. Lock-screen status, aggregator orders, tips and reviews, and AI dish suggestions built on OpenAI models are separate add-ons. A dine-in venue that does not need delivery yet can choose the cheaper QR menu level: a photo menu behind a QR code and ordering from the table. The configurator gives the total, and the contract fixes it.
The order’s path from cart to door
The guest picks dishes, drops a pin for the address and pays. An order becomes paid only once the payment provider’s confirmation reaches our server, and a repeated confirmation never creates a second charge. We attach IKPU product codes to menu items, and the payment provider passes them into the fiscal receipt. The order then appears on the kitchen display, the cook marks it ready, and the courier gets the address and route in their app. The guest follows every step through notifications and sees the courier on the map; with a native app, the status also stays on the iPhone lock screen. Cancellations, out-of-stock swaps and refunds are mapped in advance, so nobody improvises them at peak hour.
Aggregators, your own couriers and loyalty
Orders usually arrive from several places at once: your own app, Telegram and aggregators. The aggregator module gathers them into one window alongside yours, so the kitchen stops juggling tablets. Whether a particular aggregator can be connected depends on whether it offers order access through an API, and we check that before the contract is signed. Your own couriers work in the courier app: order list, route and accrued payouts. Loyalty points are earned on orders in your channel, which gives guests a reason to order directly, with no aggregator commission. Analytics shows which dishes, hours and branches bring in revenue, and which items are worth dropping from the menu.
How the work runs and what the contract says
We start with the flows: checkout, payment, cancellation, a dish running out, a courier declining an order. You get a working version every two weeks: your team places test orders from their phones, while the kitchen and couriers try their screens. Before launch we run a trial shift with live payments. If we build a native app, developer accounts in the App Store and Google Play are registered to your company; Apple requires your company’s D-U-N-S number, so we request it in the first weeks. The deadline is in the contract: every day of delay cuts the invoice by 2%, up to 10% of the contract in total. Bugs are fixed free with no time limit, and your engineer may audit the code: any unfulfilled item means a 10% refund.