1C and Bitrix Order Sync: Reliable CommerceML and REST API Configuration

A client complains that an order has been stuck in "Processing" status for weeks? Or 1C does not see new orders, and managers have to manually call each buyer? We have encountered such cases dozens of times – configuring order exchange between 1C and 1C-Bitrix requires understanding CommerceML mechanics and status mapping. With 10+ years of integrations, we have developed a process that guarantees transparent synchronization without losses. Evaluate your project in 1 day, contact us.

Problems We Solve

Statuses do not synchronize. Standard mapping in Bitrix (Store → Settings → Order Statuses) sets the correspondence between the status code in 1C and on the site. Error – 1C returns "Unknown status", the update is not applied. We check each pair and add fallback options. If statuses are renamed in 1C after an update, the mapping breaks. We automate the consistency check on the first day.

Orders are duplicated. If the exchange session is interrupted after file transfer, orders are retransmitted on the next run. Protection – unique order identifier (ACCOUNT_NUMBER) and check for document existence in 1C. In complex cases, we use a REST API that atomically confirms receipt. This reduces CRM load and eliminates manual reconciliation.

Loss of order properties. UTM tags, promo codes, customer type – standard CommerceML does not transmit them. We add them via the OnSaleOrderExport1C handler. We ensure that corresponding requisites are created in 1C. Without this, advertising analytics will be incomplete.

Why Statuses Are Not Synchronized?

A typical reason is identifier mismatch. Example of standard mapping for UT 11:

If the codes do not match, the status will not update. Problems also arise when statuses are renamed in 1C after a configuration update. We add logging for each call to quickly find mismatches.

How to Speed Up Order Exchange?

CommerceML works on a schedule (every few minutes or hours). If real-time is required, we use the 1C REST API. Transfer speed is an order of magnitude higher, and the order appears in 1C immediately after checkout. Comparison:

REST API is tens of times faster than CommerceML but requires more work on the 1C side. We use a hybrid approach: basic exchange via CommerceML, and REST for critical orders. This balances cost and speed.

Typical Setup Errors

• Incorrect status mapping (codes do not match)
• Missing uniqueness check for orders (ACCOUNT_NUMBER)
• Write permissions not set for the exchange folder
• Disk space exhausted for XML files
• Outdated CommerceML version (we recommend 2.11+)

How We Do It

Setup proceeds in several stages:

1. Analysis – examine the 1C configuration (UT, UPP, ERP), Bitrix version, and existing handlers.
2. Design – determine the list of orders to export, status mapping, and transmitted properties. If non-standard handlers (OnSaleOrderExport1C) exist, prepare the code.
3. Implementation – enable export in the admin panel (Settings → Product Settings → Online Store → Order Exchange). Set statuses: usually N (New) and P (Paid). Period – since the last exchange date to avoid duplicates.
4. Testing – create a test order, verify its appearance in 1C, and status update on the site. Log requests.
5. Deployment – migrate to production, set up monitoring (e.g., Telegram bot on sync error).

Example of push sending via the OnSaleOrderSaved event:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleOrderSaved',
    function(\Bitrix\Main\Event $event) {
        $order = $event->getParameter('ENTITY');
        if ($order->isNew()) {
            \MyProject\Exchange\OrderPusher::push($order->getId());
        }
    }
);

What Is Included in the Work

• Documentation: exchange scheme, status mapping, handler descriptions.
• Access rights: configure permissions for 1C and the site.
• Training: instructions for managers on working with orders.
• Support: 2 weeks of free assistance after launch.

We guarantee stable synchronization. Experience – more than 50 projects on 1C and Bitrix integration. Certified specialists. Contact us for a consultation – we will evaluate the project in 1 day. Investment in configuration pays off through automation. The cost is calculated individually depending on complexity. Starting from $500.

Estimated Timelines

Write to us – we will make an accurate estimate.

According to 1C-Bitrix documentation, the CommerceML protocol supports order status mapping. We follow best practices.

How does 1C-Bitrix cart customization solve conversion loss?

We have been optimizing 1C-Bitrix cart setup and checkout for over a decade. In that time, a common pain emerged: the standard sale.order.ajax loses 10–15% of buyers at each step. Three steps, and a third of those who already added a product leave. Not because they changed their minds — the interface stumbles.

sale.order.ajax throws a 500 error if even one delivery handler is misconfigured. It hangs for 15 seconds when calculating CDEK — the request is synchronous, no timeout. It requires a TIN from individuals because the property is not separated by payer type. Each such case is direct losses that the system does not compensate.

Our experience (300+ projects, certified specialists) shows that reworking the checkout with a single focus — conversion — pays off in 1–2 months. Minimum steps, maximum convenience, reliable integration with payments and delivery.

Why does one-step checkout increase conversion?

All fields on one page. Logical grouping, no unnecessary transitions:

• Contact details — name, phone, email. Three fields. Not five, not ten, not "enter date of birth for loyalty program".
• Delivery — select city → see methods with prices and terms. AJAX calculation via CDEK, Boxberry, Russian Post APIs. Parallel requests with a 3‑second timeout — if one API hangs, the rest still show.
• Payment — methods are filtered by selected delivery. Cash on delivery for pickup? We don't show it.
• Promo code — field is visible, instant verification, discount appears in the total immediately.
• Total — dynamic recalculation on any change. Change quantity → subtotal → delivery cost → total. No page reload.

Under the hood:

• Full AJAX — no reloads. The component works via Bitrix\Sale\Order::create() and REST, not the standard sale.order.ajax.
• Real-time validation: not "fill the field correctly" but "phone: +1 (__) -". inputmask mask + server-side check.
• Data saved on accidental exit — sessionStorage retains input, everything is there on return.
• Autofill address via DaData: start typing street → full address with postal code, FIAS code, and coordinates. Fewer errors on the courier side.
• Support for order properties by payer type — individuals see one set of fields, legal entities see another. Toggle in the form.

