Setting Up 1C and Bitrix Contract Synchronization

In B2B, each client works under an individual contract: their own prices, discounts, credit limits, payment terms. Without syncing these contracts from 1C to Bitrix, the site can't display the correct terms—the client sees generic prices, managers manually adjust orders, and pricing errors hit 30% per month. Manual contract reconciliation consumes up to 20 hours monthly per manager, and every price mistake is a direct profit loss. Automating this pays for itself within the first three months by cutting penalties and accounting errors.

The standard CommerceML exchange doesn't transmit contractor contracts—a platform limitation. We've built an extension that, via a 1C HTTP service or file exchange, sends a full set of contract details: GUID, number, price type, validity dates, credit limit, and status. Over five years, we've delivered more than 20 such integrations for distributors, manufacturers, and wholesale networks.

The Role of a Contract in 1C

In UT, KA, and ERP, the contractor contract (ДоговорыКонтрагентов) is the key pricing object. Associated with a contract are:

• price type—which price list applies to this client;
• discounts—personal or contract-specific discounts;
• settlement currency;
• credit limit and credit term;
• payment terms (prepayment, postpayment, deferred days).

If a client in 1C has three active contracts (e.g., retail, wholesale, and special), on the site they must see prices according to the relevant contract and be able to choose the contract during checkout.

Transferring Contracts: Architecture

Standard CommerceML doesn't transfer contracts. A custom synchronization is needed via a 1C HTTP service or file exchange. The HTTP service processes requests three times faster than file exchange and suits catalogs with frequent changes.

Minimum contract data set for the site:

{
  "guid": "a1b2c3d4-1234-...",
  "number": "Д-0015",
  "name": "Договор поставки №15 от даты",
  "contractor_guid": "контрагент-guid",
  "price_type_guid": "вид-цены-guid",
  "price_type_name": "Оптовая",
  "credit_limit": 500000,
  "payment_delay_days": 14,
  "currency": "RUB",
  "valid_from": "2025-03-01",
  "valid_to": "2026-03-01",
  "is_active": true
}

In Bitrix, contracts are stored in a HighloadBlock ContractorContracts. When the catalog opens, we determine the user's active contract and bind the corresponding price type in the trade catalog.

Comparison of Contract Storage Methods in Bitrix

The choice depends on the volume of contracts. For catalogs with thousands of contractors, HL-block is preferable.

Why Mapping Contract to Price Type Matters

The key task: a user with a specific contract must see prices from the linked price type.

Implementation:

1. On user authorization—determine their contract(s) from the HighloadBlock.
2. Determine the price type by contract (price_type_guid → price type ID in Bitrix).
3. Set a session variable or user parameter CURRENT_PRICE_TYPE.
4. The catalog component reads this variable and displays prices of the required type.

If a user has multiple contracts—offer a choice in the personal account: "Work under contract No...." The selection is saved in the session.

How Often to Sync Contracts?

Contracts change rarely—a new contract is signed once a year, terms are revised quarterly. Syncing once an hour or even once a day is sufficient.

But there's a critical scenario: a contract is terminated or expired—the client must not continue seeing wholesale prices. For this, add a check of the contract's valid_to in the authorization logic. If the date has passed, switch the user to the base price type.

How Does a Contract Affect an Order in 1C?

When transferring an order from Bitrix to 1C, you need to specify the contract under which the order is placed. In the order XML:

<ЗначениеРеквизита>
  <Наименование>ДоговорId</Наименование>
  <Значение>a1b2c3d4-1234-...</Значение>
</ЗначениеРеквизита>

In UT, when creating a customer order, the contract is taken from this attribute. Without a contract, the order is created under the default (first active contract of the counterparty), which can lead to incorrect pricing in 1C documents.

Case Study: Distributor with Individual Terms

A medical equipment distributor: 180 dealers, each with an individual contract and their own price (discount from 5% to 40% off retail). All prices are maintained in UT as separate price types per dealer (18 price types).

Task on the site: each dealer sees only their own prices upon login; other dealers' prices are inaccessible.

Implementation:

• sync contracts from UT to Bitrix every 2 hours;
• on authorization—determine the contract, extract the price type GUID;
• map the GUID to a price type in Bitrix (mapping table in settings);
• the catalog displays prices of that type.

Result: 40% time savings for managers, 95% reduction in pricing errors.

Additionally: each dealer has a "supervisor manager" in UT. When an order is created on the site, the manager is automatically added to the order (from the contract field ResponsibleManager). The manager in UT immediately sees their client's order.

Validity Period and Automatic Renewal

If a contract expires—30 days before expiration, we send a notification to the responsible manager in Bitrix24 (via REST API). A scheduled task in Bitrix checks valid_to of all contracts daily.

// Agent for checking contract expiry
function checkContractExpiry() {
    $soon = date('Y-m-d', strtotime('+30 days'));
    $contracts = getContractsExpiringBefore($soon);
    foreach ($contracts as $contract) {
        notifyManager($contract['manager_id'], $contract);
    }
    return 'checkContractExpiry()'; // agent restarts
}

What's Included in the Work

We'll assess your project and offer a turnkey solution. The service includes:

• audit of your current contract accounting schema in 1C;
• development of an HTTP service or file exchange for contract transfer;
• creation of the ContractorContracts HighloadBlock and mapping setup;
• implementation of contract selection in the personal account and session logic;
• integration with Bitrix24 for expiration notifications;
• testing and 1 month warranty for refinements.

Request a free audit of your current schema. Contact us for a consultation on integrating your 1C and Bitrix.

Synchronization: Methods and Frequency

The choice depends on data volume and freshness requirements. We recommend the HTTP service for dynamic projects with many counterparties.

5+ years of experience and over 20 successful integrations in the 1C-Bitrix domain. We guarantee correct synchronization, adherence to deadlines (from 10 business days), and post-launch support.

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.