Bitrix 1C Order Sync: Inventory Conflicts & Real-Time Exchange

A retail chain faces three simultaneous order streams: the Bitrix online store, POS terminals in physical stores, and phone orders. Without synchronization, stock is reserved multiple times in parallel—leading to up to 15% of orders being canceled due to insufficient goods. We, engineers with 10+ years of production experience, ensure two-way exchange of orders and stock between Bitrix and 1C in real time. This means: online payment instantly reserves goods in the warehouse, POS sales immediately reduce online stock, and conflicts are eliminated. Turnkey—from architecture selection to staff training.

Why three isolated order streams destroy inventory accounting?

Typical scenario: a customer pays online for a product that was already sold via POS 10 minutes ago. Bitrix deducts stock only after order creation, while the POS sale already reduced the physical stock. The online order is accepted but cannot be fulfilled. Implementing synchronization reduces double-selling losses by 15–20%.

How to choose the master of synchronization?

80% of conflicts disappear if the master is chosen before development starts. Consult our experts during the audit phase.

Synchronization architecture: protocols and schemes

1C as master

1C is the source of truth for orders and stock. Bitrix transmits online orders to 1C, offline sales are recorded there, and stock is synchronized back.

Bitrix as master

All orders (online and offline via POS) are collected in Bitrix; 1C receives data for accounting.

Synchronization via CommerceML

The standard 1C-Bitrix exchange (/bitrix/admin/1c_exchange.php) covers the basic scenario. Configuration is in the sale module. As stated in 1C-Bitrix documentation, standard exchange via CommerceML is suitable for batch exchange of orders and stock. Limitation: batch every N minutes. For real-time, webhooks or queues are needed.

REST API and message queue

For large chains and high load, a RabbitMQ queue with less than 2-second latency is recommended.

Implementation: reservation and conflicts

Offline orders from POS

When a cashier completes a sale via POS, should we create an order in Bitrix via API or only deduct stock?

Example of creating an offline order via REST API:

// Creating an offline order in Bitrix
\Bitrix\Main\Loader::includeModule('sale');
\Bitrix\Main\Loader::includeModule('catalog');

$order = \Bitrix\Sale\Order::create(SITE_ID, $userId);
$order->setField('CURRENCY', 'RUB');
$order->setField('USER_DESCRIPTION', 'In-store sale: ' . $storeName);

$basket = \Bitrix\Sale\Basket::create(SITE_ID);
foreach ($items as $item) {
    $basketItem = $basket->createItem('catalog', $item['PRODUCT_ID']);
    $basketItem->setFields([
        'QUANTITY'  => $item['QUANTITY'],
        'CURRENCY'  => 'RUB',
        'LID'       => SITE_ID,
        'PRODUCT_PROVIDER_CLASS' => '\CCatalogProductProvider',
    ]);
}
$order->setBasket($basket);

// Mark order source
$order->setField('STATUS_ID', 'F');  // Completed — offline sale finished
$order->setField('ADDITIONAL_INFO', json_encode([
    'source' => 'offline',
    'store'  => $storeId,
    'pos_transaction_id' => $transactionId,
]));

$result = $order->save();

Stock reservation on online order

Critical point is reservation timing. Bitrix manages reservations via b_catalog_store_product and b_sale_product_reserve. For Click & Collect, reserve at a specific warehouse.

Real-time stock sync

Stock changes on either side must be instantly reflected. Use an event queue:

// On stock change — add to queue
\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'catalog', 'OnProductUpdate',
    function (\Bitrix\Main\Event $event) {
        $productId = $event->getParameter('ID');
        $fields = $event->getParameter('FIELDS');

        if (isset($fields['QUANTITY'])) {
            // Push to sync queue with 1C
            \Local\Queue\InventorySync::push([
                'product_id' => $productId,
                'quantity'   => $fields['QUANTITY'],
                'timestamp'  => time(),
            ]);
        }
    }
);

Parallel sales conflicts

Solution — atomic stock deduction at DB level:

-- Atomic deduction with check
UPDATE b_catalog_store_product
SET QUANTITY = QUANTITY - 1
WHERE PRODUCT_ID = ? AND STORE_ID = ? AND QUANTITY >= 1;

-- If affected_rows = 0 — no stock, reject order

Implemented in Bitrix via CCatalogProductProvider.

How we do it: a case of a chain with 10,000 SKUs

Our client — a 12-store chain with 3 online streams and offline sales via 1C:Retail. Standard CommerceML caused a 15-minute delay. Solution: a RabbitMQ queue + custom agent with less than 2-second latency. Conflicts resolved by the first-to-commit principle. Outcome — 99.9% stock accuracy. Paid back in 2 months.

What is included in the work and process

• Audit of current architecture
• Master system and protocol selection
• Setup of order, status, and stock exchange
• Custom agent development
• Load testing
• Documentation and training
• 1 month support

Process: analysis (1–2 days) → design (1–2) → implementation (3–5) → testing (2–3) → deployment (1). Timeline: 5 to 10 working days.

Guarantee: work is performed using official Bitrix and 1C documentation. Asynchronous processing is used to minimize losses.

Contact us for a free audit of your setup. Get a synchronization plan for your business. Order integration and forget about stock problems.

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.