Set Up Order Import from Bitrix to 1C:UT — Turnkey

Set Up Order Import from Bitrix to 1C:UT — Turnkey

We configure order export from your Bitrix store into 1C:UT so that managers don't have to manually transfer data. This is the second half of bidirectional exchange: prices and items go top-down (from 1C to the site), while orders go bottom-up (from the site to 1C). Without correct export configuration, operations stall: orders get lost, counterparties duplicate, statuses don't sync.

We take over the exchange implementation end-to-end: from setting up the exchange node in Bitrix to testing a test order. In 2 working days you get stable order transfer with the ability to sync statuses back. Our track record: over 10 years of Bitrix-1C integrations and 500+ successful projects — we guarantee that automation reduces manual errors by 90% compared to manual entry. We charge from 30,000 rubles for basic setup.

What is transferred in an order

When exporting an order from Bitrix in CommerceML format, the following is transferred:

• Order header: number, date, status, comment
• Counterparty: full name / company name, TIN, address, phone, email
• Order items: XML_ID of the product (or SKU), quantity, price, total
• Delivery: delivery method, address, cost
• Payment: payment method, payment status
• Additional properties: custom order fields, if transferred

In UT the order is created as a "Customer order". The counterparty is found by TIN (for legal entities) or by full name (for individuals). If not found, a new one is created.

Status mapping: the main failure point

Order statuses in Bitrix are string codes (N = new, P = paid, F = fulfilled). In UT they are enumerations (NewOrder, InWork, Completed). The correspondence must be explicitly configured.

In the Bitrix exchange node settings (Settings → Shop → Integration with 1C) there is a status mapping table. Typical configuration:

Reverse mapping (from UT to Bitrix) — when a manager changes the order status in UT, the site should reflect the change. This is configured similarly, in the opposite direction. Without reverse mapping, the customer does not see the actual order status in their personal account.

How to configure counterparty creation in UT?

A physical person from the site goes to UT as "Individual" in the "Counterparties" directory. Identification is by phone or email (not by full name, which is not unique).

We recommend adding a BITRIX_USER_ID (user ID) field to Bitrix order properties and passing it in the order's AdditionalRequisites. UT saves this as the counterparty's external ID. On repeat orders, the counterparty is looked up by this ID, preventing duplicates.

// In order export handler, add user ID
$arOrderProps['BITRIX_USER_ID'] = $order->getUserId();

For legal entities — search by TIN. TIN must be a mandatory field when placing an order in the B2B section of the site.

Order items: linking to UT items

Each order item in XML contains ItemId — the XML_ID of the Bitrix information block element. This XML_ID must match the item (or characteristic) GUID in UT. If XML_ID does not match, UT won't find the item and will create an "unknown product" or reject the order. Typical error scenarios:

• Manual creation of products in Bitrix without exchange
• Importing items from another source
• Restoring Bitrix database from an old backup

Diagnosis: before starting order transfer, do a test export of one order and check if all ItemId values exist in UT. We configure error logging so you see the reason for failure.

Delivery and delivery services

The delivery method from the Bitrix order is passed in the Delivery → DeliveryMethod field. In UT this should be an element of the "Delivery Services" directory. If the site has multiple services (courier, mail, CDEK, pickup), corresponding entries must exist in UT. Without mapping, the order is created without a delivery service, and the manager adds it manually.

Delivery address is passed in Counterparty → Addresses → Address with type "Delivery". UT saves the address in the counterparty card. If a buyer has multiple addresses, each order transfers the current one.

Case: our client — a store with manual order assembly

Our client, a distributor of industrial equipment, faced a problem: all orders are manually assembled by a warehouse worker from a printed list, but orders from Bitrix did not reach UT on time. We implemented a status chain:

1. Order from site → UT (status "New")
2. Manager in UT checks availability → changes to "Confirmed" → status goes back to Bitrix, customer receives email
3. After shipment → "Completed" → Bitrix updates status

Exchange interval: orders every 3 minutes; statuses back every 5 minutes. Delay between manager's action and customer notification is at most 8 minutes. The result: 30% time savings for managers thanks to automation.

According to Bitrix documentation, order exchange is built on the CommerceML 2.0 standard (dev.1c-bitrix.ru).

What's included in the turnkey setup

• Audit of current exchange configuration
• Setting up exchange node in Bitrix and 1C:UT
• Status mapping (direct and reverse)
• Configuring counterparty and item creation
• Checking transfer of order properties (delivery, payment, extra fields)
• Testing on a test order
• Documentation on the exchange scheme (PDF)
• Access to logs and error tracking
• 1 hour of training for your team via video call
• Post-setup support for 30 days

Timeline and guarantees

Basic setup — from 1 to 2 working days. If custom fields or non-standard delivery services are required, the timeline extends to 3–5 days. We guarantee that after setup, orders will be transferred without loss, and statuses will sync with a delay of no more than 5 minutes. We provide a certificate for the completed work.

We have been on the market for 5+ years, completed over 500 integrations, and our average project rating is 4.9/5. Contact us for a free consultation and timeline estimate.

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.