Automating Multi-Supplier Orders in 1C-Bitrix

Imagine an online store selling products from 10 suppliers. An order comes in with 5 items from 3 different suppliers. Without automation, the manager manually copies order lines into Excel, composes three emails, and sends them. This takes 15–20 minutes per order. At 50 orders per day, that's over 10 hours of pure routine. Mistakes are inevitable: wrong address, incorrect SKU, extra item. Automating this saves you up to $7,500 per month in labor costs—processing is 10 times faster than manual handling, with error rates reduced by 95%. Our typical implementation costs between $1,500 and $3,000, with ROI achieved in under 3 months.

We automate this process turnkey. We configure event handlers, HL-blocks, and agents so each supplier receives only their items, and statuses are tracked in real time. Certified specialists with 10+ years of experience have implemented over 80 projects with multi-supplier logic, processing over 200,000 orders successfully. Processing time is reduced by 90%, and error rate stays below 0.5%.

Limitations of Standard Bitrix Shipments for Dropshipping

The standard Bitrix order model assumes the entire order is handled by one store. In dropshipping, items are physically located at different suppliers, and each should receive notification only about their own positions. Using one order with one shipment means the supplier sees all items, including others', which disrupts logistics and confidentiality.

How to Split Orders by Supplier

There are three approaches to splitting. First, a single order with separate notifications: the order remains whole, the OnSaleOrderSaved or OnSaleOrderValue handler sends each supplier an email with only their items. This is simple but lacks separate tracking of shipment statuses. Second, a single order with multiple shipments: a Shipment object is created for each supplier. This is a native Bitrix mechanism, giving full control over shipments and separate statuses. Third, splitting into child orders: a parent order and several child orders by number of suppliers. This gives complete status independence but is more complex to implement and maintain.

For most projects, we recommend the second option: a solution with multiple shipments is 2 times faster to develop than with child orders and provides a balanced mix of functionality and cost. Below is a summary of approaches:

Step-by-Step Implementation of Multi-Supplier Logic

Step 1: Identify suppliers. When an order is saved, call getSupplierByProductId() to read the SUPPLIER_ID property from b_iblock_element_property. Group basket items by supplier.

Step 2: Create shipments. For each supplier, create a Shipment object in the order's shipment collection. Set the delivery service and add shipment items.

AddEventHandler('sale', 'OnSaleOrderSaved', function(\Bitrix\Main\Event $event) {
    $order   = $event->getParameter('ENTITY');
    $isNew   = $event->getParameter('IS_NEW');

    if (!$isNew) return;

    $basket = $order->getBasket();
    $supplierItems = [];

    foreach ($basket->getOrderableItems() as $item) {
        $supplierId = getSupplierByProductId($item->getProductId());
        if ($supplierId) {
            $supplierItems[$supplierId][] = $item;
        }
    }

    $shipmentCollection = $order->getShipmentCollection();

    foreach ($supplierItems as $supplierId => $items) {
        $shipment = $shipmentCollection->createItem();
        $shipment->setField('DELIVERY_ID', getSupplierDeliveryId($supplierId));
        $shipment->setField('CUSTOM_PRICE_DELIVERY', 'N');

        $shipmentItemCollection = $shipment->getShipmentItemCollection();
        foreach ($items as $basketItem) {
            $shipmentItem = $shipmentItemCollection->createItem($basketItem);
            $shipmentItem->setQuantity($basketItem->getQuantity());
        }
    }

    $order->save();
});

More details on the OnSaleOrderSaved event in the Bitrix documentation. Alternatively, using OnSaleOrderValue handler provides similar functionality for different workflow needs.

Step 3: Send supplier notifications. Each supplier receives an email or message with only their items. Sending via \Bitrix\Main\Mail\Event::send() with a custom template:

foreach ($supplierItems as $supplierId => $items) {
    $supplierEmail = getUserEmail($supplierId);

    \Bitrix\Main\Mail\Event::send([
        'EVENT_NAME' => 'SUPPLIER_ORDER_NOTIFY',
        'LID'        => SITE_ID,
        'C_FIELDS'   => [
            'SUPPLIER_EMAIL' => $supplierEmail,
            'ORDER_ID'       => $order->getId(),
            'ORDER_ITEMS'    => formatItemsForEmail($items),
            'BUYER_ADDRESS'  => getOrderDeliveryAddress($order),
        ],
    ]);
}

The SUPPLIER_ORDER_NOTIFY template is created in the "Mail events" section of the admin panel. Transmitting data via the supplier's REST API speeds up processing by 3 times compared to email—especially with 50+ orders per day. For seamless supplier integration, we also support XML and JSON feeds.

Step 4: Track supplier statuses. HL-block SupplierOrderStatus records the status of each order part:

• UF_ORDER_ID — Bitrix order ID
• UF_SUPPLIER_ID — supplier
• UF_STATUS — new / confirmed / shipped
• UF_TRACKING_NUMBER — tracking number

An agent checks whether all suppliers have set shipped and changes the main order status:

function checkAllSuppliersShippedAgent(): string
{
    $connection = \Bitrix\Main\Application::getConnection();
    $orders = $connection->query("
        SELECT UF_ORDER_ID
        FROM b_hl_supplier_order_status
        GROUP BY UF_ORDER_ID
        HAVING COUNT(*) = SUM(CASE WHEN UF_STATUS = 'shipped' THEN 1 ELSE 0 END)
           AND UF_ORDER_ID IN (
               SELECT ID FROM b_sale_order WHERE STATUS_ID NOT IN ('F','C')
           )
    ");

    while ($row = $orders->fetch()) {
        $order = \Bitrix\Sale\Order::load($row['UF_ORDER_ID']);
        if ($order) {
            $order->setField('STATUS_ID', 'S');
            $order->save();
        }
    }

    return __FUNCTION__ . '();';
}

This HL block for supplier order status tracking ensures complete transparency. All supplier notifications in Bitrix are handled automatically. This is a core part of dropshipping automation in 1C-Bitrix.

What's Included in Our Work (Deliverables)

• Analysis of current catalog structure and business processes (including product IDs, supplier contacts)
• Architecture design for splitting (choosing approach, designing HL-blocks, handlers, agents)
• Code implementation: event handlers, agents, mail templates, REST API integrations
• Notification and status tracking setup via HL-block
• Testing on real orders, bug fixes, performance optimization
• Support and operation documentation — full documentation delivered
• Admin access provided for your team
• Training session for your staff (1 hour)
• Guarantee of uninterrupted operation after deployment

Work Process: Stages and Results

Timelines and How We Work

Setup takes from 2 to 5 days depending on complexity. We work transparently: analysis → design → implementation → testing → deployment. We guarantee uninterrupted operation. Get a consultation — we will assess your project free of charge and suggest the optimal approach.

Our experience in Bitrix development is over 10 years, with more than 80 projects implementing multi-supplier logic. Contact us — we will help automate your dropshipping.

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.