Cross-Docking on Bitrix: Automating Transit Logistics

When an e‑commerce store operates on a drop‑shipping model, every order demands instant transmission to the supplier?

Without automation, operators manually create orders, verify statuses, and control shipments. On a standard Bitrix, such a process becomes a bottleneck: the system knows nothing about suppliers, doesn't create counter‑orders, and doesn't track the transit warehouse. The result: delays, errors, and lost customers. We solve this problem with custom statuses, events, and integrations. Our specialists have been working with Bitrix for 5+ years and have implemented over 50 cross‑docking projects.

What problems we solve

The first problem is the lack of a unified status model. Standard statuses (NEW, PAID, ALLOW_DELIVERY) do not reflect the stages of working with a supplier. The second problem is manual creation of supplier orders. With 200 orders per day, an operator spends up to 4 hours on data entry. The third problem is loss of control over the transit warehouse: goods arrive but the system does not initiate shipment to the customer. We eliminate these issues with custom statuses, automation, and integrations.

How cross‑docking works in an online store on Bitrix

The scheme is simple: a customer places an order, the system automatically creates a supplier order, the supplier sends the goods to a transit warehouse, from where they are immediately shipped to the customer. In Bitrix, this uses a custom status chain:

• CROSS_WAITING — awaiting supplier (ID: CW)
• CROSS_IN_TRANSIT — goods in transit (ID: CI)
• CROSS_ARRIVED — arrived at transit warehouse (ID: CA)
• CROSS_SHIPPED — shipped to customer (ID: CS)

The difference from a regular order lies in the intermediate waiting and transit statuses. This provides transparency and control.

Why standard Bitrix statuses are not suitable

Bitrix provides predefined statuses (N, P, F, D), which do not include "awaiting supplier" or "in transit". Using standard statuses, you cannot distinguish an order waiting for a supplier from a paid one. We create custom statuses via \Bitrix\Sale\OrderStatus::add() and link them to events.

Table of custom statuses

How to automatically create a supplier order?

When the order transitions to status CW, the OnSaleStatusOrder event fires. We add a handler that loads the order and, for each item, determines the supplier via a custom class SupplierCatalog. Then SupplierOrderService creates a supplier order via API or EDI. Example code:

AddEventHandler('sale', 'OnSaleStatusOrder', function($orderId, $newStatus) {
    if ($newStatus === 'CW') {
        $order = \Bitrix\Sale\Order::load($orderId);
        $basket = $order->getBasket();

        foreach ($basket as $item) {
            $productId = $item->getProductId();
            $supplier  = SupplierCatalog::getSupplierByProduct($productId);

            if ($supplier) {
                SupplierOrderService::create($supplier, [
                    'PRODUCT_ID' => $productId,
                    'QUANTITY'   => $item->getQuantity(),
                    'ORDER_REF'  => $orderId,
                ]);
            }
        }
    }
});

Bitrix documentation on the OnSaleStatusOrder event

What is included in the setup

Our engineers carry out the work in stages:

Timeline: from 5 to 15 business days, depending on the number of suppliers and integration complexity. Cost is calculated individually.

How to choose the supplier integration method?

For cross‑docking, data exchange speed is critical. Best options:

• API — direct order transmission in JSON/XML. Requires the supplier to provide an API.
• EDI — electronic document exchange (order, confirmation, invoice). Suitable for large suppliers.
• Email — sending PDF order via email. Simple but unreliable: delays possible.

For stores with 2‑3 suppliers, API is enough. For 10 or more suppliers, it is better to implement an EDI gateway.

Typical mistakes during setup

• Agent for processing arrivals not configured — order hangs in "Arrived" status.
• No mechanism to cancel supplier order — if the customer changes their mind, the order is already created.
• Supplier stock not considered — order may be accepted when goods are unavailable.
• Incorrect handling of partial shipments — if the supplier ships in parts.

These problems are solved at the design stage. Our team has experience integrating with dozens of suppliers via various protocols. Get a consultation for your project — we will assess the complexity and propose the optimal solution. Savings on warehouse costs reach up to 40%, and order processing time is reduced by 60%.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.