Courier Delivery Route Optimization in 1C-Bitrix

Imagine: a courier service processes 20 orders daily. The dispatcher spends half an hour planning the route, but half of the clients are still dissatisfied with delays. What's the problem? Usually it's manual planning and lack of accurate traffic and time window data. Integrating 1C-Bitrix with routing services—Yandex.Routing or OR-Tools—solves this in 5 seconds. Mileage is reduced by 33%, and on-time delivery rates increase from 60% to 95%. This is not just fuel savings—it's fulfilling commitments to clients and reducing operational costs.

How integration solves the traveling salesman problem

The essence is simple: Bitrix collects order data—addresses, time windows, weight. The external service solves the NP-hard traveling salesman problem—builds the optimal visiting order. The result is passed back as route sheets. We make this connection transparent and reliable. Performance: 20 points processed in 5 seconds, while manual planning takes 30 minutes—a 360x difference.

Step 1: Data preparation

To build a route, you need a list of addresses with coordinates and time windows. Addresses are taken from order properties:

$deliveries = \Bitrix\Sale\OrderTable::getList([
    'filter' => [
        'STATUS_ID' => 'TD',  // статус "к доставке сегодня"
        '>=DATE_STATUS' => new \Bitrix\Main\Type\Date(),
    ],
    'select' => ['ID'],
])->fetchAll();

$points = [];
foreach ($deliveries as $row) {
    $order = \Bitrix\Sale\Order::load($row['ID']);
    $props = $order->getPropertyCollection();

    $points[] = [
        'order_id'       => $row['ID'],
        'address'        => $props->getItemByOrderPropertyCode('ADDRESS')?->getValue(),
        'lat'            => $props->getItemByOrderPropertyCode('LAT')?->getValue(),
        'lon'            => $props->getItemByOrderPropertyCode('LON')?->getValue(),
        'time_from'      => $props->getItemByOrderPropertyCode('DELIVERY_TIME_FROM')?->getValue(),
        'time_to'        => $props->getItemByOrderPropertyCode('DELIVERY_TIME_TO')?->getValue(),
        'weight'         => $this->getOrderWeight($order),
    ];
}

Coordinates (LAT/LON) should be obtained during order placement—via Yandex or Google geocoding API from the entered address. Save them in the order's user properties.

Why accurate geocoding is essential for optimal routes

Without coordinates, the optimization service doesn't know exactly where the point is. Geocoding converts a text address into latitude/longitude. We implement it directly in the order form—an AJAX request to the geocoder when the address field is filled. Here's how it looks:

fetch(`https://geocode-maps.yandex.ru/1.x/?apikey=KEY&format=json&geocode=${encodeURIComponent(address)}`)
    .then(r => r.json())
    .then(data => {
        const pos = data.response.GeoObjectCollection.featureMember[0]?.GeoObject?.Point?.pos;
        if (pos) {
            const [lon, lat] = pos.split(' ');
            document.getElementById('lat-field').value = lat;
            document.getElementById('lon-field').value = lon;
        }
    });

The coordinates are silently saved to hidden form fields and end up in the order properties. The driver never knows—it's all automatic.

Step 2: Integration with the optimization service

After collecting the points, send them to the route optimizer API. Example with Yandex.Routing:

$httpClient = new \Bitrix\Main\Web\HttpClient();
$response = $httpClient->post(
    'https://courier.yandex.ru/api/v1/companies/{company_id}/routes',
    json_encode(['vehicles' => $vehicles, 'orders' => $points]),
    ['Authorization' => 'Bearer ' . YANDEX_COURIER_API_KEY]
);

$routes = json_decode($response, true);

The returned routes contain an ordered list of points for each courier. Save them to the bl_courier_routes table and assign to couriers via CRM tasks or a mobile app.

Step 3: Displaying the route to the courier

Create a mobile page or send the courier a link to the route in Google Maps or Yandex.Maps with waypoints. Format for Google Maps:

https://www.google.com/maps/dir/DEPOT_LAT,DEPOT_LON/STOP1_LAT,STOP1_LON/STOP2_LAT,STOP2_LON/...

Generate this link from the bl_courier_routes data and send it to the courier via SMS or email.

What route optimization delivers

Optimized routing is 30 times faster than manual planning and reduces mileage by 33%. Every saved kilometer reduces fuel consumption significantly, and together with savings on courier and dispatcher time, the delivery budget can drop by 30–40%.

Typical setup mistakes

How we automate delivery turnkey

We perform the full cycle of work:

1. Create order user properties LAT, LON, DELIVERY_TIME_FROM, DELIVERY_TIME_TO.
2. Implement AJAX geocoding via Yandex or Google.
3. Set up an agent to collect points and call the optimizer API.
4. Create the bl_courier_routes table for storing routes.
5. Generate map links and send them to couriers.
6. Train dispatchers and couriers.
7. Provide source code and documentation for modifications.

Our clients save an average of 30,000 rubles per month on fuel and dispatcher salaries. Certified specialists, transparent code, post-delivery support. Contact us for a delivery system audit—we'll estimate budget and timeline within one day. Order turnkey setup and get a consultation on your task.

Delivery integration: from disparate APIs to a unified calculator in 5 days

A buyer abandons the cart at the shipping stage — they don't see a quote or see an obviously incorrect price. Each such case loses conversion. Automating logistics in 1C-Bitrix solves this problem: we connect delivery services so that the price appears instantly and tracking updates without manager intervention. Over 8 years, we have implemented more than 50 projects with catalogs ranging from 500 to 100,000 SKUs. Average time to connect one carrier is 4 days.

How to accelerate the connection of delivery services to 1C-Bitrix?

