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.