An order bot in Telegram is a catalogue, a cart and a payment step inside the messenger: the customer builds an order, pays by card through Click or Payme and sees the status in the same chat. For a narrow range such a bot replaces an online store; for a large catalogue with a warehouse behind it, the bot complements the store and takes over repeat purchases.
Key takeaways
A bot shortens the purchase to one screen: nobody opens a website, registers or re-enters a card that Telegram already holds. The gain shows where the range fits into a few screens and the decision is made from a photo and a price.
A full store in Telegram pays off when at least one of these is true:
If you carry thousands of items and need deep filters and search traffic, a bot will not replace the storefront: catalogue pages on a website are a separate source of visits from search and from AI answers. How such a storefront is assembled is covered in the article on launching an online store in Uzbekistan. The working combination looks like this: the website brings new buyers, the bot keeps repeat orders.
The order path is the same for a button bot and for a Mini App storefront: only the interface where a person picks goods differs. These steps are designed before development starts — each one later becomes a screen and a record in the database.
Save the payment identifier from the sixth step right away, next to the order: it is what you search by when a disputed payment is investigated and a refund is issued.
Buttons suit a short list, a Mini App suits a catalogue that people scroll, search and filter. A Mini App is a web interface that opens inside Telegram from a bot button and does everything a normal storefront does.
| What we compare | Bot buttons | Mini App storefront |
|---|---|---|
| Catalogue size | Dozens of items | Hundreds and thousands of items with search |
| How choosing looks | Messages, buttons, photos one by one | Categories, cards, filters, a cart on screen |
| Cart | Built through chat, easy to lose track of | Visible in full, quantities change in place |
| Development | Faster and cheaper | More expensive: a separate interface and a server |
| Source of prices and stock | Bot admin panel or a spreadsheet | Accounting system over an API |
| What to check in security | Rights to bot commands | Signature of user data on the server |
The user data a Mini App receives from Telegram is verified on the server: the initData string is signed with a key derived as HMAC-SHA256 of the bot token with the string WebAppData, and its contents must not be trusted before that signature is checked. Without the check, a forged request will pass any customer identifier and any price.
Tip Start with buttons if you have few items and the range rarely changes. Moving such a bot to a storefront later costs less than rebuilding a Mini App that was assembled before anyone knew what people actually order.
Both providers are connected in @BotFather: the bot settings open the Payments section, where you choose the payment system — Paycom.Uz for Payme or CLICK Uzbekistan. What differs is the requirement each provider sets on its own side.
Telegram stays an interface in this chain: it does not collect payment data and takes no commission for the Payments API, while the card is processed and stored by the provider. How the two payment mechanisms differ and which one fits your goods is covered in the article on payments and automatic notifications in a Telegram bot.
Mistake Selling a digital product through Click or Payme — a course, a subscription to a private channel, a limit upgrade inside a service — is not allowed. Digital goods and services inside Telegram are sold only for Telegram Stars in the XTR currency; cards stay for physical goods and offline services.
Payment is the middle of the process, not the end: the order has to be confirmed, written off stock, passed into work and documented for the customer. The minimum set of actions after a successful charge looks like this:
The CRM link is separate work, and it pays off first: the bot should not send thanks but create a deal and move it through statuses. How that is arranged is described in the article on integrating a Telegram bot with a CRM.
The bot does not issue the fiscal receipt: the provider does. Payme passes the receipt data to the company billing with the SetFiscalData method — the virtual fiscal module number, the fiscal sign and the receipt address; the same data arrives for cancelled payments. Store it together with the order: otherwise the only way to show a customer the receipt is a report from the provider.
Lost orders are almost never about design; they come from a few repeating slips. Each one shows up only after launch, when the money has not arrived.
Before the first working day the bot goes through a rehearsal on a real order: a small amount, a real card, a real delivery. A short list of what to look at:
A bot that takes requests and bookings starts at 1,200 $ with us, and automation of the routine around orders at 2,500 $; all prices for bot and AI assistant development are listed on the service page. Four things drive the spread inside those figures.
For comparison: an online store on a website with a catalogue, payments and exchange with an accounting system starts at 10,000 $ with us. That is why a bot is often the first step — it tests demand and shows what people order before you invest in a storefront. If you need an account area with order history and documents rather than a store, look at how a client account in Telegram instead of a mobile app works.
We start not with buttons but with the order itself: what people buy, how often, who packs it and where time is lost today. From that we decide whether buttons are enough or a storefront is needed, and which fields an order needs so that it can be packed without calling the customer.
Then we connect the provider, route orders into the CRM, set up statuses and notifications, run payments on the test terminal and move to the live one. After launch we watch the first orders and fix the steps where people stop. The bot speaks Russian and Uzbek if that suits your customers better.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
No. Digital goods and services inside Telegram are sold only for Telegram Stars in the XTR currency. A card through Click or Payme stays for physical goods, delivery and offline services.
Yes. A Telegram bot works only with a cash desk added for the bot and does not connect to the other cash desks of the business. Such a cash desk can be added only to an active business with a partner bank contract.
The payment is cancelled: the bot has 10 seconds to answer before the charge. That is why availability and price are checked with a fast query rather than a full recalculation in the accounting system.
Telegram will not pass an invoice below 12,980.89 soums or above 129,808,943.61 soums. A large order is split into parts or moved to the provider payment page.
It will, but not on buttons: thousands of items belong in a Mini App storefront with categories, search and filters. The website is still needed, because catalogue pages bring new buyers from search.
We build a bot that takes requests and bookings from 1,200 $, and a store with a catalogue, payments and exchange with an accounting system from 10,000 $. The difference comes from the storefront, filters, the client account and integrations.
The receipt is issued by the payment provider, not by the bot. Payme passes the receipt data to the company billing: the fiscal sign, the fiscal module number and the receipt address, and the bot stores them and sends the customer a link.
Sources
Cover photo: Mahdi Bafande, Pexels
