Bitrix24 and 1C:UNF Integration for B2B Sales Automation

Integration Objectives

The integration of Bitrix24 with 1C:UNF in the B2B segment focuses on automating order processing, synchronizing customer, product, and pricing data, and managing deals and document flow. This integration eliminates manual data entry errors, ensures control over sales stages fr om lead to shipment, and simplifies the monitoring of accounts receivable.

Data Exchange and Integration Scenarios

• Transferring orders from Bitrix24 to 1C:UNF for document generation
• Synchronizing product catalog, prices, and inventory from 1C to Bitrix24
• Sending back payment and shipment statuses from 1C to the CRM
• Automated generation and printing of documents in 1C (invoices, unified transfer documents, etc.) triggered by events in Bitrix24

Technology Platform: On-Premise Bitrix24

The integration is implemented using the on-premise version of Bitrix24, the 1C API, custom modules, and D7-based components. Data exchange can be organized via REST or directly through 1C HTTP services (web services or OData HTTP services).

Exchange Schema Configuration

The data exchange workflow can be implemented with a custom module. For example, the module may create an agent that periodically queries a 1C web service, retrieves inventory data, and updates the CRM catalog.

\Bitrix\Main\Loader::includeModule('custom.integration');
Custom\Integration\InventoryUpdater::updateStockData();

Data can be retrieved from a 1C endpoint configured via an HTTP service:

$response = HttpClient::get('https://1c.domain.local/odata/standard.odata/Catalog_Products?$format=json');
$items = json_decode($response, true)['value'];

Process Automation Examples

• Automatic creation of "Sales Order" documents in 1C based on the "Terms Agreement" stage in Bitrix24
• Price update scenarios wh ere 1C's price list upload syncs to Bitrix24's product catalog
• Linking deals and service acceptance certificates using UID fields in both systems

Common Integration Mistakes

• Lack of version control mechanisms for the product catalog: updated items may fail validation due to code mismatches
• Usage of outdated integration methods (e.g., Exchange module), reducing flexibility and performance
• Incorrect handling of counterparties and contact mappings between systems: duplication or incorrect entity associations
• Improperly defined event triggers (e.g., bulk deal exports without stage filtering)

Integration Implementation Checklist

• Data sources and entity roles (customers, products, orders) are clearly identified
• Synchronization order and intervals are defined
• Identifiers that link CRM and 1C entities are properly configured
• Logging and error tracking mechanisms are in place
• Compatibility with various JSON and XML formats and encodings is verified

FAQ

Is bidirectional deal synchronization possible?

Yes, though in most B2B scenarios, deals are transferred one-way from CRM to 1C, with reverse synchronization of statuses, payments, and documents.

What are the limitations of exporting inventory from 1C?

Limitations may include web service performance, data volume constraints, and insufficient filtering support in some 1C configurations.

How is contractor mapping implemented?

It is recommended to use taxpayer identification numbers (INN) and codes (KPP) as unique identifiers, along with maintaining a unified ID registry in both systems.

Can Bitrix24 REST API be used without a custom module?

For basic integration tasks, yes. However, complex logic or large volume data processing typically requires a D7-based custom module.

How is document printing from 1C organized?

Documents can be generated and printed via pre-configured 1C handlers or through REST endpoint calls, with resulting PDFs sent as CRM attachments.

Conclusion

The integration of Bitrix24 and 1C:UNF significantly enhances the automation of B2B sales. A well-configured data exchange aligned with system architectures ensures data accuracy, managerial transparency, and full synchronization across all sales stages. A modular solution based on the on-premise version of Bitrix24 allows adaptation to specific use cases, minimizing errors and optimizing technological resources.

Need to discuss a specific integration scenario?

If you're planning a similar integration or adapting the exchange model to existing processes, a preliminary discussion can help assess scope and feasibility. Common aspects clarified before launch:

• Which entities and exchange directions are business-critical
• Existing infrastructure and technical limitations across systems
• Expected frequency and volume of synchronization