Setting Up Order Export from 1C-Bitrix to 1C

Why orders don’t reach 1C and how to fix it?

A client complains: orders from the online store don’t make it into 1C, an operator manually transfers data, and every second order goes out with an error. The operator spends 2 hours a day on data entry, one in ten orders has an error. According to our estimates, manual order transfer costs the store 50,000–100,000 RUB per month in hidden losses: operator time, entry errors, customer dissatisfaction. Automation pays for itself in 1–2 months: savings on manual entry reach 80% of operator time, equivalent to 300,000 RUB per year. We set up the exchange so that the XML is formed correctly from the start — without duplicate items, lost details, or numbering conflicts.

Order export is the first stage of two-way exchange. The site forms XML and hands it over to 1C upon request. Setting it up is not difficult, but there are details that determine whether all the necessary data will reach 1C in the correct format. With 10+ years and over 50 integrations with 1C-Bitrix, we have accumulated ready-made solutions for typical problems.

According to internal analytics, 70% of exchange errors are related to mismatched item identifiers. Fixing this problem reduces the number of manual edits in 1C by 80%.

Enabling order export

Settings → Product Settings → Web Store → Exchange with 1C → Orders:

• Export orders: yes
• Order statuses for export: select the required ones. Most often “New” and “Paid”; canceled orders do not need to be exported — they create unnecessary documents in 1C.
• Export orders created no earlier than: limit history if the store worked without 1C — no need to pull orders from several years ago.

Step-by-step setup guide:

1. Go to Settings → Product Settings → Web Store → Exchange with 1C → Orders.
2. Set the “Export orders” flag.
3. Select order statuses for export.
4. Specify the date from which to export orders.
5. Configure the handler for additional details (if INN/KPP are needed).
6. Add an order number prefix if necessary.

How is the order XML formed?

The standard order XML includes buyer details, line items with quantity and prices, selected delivery, and order properties. Simplified structure:

<Документ> <Ид>ORDER_ID</Ид> <Номер>ACCOUNT_NUMBER</Номер> <Дата>202X-03-15</Дата> <Контрагенты> <Контрагент> <Ид>USER_1C_ID</Ид> <Наименование>Иванов Иван</Наименование> </Контрагент> </Контрагенты> <Товары> <Товар> <Ид>PRODUCT_1C_ID</Ид> <Количество>2</Количество> <ЦенаЗаЕдиницу>1500</ЦенаЗаЕдиницу> </Товар> </Товары> <Стоимость>3000</Стоимость> </Документ> 

For an item to be transferred to 1C, it is critical to have <Ид> — the item identifier from 1C, which is stored in the CML2_LINK property of the infoblock element. If an item was created manually on the site without this property, it will appear in 1C as “unknown nomenclature”, creating manual work for the 1C operator.

Transferring buyer details

For individuals, the standard set of details (name, phone, address) is transferred automatically from order properties. Legal entities require additional data: INN, KPP, organization name. This data is stored in separate order properties and added to XML via a handler:

\Bitrix\Main\EventManager::getInstance()->addEventHandler( 'sale', 'OnSaleOrderExport1C', function(&$arOrder) { $arOrder['COMPANY'] = $arOrder['PROPS']['COMPANY']['VALUE']; $arOrder['INN'] = $arOrder['PROPS']['INN']['VALUE']; $arOrder['KPP'] = $arOrder['PROPS']['KPP']['VALUE']; } ); 

How to avoid item duplication during export?

The main cause of duplicates is mismatched item identifiers. The XML must transmit the Ид from 1C, stored in the CML2_LINK property. If an item was added manually on the site, link it to the existing 1C item by updating CML2_LINK. Otherwise, 1C will create a new dictionary element, and you will have to clean up duplicates manually. Additionally, set up an item synchronization agent once a day — this prevents discrepancies.

Custom configuration with static identifier mapping is 2 times more reliable than standard exchange, as it eliminates human errors during manual linking.

Why don’t orders get into 1C?

A common reason is incorrect status settings or numbering conflicts. 1C looks up the order by the <Номер> field from XML. By default, Bitrix transfers ACCOUNT_NUMBER — for example, 1000423. If 1C already has documents with such numbers from another system, conflicts arise. A prefix solves the problem:

// In exchange settings or handler $arOrder['ACCOUNT_NUMBER'] = 'WEB-' . $arOrder['ACCOUNT_NUMBER']; 

Also check that the “Web Store” module settings allow export of orders with the required statuses and dates.

How are delivery and payment methods transferred in XML?

The delivery service and payment method are transferred in separate blocks:

<ЗначенияРеквизитов> <ЗначениеРеквизита> <Наименование>СпособОплаты</Наименование> <Значение>Оплата картой онлайн</Значение> </ЗначениеРеквизита> <ЗначениеРеквизита> <Наименование>СпособДоставки</Наименование> <Значение>Курьерская доставка</Значение> </ЗначениеРеквизита> </ЗначенияРеквизитов> 

Names in 1C must match what Bitrix sends — otherwise 1C will create new dictionary items “Delivery methods” for every mismatch. We recommend synchronizing dictionaries through exchange or fixing the mapping in a handler.

Comparison of standard and custom setup

Common problems and their solutions

What’s included in order export setup

• Analysis of the current exchange scheme and problem areas
• Configuring the “Web Store” module for your statuses and dates
• Adding a handler for transferring legal entity details and custom properties
• Setting a numbering prefix to avoid conflicts
• Synchronizing delivery and payment dictionaries (mapping)
• Testing the full cycle: order on site → XML → loading into 1C
• Correcting errors and training the operator

Setup time

Setting up order export in a standard scenario takes 2 to 4 hours. With legal entity details, custom properties, and custom numbering — from 4 to 8 hours. For complex projects (dozens of properties, non-standard logic), the timeline is determined after an audit.

We will evaluate your project within one business day — contact us to discuss the details. Order order export setup and get rid of routine. Get a consultation for your project.

Guarantees and experience

We are certified 1C-Bitrix specialists with 10+ years of integration experience. We guarantee correct exchange operation after setup: orders will enter 1C without duplicates, with a full set of details. We provide documentation and support after project delivery.