Integrate A1 SMS with 1C-Bitrix: Fast Sending in Belarus

Standard SMS providers (SMS.ru, SMSC) often fail with Belarusian numbers. They lack alphanumeric sender ID, have high costs, and deliverability issues. A1 (formerly Velcom) — Belarus's largest operator — offers an SMS gateway for legal entities. It uses a Belarusian sender and guarantees delivery across MTS, A1, life:) networks. For Bitrix integration, we develop a handler connecting the A1 SMS API with the messageservice module (for B24) or main.mail (for on-premise Bitrix). With 5+ years of experience and over 50 successful SMS integrations, we ensure a reliable setup. Contact our team for a consultation.

Why A1 SMS is Better Than Alternatives for Belarus

Unlike foreign SMS providers, A1 guarantees delivery to MTS, A1, and life:) numbers. It retains the alphanumeric Sender ID. The cost per message is significantly lower than via SMS.ru for Belarusian numbers. Pricing starts at $0.02 per SMS, depending on volume. A1 also provides official DLR (Delivery Report) and callback notifications, giving full control over delivery.

How the A1 SMS API Works

A1 provides an HTTP API; documentation is given after signing a contract. Main endpoints:

• POST /api/sms/send — send one or multiple messages
• GET /api/sms/status/{messageId} — delivery status
• GET /api/sms/balance — account balance

Authentication uses Basic Auth or token in the header (check your contract). Request body format is JSON:

{
  "phone": "375291234567",
  "text": "Your order #1234 confirmed",
  "sender": "MyShop"
}

Sender ID is an alphabetic name registered with A1 upon signing. Without registration, SMS come from a numeric number.

Integration with On-Premise Bitrix

In on-premise Bitrix, SMS can be sent via the messageservice module or directly via event handler. The main scenario is sending SMS on order events.

Option 1: OnSaleStatusOrder event handler

EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleStatusOrder',
    ['A1SmsHandler', 'onStatusChange']
);

class A1SmsHandler
{
    public static function onStatusChange($orderId, $status)
    {
        if ($status !== 'F') return; // F = completed

        $order = \Bitrix\Sale\Order::load($orderId);
        $phone = $order->getPropertyCollection()
            ->getPhone()->getValue();

        self::sendSms($phone, "Order #{$orderId} completed");
    }

    private static function sendSms(string $phone, string $text): void
    {
        $ch = curl_init('https://a1sms.by/api/sms/send');
        curl_setopt_array($ch, [
            CURLOPT_POST => true,
            CURLOPT_HTTPHEADER => [
                'Content-Type: application/json',
                'Authorization: Bearer ' . A1_SMS_TOKEN,
            ],
            CURLOPT_POSTFIELDS => json_encode([
                'phone' => $phone,
                'text' => $text,
                'sender' => 'MyShop',
            ]),
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_TIMEOUT => 10,
        ]);
        $response = curl_exec($ch);
        curl_close($ch);

        // Log response
    }
}

Option 2: sms.manager module. If the project uses the sms.manager module (from Marketplace or custom), we write a provider adapter. The provider is registered in settings, making A1 SMS available as a sending channel.

Integration with Bitrix24

In Bitrix24, connect an SMS provider via REST API:

1. Register the provider: messageservice.sender.add with CODE=a1sms, TYPE=SMS, HANDLER=https://your-site.by/a1sms-handler.php.
2. The handler (a1sms-handler.php) receives the request from B24 (number, text), forwards to A1 API, returns status.
3. For statuses, A1 sends DLR to a specified URL. The handler calls messageservice.sender.update to update status in B24.

After registration, A1 SMS appears in contact cards, CRM robots, and marketing campaigns.

Encoding and Transliteration

Cyrillic SMS: 70 characters per message (UCS-2). Latin: 160 characters (GSM 7-bit). To save budget, send long notifications in Latin or keep them within 70 characters. The A1 API accepts UTF-8; conversion occurs on the gateway side. However, special characters like «» and em dashes may convert incorrectly. Replace them with ASCII equivalents before sending.

Error Handling

The A1 SMS API returns error codes:

For retry in on-premise Bitrix, use a CAgent that selects unsent SMS from an HL-block SmsQueue and retries. For B24, retry at the handler level.

What's Included in the Work

• A1 SMS account registration and API access
• Developing a handler to send SMS via A1 API
• Connecting to messageservice module (B24) or event handlers (on-premise)
• Setting up a callback for delivery statuses
• Error handling and retry logic
• Logging all sent SMS (HL-block or table)
• Documentation for installation and maintenance
• Handover of access and staff training
• Post-launch technical support (optional)

For a consultation on your project, contact our team. We will assess the scope and timelines.

Timeframes

Main organizational step: contract with A1 and Sender ID registration. The technical part takes a week. Coordination with the operator takes 3 to 10 business days. Start the contract in parallel with development.

Order integration — get a consultation on your project.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.