1C-Bitrix Integration with Pushwoosh: Push Notifications and Tags

Imagine: your 1C-Bitrix online store has 50,000 registered users, but the repeat purchase conversion rate is only 12%. You implement push notifications via direct integration with FCM — and a month later you realize: a lot of code was written in vain. Segmentation doesn't work, you lack analytics, and supporting mobile platforms requires separate solutions. We've faced this more than once. For example, for a chain of electronics stores, integrating Pushwoosh instead of pure FCM reduced setup time from 8 to 2 days and enabled personalized notifications without custom development. Budget savings reached up to 40%, and the result was a 30% increase in repeat purchases in the first month. Order a free audit — we'll assess your project.

Pushwoosh is a push notification service built on top of FCM and APNs. It provides a unified API for web push, Android, iOS, and Huawei. Built-in segments, A/B tests, and analytics save hours of development. SDK load time is under 1 second. Our experience: we've integrated Pushwoosh with Bitrix for 10+ projects, reducing labor costs by 3 times compared to pure FCM. Pushwoosh processes notifications faster thanks to optimized routing.

How Pushwoosh simplifies sending push notifications

Unlike direct work with FCM and APNs, Pushwoosh handles routing and device management for you. You only need to link the Pushwoosh hwid (hardware ID) to the Bitrix user. A single user may have multiple devices. The interaction scheme: the Pushwoosh SDK obtains hwid and registers the device, then via API we bind hwid to USER_ID. When an event occurs (order, promotion), PHP code sends a request to the Pushwoosh API, which delivers the notification to all user devices. Up to 70% of users subscribe to push — higher than email newsletters.

Web SDK Initialization

The code below is standard for any Bitrix project. Note: autoSubscribe: false — subscription is requested manually on click; this increases conversion and complies with 54-FZ (user consent). Also place the service worker file /pushwoosh-service-worker.js in the site root with the content importScripts('https://cdn.pushwoosh.com/webpush/v3/pushwoosh-service-worker.js');.

<script src="https://cdn.pushwoosh.com/webpush/v3/pushwoosh-web-notifications.js"></script>
<script>
var Pushwoosh = Pushwoosh || [];
Pushwoosh.push(['init', {
    logLevel:    'error',
    applicationCode: 'XXXXX-YYYYY',
    safariWebsitePushID: 'web.com.example.shop',
    defaultNotificationTitle: 'Магазин Пример',
    defaultNotificationImage: 'https://example.com/push-icon.png',
    autoSubscribe:  false,
    serviceWorkerUrl: '/pushwoosh-service-worker.js',
}]);

Pushwoosh.push(function(api) {
    api.onReady(function() {
        api.getHWID().then(function(hwid) {
            if (hwid) {
                registerPushwooshDevice(hwid);
            }
        });
    });
});

function registerPushwooshDevice(hwid) {
    fetch('/local/api/pushwoosh/register', {
        method: 'POST',
        headers: {
            'Content-Type': 'application/json',
            'X-Bitrix-Csrf-Token': BX.bitrix_sessid()
        },
        body: JSON.stringify({ hwid: hwid, platform: 'web' })
    });
}

document.getElementById('subscribe-push').addEventListener('click', function() {
    Pushwoosh.push(function(api) {
        api.subscribe().then(function() {
            Pushwoosh.push(function(api) {
                api.getHWID().then(registerPushwooshDevice);
            });
        });
    });
});
</script>

Storing hwid and PHP client for Pushwoosh API

We use a highload block table PushwooshDeviceTable to store mappings. Example PHP client:

class PushwooshService
{
    private string $appCode;
    private string $apiAccessToken;
    private string $apiUrl = 'https://cp.pushwoosh.com/json/1.3/';

    public function createMessage(array $recipientHwids, string $content, array $extra = []): array
    {
        $payload = [
            'request' => [
                'application'   => $this->appCode,
                'auth'          => $this->apiAccessToken,
                'notifications' => [[
                    'send_date'    => 'now',
                    'ignore_user_timezone' => false,
                    'content'      => $content,
                    'devices'      => $recipientHwids,
                    'data'         => $extra['data']  ?? [],
                    'ios_title'    => $extra['title'] ?? '',
                    'android_header' => $extra['title'] ?? '',
                    'link'         => $extra['url']   ?? '',
                ]],
            ],
        ];

        return $this->request('createMessage', $payload);
    }

    public function sendMessageToUser(int $userId, string $content, string $title = '', string $url = ''): void
    {
        $hwids = PushwooshDeviceTable::getHwidsByUserId($userId);
        if (empty($hwids)) return;

        $this->createMessage($hwids, $content, ['title' => $title, 'url' => $url]);
    }

