Setting up document exchange between 1C and 1C-Bitrix

A customer paid for an order, but the invoice doesn't appear in their personal account — a familiar situation. Managers manually search for the PDF in 1C, send it via email, spending up to 15 minutes per order. With 100 orders a day, that's 25 hours per month of pure routine. Customers wait, managers get stressed, and the business loses loyalty. Standard CommerceML (Wikipedia) transfers only XML structures, not binary files, so exporting invoices or certificates to the personal account without custom development is impossible. We, certified 1C-Bitrix specialists with five years of experience, configure an integration that fully automates the process. Over 50+ projects, we've ironed out typical mistakes: for example, linking by order ID instead of ACCOUNT_NUMBER, which caused document loss. We guarantee that every customer will see their documents immediately after payment.

Automation yields direct savings: clients reduce order processing costs by 40% and document sending time by 80%. This is not just convenience but financial gain — reduced manager workload and faster turnover. Contact us — we will analyze your process free of charge and propose an optimal exchange scheme.

Document Transfer Options from 1C to Bitrix

Two main approaches:

1. 1C generates PDF → saves file → Bitrix fetches on schedule. 1C creates a print form, saves the PDF to a network folder or FTP. Bitrix scans the folder via cron, links files to orders by ACCOUNT_NUMBER. This option is cheap but does not guarantee relevance: the document on the site may become outdated.

2. Bitrix requests a document from 1C via REST API on demand. The customer clicks "Download invoice" → Bitrix makes an HTTP request to the 1C web service → 1C returns the PDF. The document is not stored on the site permanently. This is more reliable: the user always gets the latest version from 1C.

Why Proper Order Linking Matters

To link a document to an order, we need a common identifier. In 1C, this is the "Customer order" document number; on the site, it's the order's ACCOUNT_NUMBER. A typical mistake: using the Bitrix order ID, which does not match the number in 1C. During exchange setup, we always verify that numbers are identical. Otherwise, the document won't attach, and the customer won't see it.

How Documents Are Stored in the Personal Account

If we choose the file storage approach on the site, linking to the order is done via a highload-block:

How to Set Up Document Access Rights

The customer should see only their own documents. In the personal account component, we filter by UF_ORDER_ID with a check that the order belongs to the current user. We use CSaleOrder::GetByID and standard authorization methods.

Step-by-Step Exchange Setup (REST API)

1. Create a web service in 1C to issue PDF by ACCOUNT_NUMBER.
2. On the Bitrix site, register a REST route and a component for the "Download invoice" button.
3. Develop a highload-block for caching links (optional).
4. Set up access rights — verify the order owner.
5. Test on a real order: create an order in 1C, check display in the personal account.
6. Train managers and hand over documentation.

What's Included in the Setup?

• Development of the personal account component for displaying documents.
• Creation of a highload-block for storing file links.
• Configuration of a REST route or agent for file exchange.
• Integration with 1C: modification of print forms if needed.
• Testing on real orders and training for managers.
• Provision of documentation and warranty support.

How Long Does Setup Take?

Implementing document export via 1C REST API — 2–4 days. Via file exchange with number linking — 1–2 days. Timelines may increase if 1C print forms need modification or non-standard linking. Setup cost is discussed individually, but on average the project pays off in 1–2 months.

Our experience: over 50 projects integrating 1C and Bitrix, 5 years on the market, warranty on all work. We reduce document sending time by 80% — it's easy to calculate the savings. Contact us — get a consultation and demo access to a ready-made solution. Order document exchange setup and automate the routine.

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.