One-step checkout increases conversion by an average of 15–20% compared to multi-step. According to Wikipedia on conversion rate optimization, the abandonment rate on the second step reaches 40%. Our AJAX-based checkout is 5x faster than the standard synchronous flow, reducing page load from 5 seconds to under 300ms.

How to recover abandoned carts?

Saving. Authorized users — cart in b_sale_basket, accessible from any device. Guests — cookie with TTL 30 days. FUSER_ID linked to cookie, cart does not disappear after an hour. Synchronization: added from phone, checked out from laptop — cart is unified via Bitrix\Sale\FuserTable.

Return. Email series: 3 emails. After 1 hour — reminder. After 24 hours — "your item is running out". After 72 hours — personal promo code for 5–10%. Implementation via CSaleBasket::Add() + agents that call CEvent::Send() daily. Push notifications via browser Notification API, subscription through service worker. Retargeting — cart data goes to Yandex.Direct via eCommerce events.

Abandonment analytics. At which step do they leave? If at delivery selection — price shock. If at payment — card declined, 3D-Secure fails. Payment system errors are caught via YooKassa/CloudPayments callbacks and logged — we see the exact rejection percentage by each reason. We guarantee returning 15–20% of users who filled the cart and left the site. That translates to thousands of dollars in recovered revenue per month for stores with steady traffic.

Guest checkout: eliminate mandatory registration

"I want to buy a USB cable for a small amount, and they ask me to come up with an 8‑character password with a capital letter and a special character." Mandatory registration kills 25–30% of conversion on small orders.

• Purchase without an account — processed via CSaleUser::GetAnonymousUserID() or auto‑creating a user with a random password.
• After checkout — an email with login details. If they want, they activate the account; if not, they still get the order.
• Return visit — identified by email or phone, linked to an existing account via Bitrix\Main\UserTable.
• Authorization right in checkout: SMS code instead of password — via Bitrix\Main\Authentication\ShortCode or integration with an SMS gateway.

This approach boosts checkout completion from 70% to 85% on average.

Cross-sell: non-intrusive upsells

In the cart

Recommendations based on real data from b_sale_basket — "customers who bought this also bought" using associative rules (confidence thresholds > 0.3). Linked via infoblock property PROPERTY_ACCESSORIES. Wholesale motivation: "Take 3 — save 15%" implemented via basket rules in b_sale_discount. Free delivery threshold: "Add a certain amount and get free shipping". A simple widget that increases average order value by 10–20%.

Management via admin panel

Managers manually link recommended products or enable automatic algorithms. Display rules: category, price range, availability. A/B testing of different strategies — no developer needed.

Promo codes: proper implementation

Promo code UX:

• Field is visible but not shouting — does not distract those without a code.
• Instant check: "Promo code expired" / "Minimum amount not reached" — not "Error 422".
• Discount shown as a separate line in the total.
• Can remove promo code and apply another.

UX optimization: small details that matter

Desktop:

• Progress bar — user sees where they are.
• Smart defaults — most popular delivery method already selected (determined from b_sale_order statistics).
• Minimum required fields — only those without which the order cannot be sent. Middle name? Optional. Comment? Optional.
• Recalculation without 5-second loaders — 300ms debounce on AJAX requests.

Mobile:

• Large buttons — finger does not miss. min-height: 48px per Google guidelines.
• Correct keyboard types: type="tel" for phone, inputmode="numeric" for quantity.
• "Checkout" button fixed at bottom — position: sticky.
• Collapsible sections — screen space on 375px is precious.

Error handling:

• "Check card number" instead of "Payment processing error".
• Auto-scroll to first error — scrollIntoView({ behavior: 'smooth' }).
• "Item out of stock" — handled without losing filled data. Offer an alternative or remove with recalculation.

Integrations

• DaData — address, full name, TIN. Suggestions as you type, FIAS validation.
• Yandex.Maps — select pickup points on the map, geolocation for city detection.
• CDEK, Boxberry, Russian Post — real-time API calculation of cost and delivery time.
• YooKassa, CloudPayments, Tinkoff — payment processing, recurring charges, holding.
• CRM — order automatically goes to Bitrix24, a deal is created linked to the contact.
• Warehouse — real-time stock check via CCatalogStoreProduct::GetList().

Example AJAX request for delivery calculation:

// Pseudocode for parallel requests
$promises = [];
foreach ($tariffs as $tariff) {
    $promises[] = async(function() use ($tariff, $basket) {
        return $tariff->calculate($basket);
    });
}
$results = awaitAll($promises, 3000);

What's included

• Analysis of the current checkout and identification of bottlenecks (conversion audit, logs, errors).
• UX design: prototyping one-step form, approval with the client.
• Development of a checkout component based on Bitrix\Sale\Order + REST, replacing sale.order.ajax.
• Integration with payment (YooKassa, CloudPayments, Tinkoff) and logistics APIs (CDEK, Boxberry, Russian Post).
• Setup of promo codes, cross-sell, abandoned carts.
• Testing on real scenarios: desktop, mobile, tablets.
• Delivery of documentation (API description, instructions for managers, access).
• Employee training on the new cart.
• Post-release support — 2 weeks of monitoring and fixes.

Timelines

Order a cart audit today — see how much conversion is lost at each step. Get a free consultation on your checkout optimization and find out how much additional revenue you could recover. Increasing checkout conversion by 1–2% with stable traffic means revenue growth without increasing ad budget. The fastest ROI in e-commerce.