1C:UNF and Bitrix: Error-Free Data Synchronization

When the standard exchange falls short

You add products in 1C:UNF, but they don't appear on the site. Or an order is placed on the site, but it doesn't reach UNF. The standard CommerceML exchange seems to exist, but often prices are wrong, stocks don't match, and order statuses don't sync. We configure this exchange turnkey — from initial connection to custom scenarios. We have experience from over 50 projects. Saving on manual synchronization can be up to 80% of labor costs.

What problems we solve

Price mismatch. UNF transfers prices by price type, but if the site has discounts or promotions, synchronization breaks. We configure price mapping taking into account Bitrix rules.

Stocks not updating. Standard exchange occurs every 15-60 minutes. If you need real-time stock updates, we implement an HTTP service in 1C that returns stock on request. Load? We test: for a catalog of up to 10,000 items, the service response is within 0.5 seconds.

Order statuses. By default, the status from UNF does not return to Bitrix. We develop a custom handler: when the status changes in UNF, a POST request is sent to the site, and the status is updated. This solves the problem of "order completed, but the site shows 'processing'."

How to set up exchange in 3 steps

1. Diagnostics. Check 1C versions (platform not lower than 8.3.20), CommerceML settings, user permissions in Bitrix. We identify bottlenecks within an hour.
2. Configuration. Set up the exchange URL, price type, warehouse, schedule. For custom scenarios, we write PHP handlers in init.php. This stage takes up to 2 days.
3. Test and launch. Run the exchange with a group of 10-20 items. Check prices, stocks, orders. After confirmation, full launch.

Why does this work faster than standard setup? Because we already know typical errors: for example, in UNF, the price type for export is often left blank, and the exchange proceeds with empty data.

What data can be synchronized

CommerceML supports transferring nomenclature, prices, stocks, images, and orders. For extended synchronization (statuses, counterparties, requests), development of HTTP services is required. We connect Bitrix24 REST API for bidirectional exchange.

Why UNF is simpler than UT and what's the catch

Unlike UT and ERP, UNF is easier to configure for exchange. There is no multi-currency, complex discounts by contracts. But there are pitfalls:

• Characteristics. UNF supports characteristics, but if they are not set in the product card, the offers.xml will be empty.
• Counterparties. For repeat orders, UNF searches for a counterparty by email. If email is not specified, a duplicate is created. We automate linking by phone number.
• Stock by warehouse. If there are multiple warehouses in UNF, you need to explicitly specify which one to export stocks from. Otherwise, the site may show zero.

Comparison: UNF vs UT exchange

UNF wins in implementation speed: basic integration takes 1.5-2 times less time than for UT.

How to speed up exchange

Use tagged caching on the site and set up auto-exchange every 5-10 minutes. If real-time is required, implement an HTTP service or integration via REST API. We recommend a performance audit before launch.

What's included in exchange setup

Access and configuration:

• Creating a Bitrix user with rights to 1c_exchange.php
• Setting up the exchange URL in UNF
• Specifying the price type and warehouse

Data verification:

• Test exchange with 10 items
• Reconcile prices and stocks
• Check image loading

Documentation:

• Exchange diagram with field descriptions
• Instructions for launch and debugging

Support:

• 2 weeks of support after launch
• Bug fixes if they occur

We guarantee results

We have certified specialists in 1C and Bitrix. Every project is delivered with a test protocol. If the exchange does not work as intended, we refine it for free. Get a consultation on your project — we evaluate the task within 1 day. Contact us to discuss details.