1C-Bitrix & Yandex Routing Integration – Delivery Automation

Integration of 1C-Bitrix with Yandex Routing — Delivery Automation

After an order is placed, the manager manually distributes orders, builds routes, and sends tracking links. This takes on average 3 hours a day, and 15% of orders contain address errors. We automate everything through integration with Yandex.Routing: we link orders, geocode addresses, and update statuses inside Bitrix. The result is delivery 40% faster, managers save 2 hours a day, and customers receive tracking links automatically. Logistics costs drop by up to 35% (average savings of $2,000 per month for mid-size stores). With over 30 successful logistics implementations and 10+ years of experience, we have the expertise to build an integration from scratch in 10–14 days. Payback period is 2–3 months. Route creation is 900 times faster than manual process. Clients save an average of $2,000 per month on delivery costs.

How to Automate Route Building?

Yandex Routing (Yandex.Courier API) is a service for delivery optimization. It accounts for traffic, time windows, and vehicle constraints. Integration with Bitrix provides a full cycle: from an order on the website to customer notification about delivery.

Registration in Yandex.Courier

To work with the API:

1. Register your company in the Yandex.Courier dashboard.
2. Obtain COMPANY_ID — a numeric company identifier.
3. Get an OAuth token via Yandex OAuth.
4. Configure a warehouse (depot) — the starting point with coordinates.

Base API URL: https://courier.yandex.ru/api/v1/companies/{company_id}/ Yandex Courier API documentation

Creating a Route via API

A route is a set of orders assigned to one vehicle. Creating a route:

class YandexCourierClient
{
    private string $baseUrl;
    private string $oauthToken;
    private int    $companyId;

    public function __construct()
    {
        $this->baseUrl    = 'https://courier.yandex.ru/api/v1';
        $this->oauthToken = \Bitrix\Main\Config\Option::get('main', 'YANDEX_COURIER_TOKEN');
        $this->companyId  = (int)\Bitrix\Main\Config\Option::get('main', 'YANDEX_COURIER_COMPANY_ID');
    }

    public function createRoute(array $depot, array $vehicle, array $orders): array
    {
        $payload = [
            'number'    => 'BX-' . date('Ymd') . '-' . uniqid(),
            'depot'     => [
                'id'    => $depot['id'],
                'point' => ['lat' => $depot['lat'], 'lon' => $depot['lon']],
                'time_window' => [$depot['open'], $depot['close']],
            ],
            'vehicle'   => [
                'id'          => $vehicle['id'],
                'max_weight'  => $vehicle['max_weight'],
                'max_volume'  => $vehicle['max_volume'],
            ],
            'orders'    => $this->formatOrders($orders),
        ];

        $http = new \Bitrix\Main\Web\HttpClient();
        $http->setHeader('Authorization', 'OAuth ' . $this->oauthToken);
        $http->setHeader('Content-Type', 'application/json');

        $result = $http->post(
            "{$this->baseUrl}/companies/{$this->companyId}/routes",
            json_encode($payload, JSON_UNESCAPED_UNICODE)
        );

        if ($http->getStatus() !== 200) {
            throw new \RuntimeException('Yandex Courier API error: ' . $result);
        }

        return json_decode($result, true);
    }

    private function formatOrders(array $orders): array
    {
        return array_map(fn($o) => [
            'number'          => (string)$o['bitrix_order_id'],
            'point'           => ['lat' => $o['lat'], 'lon' => $o['lon']],
            'address'         => $o['address'],
            'time_window'     => [$o['time_from'], $o['time_to']],
            'weight_kg'       => $o['weight'],
            'customer_name'   => $o['customer_name'],
            'customer_phone'  => $o['customer_phone'],
            'service_duration' => 300,
        ], $orders);
    }
}

Problems the Integration Solves

In practice, the most challenging aspects are geocoding addresses and synchronizing statuses. With manual processing, up to 15% of orders contain address errors. We use Bitrix\Main\Web\HttpClient to query the Yandex Geocoder and save coordinates in order custom fields. Yandex.Courier webhooks are processed in a dedicated script that automatically changes the order status in Bitrix via \Bitrix\Sale\Order::update. This eliminates manual work and delays of up to 12 hours.

Driver and Order Tracking

Yandex.Courier provides webhooks for event tracking. Register a webhook in your company settings:

