A Bitrix site administrator should receive notifications about critical events instantly: new order, payment failure, agent error, disk quota exceeded. Standard email events cover basic scenarios, but we often encounter cases where they are insufficient: delivery delays, no Telegram channel, inability to filter by priority. We develop a notification system that combines Email, Telegram, SMS, and an internal log — turnkey with priority and digest configuration. For example, when a YooKassa payment fails, the administrator should be immediately notified via Telegram to contact the customer promptly. Or when disk space is exceeded, an agent can send an SMS if the site is business-critical. Each minute of downtime costs an average of 10,000 rubles, so notification speed is critical. We implement such scenarios on PHP 8.1+ using a custom module based on infoblocks v2.0 and tagged caching.
How does the standard Bitrix notification system work?
The Bitrix core uses an email event mechanism: event code → email template → recipients. All events are registered in the b_event table, templates in b_event_message, and the history of sent emails (if logging is enabled) in b_event_log.
For e-commerce, critical events already exist: SALE_ORDER_NEW (new order), SALE_ORDER_PAID (payment received), SALE_ORDER_CANCEL (cancellation). You configure recipients in the template through the main module → "Email events".
The problem with the standard mechanism: emails are sent synchronously at the moment of the event, which adds up to 500 ms to page load time if SMTP is slow. The solution is to use a queue via the b_email_service table or an external SMTP with fast connectivity.
Why are email events alone insufficient?
Email events have three limitations:
- Only Email channel (cannot send Telegram or SMS);
- Synchronous sending (slows down the server);
- No built-in prioritization (all events are equal).
Telegram notifications work 10 times faster than Email for critical events, and SMS guarantees delivery even when the site is down. For non-standard scenarios, we hook into module events via init.php.
How to set up custom notifications via module events
New form submission — OnAfterAddResult of the form module:
AddEventHandler("form", "OnAfterAddResult", function($formId, $resultId, $arResult) {
if ($formId == CALLBACK_FORM_ID) {
notifyAdmin('New request #' . $resultId, formatFormData($arResult));
}
});
Agent errors — agents in b_agent run without explicit logging. Wrap your agent code in try-catch and send a notification on exception:
function MyModuleAgent() {
try {
// agent code
} catch (\Throwable $e) {
notifyAdmin('Agent error', $e->getMessage() . "\n" . $e->getTraceAsString());
}
return __FUNCTION__ . '();';
}
Disk quota exceeded — Bitrix has an agent CIBlockAgent::CheckDiskQuota(). You can override it or supplement with your own agent that checks directory sizes and sends an alert when a threshold (e.g., 90% of quota) is exceeded.
Payment errors — the OnSalePaymentUpdate event with a check for status change to an error state:
AddEventHandler("sale", "OnSalePaymentUpdate", function($id, &$arFields) {
if ($arFields['IS_RETURN'] === 'Y' || strpos($arFields['PS_STATUS_MESSAGE'], 'error') !== false) {
notifyAdmin('Payment error', print_r($arFields, true));
}
});
How to send a notification via Telegram?
Create a bot via BotFather, get BOT_TOKEN and CHAT_ID of the admin chat. Send via \Bitrix\Main\Web\HttpClient:
function notifyTelegram(string $message): void {
$botToken = COption::GetOptionString('local', 'telegram_bot_token');
$chatId = COption::GetOptionString('local', 'telegram_admin_chat_id');
$httpClient = new \Bitrix\Main\Web\HttpClient();
$httpClient->post(
"https://api.telegram.org/bot{$botToken}/sendMessage",
['chat_id' => $chatId, 'text' => $message, 'parse_mode' => 'HTML']
);
}
Store tokens in b_option via COption, not in code — when rotating the token, you don't need to search through files.
Multi-channel delivery: Telegram, SMS, Push
Email is the base channel, but not always fast enough. For critical notifications, add:
Telegram bot
Delivery speed: 0.5–2 seconds. Reliability when site is down: low (requires internet). Cost: free.
SMS via API
For truly critical events (payment gateway unavailable, hacking attempts) — SMS via SMSC.ru or SMS.ru. Same HttpClient + API key. Cost per message: 2–5 rubles, justified when there is risk of losing an order.
Push notifications in browser
For notifications when the administrator is in the admin panel — via the system Bitrix Push Server (push.1c-bitrix.ru) or via Web Push API with VAPID keys.
| Channel |
Delivery speed |
Reliability when site down |
Cost |
| Email |
1 sec to 5 min |
low (depends on SMTP) |
free (via own server) |
| Telegram |
0.5–2 sec |
low (no internet) |
free |
| SMS |
1–10 sec |
high (mobile network) |
2–5 rubles per msg |
| Push (admin panel) |
instant |
medium (only admin is open) |
free (Bitrix Push Server) |
What is included in the development of the notification system
- Scenario analysis: we identify all critical events of your project.
- Design: channel architecture, priorities, digests.
- Implementation: custom module on infoblocks v2.0, events, agents.
- Channel configuration: Telegram bot, SMS gateway, push notifications.
- Integration with REST API for external services.
- Notification center in the admin panel with filtering and counters.
- Testing: load testing, fault tolerance.
- Documentation: description of events, channel setup.
- Support: maintenance for one month after implementation.
Estimated timelines
| Stage |
Duration |
| Analysis and design |
1–2 days |
| Module development |
3–5 days |
| Channel configuration |
1–2 days |
| Testing and documentation |
1–2 days |
| Total |
5–10 days |
Typical errors when designing notifications
Common problems and how to avoid them
- Sending all events to all channels creates information noise. Assign priorities.
- Storing tokens in code — use
COption or .settings.php.
- Ignoring cleanup of the
b_event_log table — after a month, the database can grow gigabytes on an active site. Set up an agent to delete records older than 30 days.
- Not testing site downtime — external monitoring (UptimeRobot, Zabbix) is mandatory, because when the server goes down, internal agents won't fire.
We have been developing notification systems for more than 8 years and have implemented over 30 projects for Bitrix online stores. Order the development of a notification system, and we'll set up all channels for your project. We'll evaluate your project in 2 days — contact us.
What Professional 1C-Bitrix Installation Includes
We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.
How to Choose Hosting and Edition for 1C-Bitrix Installation?
BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.
VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.
Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
What Server Settings Are Critical for 1C-Bitrix?
Web Server and PHP
nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.
Database and Caching
MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:
'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
SSL, Email, and Cron
SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.
Security and Administration
File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.
How Long Does 1C-Bitrix Installation and Configuration Take?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.
Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.
Deliverables
- Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
- Installed and activated license of the required edition.
- SSL certificate, email settings, cron and backups.
- Documentation: all configuration parameters, access credentials, cron tasks.
- Content manager training: how to log into admin panel, add products, upload images.
- Post-installation support for 30 days — consultations on settings.
Why Trust Professionals with Installation?
Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.