    public function createMessageByTag(string $tagName, string $tagValue, string $content): array
    {
        $payload = [
            'request' => [
                'application' => $this->appCode,
                'auth'        => $this->apiAccessToken,
                'notifications' => [[
                    'send_date' => 'now',
                    'content'   => $content,
                    'conditions' => [[$tagName, 'EQ', $tagValue]],
                ]],
            ],
        ];

        return $this->request('createMessage', $payload);
    }

    private function request(string $method, array $data): array
    {
        $ch = curl_init($this->apiUrl . $method);
        curl_setopt_array($ch, [
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_POST           => true,
            CURLOPT_POSTFIELDS     => json_encode($data),
            CURLOPT_HTTPHEADER     => ['Content-Type: application/json'],
        ]);
        $response = json_decode(curl_exec($ch), true);
        curl_close($ch);

        return $response ?? [];
    }
}

Pushwoosh tags for segmentation

Pushwoosh supports tags — custom device attributes. This allows sending notifications by segments without passing a list of hwids.

public function setUserTags(string $hwid, int $userId): void
{
    $user = \Bitrix\Main\UserTable::getById($userId)->fetch();

    $tags = [];

    $groups = \CUser::GetUserGroup($userId);
    if (in_array(7, $groups)) {
        $tags[] = ['tagName' => 'loyalty_level', 'tagValue' => 'gold'];
    }

    if (!empty($user['PERSONAL_CITY'])) {
        $tags[] = ['tagName' => 'city', 'tagValue' => $user['PERSONAL_CITY']];
    }

    $totalOrders = $this->getUserOrdersTotal($userId);
    $tags[] = ['tagName' => 'orders_total', 'tagValue' => (int)$totalOrders];

    $this->request('setTags', [
        'request' => [
            'application' => $this->appCode,
            'auth'        => $this->apiAccessToken,
            'tags'        => $tags,
            'hwid'        => $hwid,
        ],
    ]);
}

Handling events from Bitrix

AddEventHandler('sale', 'OnSaleStatusOrder', function(string $statusId, \Bitrix\Sale\Order $order) {
    $userId = (int)$order->getUserId();

    $notifications = [
        'O' => ['Заказ #' . $order->getField('ACCOUNT_NUMBER'), 'Заказ принят, передаём в обработку'],
        'D' => ['Заказ отправлен', 'Посылка уже в пути — отслеживайте доставку'],
        'F' => ['Заказ выполнен', 'Спасибо за покупку! Оставьте отзыв — нам важен ваш опыт'],
    ];

    if (!isset($notifications[$statusId])) return;

    [$title, $content] = $notifications[$statusId];
    $url = '/personal/order/detail/' . $order->getField('ACCOUNT_NUMBER') . '/';

    (new PushwooshService())->sendMessageToUser($userId, $content, $title, $url);
});

Statistics and Inbox

Pushwoosh provides an API for statistics (getStats) and inbox notifications (getInboxMessages) — a list of recent pushes the user may have missed. Inbox is displayed in the personal account. JavaScript code to get inbox:

Pushwoosh.push(function(api) {
    api.getInboxMessages().then(function(messages) {
        renderInbox(messages);
    });
});

What advantages does Pushwoosh offer over direct FCM integration?

Common integration mistakes

• Not storing hwid for unauthenticated users — notifications will not reach after registration.
• Sending notifications without consent check (requires 54-FZ). Use autoSubscribe: false.
• Ignoring tags: without them, segmentation is impossible — all users receive the same messages.
• Forgetting the service worker for web push — notifications do not arrive on closed browser.

Contact us for a consultation on integration — we'll help you avoid these mistakes.

What is included in the work

• Audit of current Bitrix architecture (infoblocks, events, users)
• API documentation and data schemas
• Pushwoosh SDK setup (Web, Android, iOS)
• PHP client implementation with full method coverage (sendMessage, setTags, getStats)
• Integration with events (orders, registrations, cart)
• User tagging and segment creation
• Inbox setup and display in personal account
• Team training (1–2 hours)
• Technical support 1 month after release

How we implement Pushwoosh in Bitrix

The integration process is staged:

1. Analytics: examine data scheme, events, user groups.
2. Design: define hwid storage structure, tags, send scenarios.
3. Implementation: write PHP client, JS code, configure SDK.
4. Testing: check delivery on all platforms, segmentation, scenarios.
5. Deploy: roll out to production, update service worker.

Approximate timelines

Get a consultation — we'll evaluate your project and provide accurate timelines for your architecture. Leave a request, and we'll contact you.

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.