1C:Accounting (BP) is not a trade system, but in practice it often ends up being the only accounting program in small businesses. An online store runs on Bitrix, item nomenclature and prices are maintained in BP, and the request arises: 'make products on the site update from 1C'. The standard exchange module in BP exists but is significantly simpler than in Trade Management (UT) or Comprehensive Automation (KA). We professionally set up exchange between 1C:Accounting and 1C-Bitrix turnkey. Our experience: over 50 successful integrations for stores with catalogs ranging from 500 to 50,000 items. We will evaluate your project and offer an optimal solution—contact us for a consultation. Time savings on manual upload—up to 40 hours per month, and configuration cost pays off on average in 3-4 months. Integration cost starts from 50,000 rubles, with average savings of 30,000 rubles per month.
Comparison of exchange capabilities in 1C:Accounting and 1C:Trade Management
| Capability | 1C:Accounting 3.0 | 1C:Trade Management |
|---|---|---|
| Nomenclature | Yes (name, article, unit) | Yes, with variants |
| Prices | One price type | Multiple price types |
| Balances | Total balance | By warehouse |
| Orders | Customer invoice | Customer order (status model) |
| Categories | Flat hierarchy (max 1 level) | Full hierarchy |
| Images | No | Yes (up to 10 MB) |
| Variants | No | Yes |
What the exchange in BP can do out of the box
In 1C:Accounting Enterprise (edition 3.0), the exchange module with the site is located in Administration → Data exchange. Functionality is limited:
- Upload of nomenclature (name, article, unit of measurement)
- Upload of prices (one type—'Main selling price')
- Upload of balances (total balance, without warehouse detail)
- Download of customer orders (creates document 'Customer invoice')
What's missing: variants (options), multiple price types, warehouse-level detail, images, categories (group hierarchy is transmitted as a flat list with no nesting deeper than one level). For a small store (up to 5000 items, one price, one warehouse) this is sufficient. For everything else—customization or switching to CommerceML (see Wikipedia) is needed.
Why the standard exchange is not suitable for stores with variants?
If a product has options (color, size, material), BP has no mechanism to transfer them. Each modification becomes a separate nomenclature item, and their relationship is lost. 80% of exchange errors are related to incorrect category hierarchy settings. Variants require custom development or upgrading to Trade Management.
Configuring price upload and order download
BP supports only one price type—'Main selling price'. On the Bitrix side, it maps to the base price type. If retail and wholesale prices are needed but not maintained in BP—a typical solution is to upload the base price from BP and calculate surcharges using Bitrix formulas:
BASE_PRICE * 0.85 Orders from Bitrix arrive as 'Customer invoice'. Configure automatic posting of the invoice via the AutomaticPosting = Yes flag in the exchange node settings. Duplicate counterparties are a common issue: we recommend transferring the buyer's unique XML_ID from Bitrix so BP searches by it.
Case study: jewelry online store (from our practice)
A jewelry store, 3000 items, all prices in BP. Prices changed multiple times a day (gold, silver—exchange rates), but the site updated once a day. We configured incremental exchange—only price changes—every 30 minutes. In BP, we wrote a scheduled task: when the metal rate changes, recalculate prices. Bitrix fetches changes at the next exchange. The XML volume during incremental exchange averages 200–400 items instead of 3000. Processing time: 8 seconds instead of 90. Incremental exchange is 3 times faster than full exchange.
How to configure incremental exchange: step-by-step guide
- In 1C:Accounting, enable upload of only changed objects (flag 'Upload only changed').
- Set up the scheduled task 'Exchange with site' with an interval of 30 minutes.
- In Bitrix, enable import by XML_ID (in the exchange module settings).
- Configure cleanup of temporary folders to prevent file duplication.
- Test on a test product: change the price in 1C and verify the update on the site.
Typical errors and their solutions
| Error | Cause | Solution |
|---|---|---|
| Categories not created | Option 'Do not update section linking' enabled | Disable, reset XML_ID, reimport |
| Prices not updating | Price type mismatch | Create 'Base' price type in Bitrix |
| Orders not visible in 1C | Exchange node settings error | Check node details and user credentials |
| Duplicate counterparties | Search by full name without XML_ID | Transfer customer external ID |
What's included in the exchange configuration work
- Audit of current exchange
- Design of synchronization scheme
- Customization of exchange module on 1C and Bitrix sides
- Setup of scheduled tasks
- Testing on live data
- Employee training (accountant, content manager)
- Technical documentation
- Post-release support for 2 weeks
Details of incremental exchange setup
Incremental exchange is built on the 'Changed' flag in 1C. After successful upload, the flag is reset. If no exchange occurs, data is not retransmitted. This is critical for saving traffic and processing time—especially for catalogs over 10,000 items.Limitations and when to upgrade to Trade Management
BP is suitable for integration with Bitrix if: up to 10,000 items, one price type (or simple formula-based surcharges), one or two warehouses, no variants. If any condition is not met—consider upgrading to 1C:Trade Management or Comprehensive Automation. Migration of data from BP to Trade Management using standard tools takes 1–2 days.
Reliable 1C and Bitrix integration from certified specialists
Our company has 7+ years of experience in 1C-Bitrix integration and over 50 successful projects. Certified specialists guarantee stable exchange operation from the first launch. Contact us for a free evaluation of your project—we will offer an optimal solution. Reduce maintenance costs by up to 60%.