No reviews found
Store notifications go to Telegram and MAX — where people actually read them
The add-on adds two channels to the standard CS-Cart notification system. The event lists, the permissions and the templates stay where they are — two columns, "Telegram" and "MAX", appear next to "E-mail". Sending goes through a queue, so checkout never waits for a messenger.
On top of standard notifications the same screen, the same events, the same order
|
Two messengers Telegram and MAX, with a fallback channel on failure
|
A queue and a log the message text, the messenger answer and the order
|
CS-Cart 4.17.1+ and Multi-Vendor; its own bot for every storefront
|
Why a store needs it
A letter about an order does not always arrive and is rarely read at once: it lands in the "Promotions" tab, gets lost among newsletters, and on a phone without a mail client it is simply invisible. The customer calls and asks what is happening with the order — although the store has already written three times. A message in a messenger arrives as a notification on the screen and is read within minutes.
Read right away
The order status arrives as a phone notification, not as a letter that will be opened in the evening or never. |
Fewer "where is my order" calls
The customer subscribes to the order with one button and sees every step: placed, processed, shipped. |
Nothing new to learn
The events and the permissions are the standard ones. Whoever set up the letters in CS-Cart will set up the messengers: same screens, same variables. |
You see what was sent
The log shows the message text, the messenger answer and the order — there is something to work from when a customer complains. |

How it works
STEP 1
Connection
The customer presses "Connect" in the account or "Track the order" on the order page and opens the store bot. The store issues a one-time code, the bot returns it — the chat is linked to the account. |
STEP 2
Event
The order changes its status. CS-Cart prepares the notification as usual; the add-on adds the enabled messengers to the e-mail. |
STEP 3
Queue
The message goes into the queue and leaves with a separate job. Checkout does not wait for the messenger to answer. |
STEP 4
Log
The result of every attempt is recorded: the text, the messenger answer, the order. Anything undelivered is re-sent with one button. |


The message text is its own, not the whole letter
A letter does not move into a chat: there are no tables, no images and no logo signature there. So every event has its own text for a messenger — and it is edited where the letter is, in the tabs of the notification card.
The same variables
The order number, the total, the status, the customer name — whatever is available in the letter is available in the message. |
Messenger markup
Bold, italic, links and monospace. Extra tags are stripped, the length is limited to 4000 characters. |
An event can be turned off
The "Disabled" status of a template turns the sending off for this event and this messenger without touching the letter. |

What the customer sees
A store cannot write into a chat first — a messenger does not know the e-mail address. The first step belongs to the customer, and the add-on puts a button in the three places where they are ready for it.
The customer account
The "Messenger notifications" section: what is connected, under which name, and an unlink button. |
The order page
"Track via Telegram" next to the standard order actions. |
Thank you for your order
A button right after the checkout — the moment people subscribe to the status most willingly. |
Guest orders
The connection belongs to the order: notifications arrive without an account in the store. |


Setting it up
A bot is needed: @BotFather creates it in Telegram, @MasterBot in MAX. The token and the bot name go into the settings, the webhook is created with a button from the same place. Then a schedule for processing the queue — the ready CRON commands are shown in the settings.
Its own bot per storefront
The settings are storefront-level: every store has its own bot, its own name and its own buttons. |
Retries on failures
A temporary messenger error is not a lost message: the add-on retries the configured number of times. |
A webhook with a check
The "Create", "Check" and "Delete" buttons sit next to the settings; foreign requests are dropped by the secret. |

