How a Small-Business Store Works Inside a Telegram Mini App: Catalog, Payment, Orders

Roman Barintsev — Wed, 04 Nov 2026 14:17:38 +0000

Some small businesses already talk to their customers in Telegram. Clothing resellers, cosmetics shops and bakers post photos in a channel, and buyers reply "is this still available?". It works until there are twenty conversations at once. Then orders get lost, prices are explained again and again, and nobody remembers who paid.

Mini Apps are one way to handle this. A Mini App is a web app that opens inside Telegram from a bot, with access to the user's Telegram identity and native UI elements. For a shop, that means a real storefront without asking the buyer to install anything or leave the chat. Below is what such a store needs, seen from the seller's side.

1. The entry point: a bot

Every Mini App store starts with a bot. The bot is the address the seller shares ("t.me/yourshop_bot"), the button that opens the storefront, and the channel for service messages: order confirmation, payment received, status changed.

Practical decisions at this stage:

Who owns the bot. The safest answer is the seller. If a platform creates the bot for you, check that it is registered to your account and that you can replace the token later.
The bot's name and username. Buyers see them in search and in forwarded links, so they should match the brand.
Where admin notifications go. A shared Telegram group for the team is better than one person's private chat.

2. The catalog

The catalog is where most of the work goes, and where Mini Apps beat channel posts. A post is a picture with text. A catalog is structured data: name, price, old price, stock, category, variants, characteristics.

Things that matter in practice:

Variants instead of duplicates. One T-shirt in five sizes and three colors is one product with variants, each with its own stock and price. Duplicating products breaks search and stock counts.
Stock that blocks sales at zero. If a buyer can order something that is gone, you are back to apologizing in chat.
"Visible but not for sale". Useful for announcements: the product is on the storefront, but the add-to-cart button is disabled.
Bulk import. Nobody types 300 products by hand. A CSV or Excel import with name and price as the only required fields is the realistic way to migrate from a spreadsheet or another platform.
Categories created first. If import maps products to categories by name, the categories should exist before the upload.

3. Cart and checkout

The checkout inside a Mini App should collect exactly what the seller needs to ship the order, and nothing else: contact, delivery method, address or pickup point, payment method, comment. For physical goods in Ukraine, delivery usually means choosing a Nova Poshta branch, a courier, or pickup.

Two choices shape the flow:

Cart or request. Products with fixed prices suit a cart. Custom work (cakes, furniture, services) often works better as a request form, where the seller confirms price and details afterwards.
Minimum order and free-delivery thresholds. They are simple rules, but they remove a lot of back-and-forth.

4. Payment

Sellers ask about this part most often. There are two broad groups of payment methods.

Without a bank agreement: bank card transfer by details, cash on pickup, card terminal or cash on delivery at the post office. Easy to start, but the seller has to match payments to orders manually, and the buyer may need to send a receipt.

Online acquiring: a payment provider charges the buyer's card and confirms the payment automatically, so the order moves to "paid" without anyone checking a bank app. This requires an agreement with the provider and a merchant account; fees are set by the provider, so check current terms before choosing.

For digital goods there is also Telegram Stars, Telegram's own in-app currency, which can be the simplest option when the product is a file, a course or access to something.

One principle: the buyer's money should go directly to the seller's account through the provider the seller chose, not through the platform. It keeps accounting clean and removes a dependency.

5. Orders after the click

A storefront does not process orders by itself. The minimum is:

a numbered order list with statuses (new, accepted, shipped, completed, cancelled), with the option to add your own;
an automatic message to the buyer when the status changes;
notifications to the team for new, paid and cancelled orders;
a list of abandoned carts and a way to remind those buyers;
export, because the accountant will ask.

6. The customer base

Every order in a Mini App store comes from a real Telegram user. That is the long-term value: a list of buyers with order history, which you can segment ("bought twice, not in 60 days") and message with a broadcast. On a marketplace the buyers belong to the marketplace; in your own Telegram store they are your customers.

Build or use a platform?

You can build all of this yourself with the Mini Apps API, a backend, a payment integration and an admin panel. For a developer that is a satisfying project; for a seller with 40 products it is a long project before the first order.

The alternative is a hosted platform. As one example, OKKKI (a Ukrainian SaaS launched in 2024) provides the bot connection, Mini App storefront, checkout, payment and delivery settings, order statuses and a customer base, and starts free for up to 10 products. Whatever you choose, check the same list: who owns the bot, how payments reach you, whether stock and variants are real data, and whether you can leave with your customers.

If you want to see how payment setup looks step by step (card transfer, online acquiring, Telegram Stars), there is a Ukrainian-language guide here: https://okkki.net/guides/nalashtuvannia-oplaty

DEV Community: Roman Barintsev