Telegram bot for a shop: catalogue, orders, status updates

Why a shop needs a bot in Telegram

The main reason is low friction for the buyer. Telegram is already installed, authorisation happens automatically. Someone clicks a link, sees the catalogue, and can buy in two minutes. No need to enter an email, invent a password, or confirm registration. This matters especially for impulse purchases and low-ticket items.

Second point - notifications. When an order is accepted, packed, or shipped, the bot messages the customer directly. The message arrives where they talk to friends, so open rates are higher than email. The customer sees order status in real time instead of hunting for a message in spam.

The bot also works as a retention tool. You can send a selection of new arrivals, remind about an abandoned cart, or offer a personal discount. Telegram broadcasts cost less than SMS and target better than ads, because you're writing to people who already bought.

But a bot does not replace a website. It's a separate channel for those who prefer messengers. If you have a large catalogue with filters and complex logic, the website handles it better. A bot is good for narrow assortments, repeat orders, and quick purchases.

How the storefront and catalogue work

The catalogue in a bot is product cards with photos, descriptions, prices, and buttons. The buyer scrolls through categories, picks a product, adds to cart. The mechanics are like a website, but the interface is built from messages and inline buttons.

Products load from a database. If you already have a website or accounting system, the bot can pull data from there. Then prices and stock update automatically: change the price on the site and it changes in the bot too. This is cheaper and more reliable than maintaining two catalogues by hand.

Categories and filters depend on assortment. If you have fewer than thirty products, a simple list is enough. More than that and you need sections: clothing, shoes, accessories. Complex filters by size, colour, and brand are possible in a bot, but they complicate navigation. Someone came for a quick purchase, not half an hour of selection.

Product photos need to be ready in advance. A bot cannot process images on the fly: if the site loads a picture at the right size automatically, here you upload it manually or via API. A bad photo in a messenger kills the sale faster than on a site, because the screen is small and there are no competitors in the next tab.

Cart and checkout

The cart in a bot works the same as on a site: the buyer adds products, changes quantity, sees the total. The difference is that cart state is stored on the server, not in the browser. Someone can close Telegram, come back a day later - the cart is still there.

Checkout usually consists of three steps: contact details, delivery address, payment method. If the customer bought before, the bot offers to use saved data. This speeds up a repeat purchase to one button.

There are several payment options in Telegram. Built-in payments via Telegram Payments work with Visa and Mastercard directly in the bot interface - the customer enters card details once, then pays in two clicks. Alternative - a link to an external payment gateway: YooKassa, Robokassa, Stripe. The customer goes to the payment page, returns to the bot after a successful transaction.

Telegram Payments is more convenient for the customer, but does not work with all acquiring banks. An external gateway gives more flexibility: you can accept local bank transfers, e-wallets, instalments. The choice depends on which payment provider you already work with.

After payment, the bot creates an order and sends data to your accounting system or a spreadsheet. The customer receives confirmation with an order number and estimated delivery time. Then status tracking begins.

Order status notifications

Statuses are why many launch a bot. The customer sees that the order is accepted, packed, handed to courier, delivered. Each status change sends a message to Telegram automatically.

The mechanics are simple: when a manager changes order status in the CRM or accounting system, the bot receives a signal via webhook and sends a notification to the customer. If there is no accounting system, statuses can be changed directly in the bot via an admin panel. It takes longer, but it works.

Notification text is better written in plain language. Not "order № 12345 moved to status 'Assembly'", but "Your order is packed and will leave soon". Someone should understand what is happening without consulting a status reference.

Notifications can be configured selectively. Not all statuses need to be shown to the customer: "Awaiting payment confirmation" is an internal status, only the manager sees it. The customer cares about three things: order accepted, order in transit, order delivered.

Integration with accounting system and warehouse

If you already run 1C, MoySklad, Bitrix, or another accounting system, the bot should integrate with it. An order from Telegram lands in the common database, the manager sees it next to orders from the site and offline location. Product stock syncs: if a product is out, the bot automatically removes it from sale.

Integration is done via API. The accounting system gives the bot a product list, prices, stock. The bot sends new orders to the system and fetches status updates. Most popular CRMs and warehouse programs can work with external services via REST API or webhook. If there is no standard API, a middleware layer is written to connect the bot and system.

Integration costs more than a simple bot without sync, but pays back quickly. You do not duplicate products manually, do not transfer orders from Telegram to a spreadsheet, do not check stock before each sale. Everything happens automatically.

Common mistakes when launching a shop bot

First mistake - trying to copy the entire site into the bot. A catalogue of 500 products with a dozen filters does not work in a messenger. Someone gets tired of scrolling, gets lost in categories, and leaves. A bot is good for a narrow assortment or popular positions. If you have many products, show top sellers in the bot and leave the rest on the site.

Second mistake - forgetting about mobile image formatting. A product photo that looks good on the site may turn out blurred or cropped in Telegram. Check pictures on a phone before upload: if the product is not visible, there will be no sale.

Third - not thinking through the scenario for questions. A customer writes to the bot "Is this product available in blue?" or "Can I get delivery tomorrow?". If the bot is silent, the customer goes to competitors. You need either a "Contact manager" button that forwards the message to a support chat, or an auto-reply with contact details.

Fourth - launching the bot and not telling anyone about it. Customers will not find the bot themselves if you do not give the link on the site, in social media, on a business card. Place a QR code in the offline location, add a widget to the site homepage. The bot should be visible where the customer makes a purchase decision.

How much development and support cost

Price depends on functionality. A simple bot with catalogue, cart, and checkout without integration costs less than a system with warehouse stock sync, CRM, and a loyalty programme. The studio site shows a "from" range for Telegram bots - an exact estimate forms after a brief, when the task list is clear.

Integration with an accounting system increases cost, but it is not always mandatory. If you have ten products and few orders, you can do without sync: the manager receives an order in Telegram, manually transfers it to a spreadsheet or CRM. It is slower, but cheaper at launch.

Support is needed if the bot is integrated with external services. APIs of payment systems and CRMs get updated, something breaks, you need to monitor and fix. If the bot works autonomously, without complex connections, support is minimal: update products, correct text, add a category. This can be done once a month or less.

Do not skimp on testing before launch. A bot with errors in checkout or payment loses money immediately: a customer tried to buy, it did not work, they will not return. Better to spend an extra day checking all scenarios than launch with loose ends.

When a bot is not needed

A bot makes no sense if you have complex B2B with specification approvals, contracts, and deferred payment. Corporate clients work via email, calls, and in-person meetings. Telegram will not speed up the process here.

If your entire audience is over 60 and does not use messengers, a bot will not work either. Check where your customers communicate now. If it is WhatsApp or phone, start there.

Do not launch a bot for the sake of a bot. If the site is handling it, orders are enough, and customers are not asking about Telegram, an additional channel will not bring growth. Problem first, tool second.