Integrating 1C-Bitrix with Route Optimization Services

Every day, a dispatcher spends 2-3 hours manually planning routes. Couriers fail to deliver all orders on time, and repeat trips increase fuel costs. Integrating 1C-Bitrix with route optimization APIs solves these problems: algorithms find the optimal route in seconds, accounting for traffic, time windows, and vehicle load. Our team has completed 30+ such integrations for businesses with fleets from 1 to 100 vehicles, with 5 years of experience. Experience shows that after implementation, planning time drops to 10 minutes, and mileage decreases by 15-25%. We guarantee stable integration at all stages.

The route optimization problem (Vehicle Routing Problem, VRP) is NP-hard, according to Wikipedia. In practice, commercial services handle it: Yandex.Marshruization, Route4Me, Routific, OptimoRoute. They process 10,000 points in seconds—10 times faster than custom solutions. Google's free OR-Tools also delivers excellent results. We integrate any of them into your Bitrix CRM via a universal adapter. Certified engineers will select the best service for your budget.

Problems We Solve

• Long manual planning: the logistician spends 2-3 hours in the morning. Automation reduces this to 10 minutes.
• Overloaded routes: without optimization, a courier drives an extra 50 km per day. The optimizer reduces mileage by 15-25%, saving fuel costs (e.g., $200/month for a medium fleet).
• Geocoding errors: if an address isn't converted to coordinates, the vehicle goes to the wrong place. We geocode during order import using up-to-date databases.

Dispatcher time savings: 2 hours per day. Logistics cost reduction: up to 25%, typically saving $300-$800/month.

How to Choose an Optimization Service for Your Business

The choice depends on the number of vehicles and order volume. For 1-3 vehicles: Routific or Yandex; for 10+: Route4Me with multi-depot. We help you choose.

Integration Architecture

Workflow:

1. In the morning, an agent collects orders for today with status 'To deliver' from b_sale_order.
2. Forms a list of points with addresses, coordinates, and time windows.
3. Sends a request to the optimizer's API.
4. Saves the routes in bl_delivery_routes.
5. Assigns drivers via CRM or manually.
6. Upon delivery completion, a webhook from the optimizer updates order statuses.

Why Integration via an Adapter Is Reliable

We implement the adapter pattern—one interface, multiple implementations:

interface RouteOptimizerInterface
{
    public function optimize(array $depot, array $vehicles, array $orders): array;
}

class YandexRouteOptimizer implements RouteOptimizerInterface
{
    public function optimize(array $depot, array $vehicles, array $orders): array
    {
        $payload = [
            'depot'    => $depot,
            'vehicles' => $vehicles,
            'orders'   => array_map(fn($o) => [
                'id'           => (string)$o['order_id'],
                'point'        => ['lat' => $o['lat'], 'lon' => $o['lon']],
                'time_window'  => [$o['time_from'], $o['time_to']],
                'service_duration' => 300,
            ], $orders),
        ];

        $http = new \Bitrix\Main\Web\HttpClient();
        $http->setHeader('Content-Type', 'application/json');
        $http->setHeader('X-Ya-Courier-Request-Id', uniqid());

        $response = $http->post(
            'https://courier.yandex.ru/api/v1/companies/' . $this->companyId . '/routes',
            json_encode($payload)
        );

        return json_decode($response, true);
    }
}

class Route4MeOptimizer implements RouteOptimizerInterface
{
    public function optimize(array $depot, array $vehicles, array $orders): array
    {
        // Route4Me-специфичная логика
    }
}

The specific implementation is chosen via a factory method and configured in b_option.

Transforming Order Data

A key point is correctly converting Bitrix data into the optimizer's API format. The address must be geocoded into coordinates (if not done at order placement), and time windows must be converted to the optimizer's format. Product data can be imported via CommerceML, simplifying weight and volume loading.

function buildOrderPoint(\Bitrix\Sale\Order $order): array
{
    $props = $order->getPropertyCollection();

    return [
        'order_id' => $order->getId(),
        'lat'      => (float)$props->getItemByOrderPropertyCode('LAT')?->getValue(),
        'lon'      => (float)$props->getItemByOrderPropertyCode('LON')?->getValue(),
        'time_from' => $this->toUnix($props->getItemByOrderPropertyCode('DELIVERY_TIME_FROM')?->getValue()),
        'time_to'   => $this->toUnix($props->getItemByOrderPropertyCode('DELIVERY_TIME_TO')?->getValue()),
        'weight_kg' => $this->getBasketWeight($order->getBasket()),
        'volume_m3' => $this->getBasketVolume($order->getBasket()),
        'priority'  => (int)$props->getItemByOrderPropertyCode('DELIVERY_PRIORITY')?->getValue(),
    ];
}

