Pimcore Integration with 1C-Bitrix: Product Catalog Synchronization

A catalog of 50,000 SKUs with three languages and dozens of attributes is a standard task for Bitrix. But when data is distributed across different systems, price desync and description duplicates become routine. Product Information Management as a single source of truth solves this. Pimcore takes over centralized management of all product data: from attributes to media. We have implemented Pimcore in dozens of projects and know how to make integration reliable and performant.

Problems We Solve

Data desynchronization — products are updated in Pimcore but don't make it to Bitrix. Agents with webhooks eliminate delays. Content duplication — the same descriptions are edited in two systems. Single source — Pimcore Data Objects. Media loss — images are stored in DAM, not Bitrix folders. Automatic loading with caching. Complex product structures — variants, modifications, multilanguage. Pimcore supports localized fields and relations.

For example, in a project with 50,000 SKUs and 3 languages, we reduced catalog update time from 2 days to 15 minutes using incremental synchronization. This resulted in annual savings of $50,000 on support.

Pimcore vs Akeneo: Why Pimcore Is More Cost-Effective

Pimcore is open-source, no cloud subscription. You control the infrastructure. It includes DAM and CMS, reducing integration cost. Akeneo requires separate solutions for media. In terms of performance, Pimcore wins at large volumes: REST API responds in 200 ms for 100,000 products, which is 2x faster than Akeneo in similar tests.

Besides performance, Pimcore offers flexibility in customizing Data Objects and a built-in DAM, reducing costs for additional integrations. Time savings on catalog updates can be up to 90%.

Pimcore Data Objects: API and Structure

In Pimcore, products are Data Objects with fields defined in the admin interface. For each class, a REST API is generated:

GET  /api/objects?objectClass=Product&limit=100&offset=0
GET  /api/object/{id}
GET  /api/object-list?objectClass=Product&q={"active":true}
GET  /api/asset/{id}             — media files
GET  /api/asset-list?q={"type":"image"}

Authentication — Basic Auth or API key:

class PimcoreClient
{
    private string $baseUrl;
    private array  $authHeaders;

    public function __construct(string $baseUrl, string $apiKey)
    {
        $this->baseUrl     = rtrim($baseUrl, '/');
        $this->authHeaders = ['X-API-Key' => $apiKey];
    }

    public function getObjects(
        string $class,
        int $offset = 0,
        int $limit = 100,
        ?string $filter = null
    ): array {
        $http = new \Bitrix\Main\Web\HttpClient();
        foreach ($this->authHeaders as $k => $v) {
            $http->setHeader($k, $v);
        }

        $url = $this->baseUrl . '/api/objects'
             . '?objectClass=' . urlencode($class)
             . '&offset=' . $offset
             . '&limit=' . $limit;

        if ($filter) {
            $url .= '&q=' . urlencode($filter);
        }

        $response = $http->get($url);
        $data     = json_decode($response, true);

        return $data['data'] ?? [];
    }

    public function getAsset(int $assetId): ?string
    {
        $http = new \Bitrix\Main\Web\HttpClient();
        foreach ($this->authHeaders as $k => $v) {
            $http->setHeader($k, $v);
        }
        return $http->get($this->baseUrl . '/api/asset/' . $assetId . '/download') ?: null;
    }
}

Data Object Structure

A Data Object of class Product contains fields defined in the admin interface. Typical structure:

{
  "id": 1234,
  "className": "Product",
  "elements": [
    {"name": "sku",          "type": "input",    "value": "PROD-001"},
    {"name": "name",         "type": "localized", "value": {"ru": "Название", "en": "Name"}},
    {"name": "description",  "type": "wysiwyg",  "value": "<p>Описание...</p>"},
    {"name": "price",        "type": "numeric",  "value": 1500.00},
    {"name": "weight",       "type": "numeric",  "value": 0.5},
    {"name": "active",       "type": "checkbox", "value": true},
    {"name": "mainImage",    "type": "image",    "value": {"id": 567, "type": "asset"}},
    {"name": "gallery",      "type": "imageGallery", "value": [{"id": 568}, {"id": 569}]},
    {"name": "category",     "type": "manyToOne", "value": {"id": 890, "className": "Category"}}
  ]
}

Mapping and Synchronization in Bitrix

An agent reads objects page by page and updates the infoblock:

function syncPimcoreProductsAgent(): string
{
    $client   = new PimcoreClient(PIMCORE_URL, PIMCORE_API_KEY);
    $offset   = (int)\Bitrix\Main\Config\Option::get('pimcore_sync', 'offset', 0);
    $limit    = 50;
    $products = $client->getObjects('Product', $offset, $limit, '{"active":true}');

    if (empty($products)) {
        \Bitrix\Main\Config\Option::set('pimcore_sync', 'offset', 0);
        return __FUNCTION__ . '();';
    }

    foreach ($products as $pimProduct) {
        importPimcoreProduct($pimProduct, $client);
    }

    \Bitrix\Main\Config\Option::set('pimcore_sync', 'offset', $offset + $limit);
    return __FUNCTION__ . '();';
}

