A Telegram shop bot
that takes an order while you sleep
A shop bot is the fastest path to a working store, for a seller whose customers already live in Telegram. A catalogue, a cart, a payment, a confirmation. No website build, and no app store review to wait on.
Where a bot beats a website
A Telegram shop bot replaces a website for a seller whose buyers are already in Telegram. Digital goods, local food, print-on-demand, small retail, anything where the catalogue is not huge. The buyer orders in two taps instead of loading a page.
It suits a seller testing a product before building a full store. It also suits a seller who already has thousands of Telegram subscribers, and would rather sell where the audience already is than drive them to a separate site.
It does not suit a catalogue of thousands of SKUs with heavy filtering. That is a job for a real store (see e-commerce development). It is also not a replacement for a storefront that needs to rank in search. For a focused catalogue and a fast path to a first sale, the bot is the cheaper, faster build.
What happens inside the chat
The bot shows categories and products with images and prices, and lets a buyer build a cart. Payment happens inside the chat. Telegram Stars for digital goods, a card processor for physical products, or a crypto gateway where that fits the market. Every order triggers an admin alert with the order details, and a confirmation goes back to the buyer automatically. Stock status updates so a sold-out item stops appearing before someone tries to pay for it.
On the admin side, you get either a web panel or a set of admin-only chat commands, to add products, change prices and mark orders fulfilled. Updating the catalogue never needs a developer. We built this exact pattern for ProBay, the marketplace we are launching. Catalogue sync, stock guards and admin tooling, the same pieces, built for a catalogue of 2,179 products across 130 categories.
If you already sell through a website or a supplier feed, the bot can sync from that source. No second, separate catalogue that someone has to update twice. That one decision, sync versus manual entry, is usually the biggest driver of both price and timeline. We size it from your actual setup, rather than assuming either way. If your store already converts well, we treat the bot as a parallel channel with its own stock sync, not a rebuild. We will say so plainly, rather than sell you a build you do not need.
How we size and ship it
We start with your actual catalogue and your typical order volume, not a generic template. A seller with 20 products and a seller with 2,000 need different data models underneath the same chat experience. We write the flow and the copy first. We test the payment path with real test transactions before anything goes live. And we ship a working demo every few days, so you can react to the bot as it takes shape, instead of seeing it only at the end.
Margin and stock guards are built in from the start. An order cannot be accepted for a product that just sold out. A price change takes effect immediately everywhere it is shown, not just on the next sync. We deploy to a small VPS or your existing server, and set up monitoring, so a crash sends an alert instead of going unnoticed. Access to everything, bot token, server, repository, is handed over on day one.
Timeline and price
| Tier | Price | Timeline | What changes |
|---|---|---|---|
| MVP | from $900 | 1 to 2 weeks | One core flow, one channel, enough to go live and test demand |
| Production | from $2,200 | 3 to 5 weeks | Full flow, admin tools, integrations, monitoring, ready for real volume |
| Full control, handover-ready | from $3,200 | 5 to 7 weeks | Same build, plus documentation, test coverage and a handover package so any developer can take over, not just us |
Running cost is typically $10 to $30 a month in hosting, plus whatever a payment provider charges per transaction.
What you own at the end
The bot token, the server it runs on, the database with every order and customer message, and the full source code in a repository under your account. Nothing sits inside an account you would lose if a contractor disappeared.
Related
Pairs well with a Telegram Mini App marketplace if your catalogue grows past what a chat interface handles comfortably. It also pairs with a Telegram CRM bot for sales teams, once order volume needs a team, not just you, watching it. See digital goods store with instant delivery for the delivery side and Telegram Stars payments for that payment option specifically. For a real build with a catalogue, pricing and margin guards at scale, see the ProBay marketplace case study.
Want to see what your catalogue would look like as a bot? Get in touch with a rough product count and we will size the build.
FAQ
How much does a Telegram shop bot cost?
A bot with a fixed catalogue, cart and one payment method starts at $900 and is live in one to two weeks. A bot with a catalogue synced from your own system, multiple payment methods and an admin panel runs $2,000 to $4,000.
How long does it take to launch?
One to two weeks for the MVP tier. A production build with stock sync, delivery integration and an admin panel takes three to five weeks depending on how many systems it needs to talk to.
What is the bot built on?
Python with aiogram, PostgreSQL for the catalogue and orders, Redis for session state, deployed with Docker behind Caddy. Payments go through Telegram Stars, a card processor or a crypto gateway depending on your market.
Who owns the bot and the data after launch?
You do. The bot runs under your own Telegram bot token. The code is in a repository in your name from the first commit. Order data lives in a database you control, not a vendor's account you could lose access to.
What if I need changes after launch?
The repository and documentation are yours, so any developer can pick it up. We also offer ongoing fixes and feature work from $500 a month if you would rather not manage a second contractor.