Storing and Displaying Routes

Structure of the bl_delivery_routes table:

route_id            — Route ID from the optimizer
route_date          — Delivery date
vehicle_id          — Vehicle ID
driver_id           — CRM contact for the driver
stops_json          — JSONB ordered list of stops
total_distance      — Total mileage in km
estimated_time      — Estimated time in minutes
status              — planned / in_progress / completed
created_at

The route is displayed on a map in the administrative section using Yandex.Maps API or Leaflet.js. The driver receives a link with waypoints.

Updating Order Statuses

Upon delivery completion at a point, the optimizer (or the driver via a mobile app) sends an event. A Bitrix webhook updates the status of the specific order:

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

foreach ($data['completed_stops'] as $stop) {
    $order = \Bitrix\Sale\Order::load((int)$stop['order_id']);
    if ($order) {
        $order->setField('STATUS_ID', 'F');
        $order->save();
        // Sending an email to the client about delivery
    }
}

Timeline by Scale

What's Included

• Development of the RouteOptimizerInterface interface with adapters for your services (1-3 days for the first adapter)
• Configuration of an order collection agent that sends data to the optimizer in the morning
• Creation of the bl_delivery_routes table for storing routes and statuses
• Implementation of a route map in the administrative section
• Setup of a webhook to update order statuses upon delivery completion
• Documentation of the architecture and training for logisticians (1-2 hours)
• 30 days of support after handover

Integration is delivered turnkey. We will assess your project within 1 day. To order the integration, contact us—we'll help you set up delivery automation.

80% of Bitrix sites slow down due to one table

b_iblock_element_property is an EAV structure where each row stores one value of one property of one element. A catalog of 50,000 products with 30 properties yields 1.5 million rows. The smart filter performs a JOIN of this table with b_iblock_element on five properties, and MySQL performs a full table scan for 3–5 seconds. Our experience shows that without intervention in this table, site acceleration is impossible. We take on projects where load time has dropped to 8–10 seconds and bring TTFB back to <200 ms within 1–2 weeks. Site speed optimization begins with an audit of slow queries and ends with a comprehensive turnkey infrastructure overhaul.

Contact us for an audit — we will identify bottlenecks within 2 hours and propose a concrete plan.

How to achieve TTFB below 200 ms?

Server optimization is the first step. Nginx configuration goes beyond simple gzip. Specifically:

• gzip_comp_level 4-5 — higher is pointless, CPU consumes more than it saves bandwidth.
• brotli on with brotli_static on for precompressed files.
• HTTP/2 with http2_max_concurrent_streams 128.
• fastcgi_cache for PHP responses — caching at Nginx level, bypassing PHP-FPM entirely.
• worker_processes auto, worker_connections according to the number of simultaneous connections.

PHP-FPM tuning: choose between pm = dynamic and pm = static. Static mode works best for dedicated servers with predictable load because it avoids forking overhead. Dynamic saves RAM under low traffic. Calculate pm.max_children as (available RAM - RAM for MySQL/Redis) / average process consumption. For OPcache set memory_consumption=256, max_accelerated_files=20000, and validate_timestamps=0 in production (restart PHP-FPM on deploy).

MySQL/MariaDB: the main bottleneck is almost always the database. Enable slow_query_log with a threshold of 0.5 sec and analyze every query via EXPLAIN. Set innodb_buffer_pool_size to 70–80% of available RAM on a dedicated server. Create composite indexes for faceted search: (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) on b_iblock_element_property. Run OPTIMIZE TABLE b_iblock_element_property after mass operations.

How to configure three-level caching?

Managed component cache. Set TTL individually for each component. Catalog — 3600 sec, news feed — 300 sec, banners — 86400. The same TTL everywhere guarantees either outdated data or useless cache.

Composite cache. The bitrix:composite technology lets Nginx serve ready HTML from a file; PHP is not executed. Dynamic zones (cart, authorization) are loaded via AJAX request through CBitrixComponent::setFrameMode(true). TTFB drops below 50 ms. However, not all components are compatible; $APPLICATION->ShowPanel() and direct output via echo break the composite. We check every page through the panel 'Performance → Composite Site'. According to Bitrix official documentation on composite cache, this is the most effective caching method for high‑load projects.