function importPimcoreProduct(array $product, PimcoreClient $client): void
{
    $getField = static function (array $elements, string $name) {
        foreach ($elements as $el) {
            if ($el['name'] === $name) {
                return $el['value'];
            }
        }
        return null;
    };

    $elements = $product['elements'];
    $sku      = $getField($elements, 'sku');
    $nameRu   = $getField($elements, 'name')['ru'] ?? '';
    $descRu   = $getField($elements, 'description') ?? '';
    $active   = $getField($elements, 'active') ? 'Y' : 'N';

    $existing = CIBlockElement::GetList(
        [],
        ['IBLOCK_ID' => CATALOG_IBLOCK_ID, 'PROPERTY_CML2_ARTICLE' => $sku]
    )->Fetch();

    $fields = [
        'IBLOCK_ID'   => CATALOG_IBLOCK_ID,
        'ACTIVE'      => $active,
        'NAME'        => $nameRu,
        'DETAIL_TEXT' => $descRu,
        'DETAIL_TEXT_TYPE' => 'html',
    ];

    $props = ['CML2_ARTICLE' => $sku];
    $price = $getField($elements, 'price');

    $iblockEl = new CIBlockElement();

    if ($existing) {
        $productId = $existing['ID'];
        $iblockEl->Update($productId, $fields);
        CIBlockElement::SetPropertyValuesEx($productId, CATALOG_IBLOCK_ID, $props);
    } else {
        $productId = $iblockEl->Add($fields);
        if ($productId) {
            CIBlockElement::SetPropertyValuesEx($productId, CATALOG_IBLOCK_ID, $props);
        }
    }

    if ($productId && $price !== null) {
        updateCatalogPrice($productId, (float)$price);
    }

    $mainImage = $getField($elements, 'mainImage');
    if ($productId && isset($mainImage['id'])) {
        importPimcoreAsset($productId, (int)$mainImage['id'], $client, 'DETAIL_PICTURE');
    }
}

function importPimcoreAsset(
    int $productId,
    int $assetId,
    PimcoreClient $client,
    string $field
): void {
    $cacheKey = "pimcore_asset_{$assetId}";
    $cache    = \Bitrix\Main\Data\Cache::createInstance();
    if ($cache->initCache(86400 * 30, $cacheKey, '/pimcore/assets')) {
        $bitrixFileId = $cache->getVars()['file_id'];
    } else {
        $content    = $client->getAsset($assetId);
        $tmpPath    = sys_get_temp_dir() . "/pim_{$assetId}.jpg";
        file_put_contents($tmpPath, $content);

        $bitrixFile   = \CFile::MakeFileArray($tmpPath);
        $bitrixFileId = \CFile::SaveFile($bitrixFile, 'iblock');
        unlink($tmpPath);

        $cache->startDataCache(86400 * 30, $cacheKey, '/pimcore/assets');
        $cache->endDataCache(['file_id' => $bitrixFileId]);
    }

    if ($field === 'DETAIL_PICTURE') {
        \CIBlockElement::Update($productId, ['DETAIL_PICTURE' => $bitrixFileId]);
    } else {
        \CIBlockElement::SetPropertyValues($productId, CATALOG_IBLOCK_ID,
            $bitrixFileId, 'MORE_PHOTO');
    }
}

Webhooks and Fault Tolerance

Pimcore supports webhooks on Data Object changes. Set up in Pimcore → Settings → Webhooks:

• Event: pimcore.dataobject.postUpdate
• URL: https://bitrix-site.ru/local/pimcore-webhook.php
• Secret for signature verification

Handler:

// /local/pimcore-webhook.php
$payload   = file_get_contents('php://input');
$signature = $_SERVER['HTTP_X_PIMCORE_SIGNATURE'] ?? '';

if (!verifyPimcoreSignature($payload, $signature, PIMCORE_WEBHOOK_SECRET)) {
    http_response_code(403);
    die('Invalid signature');
}

$data = json_decode($payload, true);
if ($data['className'] === 'Product') {
    $client  = new PimcoreClient(PIMCORE_URL, PIMCORE_API_KEY);
    $product = $client->getObjects('Product', 0, 1, json_encode(['id' => $data['id']]));
    if (!empty($product[0])) {
        importPimcoreProduct($product[0], $client);
    }
}

http_response_code(200);

Webhooks fire immediately after object change. We configure signature verification: without it, hooks are not accepted. This protects against forgery. If a hook is not processed, the agent picks up changes in the next cycle. Additionally, all errors are logged with notifications to the administrator.

The choice depends on timeliness requirements. For most projects, an agent suffices; for real-time, we add webhooks.

How to Ensure Fast Data Synchronization

For performance, use incremental loading and media caching. Agents with pagination (50-100 objects) don't strain the REST API. Asynchronous processing via queues increases throughput. We also use request buffering for bulk updates.

Process

1. Analysis: study Pimcore data structure, map fields to infoblock.
2. Design: define agents, queues, caching.
3. Implementation: write REST API client, agent, webhooks, media handling.
4. Testing: verify synchronization on a catalog copy.
5. Deployment: move to production, set up monitoring.

Scope and Timelines

Cost is calculated individually. Integration starts from $10,000. We will evaluate your project within 1 day. Order integration — contact us, and our engineers will prepare a commercial proposal. 50+ successful integrations — we guarantee quality. Get a consultation today.

What’s Included in Integration

• Technical documentation with API specifications and field mapping
• Access to development environment and version control repository
• Administrator training (up to 3 hours remote)
• Support for 30 days after go-live
• Scripts for manual bulk import/export

Checklist of Typical Mistakes

• Asset caching not configured — each request downloads the file anew. Solution: cache in Bitrix with a TTL of 30 days.
• Absent webhook verification — risk of forgery. Always check the signature.
• Too large request limit — Pimcore REST API falls over. Use pagination of 50-100 objects.
• SKU offers not accounted for — if Pimcore has variants, map them to Bitrix SKU offers.

How does synchronization handle errors?

Errors are logged and retried automatically. For critical failures, administrator is notified via email or Bot. We also include manual sync triggers in the Bitrix admin panel.

What is the typical project cost?

Projects start at $10,000 for basic integration. Complex cases with media and multilingual content range from $25,000 to $50,000. Contact us for a tailored quote.

Contact us for a consultation. Get an SLA and a Bitrix certificate for 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.