Frequently asked questions
Do I have to switch the letters off?
No. A checkbox in a messenger column adds a channel, it does not replace the letter. If the letter is not needed for an event, clear the checkbox in the "E-mail" column separately.
What is needed besides the store?
A Telegram bot (a token from @BotFather) and/or a MAX bot, the store address over HTTPS and a CRON job that processes the queue. The add-on shows the ready CRON commands in its settings.
How does a customer connect a chat?
They press the button in the account, on the order page or on the "Thank you for your order" page, open the bot and press "Start". The store issues a one-time code, the bot returns it — nothing else is required from the customer.
What if the customer ordered without registration?
The connection is bound to the order: the notifications about this order arrive without an account in the store.
Will the add-on slow the checkout down?
No. The message goes into a queue and a separate scheduled job sends it: the checkout does not depend on the availability of a messenger.
What happens if a customer blocks the bot?
The messenger returns an error, it goes into the log and no retries are made. The letter for this event is sent as usual if it is enabled.
Does it work with several storefronts?
Yes. The token, the bot name and the buttons are set for every storefront separately; the queue, the log and the templates belong to the store administrator.
- Store Builder
- Store Builder Plus
- Store Builder Ultimate
- Multi-Vendor
- Multi-Vendor Plus
- Multi-Vendor Ultimate
- 4.21.1
- 4.20.1
- 4.19.1.SP2
- 4.19.1.SP1
- 4.19.1
- 4.18.4
- 4.18.3
- 4.18.2.SP1
- 4.18.2
- 4.18.1.SP1
- 4.18.1
- 4.17.2.SP3
- 4.17.2.SP2
- 4.17.2.SP1
- 4.17.2
- 4.17.1
- English
- Русский
|
CS-Cart development · in-house team · since 2013 We build, upgrade and speed up CS-Cart stores and marketplacesAnalysts, developers, designers, QA and support under one roof — no subcontractors. We ship add-ons you can buy on this page today, and we take on the work that no ready-made add-on covers. |
|
2013 Working with |
4.98 Rating from |
200+ Solutions on this |
500+ E-commerce projects |
Flagship products
Two add-ons that change how a store performs
Everything else we publish improves one screen. These two change the numbers: how customers find products, and how often they come back.
|
Add-on · Search & merchandising Smart SearchElasticsearch-powered search for large catalogues. The customer types two letters, sees products with images and prices, and buys from the dropdown — even after a typo or with the wrong keyboard layout. Visitors who use the search bar are 24% of traffic and 44% of revenue, and convert about 2.5× better than people who only browse categories. If search returns nothing, up to 80% of them leave. | ||||||||
| ||||||||
Try it on a live catalogue: open the demo store and search with a deliberate typo. |
|
Add-on · Mobile commerce PowerApp — mobile app for your storeA native iOS and Android app running on your CS-Cart data: the same products, prices, stock, promotions, reward points and orders. There is no second catalogue to maintain — everything stays in the admin panel you already use. A mobile site brings a customer in once; an app brings them back for free. Push notifications replace the retargeting budget you spend to buy the same customer a second time. | ||||||||
| ||||||||
Screens, block types and pricing tiers: see how the app is built. |
Services
When no add-on solves it, we do the work
Fixed scope, written specification, a named project manager and a warranty on what we ship.
|
Custom CS-Cart development Functionality the platform does not have: add-ons, marketplace mechanics, integrations with 1C, CRM, ERP, payment and delivery providers. We start from a written specification, not from an estimate on a phone call. Details → |
|
CS-Cart upgrade Move to the current version without losing data, custom code or add-ons. We audit every modification first, upgrade on a staging copy, adapt what breaks and switch over with little or no downtime. Details → |
|
Speed and performance optimisation Conversion falls by about 4.4% for every extra second of load time. We profile the server, the database and the front-end, then fix what actually costs the seconds — and show you the before-and-after numbers. Details → |
|
Design for CS-Cart Mobile-first storefront design built on CS-Cart's own template structure, so the layout survives the next platform upgrade instead of becoming a migration problem. Details → |
|
SEO for CS-Cart A technical audit of indexing, duplicates, redirects, structured data and Core Web Vitals — delivered as a prioritised fix list your developers can act on, or that we implement ourselves. Details → |
How we work
What you get besides the code
|
Before we start We discuss the goal, offer options and write the specification. You approve scope and price before development begins. |
While we build A named project manager reports progress on a fixed schedule. You always know what is in work and what is next. |
|
Before release A separate QA pass on every release — the developer who wrote the code is not the person who signs it off. |
After handover Documentation for everything we ship, plus a warranty on the modifications and the project. |
Tell us what the store needs to doDescribe the task in a couple of sentences and we will come back with options, a scope and a price. The consultation is free, and we will say plainly if a ready-made add-on already solves it.
|
Client cases, our full add-on catalogue and 184 customer reviews are in the tabs above.
Similar products
Make purchases for 200$ from our entire offer and get 20% discount