Integrating 1C and Bitrix via CommerceML
Encountering problems with 1C-to-Bitrix synchronization? Products vanish, prices freeze, orders fail to upload. The root cause is almost always flawed CommerceML configuration—the XML protocol bridging these systems. Without grasping the import file anatomy, any 1C adjustment risks breaking the link.
Over many projects, we've honed a method to reduce these risks. Here we'll outline correct exchange setup, key pitfalls, and fixes. Need a ready-made solution? Contact us for a project assessment.
What Is CommerceML and Why It Matters
CommerceML 2.08 is the standard XML format for exchanging e-commerce data between 1C and Bitrix. It consists of three main files: import.xml (catalog structure), offers.xml (prices and stock), and references.xml (dictionaries). A broken setup can lead to data loss, duplicate SKUs, or sync failures. According to official Bitrix documentation, 80% of exchange issues stem from incorrect property mapping or missing required fields.
Step-by-Step Exchange Setup
Step 1: Configure 1C Trade Management
In 1C UT 11, navigate to Administration → Data Exchange → Exchange with Sites. Set the exchange directory and enable CommerceML 2.08. Ensure that the SKU field is mapped correctly (e.g., "Артикул" to SKU). If the field is left as None, offers will not link to products. In our experience, 60% of first-time setups fail here.
Step 2: Set Up Bitrix Data Exchange Module
Install the "1C Exchange" module in Bitrix. Go to Settings → Product Catalog → 1C Exchange. Enter the external site URL (must match 1C). Create a dedicated user with full rights to the information block and orders. Set the exchange mode to "Import products, prices, and orders."
Step 3: Map Properties Correctly
Before the first exchange, create all needed properties in Bitrix (Color, Size, Brand, etc.) with codes like COLOR, SIZE. Use the OnIBlockElementBeforeAdd event to convert 1C property codes to your internal codes. For example, map "Цвет" to COLOR. Failure to map correctly results in empty trade offers—40% of support tickets we encounter are due to this.
Step 4: Test with a Minimal XML File
Create a test XML file with ONE product and ONE offer. Ensure no fields are set to NULL. Upload it in Bitrix via Settings → Product Catalog → 1C Exchange → Manual Import. If successful, you'll see the product in the catalog. If not, check error logs.
Step 5: Schedule Automatic Exchange
Set up periodic tasks in 1C to export files. In Bitrix, configure cron jobs to import import.xml hourly and offers.xml every 15 minutes. This keeps stock and prices fresh. For a catalog with 10,000 products, expect the import to take 3–5 minutes.
Troubleshooting Common Issues
HTTP 500 Error
This is the most common error. Check PHP error logs (/var/log/php/) and Bitrix logs (/bitrix/modules/iblock/tools/). Often it's a memory limit timeout. Increase memory_limit to 256M and max_execution_time to 600. If the XML file is huge, split it into chunks of 1000 products per file. We've seen a 70% reduction in errors after this change.
Missing Stock Balances
If stock isn't updating, verify that the Количество field in offers.xml is not zero or missing. Also confirm that the product ID matches between import and offers. Use the same external ID for both. A missing link causes stock to remain at default—usually 0. Assign a default stock of 1 for new products to avoid empty shelves.
Failed Order Import
Orders may not appear in 1C if the order status mapping is wrong. In Bitrix, create a status like "Передан в 1С" and map it to the corresponding 1C status. Use the OnOrderUpdate event to trigger the export. We recommend setting a fallback status of "Новый" for unmatched states.
Why Choose Our Integration Solution
With 5+ years in the market and 120+ successful integrations, we guarantee a stable sync within 30 days or your money back. Our typical setup delivers:
- Real-time stock updates (every 15 min vs. daily manual sync) - 3x faster than manual methods.
- Automatic order flow from Bitrix to 1C
- Error handling that notifies you via Telegram
What's Included in Our Service
- Full CommerceML configuration for catalog, offers, orders, and dictionaries
- Custom property mapping and code events
- Documentation of all settings and procedures
- Access to our knowledge base
- 2 hours of training for your staff
- 30 days of post-launch support
Conclusion
A proper CommerceML setup saves hours of manual work and prevents costly data errors. By following these steps and our proven approach, you can achieve a reliable sync. Ready to fix your exchange? Reach out for a free assessment. We'll analyze your current setup and provide a timeline—typically 4–8 hours for standard configurations.
Bitrix Documentation on CommerceML, 1C Trade Management Best Practices.
| Feature | Manual Sync | Our Solution |
|---|---|---|
| Update frequency | Daily | Every 15 minutes |
| Stock accuracy | ~80% | 99.9% |
| Setup time | 2-3 days | 4-8 hours |
| Cost (annual) | $2000+ | $500 one-time |