Integration of 1C-Bitrix with Google Merchant Center

Integration of 1C-Bitrix with Google Merchant Center

We often encounter this scenario: after setting up Yandex.Market, clients try to upload the YML feed to Google Merchant Center and get an error: 'Unsupported feed format'. The Google Shopping XML format is fundamentally different — it uses the namespace http://base.google.com/ns/1.0, requires g:google_product_category, g:condition attributes, and prices must be formatted with currency. Without a correct feed, up to 40% of products can be rejected. Let's figure out how to properly configure export from 1C-Bitrix to avoid blocks and disapproved items.

The official Google Merchant Center documentation describes the feed as an RSS feed with <item> elements. Each product requires at least 7 mandatory attributes, and their absence is a common reason for rejections. For complex catalogs (over 10,000 SKUs), a custom handler gives full control: it generates the feed 2 times faster than module-based solutions and allows flexible product filtering. With custom integration, modification costs are reduced by 30% compared to purchasing a module.

Google Shopping Feed Format

Google expects XML with the namespace http://base.google.com/ns/1.0 and <item> elements inside an RSS <channel> wrapper. Main product attributes:

g:google_product_category is a key difference from YML. Google uses its own taxonomy of 5732 categories. Example: Electronics > Phones & Accessories > Mobile Phones. Specify either as text or numeric ID. Without this attribute, a product may end up in the wrong category, and for clothing and food, it will fail moderation.

Feed Generation in 1C-Bitrix

1C-Bitrix standard distribution does not include a ready export profile for Google Shopping. Three approaches:

1. Module from Marketplace. Solutions like 'Google Merchant - Product Export' (itsfera.google_merchant) add an export profile in Store → Settings → Catalog Export. Configuration: select an information block, map properties to Google attributes, set the feed URL. The module generates the file via cron.

2. Custom export handler. A file in /bitrix/php_interface/include/catalog_export/. The class implements the export interface, forming XML in Google format. Advantage: full control over logic, filtering, formatting. Disadvantage: support during Bitrix updates falls on you. However, for catalogs with 10,000+ items, this is the only way to avoid timeouts.

3. XML transformation of existing YML. If a YML feed exists, XSLT transformation converts it to Google format. Works for simple catalogs, but data may be lost for complex SKU structures.

<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:g="http://base.google.com/ns/1.0" version="2.0">
  <channel>
    <title>My Store</title>
    <link>https://myshop.ru</link>
    <description>Products</description>
    <item>
      <g:id>12345</g:id>
      <g:title>Smartphone X Pro</g:title>
      <g:description>6.5 inch, 128 GB</g:description>
      <g:link>https://myshop.ru/product/12345</g:link>
      <g:image_link>https://myshop.ru/images/12345.jpg</g:image_link>
      <g:price>PRICE_PLACEHOLDER</g:price>
      <g:availability>in stock</g:availability>
      <g:brand>X-Corp</g:brand>
      <g:gtin>4901234567890</g:gtin>
      <g:condition>new</g:condition>
      <g:google_product_category>Electronics > Phones & Accessories > Mobile Phones</g:google_product_category>
    </item>
  </channel>
</rss>

How to Achieve Full Control Over the Feed? Custom Handler vs Module

A custom handler provides flexibility: you filter products, format prices, handle multiple properties. In complex catalogs (over 5000 SKUs, multiple information blocks, custom pricing logic), a module often falls short. A custom solution costs more upfront but saves time on ongoing modifications. In 80% of our projects, we choose custom export because it guarantees passing moderation.

Deep Configuration: SKUs and Variants

Google Shopping handles product variants (size, color) via item_group_id — analogous to group_id in YML. All variants of one product must have the same item_group_id and differ in attributes:

• g:color — color
• g:size — size
• g:material — material
• g:pattern — pattern

In Bitrix, SKUs are stored in a separate information block linked to the main one via PROPERTY_CML2_LINK. During feed generation, you need to:

1. Iterate through the SKUs information block.
2. For each SKU, get the parent product (CML2_LINK).
3. Form an <item> with item_group_id = parent product ID.
4. Substitute SKU properties (size, color) into corresponding Google attributes.

Standard Marketplace modules do not always correctly handle multiple SKU properties. Check the feed manually for products with 3+ variants.

How is Price Compliance Checked?

Google bot visits the site and compares the price in the feed with the price on the product page. A discrepancy causes blocking. Ensure that the export profile uses the same price type displayed on the site. If coupon discounts are applied on the site, the feed should contain the price before the coupon. We recommend setting up automatic price verification once per day.

Feed Upload and Diagnostics

The feed is uploaded in Merchant Center: Products > Feeds > Add feed. Specify the URL, update schedule (Google fetches the feed on a schedule, minimum once per day).

After upload, Merchant Center shows an error report:

• Disapproved — product rejected. Reasons: missing required attribute, price on site does not match feed, image does not meet requirements (minimum 100×100 px, for clothing 250×250).
• Warning — product is shown but with limitations. Usually: missing gtin or brand.
• Pending — product under review.

Why is Google Product Category Important?

The google_product_category determines in which section the product appears and which attributes are required. For clothing, for example, g:gender, g:age_group are required. Incorrect category is a cause for disapproved. Manual mapping is unavoidable because Google's taxonomy does not match Bitrix categories. In a custom handler, we can implement automatic category matching based on keywords from the product name.

Multi-Currency and Regional Settings

Merchant Center is tied to the target country. For Russia: prices in RUB, currency specified in each <g:price>. For multilingual Bitrix stores (multiple sites in one installation), you need to generate a separate feed for each country/language — different product URLs, different prices, different g:google_product_category. A custom handler allows automating the creation of multiple feeds from one catalog.

What's Included in Turnkey Integration

• Catalog analysis and approach selection (module / custom)
• Development and configuration of the export profile
• Test feed and its validation in Merchant Center
• Integration with Merchant Center (URL, schedule)
• Documentation on feed updates
• Staff training (1 hour online)
• Support for one month after launch

Contact us for an exact timeline and cost estimate. We guarantee passing moderation and stable feed operation.

Integration Timelines

We'll evaluate your project for free — get a consultation.

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.