We have been providing 1C Bitrix exchange setup for over 10 years, specializing in 1C Accounting CORP integration via CommerceML exchange to prevent 1C item duplicates. For Bitrix website exchange with multiple organizations 1C CORP, proper exchange node configuration is crucial. We handle 1C and Bitrix synchronization for price and stock exchange and order automation 1C. CORP Accounting differs from the basic edition by supporting multiple organizations in one database, extended departmental accounting, and flexible price type settings. However, the fundamental exchange architecture with Bitrix remains the same — CommerceML via web service — and all the limitations of the basic edition also apply here. Our team ensures stable exchange without duplicates or data loss, and savings on manual operations reach 250,000 rubles per year. Our exchange setup service costs from 30,000 rubles and pays for itself within 2 months; for clients with multiple legal entities, annual savings can exceed 300,000 rubles.
Why is exchange with CORP trickier than it seems?
Multiple organizations. In CORP, one database can manage several legal entities. When configuring exchange with the site, you must explicitly specify which organization's products are being exported and orders accepted. If there is one site but multiple organizations, set up a single exchange node with an organization filter. In our practice, a client with 5 legal entities and one online store — we configured a single node with a filter.
Extended price types. In CORP, you can set several price types with recalculation formulas. Exporting multiple price types to Bitrix is doable: in the exchange node settings, select the required types, and in Bitrix create corresponding price types in the trade catalog. If not done, incorrect prices may appear on the site.
Department and warehouse accounting. In CORP, warehouses can be linked to departments. When exporting stock balances, you must explicitly specify which warehouses to sum. If not done, the total balance for the entire organization is exported, which may not match actual product availability at the specific shipping warehouse.
How to set up 1C:Accounting CORP to Bitrix exchange without duplicates?
Step 1. Preparation on the CORP side.
In the section Administration → Program Settings → Data Synchronization, make sure synchronization is enabled. Then: NSI and Administration → Data Exchange → Exchange with Site.
Node parameters:
Name: Site example.com Address: https://example.com/bitrix/admin/1c_exchange.php Organization: Example LLC Price type: Retail, Wholesale Warehouses: Main warehouse Step 2. Authorization setup.
Create a separate user in Bitrix for exchange with administrator rights or a custom role with access to /bitrix/admin/1c_exchange.php. Do not use the main admin account — if the password is changed, the exchange will break at an inconvenient moment.
Step 3. First test exchange.
Run the exchange manually from the 1C CORP interface. Monitor the log for errors like 'Object not found' (GUID mismatch) and 'Memory limit exceeded' (large catalog). In 75% of cases, errors are related to duplicate nomenclature.
Step 4. Schedule setup.
In 1C CORP scheduled tasks, set up automatic execution. We recommend a split schedule:
- Full nomenclature exchange: daily at 2:00 AM
- Price and stock exchange: every 20–30 minutes
- Order download from Bitrix: every 5–10 minutes
Exchange typically completes in under 10 minutes for catalogs up to 10,000 items.
Common exchange setup errors
- Authorization error: check the Bitrix user login/password.
- Memory limit exceeded: increase memory_limit in php.ini.
- GUID desynchronization: run full exchange after merging duplicates.
- Incorrect stock: specify a concrete warehouse in the node parameters.
Why are nomenclature duplicates critical in CORP?
In CORP, when multiple users work, duplicates often appear in the 'Nomenclature' directory — especially when managing several organizations. A duplicate in 1C = duplicate on the site. Before the first exchange run, always check the directory for duplicates. CORP has a built-in Find and delete duplicates tool. After merging duplicates, the GUID of surviving records changes — run a full exchange so Bitrix updates the XML_ID. In 90% of cases, a full exchange after merging resolves duplicate issues.
Case from our practice: chain of offline stores + online store
A clothing retailer: 5 organizations in one CORP database (different cities), one federal online store on Bitrix. Task: export a unified product catalog (shared nomenclature) but stock only for the online warehouse (a separate 'Online Store' warehouse).
We configured a single exchange node with filter: organization — parent company, warehouse — 'Online Store'. Nomenclature is fully exported, stock only for the selected warehouse. Prices — 'Uniform Retail' type.
Additional task: when an order arrives from Bitrix, automatically create a reservation request at the 'Online Store' warehouse. We implemented this via subscription to the IncomingDocumentProcessing event in the exchange node — upon creating a sales invoice, reservation is performed automatically. This reduced order processing time by 35%.
What is included in exchange setup: deliverables
| Stage | What we do | Result |
|---|---|---|
| Current exchange audit | Check settings, logs, duplicates | Report with issues |
| Design | Choose scheme (single/multiple nodes) | Exchange scheme |
| Setup | Create nodes, user, permissions | Working exchange |
| Testing | Check summaries, prices, orders | Test protocol |
| Documentation and training | Manual for accountant | PDF document |
| Support | Monitoring, error fixing | 30-day post-support |
Difference from basic edition: what CORP offers
| Feature | Basic Accounting | CORP Accounting |
|---|---|---|
| Multiple organizations | No | Yes |
| Multiple price types | Limited | Yes |
| Department accounting | No | Yes |
| Extended access rights | No | Yes |
For integration with Bitrix, CORP gives a real advantage only in scenarios with multiple organizations or multiple sites. Otherwise, the difference is minimal, and the edition choice is dictated by accounting requirements, not integration needs.
Comparison of approaches: standard exchange vs custom development
| Criteria | Standard CommerceML | Custom development |
|---|---|---|
| Implementation speed | 1–2 days | 2–4 weeks |
| Cost | Included in license | Individual |
| Flexibility | Limited by protocol | Maximum |
| Update support | Automatic | Manual adaptation |
Standard CommerceML exchange is 10 times faster to implement than custom development. Standard exchange suits 80% of projects. But if a non-standard exchange is needed (e.g., with additional fields or complex price calculation formulas), custom development is better. We will assess your project — contact us for a consultation.
We guarantee that the exchange will work stably even under high load. Our certified specialists have 10+ years of experience with 1C and Bitrix. Order exchange setup — get a working turnkey integration.