Telegram Bot for Dropshipping: Order Automation
In dropshipping, money is lost not on ads but on manual processing. A manager copies orders from direct messages into a spreadsheet, forwards them to the supplier, then manually sends the tracking number to the customer - and something gets lost at every step. A Telegram bot for dropshipping closes this whole chain automatically: from picking a product in the catalog to the tracking number landing in the buyerʼs chat.
How a Telegram bot for dropshipping is built
Technically this is an ordinary bot connected to three things: a product database, your CRM or spreadsheet, and the supplierʼs chat. The customer sees a menu, picks a category, a product and a size, then leaves a name, phone number and delivery office. The bot does not try to parse free-form text - it walks the person through steps with buttons, so the data arrives clean and in one format. That is the main difference from direct-message chats where everyone writes however they like.
After that the bot works as a dispatcher. It builds an order card, sends it to you, duplicates it to the supplier in the required format, and returns a confirmation with the total and delivery time to the customer. All the logic is described once and then repeats identically on the first order and on the thousandth. The human factor disappears along with phrases like «forgot to forward it» and «I think I already messaged this client».
A separate benefit is that the bot does not sleep. An order at two in the morning is handled the same way as one at two in the afternoon: the customer gets a confirmation, the supplier sees the request queued in the morning, and you see the number in the report. For a niche where half the traffic comes from evening prime-time ads, that is a direct conversion gain with no extra budget.
Catalog in the bot: showing products without a website
The catalog in the bot is built from categories, product cards and filters. A card is a photo or gallery, a title, a price, a short description, available sizes or colors, and an «Order» button. If you have fewer than a hundred items, a simple category tree is enough. With a bigger assortment you add search by name and a price filter, otherwise the person gets lost on the third screen and leaves.
The data source is usually Google Sheets or a supplier feed in XML or CSV. The bot pulls titles, prices and stock levels from there on a schedule, for example once an hour. Out-of-stock products are hidden automatically - so you do not sell something you will later have to cancel and refund.
Prices should be calculated by formula, not by hand. The spreadsheet holds the supplierʼs wholesale price, and the bot shows the retail price with your markup: a percentage, a fixed amount, or a rule for a specific category. If the supplier raises the wholesale price, retail recalculates itself and your margin stays where it should be.
Order intake and the card in CRM or Google Sheets
Order intake is a form of several steps: confirming the product and quantity, name, phone, city, delivery branch, payment method. The phone is validated for format, and city and branch are pulled from the carrierʼs directory, so «the post office somewhere near the market» never reaches your database. The customer can step back and fix a mistake before submitting.
A completed order lands in two places at once: a row in Google Sheets and a card in your CRM, if you have one. The card stores all customer data, the order contents, the total, the traffic source and the status. From there it is no longer chaos in a chat but a proper funnel where you can see how many requests are in progress, how many are shipped and how many are paid out.
This is also where you get analytics that chat threads never provide. At the end of the week you can see the average order value, top products, the share of unreachable customers, and how many orders each ad creative brings thanks to tags in the bot link. Decisions about what to scale and what to switch off are made on numbers, not on gut feeling.
Supplier handoff and customer notifications
The supplier handoff is configured for the channel they actually use. Some prefer messages in a separate Telegram chat, some need a row in a shared spreadsheet, and others accept orders only via API or email. The bot composes the message from a template: SKU, quantity, recipient name, city, branch, payment type. The supplier asks no follow-up questions because the request already contains everything.
The flip side is customer notifications. When the supplier sets the status to «Shipped» in the spreadsheet and enters the waybill number, the bot messages the buyer itself: the order is on its way, here is the tracking number, the estimated transit time is this. Then come reminders - about arrival at the branch and about the parcel waiting on its final day before being returned.
These automatic reminders are what shows up most clearly in money. A share of parcels comes back simply because someone forgot to pick it up, and every return means lost margin plus shipping paid in both directions. Two timely chat messages noticeably reduce the non-pickup rate, and doing that by hand at volume is not realistic.
Owner admin panel and how long setup takes
The owner needs an admin panel, otherwise every small change goes back to the developer. The minimum set: add or hide a product, change a price and markup, edit message texts, change an order status, send a broadcast to the subscriber base and view a report for a period. The admin panel is often built inside Telegram as well - a separate menu for accounts on the administrator list.
In terms of time, a basic version - catalog, order form, spreadsheet export and notifications - takes roughly one to two weeks to build. The full version with CRM, automatic supplier handoff, delivery statuses and an admin panel takes about three to four weeks, depending on how conveniently the supplier shares data. The longest part is usually not the code but agreeing on export formats.
It is worth starting simple: catalog, orders and a spreadsheet, adding integrations once the order flow justifies them. At Devlly we build such bots for a specific business - with your assortment, your suppliers and the CRM you already use, without trying to squeeze your process into someone elseʼs template.