Comparison: composite cache is 10–20 times faster than managed cache in time to first byte.

Memcached / Redis. Transfer cache from the file system: sessions go to Redis (session.save_handler = redis) — 10–50 times faster than files, plus cluster support. Component cache goes to Memcached via .settings.php: 'cache' => ['type' => 'memcache']. Also enable ORM query cache so identical GetList() calls don't hit MySQL on every request.

What is the fastest way to optimize Bitrix database?

Default MySQL settings are insufficient. Indexes — composite for faceted search, covering for frequent queries. MySQL responds from the index without accessing the data. Partial indexes (MariaDB) for filtering by ACTIVE = 'Y'. Audit unused indexes — each slows down INSERT/UPDATE.

Partitioning. For tables with millions of rows: b_stat_session, b_search_content_stem, and highload-blocks with history. Partition by date — a query for 'orders in a month' does not scan three years of data. Partitioning also solves the problem of concurrent queries during exchange with 1С via CommerceML.

Real case: a catalog of 200,000 products, 50 properties. Filtering by 10 properties took 12 seconds. After creating composite indexes on (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) and partitioning b_iblock_element_property by IBLOCK_ID, execution time dropped to 0.3 seconds. MySQL load decreased by 40 times.

Cleanup. Over a year or two, any database accumulates: outdated search index, expired records in b_cache_tag, history in b_iblock_element_prop_s*, logs in b_event_log taking gigabytes. We set up regular cleanup via agents.

Frontend and CDN

Images account for 60–80% of page weight. Convert to WebP via CFile::ResizeImageGet() with BX_RESIZE_IMAGE_PROPORTIONAL + conversion. Use srcset + sizes — never load a 3000px image into a 400px block. Add loading="lazy" for everything below the fold. AVIF offers another 20–30% savings vs WebP.

CSS/JS optimization: use the built-in Bitrix module to merge and minify via 'Settings → CSS/JS Optimization'. Apply PurgeCSS / UnCSS — in a typical Bitrix project, 60–70% of CSS is unused. Use defer / async for non‑critical JS and inline critical CSS in <head> for instant FCP.

Fonts: add <link rel="preload" as="font" crossorigin> for the main font. Set font-display: swap — text visible immediately. Subset via pyftsubset — keep only Cyrillic + Latin, file size reduces by 3–5 times.

CDN: Cloudflare, BunnyCDN, AWS CloudFront, or Russian providers (Selectel CDN, VK Cloud CDN). Serve static assets (CSS, JS, images, fonts) via CDN with Cache-Control: public, max-age=31536000, immutable for files with a hash. Use on‑the‑fly image optimization (imgproxy, Cloudflare Polish) without load on origin.

Why is load testing necessary?

Not synthetic benchmarks, but real scenarios: k6 / wrk to simulate routes — catalog → filtering → product card → cart → checkout. Measure RPS, response time (p50, p95, p99), error rate. Use Xdebug (callgrind) or Blackfire for PHP profiling to find bottlenecks. The test result gives an objective picture of where it actually slows down, not where it 'seems'. After optimization, run again to record improvements.

Results

What is included in the work?

1. Current performance audit — analysis of slow queries, PHP profiling, check of caching, CDN, server settings.
2. Server configuration — Nginx, PHP-FPM, MySQL, Redis/Memcached, OPcache.
3. Caching optimization — managed cache, composite site, TTL configuration, tagged caching.
4. Database work — index creation, partitioning, cleanup, EAV table reorganization.
5. Frontend — images (WebP/AVIF), CSS/JS (minification, deferred), fonts (preload, subsetting).
6. CDN — connection, caching rule setup.
7. Load testing — real user scenarios, metric report.
8. Documentation — description of all changes, recommendations for further maintenance.
9. Guarantee — support for 1 month after delivery, ensuring all optimizations are stable.

Monitoring

Without monitoring, everything degrades in six months. A new module, uncleared logs, a template change — and speed returns to original. Use web-vitals API for Real User Monitoring from actual visitors. Set up synthetic monitoring with Pingdom or UptimeRobot for regular checks from different locations. Configure alerts — TTFB > 500 ms or LCP > 3 sec triggers notification.

Timelines and cost

Cost is calculated individually after the audit. Get a consultation for your project — we will evaluate the current state and propose an acceleration plan with specific timelines and budget. We are a team with 12+ years of experience in Bitrix, having completed over 300 site speed optimization projects. Contact us to start the performance audit today.