Setting Up Order Transfer from Site to Bitrix24 CRM

An order is placed on the site, but CRM is empty. The manager copies data manually — 30 minutes per order. With 20 orders per day, that's 10 hours lost. The client calls back, but there's no history. Connecting the site and Bitrix24 via the OnSaleOrderSaved event and REST API is a task that takes a few hours and saves dozens of human-hours monthly. We, certified Bitrix24 specialists with over 6 years of experience, have implemented over 50 such integrations. We guarantee stable operation without data loss and with minimal modifications. We'll assess your project in one day — request a consultation.

Transferring Orders to CRM: Why It Matters?

Without automatic deal creation, managers work blind. Contacts are created manually, statuses are not synchronized, analytics are missing. The result: lost leads and reduced LTV. Integration via REST API solves these problems: all customer data, order total, and product list immediately enter the funnel. Order processing time reduction reaches up to 80% — this is not just convenience but a direct conversion boost. Manual entry takes 30 minutes, automation takes 3 minutes — 10 times faster. Operational cost savings can reach up to 150,000 rubles per month at 30 orders daily. At 50 orders per day, savings exceed 200,000 rubles monthly.

How to Implement Integration?

What Is Transferred to CRM

Upon order creation, we create in Bitrix24:

• Contact (crm.contact.add) — with name, phone, email.
• Deal (crm.deal.add) — with amount, status, and link to contact.
• Product rows (crm.deal.productrows.set) — list of items with quantity and price.

For legal entities, additionally create a Company (crm.company.add) and link via COMPANY_ID.

Order Event Handler

// В init.php или обработчике модуля
AddEventHandler('sale', 'OnSaleOrderSaved', 'onOrderSavedHandler');

function onOrderSavedHandler($order) {
    $isNew = $order->isNew();
    if (!$isNew) return; // обрабатываем только новые заказы

    $orderId    = $order->getId();
    $orderProps = $order->getPropertyCollection();
    $basket     = $order->getBasket();

    // Собираем данные покупателя из свойств заказа
    $name  = $orderProps->getItemByOrderPropertyCode('NAME')->getValue();
    $phone = $orderProps->getItemByOrderPropertyCode('PHONE')->getValue();
    $email = $orderProps->getItemByOrderPropertyCode('EMAIL')->getValue();

    // Передаём в Б24
    $b24 = new B24Integration();
    $contactId = $b24->findOrCreateContact($phone, $email, $name);
    $dealId    = $b24->createDeal($orderId, $order->getPrice(), $contactId);
    $b24->setDealProducts($dealId, $basket);
}

Field Mapping Between Order and CRM

Similarly for deals: order total → OPPORTUNITY, status → STAGE_ID.

Status Mapping Configuration

When the order status changes on the site, call crm.deal.update with the new stage. Save the Bitrix24 deal ID in the order property B24_DEAL_ID or in b_sale_order_props_value. Time saved: instead of 5 minutes of manual update — 0.5 seconds automatically.

Storing Order–Deal Link

// Сохраняем ID сделки в свойствах заказа
$dealProp = $orderProps->getItemByOrderPropertyCode('B24_DEAL_ID');
if ($dealProp) {
    $dealProp->setValue($dealId);
    $order->save();
}

Product Rows

crm.deal.productrows.set replaces the entire product list. Each item:

$products[] = [
    'PRODUCT_NAME' => $basketItem->getField('NAME'),
    'PRICE'        => $basketItem->getPrice(),
    'QUANTITY'     => $basketItem->getQuantity(),
    'CURRENCY_ID'  => 'RUB',
    'PRODUCT_ID'   => 0, // если нет каталога в Б24 — 0
];

If Bitrix24 has a product catalog synchronized with the site via CommerceML, pass the real PRODUCT_ID for correct product analytics.

How to Avoid Contact Duplicates?

On repeat orders, check for existing contact via crm.duplicate.findByComm by phone. If a contact exists, use its ID — do not create a duplicate. The new deal links to the existing contact. According to Bitrix24 REST API documentation, the crm.duplicate.findByComm method prevents duplicates. Manual check takes 5 minutes per order, automatic — 0.5 seconds.

Typical Errors and Their Solutions

Our Approach and Process

We use the stack: PHP 8.1+, infoblocks v2.0, Bitrix ORM, REST API (cloud or on-premise). Handlers are wrapped in try-catch, errors are written to an HL-block. Webhook permissions are set: crm.contact.add, crm.deal.add, crm.deal.update, crm.duplicate.findByComm, crm.deal.productrows.set. We adhere to limits — no more than 2 requests per second.

Work Stages

1. Analysis — study order structure, sales funnel, identify non-standard fields.
2. Design — create field and status mapping scheme, agree with you.
3. Implementation — write handler, configure webhook, test on a sample order.
4. Testing — check deal creation/update, duplicates, error handling.
5. Deployment — roll out to production, monitor logs for the first day, provide warranty.

Timeline Estimates

Basic setup for new orders — 6–8 hours. Full two-way status synchronization — 2–3 business days. Cost is calculated individually after auditing your site. We'll assess your project for free — request a consultation.

Typical problems arise from missing duplicate checks or incorrect status mapping. Our experience shows: 80% of errors are solved by adding checks and async processing. We guarantee stable integration and post-launch support. Contact us for a detailed audit of your system.

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.