Sales Personalization: Retail Rocket for 1C-Bitrix

We configure comprehensive integration between 1C-Bitrix and the Retail Rocket personalization platform for online stores that prioritize customer experience. Retail Rocket is a leading e-commerce personalization platform: product recommendations, personalized email campaigns, behavioral analytics boosting conversion by 20–40%. The technical integration consists of two parts: transmitting user behavior data via a JavaScript tracker and synchronizing the product catalog through an XML feed with stock and price updates.

Our team has over 7 years of Bitrix experience and has implemented more than 15 integrations with Retail Rocket for stores of various profiles—from niche boutiques to large marketplaces with millions of SKUs. We guarantee stable operation under high load, minimal data synchronization delay (less than 15 minutes), and correct functioning of recommendation blocks on all site pages. The result is an increase in average order value and repeat purchases.

How is the XML Product Feed Generated?

Retail Rocket accepts a product feed in Yandex.Market YML format or its own XML format. The easiest approach is to use the existing YML feed from Bitrix—if you already have one, it will work. A customized feed with additional fields (SKU, brand, color) enables finer segmentation. Here is a minimal PHP example:

// Minimal structure for Retail Rocket
function generateRetailRocketFeed(): string
{
    $xml = '<?xml version="1.0" encoding="UTF-8"?><yml_catalog>';
    $xml .= '<shop><name>' . htmlspecialchars(SITE_NAME) . '</name>';
    $xml .= '<url>https://' . SITE_SERVER_NAME . '</url>';
    $xml .= '<currencies><currency id="RUB" rate="1"/></currencies>';
    $xml .= '<categories>';

    $sections = CIBlockSection::GetList(
        ['LEFT_MARGIN' => 'ASC'],
        ['IBLOCK_ID' => CATALOG_IBLOCK_ID, 'ACTIVE' => 'Y'],
        false,
        ['ID', 'NAME', 'IBLOCK_SECTION_ID']
    );
    while ($section = $sections->GetNext()) {
        $parentAttr = $section['IBLOCK_SECTION_ID']
            ? ' parentId="' . $section['IBLOCK_SECTION_ID'] . '"'
            : '';
        $xml .= '<category id="' . $section['ID'] . '"' . $parentAttr . '>'
              . htmlspecialchars($section['NAME']) . '</category>';
    }
    $xml .= '</categories>';
    $xml .= '<offers>';

    $res = CIBlockElement::GetList(
        [],
        ['IBLOCK_ID' => CATALOG_IBLOCK_ID, 'ACTIVE' => 'Y'],
        false,
        false,
        ['ID', 'NAME', 'DETAIL_PAGE_URL', 'PREVIEW_PICTURE', 'DETAIL_PICTURE',
         'PREVIEW_TEXT', 'IBLOCK_SECTION_ID']
    );

    while ($el = $res->GetNextElement()) {
        $fields = $el->GetFields();
        $props  = $el->GetProperties();

        $price = CCatalogProduct::GetOptimalPrice($fields['ID']);
        $priceVal = $price['PRICE']['PRICE'] ?? 0;

        $imgId  = $fields['DETAIL_PICTURE'] ?: $fields['PREVIEW_PICTURE'];
        $imgUrl = '';
        if ($imgId) {
            $imgUrl = 'https://' . SITE_SERVER_NAME . CFile::GetPath($imgId);
        }

        $url = 'https://' . SITE_SERVER_NAME . $fields['DETAIL_PAGE_URL'];

        $xml .= '<offer id="' . $fields['ID'] . '" available="true">';
        $xml .= '<url>' . htmlspecialchars($url) . '</url>';
        $xml .= '<price>' . number_format($priceVal, 2, '.', '') . '</price>';
        $xml .= '<currencyId>RUB</currencyId>';
        $xml .= '<categoryId>' . $fields['IBLOCK_SECTION_ID'] . '</categoryId>';
        if ($imgUrl) {
            $xml .= '<picture>' . htmlspecialchars($imgUrl) . '</picture>';
        }
        $xml .= '<name>' . htmlspecialchars($fields['NAME']) . '</name>';
        if ($fields['PREVIEW_TEXT']) {
            $xml .= '<description><![CDATA['
                  . strip_tags($fields['PREVIEW_TEXT']) . ']]></description>';
        }
        $sku = $props['CML2_ARTICLE']['VALUE'] ?? $fields['ID'];
        $xml .= '<param name="sku">' . htmlspecialchars($sku) . '</param>';
        $xml .= '</offer>';
    }

    $xml .= '</offers></shop></yml_catalog>';
    return $xml;
}

The feed is cached for 2–4 hours and updated on product change invalidation. The feed URL is provided in the Retail Rocket dashboard.

How is the JavaScript Tracker Installed?

Retail Rocket provides a JS library (rrpushdown) that is included on all pages. In the Bitrix template—in footer.php or via addExternalJs:

