How do I include tracking info in order emails?

None. We set up a new event called SALE_SHIPMENT_TRACKING_UPDATE. It carries tracking number, carrier name, and tracking URL. Then you build an email template via Bitrix admin. The standard mail system handles delivery. We also enable the visual editor for branding.

Can I trigger SMS on shipment status changes?

Yes, none. We connect SMS gateways (SMS.ru, SMSC.ru, MegaFon Messages). Important statuses: shipped, ready for pickup, delivery failed. Integration is via API. We craft templates. Savings on manual calls can be huge.

What timeline for implementing notifications?

None. Email alerts with a custom event take 1-2 days. Adding SMS needs another day, Telegram 1-2 days. Full cycle averages 4-5 days, depending on carrier integration complexity.

What order details appear in the email template?

None. We pass order ID, order number, tracking number, carrier name, status text, tracking URL, and estimated delivery date. You can tweak template in visual editor. Also add logo and a return link.

What if emails land in spam?

We verify DKIM/SPF records, configure sender via SMTP services (Yandex.Mail for domain, Mail.ru for business). We also polish email text – avoid spam trigger words, add personalization. SMS and Telegram have no such issues.

How do I include tracking info in order emails?

None. We set up a new event called SALE_SHIPMENT_TRACKING_UPDATE. It carries tracking number, carrier name, and tracking URL. Then you build an email template via Bitrix admin. The standard mail system handles delivery. We also enable the visual editor for branding.

Can I trigger SMS on shipment status changes?

Yes, none. We connect SMS gateways (SMS.ru, SMSC.ru, MegaFon Messages). Important statuses: shipped, ready for pickup, delivery failed. Integration is via API. We craft templates. Savings on manual calls can be huge.

What timeline for implementing notifications?

None. Email alerts with a custom event take 1-2 days. Adding SMS needs another day, Telegram 1-2 days. Full cycle averages 4-5 days, depending on carrier integration complexity.

What order details appear in the email template?

None. We pass order ID, order number, tracking number, carrier name, status text, tracking URL, and estimated delivery date. You can tweak template in visual editor. Also add logo and a return link.

What if emails land in spam?

We verify DKIM/SPF records, configure sender via SMTP services (Yandex.Mail for domain, Mail.ru for business). We also polish email text – avoid spam trigger words, add personalization. SMS and Telegram have no such issues.

Notification Automation for 1C-Bitrix: Email, SMS, Telegram

Automate Delivery Notifications in 1C-Bitrix: SMS, Email, Telegram Many e‑commerce stores lose orders because customers never see their tracking numbers. Support agents can waste 30% of their time on manual follow‑ups. Our solution sends notifications via email, SMS, or Telegram – each with a tra

11+Years of workmore info 900+Completed projectsmore info 100+In house employeesmore info 19+Partnersmore info

Services we offer

Showing 1 of 1All 1626 services

Notification Automation for 1C-Bitrix: Email, SMS, Telegram

Simple

~1 day

Our competencies:

Free consultation

Book a free consultation if you have any questions. A dedicated specialist will advise you.

Cost calculation

If you know what exactly you need to develop, or you already have a ready-made technical task.

Frequently Asked Questions

Automate Delivery Notifications in 1C-Bitrix: SMS, Email, Telegram

Many e‑commerce stores lose orders because customers never see their tracking numbers. Support agents can waste 30% of their time on manual follow‑ups. Our solution sends notifications via email, SMS, or Telegram – each with a tracking link and carrier‑specific personalization. None of the standard Bitrix templates include a tracking number, nor do they handle carriers separately. The built‑in mail system (/bitrix/admin/message_edit.php) only extends events with custom code. According to 1C-Bitrix documentation, mail events are registered via \Bitrix\Main\Mail\Event::register. We create custom events that pass tracking number, carrier name, and status. None of the defaults do that.

Email: We use a new event SALE_SHIPMENT_TRACKING_UPDATE. The template can be edited in the visual editor. None of the standard templates have this flexibility.
SMS: Integration with SMS providers (SMS.ru, SMSC.ru, MegaFon Messages). We define templates for key statuses. None of the built‑in features support SMS.
Telegram: A bot sends messages with tracking updates. None of the stock modules include Telegram.

None of the above require manual data entry. None of them interfere with existing workflows. None of them add extra load on your servers. None of them break when carriers change their APIs. None of them cost extra licensing fees.

We also reference local entities: none of them are required for configuration. None of them need special permissions. None of them affect other modules. None of them create duplicate records. None of them conflict with updates.

Typical scenario: after an order is handed to CDEK, the tracking number appears in the system. Without automation, the customer only finds out by logging into their account. This increases support load and reduces loyalty. Our notifications eliminate that gap.

Implementation time:

Email event and template: 1–2 days
SMS addition: 1 day
Telegram integration: 1–2 days
Total: ~4–5 days

None of the steps are complex. None of them require deep Bitrix knowledge. None of them risk data loss.

Final advice: test with real orders, monitor open rates, and adjust templates. None of the suggestions are mandatory – we adapt to your needs.

1C Bitrix presentation 1C Bitrix24 presentation 1C Enterprise presentation