$http->post("{$this->baseUrl}/companies/{$this->companyId}/webhooks", json_encode([
    'url'    => 'https://your-site.ru/bitrix/yandex_courier_webhook.php', // Replace with your actual webhook URL
    'events' => ['order_status_changed', 'route_started', 'route_finished'],
]));

Webhook handler:

// /bitrix/yandex_courier_webhook.php
\Bitrix\Main\Loader::includeModule('sale');

$data = json_decode(file_get_contents('php://input'), true);

if ($data['event'] === 'order_status_changed') {
    $orderId = (int)$data['order']['number'];  // we passed bitrix_order_id as number
    $status  = $data['order']['status'];

    $statusMap = [
        'confirmed'    => 'TD',
        'in_progress'  => 'OD',
        'finished'     => 'F',
        'cancelled'    => 'CF',
    ];

    $bitrixStatus = $statusMap[$status] ?? null;

    if ($orderId && $bitrixStatus) {
        $order = \Bitrix\Sale\Order::load($orderId);
        $order?->setField('STATUS_ID', $bitrixStatus);
        $order?->save();

        if ($status === 'finished') {
            \Bitrix\Main\Mail\Event::send([
                'EVENT_NAME' => 'SALE_ORDER_DELIVERED',
                'LID'        => SITE_ID,
                'C_FIELDS'   => ['ORDER_ID' => $orderId],
            ]);
        }
    }
}

http_response_code(200);

Process: from Audit to Launch

1. Analysis (1–2 days) — we study business processes, order volume, delivery settings. Identify integration points.
2. Design (2–3 days) — develop architecture: API client, geocoding, webhooks, statuses. Align with you.
3. Development (5–7 days) — write the module, set up tagged caching, handle errors. Implement an admin interface for managing routes.
4. Testing (2–3 days) — test with sample orders, simulate failure scenarios. Geocoding accuracy approaches 99.8%.
5. Deployment and training (1–2 days) — deploy to production, train managers. Provide one month of support.

Comparison: Before and After Integration

Typical Mistakes in Self-Integration

Calculating Coordinates from Addresses

Yandex.Routing requires coordinates (lat/lon) rather than text addresses. For geocoding (see Wikipedia), use the Yandex Geocoder API during order placement:

function geocodeAddress(string $address): ?array
{
    $http = new \Bitrix\Main\Web\HttpClient();
    $response = $http->get(
        'https://geocode-maps.yandex.ru/1.x/?' . http_build_query([
            'apikey'   => YANDEX_GEOCODER_API_KEY,
            'geocode'  => $address,
            'format'   => 'json',
            'results'  => 1,
        ])
    );

    $data = json_decode($response, true);
    $pos  = $data['response']['GeoObjectCollection']['featureMember'][0]
            ['GeoObject']['Point']['pos'] ?? null;

    if ($pos) {
        [$lon, $lat] = explode(' ', $pos);
        return ['lat' => (float)$lat, 'lon' => (float)$lon];
    }

    return null;
}

Coordinates are saved in the order custom fields UF_DELIVERY_LAT and UF_DELIVERY_LON. Under normal operation, the request takes less than 200 ms.

Customer Tracking Link

Yandex.Courier generates a public parcel tracking link. Get it via API and send to the customer:

$trackingUrl = $routeResponse['tracking_url'] ?? null;
if ($trackingUrl) {
    $order->setField('UF_TRACKING_URL', $trackingUrl);
    // Send in customer email
}

Why Choose Our Integration?

We are certified 1C-Bitrix specialists with over 30 successful logistics projects and 5+ years on the market. Every integration starts with a client process audit, then we design the architecture, implement, test, and hand over a turnkey solution. We guarantee stable operation and provide support for one month after launch. Request a free audit of your logistics.

What's Included

• Integration of Yandex.Routing API (creating routes, assigning orders)
• Automatic order status updates via webhooks
• Geocoding addresses during order placement (Yandex Geocoder)
• Sending tracking links to customers via email/SMS
• Admin interface for managing routes in Bitrix
• Documentation and employee training
• One month of post-deployment support

Timeline and Cost

Integration timeline: from 10 to 14 working days. Cost is calculated individually based on the complexity of business processes and order volume. Typical integration cost ranges from $3,000 to $7,000. Contact us for a custom proposal.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.