// Base Retail Rocket code (inserted once)
var retailrocket = window.retailrocket || [];
(function(d, w) {
    var rr = d.createElement('script');
    rr.type = 'text/javascript';
    rr.src = '//cdn.retailrocket.net/content/javascript/tracking.js';
    d.head.appendChild(rr);
})(document, window);

Product card view event. In the catalog.element template:

// template.php
$productId = $arResult['ID'];
?>
<script>
retailrocket.push(['setAccountId', '<?= RETAIL_ROCKET_ACCOUNT_ID ?>']);
retailrocket.push(['track', 'view', { productId: '<?= $productId ?>' }]);
</script>

Add‑to‑cart event. In the AJAX add handler:

// On successful add to basket
retailrocket.push(['track', 'addToBasket', {
    productId: String(productId),
    quantity: qty
}]);

Checkout event. On the order confirmation page or via a handler for OnSaleOrderSaved:

// In the order confirmation page template
$orderId    = $arOrder['ID'];
$orderPrice = $arOrder['PRICE'];
$items      = [];

foreach ($arOrder['BASKET'] as $item) {
    $items[] = [
        'id'       => $item['PRODUCT_ID'],
        'qnt'      => $item['QUANTITY'],
        'price'    => $item['PRICE'],
    ];
}
?>
<script>
retailrocket.push(['track', 'transaction', {
    transaction: '<?= $orderId ?>',
    revenue: <?= $orderPrice ?>,
    lineItems: <?= json_encode($items) ?>
}]);
</script>

Search event:

retailrocket.push(['track', 'search', { searchPhrase: searchQuery }]);

What Benefits Does Retail Rocket Provide?

Stores using Retail Rocket see conversion rates 2-3x higher than those with basic recommendations. In a typical e‑commerce site, personalization lifts conversions by 15–25%, and the average order value rises 10–15%. With these metrics, a store with $500K annual turnover can generate over $50K in additional revenue each year.

Recommendation Blocks

After configuration in the Retail Rocket dashboard, insert the blocks into templates:

<!-- On the homepage: "Recommended" -->
<div data-retailrocket-markup-block="5f4a3b2c1d0e9f8e7d6c5b4a"
     data-algorithm="popular">
</div>

<!-- In product card: "Frequently bought together" -->
<div data-retailrocket-markup-block="5f4a3b2c1d0e9f8e7d6c5b4b"
     data-algorithm="related"
     data-item-id="<?= $arResult['ID'] ?>">
</div>

<!-- In cart: "You might also like" -->
<div data-retailrocket-markup-block="5f4a3b2c1d0e9f8e7d6c5b4c"
     data-algorithm="basket">
</div>

Widgets render on the Retail Rocket side—they load product IDs and request display data from your catalog via JS.

User Authorization and Email Binding

To link behavior to a user profile, we pass the email on login:

// In the successful authorization handler
if ($USER->IsAuthorized()) {
    $email = $USER->GetEmail();
?>
<script>
retailrocket.push(['setEmail', '<?= htmlspecialchars($email) ?>',
    function() { console.log('RR email set'); }
]);
</script>
<?php } ?>

Implementation Timeline

What's Included in the Integration

• Documentation: detailed technical guide and API reference for your team.
• Access: credentials to Retail Rocket dashboard and feed URLs.
• Training: up to 2 hours of online training for your developers and marketers.
• Support: 12‑month post‑launch support with free bug fixes and minor updates.
• Deliverables: complete source code for feed generation, tracker integration, and recommendation widgets.

Our Process

1. Data collection: gather existing feed configurations, site structure, and business goals.
2. Audit & analysis: review current Bitrix setup, identify integration points and potential conflicts.
3. Design: define feed schema, event mapping, and widget placement.
4. Estimation: provide a precise scope and timeline after analysis—costs determined per project.
5. Development: implement feed generation, tracker installation, and widget integration.
6. Testing: validate on a staging environment with real product data and traffic simulations.
7. Launch: deploy to production and monitor initial performance.

We provide full documentation and training for your team, ensuring you can maintain the system independently. Every project includes a 12-month support period—any issues found within that year are fixed free of charge.

Typical Integration Challenges

• Incomplete product data: missing SKU, price, or category fields in the feed lead to incorrect recommendations. We enforce data completeness with validation rules.
• JavaScript conflicts: custom scripts interfering with the Retail Rocket tracker. We isolate the tracker code and test across all page types.
• Cache issues: outdated feed or cached pages showing stale recommendations. We configure proper cache invalidation on product updates.

Retail Rocket documentation recommends including all product attributes for optimal recommendation accuracy.

Want to personalize your store with Retail Rocket? Leave a request for a free consultation—we will analyze your system and offer the best solution. Pricing is determined after a detailed assessment of your requirements.

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.