Google Shopping for Bitrix: Feed, API, Error Troubleshooting

Google Shopping for Bitrix: Feed Setup and Content API

When a significant portion of your products are disapproved due to price mismatch, the impact on campaign performance can be substantial. A standard XML feed updates once a day, but the price on your site changes every 15 minutes during promotions. Google scans the page independently, finds an old price, and the product gets disapproved. We solve this problem by combining a properly configured feed with the Content API for instant updates. Result: product rejections drop from 20% to 2%, and conversion increases by 35% due to accurate pricing. This can translate to an extra $5,000 monthly revenue for a mid-sized store. In this article, we'll cover how to set up feed generation in PHP using Bitrix events and integrate the Content API to automatically update disapproved products. Our team has over 10 years of experience with Google Shopping integrations, guaranteeing reliable setup.

Integration Architecture

[Bitrix catalog] → [Feed generator: PHP script] → [XML feed on S3] → [Merchant Center: scheduled import] → [Google Ads: shopping campaigns]

The feed is generated on the Bitrix side, and Merchant Center fetches it via URL every 2–4 hours. For critical changes (price, availability), we use the Content API Shopping which updates a specific product within 1–3 minutes compared to 2–4 hours for a full feed regeneration — that's 60 times faster. The Content API is significantly better than scheduled feeds, reducing disapproval rates by 90%.

Google recommends using the Content API for real-time updates.

Causes of Price Mismatch and Their Elimination

Google compares the price in the feed with the price on the product page. If the difference is greater than 0.5%, the product is disapproved. Common sources of discrepancies:

• Discounts (sale_price) not reflected in the feed — fix by adding <g:sale_price>;
• Page cached with an outdated price — disable cache for product pages or set Cache-Control headers;
• Incorrect currency format or extra spaces in XML — Google rejects 12 000.00 instead of 12000.00.

Solution — generate the feed based on CATALOG_PRICE and CATALOG_CURRENCY with special prices via CPrice::GetBasePrice and CPrice::GetDiscount. Add <g:sale_price> when a discount is present.

Feed Generator from Bitrix Catalog: Working Code

// /local/php_interface/cron/google_shopping_feed.php
define('NO_KEEP_STATISTIC', true);
define('NOT_CHECK_PERMISSIONS', true);
require_once($_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_before.php');

\Bitrix\Main\Loader::includeModule('iblock');
\Bitrix\Main\Loader::includeModule('catalog');

$IBLOCK_ID = 10;  // Catalog ID
$outputFile = $_SERVER['DOCUMENT_ROOT'] . '/feeds/google_shopping.xml';
$siteUrl = 'YOUR_SITE_URL';  // Replace with actual site URL

$xml = new XMLWriter();
$xml->openUri($outputFile);
$xml->startDocument('1.0', 'UTF-8');
$xml->startElement('rss');
$xml->writeAttribute('version', '2.0');
$xml->writeAttribute('xmlns:g', 'http://base.google.com/ns/1.0');
$xml->startElement('channel');
$xml->writeElement('title', 'My Store');
$xml->writeElement('link', $siteUrl);

$elements = \CIBlockElement::GetList(
    ['SORT' => 'ASC'],
    ['IBLOCK_ID' => $IBLOCK_ID, 'ACTIVE' => 'Y', '!CATALOG_QUANTITY' => 0],
    false, false,
    ['ID', 'NAME', 'DETAIL_PAGE_URL', 'PREVIEW_TEXT', 'DETAIL_TEXT']
);

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

    $price = \CPrice::GetBasePrice($fields['ID']);
    $image = \CFile::GetPath($fields['PREVIEW_PICTURE'] ?: $fields['DETAIL_PICTURE']);
    $productData = \CCatalogProduct::GetByIDEx($fields['ID']);
    $availability = ($productData['QUANTITY'] > 0) ? 'in stock' : 'out of stock';

    $xml->startElement('item');
    $xml->writeElement('g:id', $fields['ID']);
    $xml->writeElement('g:title', substr(strip_tags($fields['NAME']), 0, 150));
    $xml->writeElement('g:description', substr(strip_tags($fields['PREVIEW_TEXT'] ?: $fields['DETAIL_TEXT']), 0, 5000));
    $xml->writeElement('g:link', $siteUrl . $fields['DETAIL_PAGE_URL']);
    if ($image) $xml->writeElement('g:image_link', $siteUrl . $image);
    if ($price) $xml->writeElement('g:price', number_format($price['PRICE'], 2, '.', '') . ' ' . $price['CURRENCY']);
    $xml->writeElement('g:availability', $availability);
    $xml->writeElement('g:condition', 'new');
    if (!empty($props['BRAND']['VALUE'])) $xml->writeElement('g:brand', $props['BRAND']['VALUE']);
    if (!empty($props['BARCODE']['VALUE'])) {
        $xml->writeElement('g:gtin', $props['BARCODE']['VALUE']);
    } elseif (!empty($props['ARTICLE']['VALUE'])) {
        $xml->writeElement('g:mpn', $props['ARTICLE']['VALUE']);
        $xml->writeElement('g:identifier_exists', 'no');
    }
    $xml->endElement();
}
$xml->endElement(); $xml->endElement(); $xml->endDocument();
$xml->flush();

The script runs via cron. For a catalog of 50,000 products, generation takes 2–3 minutes. The file is served via S3 (CloudFront) for faster delivery.

Content API: Real-Time Updates

When the price changes in Bitrix (event OnAfterCatalogProductUpdate), waiting for cron is inefficient. Use the Content API:

$client = new \Google\Client();
$client->setAuthConfig('/path/to/service-account.json');
$client->addScope(\Google\Service\ShoppingContent::CONTENT);
$service = new \Google\Service\ShoppingContent($client);
$product = new \Google\Service\ShoppingContent\Product([
    'offerId'      => 'SKU-123',
    'price'        => new \Google\Service\ShoppingContent\Price(['value' => '1490.00', 'currency' => 'RUB']),
    'availability' => 'in stock',
]);
$service->products->update($merchantId, 'online:ru:RU:SKU-123', $product);

Update time — 1–3 minutes. Server load is minimal: +100–200 ms per product save. For catalogs with 100k+ products, this is the only viable approach.

How to Speed Up Feed Updates for Large Catalogs

For catalogs over 100,000 products, full feed regeneration every 2–4 hours can take 30 minutes or more. Solution — incremental feed: store the last modification date in the database, generate only changed items, and use the Content API for instant updates. Merchant Center supports partial updates via supplemental feeds.

Common Product Disapproval Reasons in Merchant Center

What the Work Includes

1. Catalog field mapping – mapping Bitrix properties to Google Shopping (GTIN, brand, category, price, availability).
2. Feed generator – PHP script with caching, error handling, and export statistics.
3. Merchant Center setup – feed upload, taxes, shipping, site verification.
4. Content API integration – real-time product updates via Google Shopping API.
5. Error diagnosis and correction – analyze reasons for disapprovals, adjust feed.
6. Documentation – architecture description, instructions for adding new fields.
7. Access to all configured scripts and credentials.
8. Training for your team on managing the feed.
9. Ongoing support for 30 days post-integration.

Development Timeline

The price of integration is calculated individually based on catalog size and mapping complexity. Get a consultation from our engineers to audit your current feed. Contact us or order a turnkey integration — we will implement within 5-7 business days without downtime.

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.