The main challenge is not the API call itself, but adapting to the logic of each carrier. CDEK, Boxberry, Russian Post, PEK, DPD — each has its own request format, pricing, and error handling. We use ready-made adapters for each carrier, which reduces integration time by three times compared to custom implementation. Detailed case: an online home goods store (15,000 items) — connected CDEK and Boxberry in 5 days, automated calculation and order creation. Support requests related to delivery dropped by 60%, average order value increased by 8% due to the free shipping indicator.

Why is each carrier's API a separate challenge?

CDEK — volumetric weight and pickup point map

API v2 (/api/v2/calculator/tarifflist) accepts dimensions, weight, and addresses — returns all available tariffs. Pitfalls: volumetric weight is calculated using the formula (L × W × H) / 5000. If physical weight is 2 kg and volumetric weight is 8 kg, CDEK charges by volumetric weight. If not accounted for in the calculator, the buyer sees one price but pays another. The pickup point map is loaded via /deliverypoints. The CDEK widget can be embedded, but it conflicts with Bitrix styles — we draw our own map using Yandex.Maps. Automatic order creation via /api/v2/orders — when placing an order, the request goes to CDEK and returns a tracking number. Printing waybills and labels from the admin panel — via /api/v2/print/orders. Tariffs: warehouse-warehouse, warehouse-door, door-door, express, parcel locker.

Boxberry — extensive pickup point network in regions

The most extensive pickup point network in small towns. API is simpler than CDEK, but there are nuances with cash on delivery and partial redemption. Pickup point map with filters: fitting, card payment, weekend operation. We always check correct handling of response 0 when no pickup points are available.

Russian Post — stability at the cost of speed

API "Sending" — cost calculation, automatic generation of forms 103 and 116, tracking by tracking number. Tariffs: parcel, printed matter, EMS. International shipments. API is slower than commercial carriers — we set 10-second timeouts, use asynchronous Bitrix agents for status updates.

PEK — heavy loads and groupage

When you need to ship a sofa or equipment. Calculation of groupage cargo, insurance, crate. Delivery to terminal and door-to-door. PEK terminal indices are loaded into an infoblock for auto-completion.

DPD — express delivery with time slots

DPD across Russia and abroad. Delivery within a selected time interval, return of signed documents. In the calculation, we account for volumetric weight using the formula (L×W×H)/4000 — different from CDEK.

How to combine different carriers in a single calculator?

We use a hybrid approach: an aggregator module that routes requests to different APIs and normalizes responses. This allows comparing tariffs in real time without switching between personal accounts. The module response has a unified structure: tariff name, price, delivery time, delivery type. Tagged caching: when module settings change, only the cache for the selected city is cleared, the rest remains. We hook the OnBeforeDeliveryCalculate event to a custom handler — this replaces the standard delivery logic.

Cost calculation: what pitfalls are encountered?

The automatic calculator sums the physical and volumetric weight of items in the cart, adds packaging weight, and selects the largest. Sounds simple, but:

• Dimensions must be filled for each item. No dimensions — no calculation. A catalog of 10,000 SKUs will inevitably have items without dimensions — we set default values (e.g., 0.1×0.1×0.1 m) and warn the manager via a mail event.
• Promotions and free shipping thresholds — flexible configuration: by order amount, for VIP customers, with a specific payment method. Implemented via custom cart properties.
• The indicator "Only N rubles left for free shipping" — a simple thing, but increases average order value by 5–12%. Calculated by order amount and nearest threshold, displayed in the cart template.

How to automate tracking, pickup, and courier delivery?

Tracking. Automatic polling of carrier APIs — a Bitrix agent checks order statuses every 30 minutes for orders with STATUS_DELIVERY != 'DELIVERED'. Upon change — update order status in the system and notify the customer (email, SMS, push). Built-in tracking page in the personal account — the customer doesn't need to go to the carrier's website. Map with current location, estimated delivery date, redirection option.

Pickup. Own pickup points on the map: addresses, schedule, contacts. Search for the nearest by customer address. Real-time availability check, reservation until a specific time. QR code for quick pickup and SMS about readiness.

Courier delivery. Delivery zones with different costs. 2-hour slots, courier schedule management, order limit per slot. Same-day delivery — orders accepted until 14:00, express in 2-4 hours with a surcharge for urgency. Integration with navigation for route optimization.

Multi-warehouse. Multiple warehouses with addresses and service zones. Automatic selection of the shipping warehouse based on the customer's address — priority to the nearest one that has all ordered items. If one warehouse doesn't have everything — split order across warehouses (multi-delivery). Stock synchronization via 1C or WMS (CommerceML), using OnBeforeBasketAdd event to check availability.

Comparison of transport companies

What stages does connecting delivery services consist of?

1. Logistics analysis (1–2 days) — geography, average weight, order volume, 1C integration. We recommend a combination of carriers.
2. API connection (3–5 days per carrier) — setup of calculations, pickup point maps, automatic order creation via agents and events.
3. Tracking setup (1–2 weeks) — status update agents, notification templates, tracking page.
4. Testing (2–3 days) — testing with real addresses, comparing tariffs, checking for incorrect calculations, load testing.
5. Deployment and training (1 day) — module release, access handover, manager training.
6. Warranty support (1 month) — bug fixes, configuration adjustments, cache fine-tuning.

Estimated implementation timelines

Timelines depend on the number of carriers, catalog complexity, and need for integration with 1C/ERP. Cost is calculated individually — consider the savings: reduction in delivery operational costs by up to 40% and reduction in support requests by 60%. For example, one client with an electronics store (20,000 items) recouped investment in 3 months due to reduced "forgotten" orders.

Ready to accelerate your online store's logistics? Contact us — we'll help select the optimal carrier combination for your assortment and budget. Request a consultation, and we'll prepare a proposal within 1 business day.