Order status sync from 1C to 1C-Bitrix
Order paid, goods shipped, but the customer sees „In Processing.“ With 50 orders a day, a manager spends 12.5 hours manually updating statuses. One status mistake — wrong shipment or duplicate accounting. We configure automatic status import from 1C to Bitrix: after each exchange session, statuses update automatically. Managers save up to 12 hours per week, directly cutting operational costs.
Source: Official CommerceML documentation states that status synchronization is only possible with correct identifier mapping.
Why statuses don't update automatically?
The typical reason — missing or incorrect mapping. 1C sends the status in an XML document, but Bitrix doesn't know which internal code it corresponds to. If the 1C status ID (e.g., „Shipped“) is not linked to Bitrix code „D“, the order stays in the previous status. Also, often confuse the order ID and ACCOUNT_NUMBER — exchange only works with the latter.
Mapping table for UT 11:
| 1C status ID | Bitrix status code | Description |
|---|---|---|
| Новый | N | New order |
| В работе | P | Accepted |
| Подготовлен | D | Delivering |
| Выполнен | F | Completed |
| Отменён | C | Cancelled |
How statuses are transferred
1C sends changed order statuses in the same orders.xml file as when exporting new orders. Each document's XML contains a <Статус> tag:
<Документ> <Ид>12345</Ид> <Статус> <Ид>STATUS_1C_ID</Ид> <Наименование>Shipped</Наименование> </Статус> </Документ> On import, Bitrix looks up the order by identifier and updates the status according to the mapping. The exchange format is described in CommerceML. To speed up exchange, use tagged caching and agents.
How to set up status mapping
- Go to
Store → Settings → Order statuses. - For each status, fill the field „1C identifier“ — this is the status code from 1C (e.g., „Shipped“). You can get the list from the XML file or 1C reference.
- Save changes and test on a test order.
How to check mapping correctness without a test order?
You can analyze the exchange log right after the 1C export. Look for lines with “Status mapping error”. If none and the status in XML matches the configured one — it's correct. You can also manually open the exchange XML file and compare status identifiers with those set in Bitrix.
Diagnosis when error „Status not updating“ appears
Step-by-step check:
- Look at the exchange log — mapping errors indicate mismatched identifiers.
- Compare the order
<Ид>in XML withACCOUNT_NUMBERon the site (that one, not ID). - Check the exchange user's permissions: they must have the right to change order statuses.
If the problem persists — contact us for an integration audit.
Customer notifications on status change
When the status changes automatically via exchange, the OnSaleStatusOrder event fires, triggering standard email notifications. Ensure the mail template is set for each status: Settings → Mail events → ORDER_STATUS_CHANGED.
What's included in turnkey setup?
- Audit of the current exchange scheme (component versions, mapping, access rights).
- Mapping of all statuses used in 1C.
- Testing on a test order with logic verification.
- Setup of email notifications for each status.
- Documentation of the mapping scheme.
- Manager training (how to check exchange, what to do on error).
Exchange recommendations from official 1C-Bitrix documentation.
Manual vs automatic: comparison
Manual status updates take up to 15 minutes per order. With 50 orders a day — that's 12.5 hours of manager time. Automatic import from 1C processes the order in 0 seconds after exchange. The difference is tens of times faster. Order the setup — your managers can focus on more important tasks. The setup cost pays off by preventing shipment errors and saving time.
Typical errors and solutions
| Error | Cause | Solution |
|---|---|---|
| Status not updating | Incorrect mapping or order ID | Check ID and mapping |
| Duplicate notifications | Event duplication | Disable redundant handlers |
| Permission error | Exchange user lacks rights to change statuses | Assign rights to „Managers“ group |
Setup timeline
Status import setup with mapping and notifications — from 3 to 6 hours. Complex schemes (multiple statuses, custom rules) require individual estimation.
Our team has 10+ years of 1C and Bitrix integration experience, completed over 50 projects. We guarantee that statuses will update correctly. Get a consultation for your project — contact us for an audit.