What a 1C Telegram bot actually is
It is not a separate product but a pairing. The Telegram bot acts as a convenient front end, while 1C remains the source and the destination of the data. The bot does not replace your accounting system. It shows what people need from it and writes back what used to be typed in by hand.
In Uzbekistan the idea fits naturally. Customers and staff already talk in Telegram, while 1C sits with the accountants, the warehouse and the sales team. For a sales rep on the road, messaging a bot is easier than calling the warehouse or opening the database over a remote desktop.
Use cases that pay off first
Start with two or three scenarios where the manual work is obvious and repeats every day. A full self-service account inside a messenger is almost always too much for a first release.
- Stock and prices for managers and wholesale buyers: look up an item by name or SKU instead of phoning the warehouse.
- Taking an order in the bot and passing it to 1C as a sales order document, with no retyping.
- Order and shipment status sent to the customer automatically when the document changes.
- A daily summary for the owner: sales, incoming payments, overdue receivables.
- Approving payment or purchase requests directly in the chat.
- Tasks for couriers and field reps, with a completion mark that flows back into the records.
- Payment through Click or Payme with a link in the chat and a paid flag in the database.
How the bot connects to 1C
Letting Telegram talk to the database directly is not a good idea. Usually a middle layer sits between them: a server that receives the bot's messages, checks the user's permissions, calls 1C and sends the answer back to the chat.
On the 1C side, teams most often use HTTP services or the standard OData interface when your platform version supports it. The choice depends on whether your configuration is standard or customised, where it is hosted and whether outside access can be opened safely.
- The bot receives a request and works out who is writing and what role they have.
- The middle server builds the request to 1C and limits the data it can return.
- 1C replies, and the reply becomes a short, readable message.
- Every call and error is logged so problems can be traced later.
Pitfalls that rarely come up in advance
The first is access rights. A bot should not reveal purchase prices or other clients' accounts just because a user knows how to phrase a question. Roles in the bot need to match roles in 1C.
The second is availability. If 1C runs on a local server in the office, you need a secured channel, and when power or internet drops, the bot should report a delay politely instead of going silent.
The third is data quality. Duplicate items, empty SKUs and several names for one product will not be fixed by a bot. It will simply show them to your customer. Cleaning up reference data before launch is common.
The fourth is support. A 1C configuration update can break the exchange, so someone has to own the integration after go-live.
What drives the cost
There is no fixed price for this kind of work, and that is normal because projects differ. The total depends on the number of scenarios, how complex your configuration is, whether changes on the 1C side are needed, whether Click or Payme is connected, how many roles you have and which languages the bot speaks: Uzbek and Russian, or just one.
The intermediary server and post-launch support are separate items. If a contractor quotes a price without asking about your database, treat that as a warning sign.
Where to start
Pick the one process that eats the most time today and decide in advance how you will know the bot works: fewer calls to the warehouse, faster order handling, fewer entry errors. Run a pilot with a small group of employees and expand only after that.
If you want to discuss how to connect a Telegram bot to your 1C, the markdev team can review your configuration and suggest a realistic first stage. Describe the task in the request form and we will come back with questions and options.
FAQ
Can a bot be connected to any version of 1C?
Most of the time yes, but the method depends on the platform and configuration. Older or heavily customised databases sometimes need a separate exchange layer, so it is worth assessing your database first.
Do I have to expose my 1C database to the internet?
Not necessarily. Teams usually use an intermediary server and a secured channel, so Telegram never reaches the database directly.
Can the bot work in both Uzbek and Russian?
Yes. The interface language is part of the bot's scenario. If you need both, prepare texts and product names in both languages in advance.
What if the data in 1C is messy?
Tidy up the reference data the bot will expose first: items, prices and counterparties. Otherwise the bot will only make the errors more visible.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.